Cursor jobs, judged for you, free

What they do

Cursor makes an AI coding product. It has a desktop editor, local and cloud agents, a CLI, and Bugbot for pull request reviews. It also trains its own Composer models. Millions of developers use Cursor, including over half of the Fortune 500. Cursor is now part of SpaceX, and postings name the employer as SpaceXAI.

What they value

• Seek the truth.
• Bring passion and creativity.
• Enjoy spirited debate and crazy ideas.
• Ship code.
• Work as a self-motivated individual contributor in a flat team.

Where they hire

Most engineering, research, and design roles are on site in San Francisco or New York. Go-to-market roles are in London, Singapore, Australia, Japan, and remote in the US. India roles are all remote and all go-to-market, in enterprise sales, field engineering, AI deployment, and partnerships.

Teams and roles

Most engineering roles are for software engineers on named teams, with some engineering managers. Postings ask for strong fundamentals, taste, and production experience, not a fixed stack. Python and TypeScript are the most common languages.

• Agents: the agent harness, the default model choice, and Bugbot.
• Client infrastructure: an Electron desktop app on macOS, Windows, and Linux.
• Infrastructure: model routing and inference across providers, core services, Postgres storage, and AWS with Kubernetes.
• Enterprise platform: RBAC, SCIM provisioning, and audit logs.
• Other teams: security, growth, and developer productivity.
• Research: reinforcement learning, pretraining data and crawling, RL environments, and evals such as CursorBench.
• Design: design engineers who work in Figma and in TypeScript, React, SolidJS, and CSS.

There are no product manager roles, so product engineers own features end to end. Sales makes up most of the rest of the board, with field and forward deployed engineers.

What they look for

Cursor has a small, talent-dense team. It wants people who own features and run experiments on millions of users. India roles ask for credibility with engineering leaders and CTOs, and a solid grasp of developer workflows. Engineering candidates do two to three short technical interviews. Then they do an onsite in the office, where they work on a small project and meet the team.