How Cursor Does Forward Deployed Engineering
Notes from Pauline Brunet on Cursor's FDE model: the customer maturity versus customization matrix, where FDE adds leverage, and where it does not.
These are my notes from the Forward Deployed Engineering workshop at @aiDotEngineer on June 30, 2026.
Session: How Forward Deployed Engineering Is Done at @cursor_ai
Speaker: Pauline Brunet
Company: Cursor
Company X: @cursor_ai
FDE Function
Cursor's framing separated FDE from traditional professional services and staff augmentation.
Before building an FDE motion, the important questions are:
- Who is the target customer?
- Where are they in their transformation journey?
- How customizable is the product?
Customer Maturity vs. Customization Matrix
- Low maturity, low customization: basic adoption support, not high-value FDE.
- High maturity, low customization: self-service works; FDE adds little.
- High maturity, high customization: FDE acts as advisor and accelerator.
- Low maturity, high customization: prime FDE territory.
Where FDE Teams Fit
FDE can extend features and create feedback loops, but it should not collapse into solution architecture or bug-writing.
The warning was practical: avoid deploying expensive senior engineers on work that does not use their depth.
My Take
Cursor's framework is useful because it gives a way to decide when FDE is actually worth it. The role is highest leverage when customers have low transformation maturity and the product needs meaningful customization.
That is also the danger zone. If FDE becomes general support, solution architecture, or bug execution, it burns senior engineering capacity without creating product learning.
Bhaulik Patel
Forward deployed AI engineer and creator of Deployed Engineer.