2 min lesson
Individual contributor, not manager
Work through the cases in "Individual contributor, not manager", pairing each signal with the move that fits.
Step 1 of 2
Individual contributor, not managerwhat “staff” means here
The fastest way to mis-read this role is to hear “senior” and reach for a leadership story about running a team. Cursor is hiring a builder. Your success metric is shipped systems that hold up under audit and scale, not org charts or roadmaps you delegated.
A hands-on developer: SQL, code, integrations, workflow automation that you write and own.
The architect of the billing engine, ERP, revenue subledger and the seams between them.
The standard-setter - your CI/CDContinuous Integration / Continuous Delivery. The automated pipeline that builds, tests and ships code so changes reach production safely and often. Press Enter for the full definition., sandbox strategy and testing become the team's playbook.
A people manager hiring and running a finance-systems org.
A functional admin who only configures off-the-shelf modules.
A controller or accountant - you build the systems accounting depends on, you don't close the books.
You set the standards future hires inherit. That phrase carries weight in the interview: every architectural choice you describe should sound like something a second and third engineer could safely build on, not a clever one-off only you understand.
When asked “what does this role own?”, lead with the one-sentence mandate - first finance-systems hire, hands-on IC, architecting O2C then R2R - then add the framing unprompted: “and because I'm employee one in this function, I'd build it so a future hire can extend it without me in the loop.” That last clause signals you understand the founding nature of the charter, not just the acronyms.