- A candidate needs four answers: what problem they own, what they build, which decisions are theirs, and what the conditions are.
- Open with the real assignment — the product, the customer and the first problem — instead of a paragraph about innovation.
- List three to six outcomes someone could observe, because "be a trusted partner" is a working style and not an outcome.
- Put a requirement in "preferred" only when a capable engineer could learn it after joining.
- Name the pay range, the location it applies to and the travel expectation before you ask anyone to be interested.
Write the assignment as a sentence you fill in
Replace "drive innovation" with a concrete assignment:
You will work with [customer type] to move [product or capability] from [current state] to [production outcome]. You will own [discovery, build, deployment, or operations] and work with [teams].
Then name the outcomes the team can check at the end of the first period: a production integration, a validated workflow, a deployment runbook, a reusable component. OpenAI describes FDEs owning discovery, technical scoping, system design, build and production rollout, with success measured through production adoption. Notion's India FDE posting separates customer discovery and solution architecture from hands-on migration execution in some teams. A smaller company combines all of it. Say which model applies here.
Separate required and preferred experience
Required qualifications describe the evidence a person needs to do the stated work, and the list should be short. A production AI role needs shipping production software, designing a service or workflow, and working with technical customer stakeholders. A data and integration role needs APIs, SQL, data modelling, authentication, testing and production rollout.
Do not use "preferred" to hide a requirement the first project depends on. Name equivalent paths where they are real: Notion lists backend, data, integration, implementation, consulting and solutions engineering backgrounds for one migration role, which is clearer than requiring a previous FDE title.
Describe the customer contact, not the label
Say who the engineer meets and what those conversations accomplish: mapping a workflow, agreeing data access, explaining trade-offs, running acceptance testing, handing over an operating system. If a manager owns the relationship and the FDE owns implementation, say so. "Customer-facing" without a description leaves a candidate guessing between discovery, demos, implementation, incident response and training.
Connect each technology to a task
"Python for services and data transformations" is more useful than a list of ten tools. Say whether the engineer will write production code, prototypes, configuration, integration scripts, or all four. Notion describes APIs, data pipelines, migrations, custom agents, permissions and governance. Firecrawl's revenue FDE posting describes technical discovery, integrations and proofs of concept carried into production. That is the level of specificity candidates need, not a universal FDE stack.
Every condition, including the undecided ones
Include the employing entity, employment type, work location, office expectation, travel expectation, work authorisation policy, pay range, equity or bonus approach, and application contact. Give the range for the stated location and explain what varies by location or level. Where a term is undecided, say it is undecided.
Replace the six phrases that say nothing
| Vague phrase | Replace it with |
|---|---|
| "Own end to end" | The stages and decisions the role owns |
| "Work cross-functionally" | The teams, meetings and handoffs involved |
| "Move fast in ambiguity" | An example of an unclear input and the decision expected |
| "Customer obsessed" | The customer activity and the outcome to deliver |
| "Full-stack" | The layers the engineer will change in the first project |
| "High impact" | The user, workflow, reliability or adoption result |
Do not promise autonomy, rapid promotion or a career path the company cannot support. Do not ask for ten years of experience for a first FDE hire because the role is undefined.
The publishing check
Ask a hiring manager who did not write the draft to point to the first project, the required decisions, the customer contact and the working conditions. Ask an engineer outside the team to name the evidence each requirement is testing. If either reader has to infer an answer, revise it.
Start from an editable template: