The Role & Your Charter

Cursor calls this seat the tip of the spear for pipeline generation. You are the first human a prospective customer meets - the person who turns a cold company into a real conversation an Account Executive can close.

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.

The title on the offer letter is Account Associate, but the function is classic SDR: high-volume, multi-channel outbound into engineering organizations. The honest one-sentence charter is this: you create qualified pipeline that an AE converts to revenue and you carry the number that measures whether that pipeline showed up.

Notice what you do not own. You don't close deals, you don't run security reviews and you don't negotiate price. Your job ends the moment a qualified meeting lands cleanly on an AE's calendar with enough context for them to take it from there.

Your top three deliverables

One detail changes how you should read this whole role: it is a builder seat, not a run-the-machine seat. At a mature company an SDR inherits a tested sequence and a script. Here you help write them, which is why interviewers probe for self-starter energy rather than process-following.

Your ICP is narrow on purpose: startup and mid-market engineering organizations. Not consumers, not non-technical departments, not enterprise IT committees. The buyer is a team that ships code and feels the pain Cursor removes.

Inside that org, three groups care about different outcomes and the message that opens a door for one falls flat for another. An IC engineer wants to know it won't slow them down. A VP Eng wants throughput and a standard tool. Reaching the wrong persona with the right message still gets you ignored.

The defining dynamic is bottom-up adoption. Engineers find Cursor, install it and use it daily - often before anyone in sales has touched the account. That fact rewrites your opener.

Whatever door you pick, you have to answer one question before you dial: why would this specific person take a meeting now? A new funding round, a hiring spike, a public migration or visible organic Cursor usage all qualify. “Because I have a quota” does not.

An SDR who can't talk about their own funnel reads as someone who waits to be told what to do. The job is a numbers machine and you're expected to read your own dashboard and adjust before a manager has to.

The funnel has four stages and each one converts to the next at a rate you should be able to estimate. Activities become conversations, conversations become qualified meetings and qualified meetings become opportunities the AE works.

1. 1Activities. Calls dialed, emails sent, LinkedIn touches - the raw top of funnel you control directly.
2. 2Conversations. Live connects and genuine replies, where a human actually engages with you.
3. 3Qualified meetings (SQLs). Booked discovery calls with a fit buyer that an AE accepts.
4. 4Opportunities. SQLs the AE qualifies into a real, working deal.

You don't need to recite Cursor's exact internal numbers, which you won't have. You do need to reason with rough industry benchmarks so you can answer “how many touches yield a meeting?” without freezing.

Now use the math. If a booked meeting takes roughly 8-10 live connects and a connect takes roughly 15-20 dials, then one meeting can sit behind well over a hundred dials. That arithmetic is exactly why activity floors and resilience are part of the job, not nagging.

Cursor is a developer tool with strong bottom-up adoption. Engineers adopt it on their own, love it, tell teammates and only later does a team or company decide to standardize and pay. That sequence runs in reverse from a classic top-down enterprise sale.

For you, that means a lot of outbound isn't truly cold. A real slice of the job is finding accounts where Cursor is already in use and converting that organic usage into a team or enterprise conversation. You also run genuinely net-new cold accounts, so you operate on two tracks at once.

The second thing that shapes the job is stage. This is an early sales team, so the playbook barely exists. You co-author sequences, test messaging and help define process rather than inheriting a polished machine.

1. 1Test messaging. Try angles in real outbound and watch which ones earn replies.
2. 2Read the signal. Note which value props land with which persona and which objections recur.
3. 3Feed it back. Bring that intelligence to the team so the next rep starts from your learning.
4. 4Codify. Help turn what works into a repeatable sequence and process.

There's a third reality that raises the bar: you're the brand's first impression and you're making it to engineers. A technical buyer can smell a generic, hype-loaded pitch in one line. Credibility comes from speaking their language and being honest about what Cursor does and doesn't do.

Every line of the job description is a question in disguise. The interviewer isn't checking whether the words describe you - they're checking whether you have a specific story that proves the trait. Walk in with one ready per line.

The trap is answering with adjectives. “I'm a relentless self-starter” is worth nothing; the time you built a target list from scratch and booked three meetings before anyone gave you leads is worth everything. Convert each requirement into evidence.

Two of those lines deserve special prep because Cursor weights them. Curiosity about engineering is cultural here and the values round looks for passion for the problem of automating coding rather than someone treating this as just a job. The AE-ambition line is checked because the seat is a launchpad and they want people who actually want the next rung.