Why do you want to work at Cursor?

"I cold applied, and a recruiter reached out. The whole process felt super straightforward and unusually practical: no coding rounds, just a recruiter screen, a hiring manager screen, a live enablement presentation with a Cursor demo, and then an onsite with multiple conversations plus a CTO-style pilot presentation. Everybody I talked to was very warm, gentle, and surprisingly unassuming, and both the recruiter and hiring manager were extremely responsive. The role itself felt much more like a go-to-market solutions architecture job than a traditional engineering manager role, centered on helping entire engineering orgs adopt Cursor as a platform. It's still in progress for me, but in terms of how effective the company was at conveying the job and running a useful process, it was one of the better ones I've done."

"The whole process felt way more startup-y than normal. First was a 45 minute informal chat where he went through my background, asked why Cursor, and was very candid about the company and pace. Then I had a 60 minute repo-based coding round where I implemented a hash tree they actually use, and I was allowed to use Google, GPT, and Cursor for targeted syntax help. The final was the most unusual part: an 8 to 9 hour remote onsite where they gave me part of the codebase, a Slack channel, and asked me to figure it out, build a feature autonomously, and present it. They told me they're still figuring out what new grad hiring even looks like, so the process felt unconventional and a little vague, but also much more like real work than the standard interview loop."