How to write a one-page FDE CV: lead every bullet with the customer outcome, and don't call a prototype a deployment

FDE Times has published a step-by-step guide to writing a Forward Deployed Engineer CV, drawing on CV advice from Aced, fde.academy and Final Round AI and on Palantir's FDSE posting. It recommends one page unless you have eight or more years of experience, and a simple frame recruiters can scan: a short summary of what you put into production and for whom, skills grouped by category, and experience written as bullets.

The core advice is to write each bullet in this order: business outcome, number, scale, and only then the technology. So "built a Python pipeline syncing CRM and accounting data" becomes a line about cutting manual sync time by 80% across 20 customer accounts. Each role should also include at least one bullet naming the users or stakeholders you worked with and one showing you owned the work from design to go-live, which the guide says Palantir's posting explicitly looks for.

Why it matters for FDEs: the guide warns that interviewers dig into claims, so presenting a demo as a production system, internal tooling as customer deployment, or an unused side project as experience tends to fall apart quickly. For engineers moving in from product or platform roles, it suggests describing internal work honestly, including who the users were and which number changed, since that still counts as evidence of working with users.