Skip to main content

Cursor

Software Engineer, Model Routing & Inference

New YorkfulltimemidAdded 1 month ago

About this role

Build the inference platform powering Cursor's AI interactions, focusing on making model serving faster, more reliable, and cost-effective at scale. You'll own the complete inference path from routing to failover, handling millions of requests daily across multiple AI providers.

What you'll do

  • Design and maintain the inference gateway abstracting multiple provider APIs
  • Implement cross-provider failover mechanisms to prevent outages
  • Build routing, backpressure, and admission control systems for traffic spikes
  • Optimize for cost, latency, and reliability tradeoffs in production
  • Handle the inference path for agent sessions, completions, and chat messages
  • Scale the system to support millions of AI requests

What they're looking for

  • Distributed systems design and implementation
  • High-throughput, low-latency system architecture
  • Inference serving or traffic routing experience
  • Real-time data pipeline design
  • Cost and capacity planning optimization
  • Production systems at scale
  • API abstraction and integration
  • Software engineering fundamentals
Apply with Autofill

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
View all jobs at Cursor

Likely interview questions

  • Walk us through a time you designed a high-throughput, low-latency distributed system. What were the bottlenecks, and how did you optimize for both performance and cost?
  • How would you approach building an abstraction layer over multiple LLM provider APIs with different semantics and rate limits?