Chapter 08Artifacts and Resources4 min read

Common failure modes

What you’ll learn

Ten patterns that account for roughly 80% of botched FDE searches. Each one has a detect / avoid recipe.

01

Hiring a pure SWE who can't talk to customers

Backend / data engineer with strong Leetcode and a top-tier resume; freezes on customer calls, calls customer interviews ‘context switching that hurts focus.’

Detect

Bloomberry's analysis confirms most FDEs lack customer-facing skills, not the inverse, and the #1 predictor is ‘first 10 engineers at a startup’ experience.

Avoid

‘Would I want to be in the trenches with this person?’ sign-off (Shilpa Balaji's bar). Require travel willingness in writing.

02

Hiring a sales engineer who can't ship

Polished demo-er; ‘ships’ via PowerPoint.

Detect

0% of true FDE roles carry a quota. If the candidate's last role was sales-engineer equal: ask ‘Show me a PR you merged into your last company's core product.’ A real FDE has merged code; a sales engineer has merged slides.

Avoid

Per Bloomberry's Pablo Siu (2025), hire for software fundamentals first.

03

Mistaking AI tool fluency for customer judgment (‘AI Tourist’)

Candidate name-drops LangChain, has bolt-side project agents, but in a real-world scenario can't decompose a customer problem before recurring for an LLM.

Detect

The Palantir-style decomposition interview gives a 60-minute open-ended customer problem (‘city wants to reduce 911 response times, call/traffic/GPS data, go’). Tourists jump to solutions; real FDEs ask 5–10 clarifying questions and constraints, stakeholders, and existing data first.

Avoid

A METR randomized study (2025) found developers using AI tools were actually 19% slower than they thought; only 20% faster, a 39-point perception gap. Avoid: treat AI as an accelerator inside engineering discipline, not as a substitute. Final Round AI's 2025 CTO survey: 16 of 18 CTOs reported production disasters from AI-generated code shipped without engineering judgment.

04

Title inflation / dilution

Every customer-adjacent role is now ‘FDE.’ Candidates self-label as FDE on LinkedIn after a 6-month implementation gig.

Detect

Read each candidate's most-recent JD and re-derive the role from first principles, ignore the title stamp.

Avoid

Avoid: before opening a req, the hiring manager must articulate which archetype in one sentence.

05

Mismatching FDE archetype to company stage

A 10-person AI startup tries to hire a Palantir-style heavy-process FDE who needs deployment strategist support and 6-month customer engagements.

Detect

58% of FDE roles are at 11–200 employee companies, the FDE is a growth-stage scaling strategy, not seed-stage (founders should be doing it themselves) and not large-enterprise (which has full PS functions). Avoid: per Florian Nègre (April 2026), the cleanest signal you need FDEs is enterprise accounts churning because the product was never fully deployed, not because they stopped valuing it.

Avoid

See above, match candidate's prior environment (FAANG, Palantir, startup) to your stage and customer mix.

06

Hiring for AI lab when the role is actually app/gov (or vice versa)

A candidate from OpenAI FDE lands at a $1B regulated AI startup as their #1 FDE; is overwhelmed by domain depth required (insurance, healthcare, supply chain).

Detect

At AI Labs spend significant time on model behavior tuning, eval suites, and helping enterprises pick use cases. App/Sage/Gov FDEs spend significantly more on model workflow modeling and integrations with legacy systems (SAP, Salesforce, Snowflake).

Avoid

Match candidate's prior environment to the role's core archetype.

07

Optimizing for prestige resume over actual skills

Pipelines stuffed with ex-Palantir, ex-McKinsey, Stanford CS folks; misses the Liberty University grad who founded an industry analytics company.

Detect

Detect: First Round explicitly notes ‘stellar FDEs don't bring a playbook (and are often early in their career).’

Avoid

Avoid: required interview question, ‘Tell me about a time the customer's reality broke your design.’

08

Over-rotating on AI tool fluency vs. fundamentals

Hiring managers add ‘must use AI tools for 100% of output’ as a screen.

Detect

Stack Overflow 2025, 46% of devs distrust AI tool accuracy vs. 33% trust; 45% say debugging AI-generated code takes longer than self-written.

Avoid

Avoid: test fundamentals (live debugging in a real codebase, API integration patterns) without AI tools first; then test AI augmentation as a separate skill.

09

Underestimating travel / on-site requirements

Candidate accepts thinking ‘hybrid’ means 1 day/week. Reality: 50% travel including two-week customer onsites. Burnout / quit within 6 months.

Detect

Detect: disclose travel % in writing, in JD and in first recruiter screen. Sourcegraph requires 80% Mon–Thu. Defense/gov roles add SERE training, ISOPREP, foreign-travel pre-clearance.

Avoid

Avoid: match candidate's life situation (kids, location, passport, clearance eligibility) to actual demands.

10

Compensation mismatches

Startup offers $180K base for a candidate with a $345K + equity counter from OpenAI.

Detect

Detect: comp data is fragmented, Salary.com says median $127K; Bloomberry $173K; Levels.fyi (Palantir) $215K; Hashnode says OpenAI/Anthropic $350–550K mid-senior.

Avoid

Avoid: benchmark across Levels.fyi, Bloomberry, Hashnode, the a16z piece, and Pragmatic Engineer. Lead with equity story for early-stage; lead with cash + RSU for later-stage. New York pricing now exceeds SF for many FDE roles.

Key takeaways

  • The single biggest failure: hiring a great SWE who freezes on customer calls. Use Shilpa Balaji’s ‘trenches’ sign-off and require travel willingness in writing.
  • AI tourists name-drop LangChain but jump to solutions before scoping. Real FDEs ask 5–10 clarifying questions first.
  • 58% of FDE roles are at 11–200 employee companies. Not seed (founders should do it) and not large enterprise (which has full PS).