1 min lesson
What Core Services owns
Put this lesson point into plain words: "The Engineering Manager, Core Services leads the team that owns Cursor's critical shared backend."
Step 1 of 2
The Engineering Manager, Core Services leads the team that owns Cursor's critical shared backend - the layer that sits between every product surface and the raw infrastructure. Four domains live under that charter and none of them is a back-office nicety: auth, webhooks, the backend systems powering agent workflows and source-control (SCM) integrations.
Read this section as the role contract. The diagram or table names the surface area, but the interview signal is whether you can turn it into a clear operating claim: what you own, what you do not own, what evidence proves the work is working and where judgment matters.
Think of this team as the load-bearing wall of a tool with over a million daily active users. Product teams build rooms on top of it. When the wall cracks, every room shakes at once. That is what people mean when they call this layer existential.
Learn more
Full explanation
The Layer Core Services Owns
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Core Services sits between every product surface and the raw infrastructure.
Two of these - webhooks and SCM - are how Cursor talks to systems it does not control. When GitHub throttles you or fires a duplicate event, your code is the thing that has to stay correct. The other two - auth and the agent backend - are the parts users feel on literally every action they take.
Learn more
Optional practice
Practice: What Core Services owns
QWhich framing best captures why Core Services is treated as existential rather than back-office?