Forward Deployed Engineering at Cursor — Pauline Brunet

The first question at Cursor is not how to deploy a forward deployed engineer, it is whether to. If a customer's teams are already mature in their transformation and can self serve on an AI coding platform, sending a 10x engineer to sit with them is a waste. Pauline Brunet's frame is to read where the customer actually is: the forward deployed engineer earns their place where teams cannot hire or staff the talent, need an advisor, and want a real outcome rather than a demo. On the ground that means working with VPs of engineering, understanding how they operate today, and driving a strict, measurable return on investment as the tip of the spear. The other half is who you send and how you scope it. Cursor hires what she calls unicorns by splitting the role: one person who is the deep industry expert, another with the aptitude to learn fast, often pulled from the system integrators and consultants who already know change management. Engagements stay short, roughly six week cycles that co design the solution with the customer, check honestly whether you are close, and pivot on the learnings instead of grinding on a symptom. The discipline is scope: solve the problem the buyer actually cares about, prove the return, and stay honest about where the product really is. Speaker info:   / pauline-brunet   Timestamps: 0:00 - Introduction: forward deployed at Cursor 1:52 - When NOT to send a forward deployed engineer 4:00 - Where the forward deployed engineer fits 5:31 - What the job actually entails 7:50 - The economic buyer and a strict ROI 9:43 - Scope discipline: knowing what you can't solve 11:22 - Hiring unicorns by splitting the role 14:06 - Who to hire, and being an honest partner 16:41 - Six week engagements and scope 18:14 - Pivoting on the learnings 19:55 - Wrap up: build trust