Cursor
Software Engineer, Bugbot
About this role
Join a small, talented team building Bugbot, an AI-powered code review tool that catches bugs and suggests improvements for professional developers. As a full-stack Software Engineer, you'll own Bugbot's product end-to-end—from UI and integrations to model behavior and onboarding—directly shaping how millions of engineers interact with AI during code review.
What you'll do
- Ship new Bugbot features end-to-end, from product definition and UI to backend and model optimization
- Evolve the review pipeline by adapting prompting strategies, model routing, and agent orchestration
- Build and maintain integrations that embed Bugbot seamlessly into developer workflows
- Monitor product quality, triage false positives, and ensure review accuracy and reliability
- Design onboarding and adoption flows that drive user activation and daily engagement
- Collaborate with ML, infrastructure, and product teams to inform roadmap and scale the system
What they're looking for
- Full-stack software development (frontend, backend, and model integration)
- LLM integration and prompt engineering
- Agent design and orchestration
- Product metrics and evaluation design
- CI/CD and developer tool integrations
- Code review workflow knowledge
- System design and scalability
- Product-focused problem-solving
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 full-stack feature you shipped end-to-end. How did you balance speed with quality, especially when it involved ML or model behavior?
- Tell us about a time you worked on integrating a tool into a developer workflow (CI/CD, code review, IDE, etc.). What made adoption and daily usage difficult, and how did you solve for it?