No narrow job descriptions

Cursor states it plainly: there are no narrow job descriptions. Engineers write marketing copy, answer user issues, optimize infra and help hire. The SA role inherits that ethos completely.

For you, "no narrow job descriptions" is not a slogan, it's the day-to-day. The same week can hold a security review, a debugging session inside a customer's broken environment, an enablement deck you wrote from scratch and a cross-functional thread nobody else owns.

• Write enablement content and curricula when none exists.
• Debug thorny customer environments - model routing, MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. wiring, CI integration - hands on the keyboard.
• Support security and governance reviews alongside the customer's risk team.
• Own ambiguous cross-functional work that falls between Product, Sales and Support.

Two attributes Cursor names explicitly map directly onto this: extreme ownership and execution in ambiguity - driving outcomes without a playbook. Come with stories that prove them, not adjectives that claim them.