The Written Take-Home

The grader can tell in one sentence whether you researched the account or guessed at it. The take-home is won before you write the email, in the half hour you spend reading what the company has already told the world about how it builds software.

Personalization that lands is specific to their engineering reality, not a stitched-in name. An engineer reading your email is asking one question: did this person bother to understand my team or am I row 4,000 in a sequence. Your research has to answer that in the hook.

Where the real signals livemine these before writing a word

That last card is the Cursor-specific twist. This is a bottom-up product, so the question is rarely do you use an AI editor - it's whether the team has standardized. If you find scattered individual adoption, your reason to reach out becomes governance and team rollout, not a first introduction.

Find the trigger that justifies reaching out now

A good email has a reason it arrived this week and not last quarter. That reason is a trigger event and naming it credibly is most of your personalization.

• A funding round or a hiring spike on the engineering team.
• A public migration - new language, monorepo move, platform rebuild.
• A new VP Eng or CTO who tends to reset tooling in their first 90 days.
• A stated AI mandate or an exec talking publicly about AI-assisted development.

Map the persona before you pick the angle

A cold email to an engineer survives on restraint. It does one job: earn a reply, not close a deal. Every extra sentence is a reason to archive it.

The structure is small on purpose. Hook them with something only true for their team, connect it to a single concrete value, then ask for almost nothing.

1. 1Relevant hook. One line proving you researched them - a trigger event or a specific engineering detail.
2. 2One-line value tied to their context. What Cursor does for a team like theirs, in plain words, not a feature dump.
3. 3Single soft CTA. One ask, low-friction - interest, not a calendar demand.

The CTA: interest beats a meeting demand

Asking a stranger for thirty minutes cold is a big request and engineers protect their calendar fiercely. An interest-based CTA lowers the bar to a one-word reply and a yes converts into the meeting on the next touch.

Subject: your Go monorepo + 6 backend hires

Hi Priya -

Saw you're hiring six backend engineers and just moved to a Go
monorepo. Ramping that many people on a large codebase is usually
where velocity goes to die.

Cursor is an AI editor that reads your whole repo for context, so
new hires get accurate, codebase-aware edits and explanations from
day one instead of week three. A few teams your size use it mostly
to cut onboarding time.

Worth a quick look or is now the wrong time?

- Alex

LinkedIn is a hallway, not an inbox. The register is shorter, more conversational and far less tolerant of a pitch dropped into a connection request.

The cardinal error is treating LinkedIn as email with a smaller box. Copy-pasting your cold email into a DM reads as automation and engineers spot it instantly. Each channel earns its own version of the message.

Don't pitch in the connection request

The connection request earns the right to message, nothing more. A pitch crammed into that 300-character note is the fastest way to get ignored or marked spam. Keep it to genuine relevance and let the reply open the door.

Every touch adds something new

If your second message just repeats the first louder, you've taught them to ignore you. A multi-touch effort across email, LinkedIn and a call should feel like one person approaching the problem from different sides, never the same message three times.

A sequence is a short story told across touches, not the same message sent five times until they break. Each step changes the angle so a non-reply on touch one doesn't doom touch three.

The take-home sometimes asks for the full sequence and graders look for an arc. The classic angles move from their problem, to proof it's solvable, to a peer who solved it, to a graceful exit.

1. 1Problem. Open on their trigger and the pain it implies - the personalized hook.
2. 2Proof. Show the win is real: a concrete capability or a quantified result for a team like theirs.
3. 3Peer. Reference a comparable company or engineer who solved the same problem with Cursor.
4. 4Breakup. A short, honest “I'll stop reaching out - wrong time or wrong person?” Often the highest-reply touch.

Tie cadence back to the activity math

An SDR's pipeline is arithmetic and a strong take-home rationale shows you think that way. The funnel runs from touches to conversations to qualified meetings and your sequence is the engine that feeds it.

Engineers are the hardest audience for a marketing voice on earth. They detect exaggeration instantly and punish it by tuning you out, so your edge in this take-home is precision, not enthusiasm.

The whole point of the written exercise is whether you can make a complex AI tool simple and accurate. Hype reads as a tell that you don't understand the product. Restraint reads as someone an engineer could trust.

Reference real capabilities, correctly

Product literacy is the cheapest credibility you can buy and getting a feature name wrong is the cheapest way to lose it. Know what Cursor actually does before you write a word about it.

Frame value as workflow, not magic

• Say what changes in their day: less boilerplate, faster onboarding, fewer context-switches out of the editor.
• Talk team standardization for managers - one tool, consistent practice, faster ramp.
• Keep claims testable: “codebase-aware edits,” not “10x your engineers.” Engineers will check.

Acknowledge competitors honestly

If a team already runs Copilot or evaluated Windsurf, pretending those don't exist makes you look naive. Honesty about the landscape is more persuasive than spin - name the comparison and point to where Cursor is genuinely differentiated, like deep codebase context and the agent workflow.

HYPE (delete on sight):
  “Cursor's revolutionary AI will 10x your team and
   automate your entire codebase overnight.”

CREDIBLE (an engineer keeps reading):
  “Cursor reads your whole repo for context, so edits
   and explanations are grounded in your actual code -
   most teams feel it first on onboarding and big refactors.”

The take-home is a writing sample disguised as an exercise. Whoever hires you is asking whether they'd trust you to be the brand's first impression to a technical buyer and a sloppy submission answers no.

Cursor's bar on authenticity and craft is unusually high because it sells to skeptical engineers. The polish pass is where you separate from candidates who wrote a decent draft and stopped.

Cut until every sentence earns its place

Tightness signals respect for the reader's time, which is exactly the quality the job needs. Read your draft and delete any sentence that doesn't move the prospect toward a reply.

Add a brief rationale if asked

Many take-homes ask why you chose this account, persona and angle. A short, sharp rationale is where you prove the thinking behind the writing and it's often weighted as heavily as the email itself.

1. 1Why this account. The trigger event and the signal that made it timely.
2. 2Why this persona. Who owns the pain and can act and why you chose them over a peer.
3. 3Why this angle. The single value you led with and why it fits their reality.