2 min lesson
Show genuine product passion
Answer "Why does the 2-day on-site project raise the stakes on a credible 'why Cursor' and what makes an infra motivation answer survive follow-ups?" Use one lesson detail to support it.
Step 1 of 2
Show genuine product passion
The 2-day on-site project exists to filter out people just viewing it as a job. By the time you sit with the team, your interest in the product has to be real and visible. Use Cursor heavily before you interview and form opinions about its infra-visible behavior.
- Use Cursor daily on a codebase you care about for weeks before you apply, until you have real opinions instead of borrowed ones.
- Notice the infra-visible behavior an engineer would: tab-completion latency, how it degrades on a flaky network, retry behavior when a model call times out.
- Have one specific thing you'd want to dig into under the hood, framed as a hypothesis you'd test, not a fact you're asserting.
Connect the mission to why the infra matters, out loud. “If the mission is to automate coding for millions of developers, the editor only feels magic when the foundation is invisible - sub-100ms suggestions, no rate-limit pain, no regional brownouts. That foundation is the product as far as the user is concerned and that's the seat I want.” It reframes infra from plumbing to product.
Do not assert Cursor-internal architecture facts you can't support to a team that built it. If you haven't verified how their edge or autoscaling works, say “I'd guess” or “I'd want to confirm,” and frame it as curiosity. Honest hypotheses survive; a confident wrong claim about their stack ends the conversation.