One-page evidence resume
Translate projects into customer, system and outcome signals—not a technology inventory.
Evidence gateThree bullets each show problem → action → measured result; every claim can be defended.
Build the resume →PHASE 6 · EVIDENCE TO OPPORTUNITY
Forward Deployed Engineer
Job Readiness.
Prove you can do the job, then practise proving it. Package your work, survive a realistic interview loop and use an honest scorecard to decide whether to apply now or remediate first.
0/9capstone artifacts
0/4launch assets
0/6mock rounds
0/18self-review score
01 · GET INTERVIEWED
Build a recruiter-readable launch kit.
Do not claim “customer impact” without evidence. College projects count when the problem, constraints, users and measured result are real and inspectable.
Recruiter-safe GitHub
Make the strongest work understandable in a two-minute scan.
Evidence gatePinned capstone, clean README, setup path, architecture, tests, demo and honest limitations.
Package the capstone →FDE case study
Tell the full customer arc from ambiguity to adoption and handoff.
Evidence gatePublished narrative links the nine capstone artifacts and names rejected alternatives.
Export a case study →Six-story evidence bank
Prepare specific stories for conflict, failure, ambiguity, ownership, learning and adoption.
Evidence gateEach story has context, your decision, consequence, evidence and what changed afterward.
Use the question bank →02 · PASS THE LOOP
Run one complete mock day.
Use a reviewer wherever possible. Run it timed, preserve the artifacts, score it, remediate one weakness, then rerun that round within seven days.
1
25 min
Motivation + ownership
Why FDE? Defend one failure, one conflict and one decision that cost you something.
LEAVE BEHIND Record answers; reviewer flags vague claims and missing personal ownership.Open practice →2
60 min
Coding + debugging
Repair unfamiliar integration code while narrating hypotheses, tests and trade-offs.
LEAVE BEHIND Commit diff, passing tests and a short debugging log.Open practice →3
45 min
Customer decomposition
Turn an underspecified customer goal into users, decisions, constraints and a thin slice.
LEAVE BEHIND One-page problem tree, success metric and explicit scope cuts.Open practice →4
60 min
Customer system design
Design a production integration; cover identity, failure, observability, rollout and ownership.
LEAVE BEHIND Diagram plus two defended trade-offs and one failure drill.Open practice →5
40 min
Client roleplay
Handle a bad request, a failed demo and a stakeholder blocking adoption without losing trust.
LEAVE BEHIND Reviewer scores listening, clarity, pushback and next-step ownership.Open practice →6
45 min
Project defense
Demo the capstone, show an unhappy path, defend evaluation and ROI, then accept challenge.
LEAVE BEHIND Recorded defense plus reviewer notes against the capstone rubric.Open practice →03 · CHOOSE THE BRIDGE
A college-year strategy that stays honest.
Direct new-grad FDE roles exist but are scarce. A stepping-stone role is useful only when it builds production ownership, customer context or applied-AI evidence.
YOUR PRIORITY
Earn engineering fundamentals and evidence of finishing.
ROLES TO TARGET
- SWE intern
- Backend intern
- Data engineering intern
- Campus developer role
NEXT 90 DAYS
- Ship one deployed API with tests and observability
- Join a team project and own one production-like integration
- Practise explaining decisions in public READMEs
04 · EVIDENCE SCORECARD
Score what a reviewer can inspect.
0 = absent · 1 = fragile · 2 = apply-ready · 3 = standout. A quiz score or checked box is not evidence.
01
Coding & debugging
Can you ship and repair unfamiliar integration code under time pressure?
PROOF Timed repository, tests, commit history and narrated debugging log.02
Systems & production
Can you design for failure, security, observation and handoff—not only the happy path?
PROOF Architecture, threat model, incident evidence and runbook.03
Applied AI rigor
Can you measure quality, classify failures and gate regressions?
PROOF Golden set, eval report, threshold and CI regression behavior.04
Customer delivery
Can you discover the real workflow, cut scope and earn adoption?
PROOF Discovery notes, scoped metric, constraint revisions and adoption evidence.REMEDIATEScoping simulator →Client roleplay →
05
Communication
Can different audiences understand the decision, risk and next action?
PROOF Executive update, technical handoff and reviewed recorded demo.REMEDIATEStakeholder lab →Handoff handbook →
06
Interview performance
Can you reproduce these signals across a complete, timed loop?
PROOF All six mock rounds, reviewer scores and a written remediation rerun.READINESS VERDICT
Keep building evidence before calling it ready.
Your next weakest gate is Coding & debugging. Complete its remediation, attach proof and rerun that mock round.
This is a local self-review tool, not a credential, hiring guarantee or substitute for human review. Scores should reflect linked artifacts and reviewer feedback.