Support Operations Systems Lead

Cursor Cursor · Coding AI · Remote · User Ops

This role is for a Support Operations Systems Lead at Cursor, a company focused on automating coding. The role involves owning and managing the systems, workflows, and operating rhythms for User Operations to ensure reliability at scale. Responsibilities include live triage, backlog management, systems health monitoring, stakeholder communication, and program ownership across ticketing systems, routing logic, queue health, labeling taxonomy, and escalation paths. The ideal candidate is technical, comfortable investigating operational issues, making system changes, and driving technical/operational programs end-to-end, while also using AI-native workflows to reduce manual work.

What you'd actually do

  1. Own day-to-day operations for core support systems, including ticketing workflows, routing, queues, labels, taxonomy, escalations, and related tooling.
  2. Triage urgent operational issues as they arise, especially when system behavior, workforce distribution, queue health, or SLA risk looks off.
  3. Manage intake, prioritization, and follow-through for systems requests from support managers, TSEs, operations leads, engineering, product, and other internal teams.
  4. Help maintain the team’s roadmap by distinguishing one-off fixes from broader system improvements, surfacing recurring pain points, and pushing back on low-leverage work.
  5. Drive smaller technical and operational programs end-to-end, being responsible for discovery, scoping and execution, rollout, documentation and success metrics.

Skills

Required

  • Experience in support operations, systems operations, technical program management, or a similarly cross-functional technical systems role.
  • Comfortable working close to operational systems such as ticketing platforms, routing workflows, queue configuration, labels/taxonomies, dashboards, Slack workflows, and internal tools.
  • Technical enough to investigate system issues, read configuration or code, and partner effectively with engineers.
  • Excellent at triage and prioritization.
  • Ability to own work end to end: clarify the problem, align stakeholders, sequence the work, communicate tradeoffs, launch safely, and measure whether the change worked.
  • Comfortable pushing back thoughtfully and can tell stakeholders “not yet,” “not this way,” or “this should be part of a broader fix” while maintaining trust.
  • Strong bias toward action, clarity, and continuous improvement.

Nice to have

  • More technical than a traditional operations lead.
  • More hands-on than a traditional TPM.
  • Less software-engineering-heavy than a dedicated SWE.

What the JD emphasized

  • systems, workflows, and operating rhythms
  • live triage
  • backlog management
  • systems health
  • stakeholder communication
  • end-to-end program ownership
  • ticketing workflows
  • routing logic
  • queue health
  • labeling taxonomy
  • escalation paths
  • workforce signals
  • internal tooling requests
  • investigating messy operational issues
  • making or coordinating safe system changes
  • pushing back on unclear requests
  • turning recurring problems into durable improvements
  • systems requests
  • recurring pain points
  • low-leverage work
  • technical and operational programs end-to-end
  • discovery, scoping and execution, rollout, documentation and success metrics
  • debug issues
  • validate changes
  • improve monitoring
  • prevent repeat failures
  • AI-native workflows
  • reduce manual toil
  • investigate issues
  • summarize signals
  • draft documentation
  • test changes
  • improve how the team operates
  • support operations
  • systems operations
  • technical program management
  • cross-functional technical systems role
  • operational systems
  • ticketing platforms
  • routing workflows
  • queue configuration
  • labels/taxonomies
  • dashboards
  • Slack workflows
  • internal tools
  • investigate system issues
  • read configuration or code
  • partner effectively with engineers
  • triage and prioritization
  • urgent
  • investigation
  • escalation
  • longer-term fix
  • own work end to end
  • clarify the problem
  • align stakeholders
  • sequence the work
  • communicate tradeoffs
  • launch safely
  • measure whether the change worked
  • pushing back thoughtfully
  • tell stakeholders “not yet,” “not this way,” or “this should be part of a broader fix”
  • maintaining trust
  • firefighting
  • systems-building
  • bias toward action, clarity, and continuous improvement