Skip to main content

Cursor

Forward Deployed Engineer

San FranciscofulltimemidAdded 1 month ago

About this role

Embed with customer engineering teams to design and ship production-grade AI-powered workflows using Cursor that meaningfully accelerate their development process. You'll own the complete lifecycle from discovery through production support, solving real bottlenecks with measurable impact.

What you'll do

  • Conduct discovery with customer engineers to identify bottlenecks and establish success metrics
  • Design and build Cursor-powered workflows for tasks like refactors, migrations, and PR review automation
  • Ship rapid initial versions, then harden them into reliable systems with monitoring and rollout plans
  • Ensure production quality through tracing, evaluations, metrics, and model behavior debugging
  • Communicate clearly with senior engineering leaders about technical tradeoffs and results
  • Extract reusable patterns from deployments to improve the core Cursor product

What they're looking for

  • Software development (5+ years experience)
  • Python and JavaScript/TypeScript
  • Customer discovery and outcome accountability
  • AI-native workflow development and debugging
  • Full-stack engineering (frontend, backend, infrastructure)
  • Production reliability and incident response
  • Problem scoping and shipping under ambiguity
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

  • Tell us about a time you owned an end-to-end AI or ML system in production. How did you debug when the model behavior wasn't what you expected?
  • Walk us through a discovery process where you identified a real bottleneck for a customer and defined success metrics. What did you learn that surprised you?