Senior Forward Deployed Engineer – Key Accounts (AI Solutions)
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting for content.
Key sections:
- About The Team (maybe not needed as heading? Could be part of About the role? The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings.
We have:
- About The Team: description of team. Could go under "About the role"? Or maybe we can treat as "About the role" includes team context. But we need to preserve all substantive info. We could create a section "About the role" that includes description of role and team.
- About The Role: details of role responsibilities.
- What You'll Do: list of duties (bullets). That's responsibilities.
- What You'll Bring: qualifications/requirements/skills.
- What Success Looks Like: maybe could be part of responsibilities or outcomes; but we could treat as part of responsibilities or maybe as separate "Qualifications"? Not exactly. Could be part of responsibilities (what success looks like). But we need to avoid thin sections. Perhaps combine "What You'll Do" and "What Success Looks Like" under Responsibilities.
- Base Salary Range: $175,000 - $230,000 USD => Pay section.
- Why join us? bullet list of benefits: includes key moment, work-life balance, fast-learning environment, 45+ nationalities, competitive salary package & benefits. That's benefits.
- DE&I Statement: could be considered boilerplate? It's diversity statement; maybe we should drop as it's EEO/equal-opportunity boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So drop DE&I statement.
- Candidate Privacy Notice, AI tools note, etc: drop.
- Application instructions (Create a Job Alert, Apply for this job, fields) drop.
- Also the list of country codes etc is navigation boilerplate; drop.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We may not have Schedule info (no mention). So we should not create Schedule section.
We may not have separate Requirements vs Qualifications vs Skills; we need to decide how to split. The posting has "What You'll Bring" which includes experience, client facing experience, technical skills, nice-to-haves. That can be split into Requirements (mandatory) and Skills (maybe technical skills) and Qualifications (experience). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section "Requirements". Or we could have "Requirements" for mandatory experience, "Skills" for technical skills, and "Qualifications" maybe not needed. But we need to follow instruction: use headings only when posting has real, specific content for it. So we can create sections for those that have content.
We have content for:
- About the role (including About The Team and About The Role description). We'll put that in About the role.
- Responsibilities: What You'll Do (list) plus maybe What Success Looks Like (outcomes). We'll combine.
- Requirements: mandatory experience (6+ years, client facing experience, proven ability, etc). Could be separate.
- Skills: technical skills (APIs, scripting, low-code tools, AI workflow config, etc). Could be separate.
- Benefits: Why join us? list.
- Pay: Base Salary Range.
We should not create Schedule.
We need to ensure we don't repeat content unnecessarily.
Let's extract substantive content.
About The Team:
"Aircall's Forward Deployed Engineering team connects our innovative AI Agents technology to real-world customer workflows. We turn possibility into production by delivering automation that improves customer experience, boosts productivity, and unlocks new business value. Working cross-functionally with Product, Engineering, Sales, Solutions, and Customer Success, the team ensures every deployment delivers measurable impact. Within that team, this is a senior, Key Accounts–focused role for someone who wants to go deep rather than broad — embedding with a portfolio of Aircall's most strategic global customers and growing agentic adoption inside each one over time. It sits at the intersection of technical consulting, project leadership, and AI adoption strategy. You don't need to be a full-time software engineer, but you should be fluent in APIs, highly confident leading complex technical engagements, and credible in the room with senior customer stakeholders."
About The Role:
"As a Senior Forward Deployed Engineer for Key Accounts, you are the embedded technical owner for a portfolio of Aircall's highest-value global customers. You don't run a deployment and move on — you stay with the account, building a long-term agentic roadmap alongside the Key Account Manager (KAM). You land a first high-impact use case, prove value fast, then systematically expand the footprint use case by use case until Aircall's AI Agents are woven through the customer's core workflows. This is a high-autonomy role: you set the technical strategy for your accounts, you're trusted in the room with customer leadership, and you act as the connective tissue between the customer, the KAM, Product, and Engineering. Please note, this is not a software engineering role. This is a hybrid, revenue-driving role spanning Solutions Engineering, Consulting, Professional Services, and Product Ownership"
We can combine these into About the role section.
Now Responsibilities (What You'll Do):
List items:
- Own a sustained, embedded relationship with each account in your portfolio — you are the customer's go-to technical authority on agentic AI, not a project resource who rotates off once a deployment ships.
- Partner directly with the Key Account Manager on a joint account plan: the KAM owns the commercial relationship and quota; you own the agentic use-case roadmap and technical execution; together you build and drive the pipeline of expansion use cases.
- Land the first use case fast, then expand — deploy an initial high-value workflow, instrument the outcome, and use proven value to open the next use case and the next buying centre within the account.
- Run an evergreen use-case discovery cadence — continuously surface, qualify, and prioritise new automation opportunities across the customer's teams, so there is always a next use case in flight.
- Serve as the customer's trusted advisor on agentic strategy — map their AI roadmap 6–12 months out, not just the deployment in front of you, and keep Aircall positioned as the platform of record.
- Lead discovery and solution-design sessions with customer stakeholders to map business processes, identify automation opportunities, and define solution architecture.
- Design, build, and deploy integrations using low/no-code platforms (Zapier, Make, n8n, Workato) and CRM automation tools (HubSpot Workflows, Salesforce Flow) with API connectors.
- Configure and optimise the AI Agent — defining intents, prompts, actions, guardrails, and performance metrics tailored to each account's workflows.
- Manage complex, cross-functional deployments — defining timelines, aligning stakeholders, ensuring accountability, and delivering on time and within scope.
- Collaborate with Engineering to validate technical feasibility, resolve blockers, and feed field learnings back into the product.
- Create scalable models and reusable frameworks (templates, playbooks, reference architectures) that make expansion within your accounts — and future Key Account engagements across the team — faster and more consistent.
- Champion continuous learning and enablement — mentor FDEs, run internal workshops, and document best practices to raise the technical bar across the team.
- Collaborate with GTM leadership to embed the routines and cadences that drive accountability for expansion pipeline, forecast accuracy, and performance tracking within Key Accounts.
- Contribute to expansion pipeline and MRR within your portfolio, jointly with the KAM — defining use-case-specific expansion strategies, coordinating cross-functional support, and ensuring Aircall delivers the leading AI-enabled communication platform.
- Shape the AI Agent roadmap with Product and PMM, based on customer needs, integration insights, and field learnings from your accounts.
- Drive internal and external product education, including enablement for System Integrators (SIs) and channel partners where they support your accounts.
- Maintain deep awareness of AI and CX industry trends, ensuring Aircall's positioning stays competitive and insights continuously feed back into product and GTM strategy.
What Success Looks Like:
- Depth and expansion within each account — a growing number of live agentic use cases, and adoption spreading into new teams and buying centres over time.
- Net revenue retention and expansion MRR across your portfolio, driven jointly with the KAM.
- Trusted-partner status — reflected in access, executive relationships, and roadmap influence, not just tickets closed.
- Shortened time-to-first-value on the initial use case, then a repeatable path to use case two and beyond.
- Reusable frameworks and models actively used by peers and partners on other Key Account engagements.
- Strong collaboration with Engineering and Product to enhance platform capabilities.
- Sustained improvements in customer metrics (containment, AHT, CSAT) and revenue impact (ARR, NRR) driven by your solutions.
We can combine these as responsibilities (outcomes). Could be separate but we can keep as part of responsibilities.
Now Requirements (What You'll Bring mandatory):
- 6+ years in technical consulting, solutions engineering, forward-deployed engineering, or integration-focused professional services — ideally with time owning strategic or enterprise accounts.
- Client facing experience:
- Proven ability to own a long-term customer relationship as the technical authority, operating with autonomy and credibility in front of senior (VP / CxO) stakeholders.
- Proven experience running account-based motions in partnership with sales / account management on strategic or enterprise customers.
- Technical skills:
- Strong command of APIs, webhooks, and data structures (JSON, REST, GraphQL) — able to design and troubleshoot integrations confidently. Even better if you have experience with MCP Servers.
- Proficiency in scripting (JavaScript and/or Python) — used to build, customise, and debug integrations, not just read them.
- Hands-on experience with low-code orchestration tools (Zapier, Make, n8n, Workato) and CRM automation (HubSpot, Salesforce).
- Practical understanding of AI workflow configuration, including prompt engineering, evaluation, and monitoring.
- Proven ability to lead complex, cross-functional programs with Engineering, Product, and Customer Success to deliver scalable outcomes.
- Excellent communication and stakeholder management skills, translating fluently between technical and business audiences.
- A growth mindset — constantly learning new tools, frameworks, and ways to improve the customer experience and team capability.
Nice-to-haves (optional):
- Experience in telephony, voice, or contact centre systems (SIP/WebRTC, call routing, containment, AHT).
- Familiarity with BI and analytics tools (Looker, BigQuery, Snowflake).
We could treat mandatory as Requirements, nice-to-haves as Skills? Or we could separate Skills as technical skills (APIs, scripting, low-code, AI workflow config, etc). But we already have technical skills in mandatory. Perhaps we separate:
- Requirements: years of experience, client facing experience, ability to own long-term relationship, account-based motions.
- Skills: technical skills (APIs, scripting, low-code, AI workflow
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting for content. Key sections: - About The Team (maybe not needed as heading? Could be part of About the role? The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. We have: - About The Team: description of team. Could go under "About the role"? Or maybe we can treat as "About the role" includes team context. But we need to preserve all substantive info. We could create a section "About the role" that includes description of role and team. - About The Role: details of role responsibilities. - What You'll Do: list of duties (bullets). That's responsibilities. - What You'll Bring: qualifications/requirements/skills. - What Success Looks Like: maybe could be part of responsibilities or outcomes; but we could treat as part of responsibilities or maybe as separate "Qualifications"? Not exactly. Could be part of responsibilities (what success looks like). But we need to avoid thin sections. Perhaps combine "What You'll Do" and "What Success Looks Like" under Responsibilities. - Base Salary Range: $175,000 - $230,000 USD => Pay section. - Why join us? bullet list of benefits: includes key moment, work-life balance, fast-learning environment, 45+ nationalities, competitive salary package & benefits. That's benefits. - DE&I Statement: could be considered boilerplate? It's diversity statement; maybe we should drop as it's EEO/equal-opportunity boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So drop DE&I statement. - Candidate Privacy Notice, AI tools note, etc: drop. - Application instructions (Create a Job Alert, Apply for this job, fields) drop. - Also the list of country codes etc is navigation boilerplate; drop. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We may not have Schedule info (no mention). So we should not create Schedule section. We may not have separate Requirements vs Qualifications vs Skills; we need to decide how to split. The posting has "What You'll Bring" which includes experience, client facing experience, technical skills, nice-to-haves. That can be split into Requirements (mandatory) and Skills (maybe technical skills) and Qualifications (experience). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section "Requirements". Or we could have "Requirements" for mandatory experience, "Skills" for technical skills, and "Qualifications" maybe not needed. But we need to follow instruction: use headings only when posting has real, specific content for it. So we can create sections for those that have content. We have content for: - About the role (including About The Team and About The Role description). We'll put that in About the role. - Responsibilities: What You'll Do (list) plus maybe What Success Looks Like (outcomes). We'll combine. - Requirements: mandatory experience (6+ years, client facing experience, proven ability, etc). Could be separate. - Skills: technical skills (APIs, scripting, low-code tools, AI workflow config, etc). Could be separate. - Benefits: Why join us? list. - Pay: Base Salary Range. We should not create Schedule. We need to ensure we don't repeat content unnecessarily. Let's extract substantive content. About The Team: "Aircall's Forward Deployed Engineering team connects our innovative AI Agents technology to real-world customer workflows. We turn possibility into production by delivering automation that improves customer experience, boosts productivity, and unlocks new business value. Working cross-functionally with Product, Engineering, Sales, Solutions, and Customer Success, the team ensures every deployment delivers measurable impact. Within that team, this is a senior, Key Accounts–focused role for someone who wants to go deep rather than broad — embedding with a portfolio of Aircall's most strategic global customers and growing agentic adoption inside each one over time. It sits at the intersection of technical consulting, project leadership, and AI adoption strategy. You don't need to be a full-time software engineer, but you should be fluent in APIs, highly confident leading complex technical engagements, and credible in the room with senior customer stakeholders." About The Role: "As a Senior Forward Deployed Engineer for Key Accounts, you are the embedded technical owner for a portfolio of Aircall's highest-value global customers. You don't run a deployment and move on — you stay with the account, building a long-term agentic roadmap alongside the Key Account Manager (KAM). You land a first high-impact use case, prove value fast, then systematically expand the footprint use case by use case until Aircall's AI Agents are woven through the customer's core workflows. This is a high-autonomy role: you set the technical strategy for your accounts, you're trusted in the room with customer leadership, and you act as the connective tissue between the customer, the KAM, Product, and Engineering. Please note, this is not a software engineering role. This is a hybrid, revenue-driving role spanning Solutions Engineering, Consulting, Professional Services, and Product Ownership" We can combine these into About the role section. Now Responsibilities (What You'll Do): List items: - Own a sustained, embedded relationship with each account in your portfolio — you are the customer's go-to technical authority on agentic AI, not a project resource who rotates off once a deployment ships. - Partner directly with the Key Account Manager on a joint account plan: the KAM owns the commercial relationship and quota; you own the agentic use-case roadmap and technical execution; together you build and drive the pipeline of expansion use cases. - Land the first use case fast, then expand — deploy an initial high-value workflow, instrument the outcome, and use proven value to open the next use case and the next buying centre within the account. - Run an evergreen use-case discovery cadence — continuously surface, qualify, and prioritise new automation opportunities across the customer's teams, so there is always a next use case in flight. - Serve as the customer's trusted advisor on agentic strategy — map their AI roadmap 6–12 months out, not just the deployment in front of you, and keep Aircall positioned as the platform of record. - Lead discovery and solution-design sessions with customer stakeholders to map business processes, identify automation opportunities, and define solution architecture. - Design, build, and deploy integrations using low/no-code platforms (Zapier, Make, n8n, Workato) and CRM automation tools (HubSpot Workflows, Salesforce Flow) with API connectors. - Configure and optimise the AI Agent — defining intents, prompts, actions, guardrails, and performance metrics tailored to each account's workflows. - Manage complex, cross-functional deployments — defining timelines, aligning stakeholders, ensuring accountability, and delivering on time and within scope. - Collaborate with Engineering to validate technical feasibility, resolve blockers, and feed field learnings back into the product. - Create scalable models and reusable frameworks (templates, playbooks, reference architectures) that make expansion within your accounts — and future Key Account engagements across the team — faster and more consistent. - Champion continuous learning and enablement — mentor FDEs, run internal workshops, and document best practices to raise the technical bar across the team. - Collaborate with GTM leadership to embed the routines and cadences that drive accountability for expansion pipeline, forecast accuracy, and performance tracking within Key Accounts. - Contribute to expansion pipeline and MRR within your portfolio, jointly with the KAM — defining use-case-specific expansion strategies, coordinating cross-functional support, and ensuring Aircall delivers the leading AI-enabled communication platform. - Shape the AI Agent roadmap with Product and PMM, based on customer needs, integration insights, and field learnings from your accounts. - Drive internal and external product education, including enablement for System Integrators (SIs) and channel partners where they support your accounts. - Maintain deep awareness of AI and CX industry trends, ensuring Aircall's positioning stays competitive and insights continuously feed back into product and GTM strategy. What Success Looks Like: - Depth and expansion within each account — a growing number of live agentic use cases, and adoption spreading into new teams and buying centres over time. - Net revenue retention and expansion MRR across your portfolio, driven jointly with the KAM. - Trusted-partner status — reflected in access, executive relationships, and roadmap influence, not just tickets closed. - Shortened time-to-first-value on the initial use case, then a repeatable path to use case two and beyond. - Reusable frameworks and models actively used by peers and partners on other Key Account engagements. - Strong collaboration with Engineering and Product to enhance platform capabilities. - Sustained improvements in customer metrics (containment, AHT, CSAT) and revenue impact (ARR, NRR) driven by your solutions. We can combine these as responsibilities (outcomes). Could be separate but we can keep as part of responsibilities. Now Requirements (What You'll Bring mandatory): - 6+ years in technical consulting, solutions engineering, forward-deployed engineering, or integration-focused professional services — ideally with time owning strategic or enterprise accounts. - Client facing experience: - Proven ability to own a long-term customer relationship as the technical authority, operating with autonomy and credibility in front of senior (VP / CxO) stakeholders. - Proven experience running account-based motions in partnership with sales / account management on strategic or enterprise customers. - Technical skills: - Strong command of APIs, webhooks, and data structures (JSON, REST, GraphQL) — able to design and troubleshoot integrations confidently. Even better if you have experience with MCP Servers. - Proficiency in scripting (JavaScript and/or Python) — used to build, customise, and debug integrations, not just read them. - Hands-on experience with low-code orchestration tools (Zapier, Make, n8n, Workato) and CRM automation (HubSpot, Salesforce). - Practical understanding of AI workflow configuration, including prompt engineering, evaluation, and monitoring. - Proven ability to lead complex, cross-functional programs with Engineering, Product, and Customer Success to deliver scalable outcomes. - Excellent communication and stakeholder management skills, translating fluently between technical and business audiences. - A growth mindset — constantly learning new tools, frameworks, and ways to improve the customer experience and team capability. Nice-to-haves (optional): - Experience in telephony, voice, or contact centre systems (SIP/WebRTC, call routing, containment, AHT). - Familiarity with BI and analytics tools (Looker, BigQuery, Snowflake). We could treat mandatory as Requirements, nice-to-haves as Skills? Or we could separate Skills as technical skills (APIs, scripting, low-code, AI workflow config, etc). But we already have technical skills in mandatory. Perhaps we separate: - Requirements: years of experience, client facing experience, ability to own long-term relationship, account-based motions. - Skills: technical skills (APIs, scripting, low-code, AI workflow