Aircall 前置部署工程师（FDE）岗位与薪资
Aircall 目前有 18 个 FDE 在招岗位，公示基本工资 $90K–$299K。
在招岗位
Aircall 的技能要求
提到 Aircall 的文章
- The FDE job market, mapped: 1262 live roles
First-party census of 1262 forward-deployed engineer openings across 555 companies, by vertical, stage, region, and salary. Drill down to any single posting.
- The shared context problem for FDE teams: why the brain you built in Claude Code stops at one person
Why a Claude Code brain stays personal, the four points where it breaks, and how shared account memory got Aircall to 3x rollouts per engineer.
- Build vs buy a shared context layer: the Supabase + Claude Code pattern and where it drifts
Internal AI builds succeed about a third of the time vs 67% for purchased tools. Where the Supabase + Claude Code pattern drifts, and when to build anyway.
- The FDE operating system: what teams building an "FD OS" actually put in it
FDE teams converge on five OS layers: playbooks, shared context, tasks, briefs, time. Shared context carries the load, with 3x rollouts per engineer at Aircall.
- FDE handoffs: keeping an engagement alive when the builder changes
A seven-step engagement handoff runbook for FDE teams, covering planned, pool, and acquisition handoffs. Spendesk engineers pick up any account in five minutes.
- Onboarding a second FDE onto a live account: the ramp playbook, and the context it depends on
The FDE onboarding playbook: self-serve account briefs, paired calls, 90-day checkpoints. At Spendesk an engineer picks up any account in five minutes.
- Why your engineers (and their coding agents) can't write good code without the FDE's context
Engineers and coding agents write wrong code without account context. See how teams make it queryable, like Aircall's 3x rollouts per engineer.
- What is shared context? The definition for AI-assisted teams, and the four questions it must answer
Shared context is the account memory a team and its AI agents can query. It answers what was promised, decided, at risk, and next, with sources.
- Obsidian as a second brain for FDE work: the solo setup that works and the four places it breaks
The Obsidian + Claude Code solo setup works. It breaks at sharing, second editors, outside readers, and drift. Spendesk got 3 weeks shorter go-lives.
- Claude Code memory for teams: CLAUDE.md, auto-memory, and what never carries across people
CLAUDE.md shares coding conventions via git, but auto memory never leaves your machine. Where account context lives: the team memory Aircall queries via MCP.