Cursor
Software Engineer, New Grad 2027
About this role
Join a mission-driven team building AI-powered coding tools as a new grad software engineer. You'll own end-to-end product work on developer-facing products like Grok Bot and Cursor, designing and shipping features that blend strong engineering fundamentals with effective use of AI leverage.
What you'll do
- Design, build, and ship full-stack features across AI-powered products (Grok Bot, Cloud Agents, Cursor)
- Drive problems end-to-end from UI through backend implementation, balancing speed with correctness
- Collaborate with a small, high-ownership team to raise standards on code quality and user experience
- Leverage AI tools effectively as development leverage without compromising correctness or design taste
- Iterate on shipped features based on user feedback and real-world usage patterns
- Participate in early-stage prototyping and rapid iteration cycles
What they're looking for
- Full-stack software development (frontend and backend)
- Strong computer science fundamentals and first-principles reasoning
- Proficiency with modern development tools and AI coding assistants
- Product-oriented thinking and attention to detail
- Ability to learn quickly and take ownership of complex problems
- Code review and collaboration skills
- System design and architecture thinking
- UI/UX sensibility and design taste
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Cursor
Cursor builds an AI-driven code editor used by millions of developers to transform how software is built. The company is hiring for infrastructure engineers, ML systems specialists, enterprise platform builders, security engineers, and customer success roles focused on driving adoption within large organizations.
- Website
- cursor.com
Likely interview questions
- Walk us through a project you've built from start to finish—what was the most challenging part and how did you solve it?
- Tell us about a time you shipped something imperfect initially and had to iterate based on feedback. How did you prioritize improvements?