2 min lesson
Where DX sits vs. Field Engineering, Support and Product
Talk through "How would you crisply distinguish DX/DevRel from Field Engineering at Cursor?" Then name the practical move.
Step 1 of 3
Four roles all sit near Cursor's developers and an interviewer will check whether you know which one you applied to. The cleanest cut is reach and direction: who you serve, how many at once and which way the work flows.
DX/DevRel is one-to-many and proactive. You teach at scale through public artifacts. Field Engineering is one-to-few and hands-on with named enterprise accounts. Support is reactive - it resolves the issue a user already hit. Product builds the surface itself.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Read the two axes - reach and posture - to know which seat you applied to.
Learn more
Full explanation
Full explanation
The near-certain question is "why this role and not Field Engineering?" Answer with reach and posture, then pivot to motivation: "Field Engineering goes deep with a few accounts. DX teaches at scale - one demo can reach every developer at once and I want the impact of one-to-many plus the research at what's new. That's the work I'd do for free." Naming the distinction crisply proves you chose this seat on purpose.
Don't blur DX into Support. Support is reactive and one-to-one; DX is proactive and one-to-many. If a story you tell is really a support story - "a user was stuck, I helped them" - recast it as the scaled version: you saw the same confusion across many developers and shipped a tutorial or fix that closed it for all of them at once.