Forward Deployed Engineering Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings exactly those strings? Probably yes: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We include only those with content.
We need to decide what goes where.
- About the role: Should contain description of role, maybe from About The Team and About The Role paragraphs. Could combine.
- Responsibilities: Core Responsibilities list.
- Requirements: What We're Looking For (the bullet list of required qualifications). Could be Requirements.
- Qualifications: maybe Nice to haves? Or could be Qualifications separate from Requirements. But we have Nice to haves as optional qualifications. Could treat as Qualifications.
- Skills: maybe technical fluency etc. Could be part of Requirements. But we need to decide.
- Benefits: Why join us? includes bullet points: growth, work-life balance, fast-learning, 45+ nationalities, competitive salary package & benefits. Also maybe DE&I statement but that's boilerplate to remove. So Benefits section can include those.
- Pay: Base Salary Range: $185,000 - $256,000 USD.
- Schedule: Not explicitly mentioned. There's hybrid role requiring some regular in-office time, 3 days per week? Actually later in application form: "This role is a hybrid role and requires some regular in office time. Are you comfortable with being in the office 3 days per week?" That's in the form, not in posting. The posting didn't mention schedule. So we should not include Schedule section because no specific content.
Thus we will include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We must not repeat job title as heading. Not include Job ID etc.
We must use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we ignore the form fields etc.
We need to output only HTML fragment.
Let's extract content.
About The Team: "Forward Deployed Engineering connects Aircall's AI Voice Agent (AIVA) and AI Messaging Agent (AIMA) to real-world customer workflows, turning possibility into production. The team sits within Customer Solutions & Applied AI and works cross-functionally with Product, Engineering, Sales, Solutions, and Customer Success, globally across EMEA, AMER, and APAC. This role owns the FDE motion for one region, reporting to the SVP, Customer Solutions & Applied AI."
About The Role: "The FDE Lead is a player-coach, not a traditional people-manager. You'll still be building: personally configuring, deploying, and debugging AI Agent solutions on real customer engagements, because the fastest way to raise the bar for your team is to keep raising your own. You'll also coach the regional FDE team, own the region's AIVA number, and turn what you build yourself into the playbooks and frameworks the team runs on. Your remit doesn't stop at FDE. You are helping drive the agentic revolution across the whole region, educating our internal teams, collaborating with our marketing team, impact the whole customer journey in your region."
We can combine these into About the role section.
Responsibilities: list under Core Responsibilities. Let's extract each bullet:
- Co-own the AIVA number for the region with the regional GM, partnering with AEs, AMs, and CSMs on pipeline and revenue targets, and staying personally accountable for hitting it.
- Stay hands-on and technical: personally configure, build, and deploy AI Agent solutions on a portfolio of strategic or complex accounts, leading by building rather than only reviewing.
- Coach and upskill the regional FDE team on technical execution, agent configuration, and deployment quality through pairing and hands-on review, not just process.
- Build and evolve the global playbooks, reference architectures, and deployment frameworks the team runs on by compounding the team’s knowledge and expertise.
- Drive the region's AIVA go-to-market motion, embedding pipeline hygiene, forecasting discipline, and clear input/output KPIs across the team.
- Run enablement and upskilling sessions in the region, collaborating with the Enablement team so the wider organisation can speak to and support agentic adoption.
- Represent field reality to Product and Engineering, translating what you and the team are building, and where you hit friction, into roadmap input.
- Lead cross-functional initiatives that grow agentic adoption region-wide, coordinating with Marketing, Support, and other GTM teams as needed.
We need to preserve all detail. Use
- for each.
Requirements: What We're Looking For bullet list (required). Let's extract:
- Hands-on technical depth: 5–6+ years in forward deployed engineering, solutions engineering, technical consulting, or a comparable role, with a proven track record of personally building, configuring, and shipping integrations or agent solutions, not just directing others who do.
- Technical fluency: comfortable with APIs, integrations, and at least one programming language, with the technical aptitude to quickly get hands-on with new agent capabilities as they ship.
- Commercial and business acumen: able to align technical delivery with revenue outcomes — deal structures, forecasting, pipeline hygiene, and how a deployment translates into the region's AIVA number.
- Executive stakeholder engagement: proven experience engaging and influencing VP and C-suite stakeholders, both internally and at customer organisations, without losing technical credibility.
- People leadership through coaching: demonstrated ability to raise a team's technical bar by building alongside them and reviewing their work hands-on, not by managing from a distance.
- Strategic thinking: able to scope new use cases and opportunities from ambiguity, not only execute against a defined brief.
- Track record of ownership: a clear history of taking complex, cross-functional projects from idea to delivered outcome, and being accountable for the result.
- Entrepreneurial mindset: treats the region like a startup within a startup and doesn't wait for permission to fix what's broken.
We need to keep each as list item.
Qualifications: Nice to haves:
- Experience in conversational AI, voice AI, or contact centre technology.
- Experience with CRMs, help desks, or System-of-Truth integrations.
- Prior experience in an overlay or specialist GTM motion.
We'll put these under Qualifications.
Skills: Could be separate but we already have technical fluency etc. Might be redundant. Could combine Skills with Requirements? But we need to follow instruction: include sections only when posting has real specific content. We have content for Skills? Could extract technical fluency etc as skills. But we already used them in Requirements. Might be okay to have Skills section with same items? Might duplicate. Better to treat Requirements as the list of required qualifications, and Qualifications as nice-to-haves. Skills maybe not needed separately. But we could still include Skills if we have content like "comfortable with APIs, integrations, and at least one programming language". However that is already in Requirements. To avoid duplication, we could omit Skills section. The instruction: prefer a few substantive sections over many thin ones. So we can omit Skills.
Benefits: Why join us? bullet points:
- 🚀 Key moment to join Aircall in terms of growth and opportunities
- 💆♀️ Our people matter, work-life balance is important at Aircall
- 📚 Fast-learning environment, entrepreneurial and strong team spirit
- 🌍 45+ Nationalities: cosmopolite & multi-cultural mindset
- 💶 Competitive salary package & benefits
We should keep the substance, maybe remove emojis? They are part of content but could keep. Probably fine to keep.
Pay: Base Salary Range: $185,000 - $256,000 USD.
Schedule: none.
Now produce HTML.
Structure:
About the role
...combined prose...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Benefits
...
Pay
$185,000 - $256,000 USD
Make sure no extra whitespace? It's fine.
Check for any duplicated lines: we must not repeat.
Check for boilerplate: we removed DE&I statement, application instructions, etc.
Check for any mention of "cookie/navigation/legal/EEO/equal-opportunity/scam-warning": none.
Now craft the prose for About the role: combine About The Team and About The Role paragraphs into maybe two paragraphs.
Let's write:
Forward Deployed Engineering connects Aircall's AI Voice Agent (AIVA) and AI Messaging Agent (AIMA) to real-world customer workflows, turning possibility into production. The team sits within Customer Solutions & Applied AI and works cross-functionally with Product, Engineering, Sales, Solutions, and Customer Success, globally across EMEA, AMER, and APAC. This role owns the FDE motion for one region, reporting to the SVP, Customer Solutions & Applied AI.
The FDE Lead is a player-coach, not a traditional people-manager. You'll still be building: personally configuring, deploying, and debugging AI Agent solutions on real customer engagements, because the fastest way to raise the bar for your team is to keep raising your own. You'll also coach the regional FDE team, own the region's AIVA number, and turn what you build yourself into the playbooks and frameworks the team runs on. Your remit doesn't stop at FDE. You are helping drive the agentic revolution across the whole region, educating our internal teams, collaborating with our marketing team, and impacting the whole customer journey in your region.
That preserves all.
Now Responsibilities list: ensure each bullet exactly as in posting.
Let's copy each:
- Co-own the AIVA number for the region with the regional GM, partnering with AEs, AMs, and CSMs on pipeline and revenue targets, and staying personally accountable for hitting it.
- Stay hands-on and technical: personally configure, build, and deploy AI Agent solutions on a portfolio of strategic or complex accounts, leading by building rather than only reviewing.
- Coach and upskill the regional FDE team on technical execution, agent configuration, and deployment quality through pairing and hands-on review, not just process.
- Build and evolve the global playbooks, reference architectures, and deployment frameworks the team runs on by compounding the team’s knowledge and expertise.
- Drive the region's AIVA go-to-market motion, embedding pipeline hygiene, forecasting discipline, and clear input/output KPIs across the team.
- Run enablement and upskilling sessions in the region, collaborating with the Enablement team so the wider organisation can speak to and support agentic adoption.
- Represent field reality to Product and Engineering, translating what you and the
for prose. We must preserve all substantive information, not invent or summarize away detail. Must not include filler like "commensurate with experience". Not present. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we ignore the form fields etc. We need to output only HTML fragment. Let's extract content. About The Team: "Forward Deployed Engineering connects Aircall's AI Voice Agent (AIVA) and AI Messaging Agent (AIMA) to real-world customer workflows, turning possibility into production. The team sits within Customer Solutions & Applied AI and works cross-functionally with Product, Engineering, Sales, Solutions, and Customer Success, globally across EMEA, AMER, and APAC. This role owns the FDE motion for one region, reporting to the SVP, Customer Solutions & Applied AI." About The Role: "The FDE Lead is a player-coach, not a traditional people-manager. You'll still be building: personally configuring, deploying, and debugging AI Agent solutions on real customer engagements, because the fastest way to raise the bar for your team is to keep raising your own. You'll also coach the regional FDE team, own the region's AIVA number, and turn what you build yourself into the playbooks and frameworks the team runs on. Your remit doesn't stop at FDE. You are helping drive the agentic revolution across the whole region, educating our internal teams, collaborating with our marketing team, impact the whole customer journey in your region." We can combine these into About the role section. Responsibilities: list under Core Responsibilities. Let's extract each bullet: - Co-own the AIVA number for the region with the regional GM, partnering with AEs, AMs, and CSMs on pipeline and revenue targets, and staying personally accountable for hitting it. - Stay hands-on and technical: personally configure, build, and deploy AI Agent solutions on a portfolio of strategic or complex accounts, leading by building rather than only reviewing. - Coach and upskill the regional FDE team on technical execution, agent configuration, and deployment quality through pairing and hands-on review, not just process. - Build and evolve the global playbooks, reference architectures, and deployment frameworks the team runs on by compounding the team’s knowledge and expertise. - Drive the region's AIVA go-to-market motion, embedding pipeline hygiene, forecasting discipline, and clear input/output KPIs across the team. - Run enablement and upskilling sessions in the region, collaborating with the Enablement team so the wider organisation can speak to and support agentic adoption. - Represent field reality to Product and Engineering, translating what you and the team are building, and where you hit friction, into roadmap input. - Lead cross-functional initiatives that grow agentic adoption region-wide, coordinating with Marketing, Support, and other GTM teams as needed. We need to preserve all detail. Use
- for each.
Requirements: What We're Looking For bullet list (required). Let's extract:
- Hands-on technical depth: 5–6+ years in forward deployed engineering, solutions engineering, technical consulting, or a comparable role, with a proven track record of personally building, configuring, and shipping integrations or agent solutions, not just directing others who do.
- Technical fluency: comfortable with APIs, integrations, and at least one programming language, with the technical aptitude to quickly get hands-on with new agent capabilities as they ship.
- Commercial and business acumen: able to align technical delivery with revenue outcomes — deal structures, forecasting, pipeline hygiene, and how a deployment translates into the region's AIVA number.
- Executive stakeholder engagement: proven experience engaging and influencing VP and C-suite stakeholders, both internally and at customer organisations, without losing technical credibility.
- People leadership through coaching: demonstrated ability to raise a team's technical bar by building alongside them and reviewing their work hands-on, not by managing from a distance.
- Strategic thinking: able to scope new use cases and opportunities from ambiguity, not only execute against a defined brief.
- Track record of ownership: a clear history of taking complex, cross-functional projects from idea to delivered outcome, and being accountable for the result.
- Entrepreneurial mindset: treats the region like a startup within a startup and doesn't wait for permission to fix what's broken.
We need to keep each as list item.
Qualifications: Nice to haves:
- Experience in conversational AI, voice AI, or contact centre technology.
- Experience with CRMs, help desks, or System-of-Truth integrations.
- Prior experience in an overlay or specialist GTM motion.
We'll put these under Qualifications.
Skills: Could be separate but we already have technical fluency etc. Might be redundant. Could combine Skills with Requirements? But we need to follow instruction: include sections only when posting has real specific content. We have content for Skills? Could extract technical fluency etc as skills. But we already used them in Requirements. Might be okay to have Skills section with same items? Might duplicate. Better to treat Requirements as the list of required qualifications, and Qualifications as nice-to-haves. Skills maybe not needed separately. But we could still include Skills if we have content like "comfortable with APIs, integrations, and at least one programming language". However that is already in Requirements. To avoid duplication, we could omit Skills section. The instruction: prefer a few substantive sections over many thin ones. So we can omit Skills.
Benefits: Why join us? bullet points:
- 🚀 Key moment to join Aircall in terms of growth and opportunities
- 💆♀️ Our people matter, work-life balance is important at Aircall
- 📚 Fast-learning environment, entrepreneurial and strong team spirit
- 🌍 45+ Nationalities: cosmopolite & multi-cultural mindset
- 💶 Competitive salary package & benefits
We should keep the substance, maybe remove emojis? They are part of content but could keep. Probably fine to keep.
Pay: Base Salary Range: $185,000 - $256,000 USD.
Schedule: none.
Now produce HTML.
Structure:
About the role
...combined prose...
Responsibilities
- ... ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
Pay
$185,000 - $256,000 USD
Make sure no extra whitespace? It's fine. Check for any duplicated lines: we must not repeat. Check for boilerplate: we removed DE&I statement, application instructions, etc. Check for any mention of "cookie/navigation/legal/EEO/equal-opportunity/scam-warning": none. Now craft the prose for About the role: combine About The Team and About The Role paragraphs into maybe two paragraphs. Let's write:Forward Deployed Engineering connects Aircall's AI Voice Agent (AIVA) and AI Messaging Agent (AIMA) to real-world customer workflows, turning possibility into production. The team sits within Customer Solutions & Applied AI and works cross-functionally with Product, Engineering, Sales, Solutions, and Customer Success, globally across EMEA, AMER, and APAC. This role owns the FDE motion for one region, reporting to the SVP, Customer Solutions & Applied AI.
The FDE Lead is a player-coach, not a traditional people-manager. You'll still be building: personally configuring, deploying, and debugging AI Agent solutions on real customer engagements, because the fastest way to raise the bar for your team is to keep raising your own. You'll also coach the regional FDE team, own the region's AIVA number, and turn what you build yourself into the playbooks and frameworks the team runs on. Your remit doesn't stop at FDE. You are helping drive the agentic revolution across the whole region, educating our internal teams, collaborating with our marketing team, and impacting the whole customer journey in your region.
That preserves all. Now Responsibilities list: ensure each bullet exactly as in posting. Let's copy each: - Co-own the AIVA number for the region with the regional GM, partnering with AEs, AMs, and CSMs on pipeline and revenue targets, and staying personally accountable for hitting it. - Stay hands-on and technical: personally configure, build, and deploy AI Agent solutions on a portfolio of strategic or complex accounts, leading by building rather than only reviewing. - Coach and upskill the regional FDE team on technical execution, agent configuration, and deployment quality through pairing and hands-on review, not just process. - Build and evolve the global playbooks, reference architectures, and deployment frameworks the team runs on by compounding the team’s knowledge and expertise. - Drive the region's AIVA go-to-market motion, embedding pipeline hygiene, forecasting discipline, and clear input/output KPIs across the team. - Run enablement and upskilling sessions in the region, collaborating with the Enablement team so the wider organisation can speak to and support agentic adoption. - Represent field reality to Product and Engineering, translating what you and the