Cursor
Software Engineer, Core Services
About this role
Cursor is seeking a Software Engineer for the Core Services team to build and maintain critical backend infrastructure powering their AI-driven code automation platform. You'll own authentication systems, webhooks, and agent workflow backends that support millions of developers, focusing on reliability, performance, and clean abstractions.
What you'll do
- Design and implement scalable authentication architecture for a widely-used developer tool
- Own agent backend infrastructure, optimizing for end-to-end performance and reliability
- Build robust webhook server with high-throughput event delivery and proper retry semantics
- Develop resilient abstractions over source control providers and third-party integrations
- Partner with client and inference teams to improve multi-step agent workflows
- Own the full lifecycle of production services from design through operation
What they're looking for
- Backend service architecture and operations
- Authentication/authorization (OAuth, JWTs, RBAC)
- Event-driven architectures and webhook systems
- Agentic systems and complex multi-step workflows
- API design and clean abstractions
- Production service reliability and performance optimization
- Database and infrastructure design
- Source control system integration
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
- Tell us about a time you designed and implemented authentication or authorization for a production system. What were the key security and scalability considerations?
- Describe your experience building or operating webhook/event delivery systems. How did you handle reliability, retries, and failure cases?