Onboarding an FDE in the First 30 Days: From Context to First Deliverable

The short answer

FDE onboarding fails by drowning hires in product docs while starving them of customer context. Flip it: customers and delivery rituals first, product details as needed. The 30-day goal is one owned, scoped deliverable - proving the working rhythm, not memorizing the platform.

Week 1 - Context absorption

• Shadow 2+ customer calls (any stage: discovery, status, incident).
• Read the last two project briefs and one runbook - annotate questions.
• Ship one tiny internal fix (build pipeline check, not a customer deliverable).
• Meet the ops/support folks they'll coordinate with; learn the escalation path.

Manager check: can they summarize the two active projects' success metrics from memory?

Week 2 - Co-delivery

• Pair on a live deliverable: they write the brief draft, mentor reviews against the brief template.
• Attend the deployment/change process once end-to-end.
• Own one small customer-facing ticket with mentor as safety net.

Manager check: does their brief draft pass the one-page test with a number in it?

Weeks 3-4 - First owned deliverable

• A scoped project: 1-2 week size, real (small) customer impact.
• They run the discovery or requirements confirmation themselves.
• They present the result - and the trade-offs made - at the team review.

Gate (day 30): the written brief + shipped deliverable + one recorded customer interaction reviewed together.

What to avoid

• 30 days of docs and environment setup with zero customer contact - your hire is learning the wrong job.
• First project = the crisis nobody wants. Tempting; too risky; do it at day 60.
• Skipping the recorded-interaction review - it's the highest-leverage coaching minute you'll get.

Continue: Hiring playbook · Assessing discovery