2 min lesson
Recruiter screen & 'why Cursor'
Take this situation: "A recruiter asks why you want to work at Cursor. Draft the core of a strong answer for a Design Engineer." Lead with your decision, then add the reason.
Step 1 of 2
The first call is short, friendly and easy to underestimate. It sorts for one thing above all: a reason you want this product that nobody could swap out for any other AI company. Generic enthusiasm fails here faster than anywhere else in the loop.
- Length & tone
- ~30 min, conversational - background, motivation and which surface excites you.
- Why Cursor
- A concrete, non-swappable reason tied to the product, not to AI hype.
- Identity
- Your design↔code self-description in two crisp sentences.
- Logistics
- Location (SF or NY), the in-person two-day trial expectation and timeline.
Lead with the product, not the category. “I love AI” is the answer everyone gives and it reads as low signal. Name an actual interaction and what you'd push on.
“I live in Cursor's inline diff every day and the moment a multi-file edit lands is where the magic either holds or breaks for me - the diff gutter, the accept/reject affordance, how it animates in. I want to own that seam. I'm a design engineer: I move between Figma and the component and I'm happiest taking an interaction from working to right.”
Cursor evaluates passion explicitly and the trial is where they confirm it - but the recruiter is already listening for whether you treat this as a craft. Answering “why Cursor” with vague market enthusiasm flags you as someone here for a job, not the product. They would rather pass on a strong engineer who doesn't care than hire one who'll coast.