Forward Deployed Engineering Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from posting. We need to avoid repeating job title as heading. No job ID. Remove boilerplate. We need to preserve all substantive info. Let's parse posting. First paragraph: description of Aircall (company overview). Might be considered "About the role"? Actually "About The Team" and "About The Role". The posting includes "About The Team" and "About The Role". We need to decide which sections to include. We have sections: About the role (maybe combine About The Team and About The Role). Responsibilities: Core Responsibilities list. Requirements: What We're Looking For list. Qualifications: maybe same as requirements? Could treat as Requirements. Skills: maybe technical fluency etc. Benefits: "Why join us?" list includes bullet points with emojis. Pay: Base salary range. Schedule: not mentioned. So we should not include Schedule. We need to include only sections with real content. Thus sections: About the role (maybe include About The Team and About The Role combined). Responsibilities. Requirements (What We're Looking For). Skills (maybe technical fluency etc). Benefits (Why join us?). Pay (Base salary range). Possibly also "Qualifications" but we can merge with Requirements. We must not create empty sections. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO etc. The DE&I statement is boilerplate? It's diversity statement; maybe considered EEO/equal-opportunity boilerplate, should be removed. Also candidate privacy notice, AI tools note - remove. We need to keep the substantive content: company overview, About The Team, About The Role, Core Responsibilities, What We're Looking For, Why join us? (benefits), Base salary range. We need to format. Let's extract prose. Company overview: "Aircall is a unicorn, AI-powered customer communications platform used by 22,000+ companies worldwide to drive revenue, resolve issues faster, and scale customer-facing teams. We’re redefining customer communications by bringing voice, SMS, WhatsApp, and AI together into one seamless workspace. Our momentum comes from a simple idea: help teams work smarter, not harder. Aircall’s AI Voice Agent automates routine calls, AI Assist streamlines post-call work, and AI Assist Pro delivers real-time guidance so people can do their best work. The result is higher revenue, faster resolutions, and teams that scale with confidence. Aircall is headquartered in Paris, our European HQ, with a strong North American presence anchored in Seattle, our North American HQ, and teams across Madrid, London, Berlin, San Francisco, New York City, Sydney, and Mexico City. We’ve built a product customers love and a business that’s scaling quickly, backed by world-class investors and driven by rapid AI innovation across multiple product lines. At Aircall, you’ll join a company in motion. We’re ambitious, product-driven, and execution-focused, with visible impact, fast decisions, and real growth. How we work at Aircall: We’re customer-obsessed, data-driven, and focused on delivering meaningful outcomes. We value ownership, continuous learning, and thoughtful speed. If you thrive in a collaborative, fast-moving environment where trust and impact matter, you’ll feel at home here." That's a lot of prose. Could be part of About the role? Might be considered company overview; we can include as part of About the role section. 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 could combine About The Team and About The Role into About the role section. Now Core Responsibilities list: bullet points each sentence. 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. Now What We're Looking For list: bullet points: - 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. Nice to haves list (maybe under Skills or separate). Could be included under Skills as "Nice to have". But we need to decide sections: Skills maybe include technical fluency etc. However the "Nice to haves" are: 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 could put them under Skills as a list. Benefits: "Why join us?" list with emojis: - 🚀 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 need to preserve the emojis? Probably okay to keep as text. Pay: Base salary range:: $185,000 USD - $256,000 USD (note double colon). We'll output as "$185,000 USD – $256,000 USD". Schedule: none. Now we need to output HTML fragment with headings

  and content. We need to avoid duplicate content. Ensure we include all substantive info. Let's craft sections:

  About the role

  ... combine company overview, About The Team, About The Role ...

  But we might split into two paragraphs: company overview and team/role. We'll include all. Then

  Responsibilities

  • ... each bullet ...
  Then

  Requirements

  • ... each bullet from What We're Looking For ...
  Then

  Skills

  Maybe include technical fluency etc? But those are already in Requirements. Could separate Nice to haves as Skills. Better:

  Skills

  • Nice to have: 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.
  But we also have technical fluency etc already in Requirements; we could keep them there. Alternatively we could have

  Qualifications

  for Requirements and

  Skills

  for Nice to haves. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if we have content. But we should not create empty sections. We have content for Requirements (What We're Looking For). Qualifications could be same as Requirements? Might be redundant. Better to treat Requirements as the list, and Qualifications maybe not needed. But we could put the Nice to haves under Skills. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to ensure we don't miss any substantive info like "Base salary range:: $185,000 USD - $256,000 USD". We'll put under Pay. Now we need to ensure we don't include boilerplate like DE&I statement, candidate privacy, AI tools note. Now produce HTML. Let's craft About the role paragraph: We'll combine: "Aircall is a unicorn, AI-powered customer communications platform used by 22,000+ companies worldwide to drive revenue, resolve issues faster, and scale customer-facing teams. We’re redefining customer communications by bringing voice, SMS, WhatsApp, and AI together into one seamless workspace. Our momentum comes from a simple idea: help teams work smarter, not harder. Aircall’s AI Voice Agent automates routine calls, AI Assist streamlines post-call work, and AI Assist Pro delivers real-time guidance so people can do their best work. The result is higher revenue, faster resolutions, and teams that scale with confidence. Aircall is headquartered in Paris, our European HQ, with a strong North American presence anchored in Seattle, our North American HQ, and teams across Madrid, London, Berlin, San Francisco, New York City, Sydney, and Mexico City. We’ve built a product customers love and a