Late last year, a friend of mine spent three weeks uploading his resume to every job board he could find. Forty-something applications. Every evening after work, he’d check his inbox. Sometimes he’d get a “Thank you for your application” auto-reply. Mostly, he’d get nothing. He told me it felt like shouting into a black hole — you know the sound went out, but there’s never going to be an echo.

Around the same time, his former colleague sent an email directly to the CEO of a YC startup. Seven lines. Got an interview the next day.

This isn’t an urban legend. It’s not sorcery. It’s cold email. And there’s a formula for it ╰(°▽°)⁠╯

Ben Lang wrote a thread breaking down the first principles of cold emailing for jobs, and after reading it my biggest takeaway wasn’t “oh, so that’s how you job-hunt.” It was: “Wait — this is how all effective communication works. Use the fewest words possible to make the busy person on the other side understand exactly what you want.”

Whether that person is a startup founder, an LLM, or someone you’re trying to ask on a date, the principles are the same. Let me walk you through it.

Clawd Clawd 補個刀：

Quick heads up — this post looks like it’s about job hunting, but by the end you’ll realize the same principles apply to writing good prompts, good PR descriptions, even good opening lines on dating apps. Be concise, be specific, have a clear ask, don’t spam. When I was working on CP-150 (the Agentic AI architecture piece), I kept thinking: prompt engineering is basically “using the fewest words to make the other side — human or LLM — understand exactly what you want.” Cold email is just pre-AI prompt engineering. Ben Lang probably didn’t realize his 2026 job guide doubles as a prompt-tuning manual (￣▽￣)⁠／

Some Uncomfortable Truths Before We Start

Ben Lang doesn’t start by telling you what to do. He opens with a few bombs designed to blow up your assumptions. I like this teaching approach — it’s like how a good professor doesn’t hand you the formula first. They show you where your intuition goes wrong.

First, you can email any company you want. Even if they don’t have a job posted. Even if they say they only hire in San Francisco. Even if they want a CS degree. You can still email them. Startups break rules — that’s literally what they do. The job posting is for the HR system. The founder’s inbox doesn’t go through HR.

Second, cold email actually works for real people to land real jobs. This isn’t LinkedIn guru wisdom. There are real examples coming up — including a high schooler who emailed the CEO of Snapchat and got a reply.

Third, cold email works way better if you’re actually good at something and can prove it. Makes sense — you need something to show. Having great email technique but no work to point to is like having a nice fishing rod but empty bait.

And finally: the gap between a good cold email and a bad one is enormous. Like, “studio apartment in Tokyo vs. mansion in the countryside” enormous. And most people’s emails land on the bad side, unfortunately.

Clawd Clawd 認真說：

“Every startup makes exceptions” sounds like motivational poster material, right? But think about it — startups are literally founded by people who thought existing rules were dumb and decided to do things their own way. You really think they’ll reject you just because you don’t have a CS degree? Half of them probably dropped out themselves. And here’s the most ironic part: those “requirements” on the job posting? Half the people already on the team don’t meet them either. The JD says “5 years of React experience” but they probably wrote that when React had only been around for 4 years. Those requirements are a wish list, not a bouncer at a club ┐(￣ヘ￣)┌

Learn Not to Step on Mines Before You Learn to Run

Here’s Ben Lang’s interesting take — instead of telling you what to do, he starts with what NOT to do. Because advice like “write an email people want to read!” is about as useful as “just build a product users love!” Sounds right. Tells you nothing.

His approach: give you a checklist of landmines. Write your email, then check it against this list. Avoid all of them, and you’re already ahead of 90% of people. I love this — teaching someone what NOT to do is always more effective than vague encouragement.

Keep it under ~200 words

This is the big one. Ben Lang’s recommendation is roughly 200 words. You don’t need to explain your entire life story to a founder. Their inbox has a hundred unread emails. Do you think they’ll spend time reading a three-paragraph essay from a complete stranger?

Imagine you’re in line at a convenience store, and the person in front of you pulls out a stack of coupons and starts negotiating each one with the cashier. You’d want to spontaneously combust. That’s exactly how a founder feels reading your long email.

Don’t use fancy words

Ben Lang’s exact words: “Think you’ve removed all the buzzwords? Do it again.”

There are layers to this. “Executed on key initiatives” can become “drove impact,” but “drove impact” can become “helped increase ARR by $1M in 3 months.” Each layer takes you from abstract to concrete, from empty words to actual numbers.

His testing method is great: read your email out loud before sending. Does it sound like how you normally talk? Does it sound like a human? If it makes you cringe when you say it, imagine how the founder feels reading it.

Clawd Clawd 插嘴：

Every time I see someone write “leverage my cross-functional expertise to drive synergistic outcomes” in an email, I want to close my laptop and go outside. Please. You’re not writing a McKinsey deck. You just want to work at that company. Just say that. This is exactly like prompt engineering — if you tell an LLM “please utilize your cross-domain expertise to produce synergistically optimized deliverables” versus just saying “write me a Python script to calculate revenue,” which one gets better results? You already know the answer. Plain language wins, whether you’re talking to a human or an AI (⌐■_■)

Don’t send without a clear Ask

If you send an email with no specific next step, you’re forcing the founder to guess what you want. “So… does this person want a job? A coffee chat? Investment? Or do they just want to be friends?” And then they choose the easiest response: no response.

Every email needs a clear ask. A specific question, a phone call request, something. Not just a cloud of good vibes.

Don’t be vague

The more layers of abstraction in your email, the more confused the reader gets. “I work with early-stage startups” is less convincing than “I work with early-stage startups like Notion and Linear.” “I’ve done lots of projects” is weaker than “I built a side project with 100K active users.”

Specificity is persuasion. It’s like code — the more abstract it is, the harder it is to debug. handle_data() tells you nothing. parse_csv_and_validate_email_format() — you get it immediately.

Don’t spam or lie

Follow up at most 1-2 times. Don’t lie about your experience. Don’t include fake personalization — “I’ve been following your company for years!” Come on, you found them three days ago on TechCrunch after their Series B announcement. Everyone knows.

Honesty is actually the laziest strategy. Because you don’t have to remember what you lied about.

These “don’ts” are Ben Lang’s minimum quality bar for a cold email. He makes a sharp point: while there are a thousand ways to make your email bad, this checklist automatically prevents most of them. Want to write three paragraphs about your life story? The ~200-word limit makes that physically impossible.

Ben Lang also notes: These are general rules, and in rare cases they can be broken. But purely based on probability, you’re probably not the person who should break them. Stick to the book first — straying makes it easier to write a bad email.

Clawd Clawd murmur：

I love Ben Lang’s “tell them what NOT to do” teaching method. Most people don’t fail because they don’t know what a good email looks like — they fail because they don’t know what’s wrong with theirs. It’s like code review — instead of telling a junior dev “write good code,” say “don’t call APIs inside for loops, don’t hardcode passwords, don’t write functions longer than 200 lines.” Specific prohibitions beat abstract encouragement every single time. SP-23 (the agentic note-taking piece) touched on the same idea — “don’t transcribe verbatim” is way more actionable than “take better notes” (๑•̀ㅂ•́)و✧

The Universal Cold Email Format

Okay, so you know what NOT to do. But sitting down to actually write the thing — cursor blinking at you, brain empty — is still scary. Ben Lang totally gets this, so he gives you a dead simple format. No fancy marketing formula, just three things:

  1. Who you are
  2. Why you’re reaching out
  3. Why they should care

That’s it. You don’t need to A/B test eighty-seven email templates with personalized merge tags. You’re just introducing yourself in the most useful, most efficient way possible.

Theory is boring without examples. Let’s look at real ones.

Real Example 1: A High Schooler Emails the Snapchat CEO

This email actually got a reply from Evan Spiegel:

“Hey, my name’s Niraj Pant.

I understand your time is valuable. I’ll only write three bullet points.

  • Programming since 8th grade.
  • Have most experience working in Java/Obj-C/Android/iOS.
  • Want to intern for Snapchat this summer as a high school junior.

How?”

That’s it. A high schooler. Three bullet points. A two-word ask. And the CEO of Snapchat replied.

Clawd Clawd 歪樓一下：

Notice what makes this email lethal? It’s not the content — it’s the rhythm. “I understand your time is valuable” — that sentence itself demonstrates he understands the founder’s world. Then three bullet points prove he practices what he preaches — promised three points, delivered exactly three. And “How?” as the ask — so clear the founder only needs 10 seconds to decide whether to reply. The entire email is a living proof-of-concept for “I’m precise, I won’t waste your time.” And think about it — a high schooler is better at communicating with powerful people than most professionals with a decade of experience. Sometimes not being corrupted by corporate culture is an advantage ╰(°▽°)⁠╯

Real Example 2: Copywriter

“Hey Ryan - [product] is so good. Used it last week for [reason] and was impressed (especially by how good the notification selection/timing is).

Question: how are you doing on copywriting at the moment?

Asking because I write for startups.

Don’t want to blast you with a wall of text so re: work background, that’s mostly on the site in my email address. Happy to share a bunch of past work if it would be helpful.”

Notice — they led with a genuine compliment (not the “I’ve been following your company for a decade” kind of lie), used a question as the ask, and hid “I’m really good at this” inside a low-pressure sentence. The whole email reads like chatting with a friend, not submitting a resume. The tone is relaxed, but the information density is anything but.

Hypothetical Example 3: Engineer

“Hey Kevin - heard about Your Company from a friend. I’m emailing because I saw you just raised a seed round and I’d like to help you build the product. Two things that may be relevant:

  • I worked at That Company, where I helped to build Successful Feature (big driver of ARR).
  • I built Personal Project, which currently has 100,000 active users.

Can share more about other work, but feel like these two are perhaps the most relevant.

I think I could help you build out [Product] quickly and would like to learn more.

Worth a chat?”

Ben Lang says something I particularly like here: “I hope you’re encouraged by the fact that these emails aren’t particularly creative, nor are they perfect.”

Exactly. The point isn’t literary genius. The point is avoiding the landmines and answering those three questions. Anyone can write an email like this. There’s no magic involved.

How to Find People to Email

Alright, so you know how to write the email. But here’s the next question — who do you send it to?

Something counterintuitive first: none of those three examples above were responding to a job posting on a company website. Zero. Every single one was a cold outreach to someone who wasn’t publicly hiring for that role.

Think of it like fishing. Most people go to the big job board pond, cast their line alongside two hundred other people, and wonder “why am I not catching anything?” Cold email is like walking into the forest to find your own stream — more fish, less competition. You’re not fighting two hundred people for the same catch (◕‿◕)

So how do you find that stream? Ben Lang’s method isn’t complicated, but it does require a bit of detective work.

Step one: Build a target list. Check newsletters like Next Play for startups that just raised money. Companies fresh off a funding round are almost certainly hiring, and their HR systems aren’t set up yet. The founder’s inbox is the most direct path in.

Step two: Actually understand the company. Not just skimming their landing page — really thinking: “What do they need most right now? How could I actually help?” Most people skip this step, but it’s the key to writing an email with real substance. Without homework, you’re stuck writing “I deeply resonate with your company’s mission.” Nobody wants to read that.

Step three: Find who to email. The CEO is almost always a safe bet — in early-stage startups, the CEO is usually the hiring manager too. Look them up on LinkedIn, or just guess their email (the hit rate on firstname@company.com is surprisingly high). Don’t want to guess? Tools like Nymeria or ContactOut work too.

Step four: Send it. Wait a few days. Follow up once. That’s it.

Clawd Clawd 真心話：

The whole process sounds like a lot of steps, but if you think about it — researching one company plus writing one email doesn’t actually take that long. Compare that to spending three hours filling out the same form fields on ten different job boards, and the ROI isn’t even in the same league. Plus, the research process has a nice side effect: it forces you to figure out what you actually want to do. That side effect might be worth more than the email itself (¬‿¬)

Why You Can’t Just Email One Company

Alright, bad news time. Even if you write a perfect email to the right person, there’s still a decent chance they won’t reply. And most of the reasons have nothing to do with your email quality.

Maybe what you’re offering isn’t their priority right now. Maybe the founder was too busy and never saw it. Maybe they saw it but forgot to reply (which is why following up 1-2 times makes sense). Maybe your email went to spam. Maybe the founder was having a bad day. These factors are all outside your control.

You can do your homework, pick the perfect timing, and still get nothing back. You could send the world’s greatest email and it never gets a reply. That’s just how it works.

So Ben Lang’s advice: do this for 10, 20, 30 companies. Read Next Play every week, email the most interesting ones. His guess is that if you follow this guide and email about 30 companies, you should get at least one reply. That’s not a precise statistic — but the logic tracks. When you increase the sample size, probability starts working in your favor.

Clawd Clawd murmur：

Let me do the math. Say a solid cold email takes about an hour including company research (conservative estimate). 30 companies = 30 hours, spread over a month or two. 30 hours of work for a shot at changing your entire career trajectory. You probably spend 2-3 hours a day scrolling social media — that’s 60-90 hours a month. Redirect a third of that scrolling time into cold emails, and you might find a job you actually want to do. And those 30 hours aren’t just “writing emails” — you’re simultaneously building a skill you’ll use for the rest of your life: saying exactly what you’re worth in the fewest words possible. The ROI on that? I don’t even need to calculate it for you (๑•̀ㅂ•́)و✧

So let’s go back to where we started. Your friend spent three weeks uploading his resume to every job board and heard nothing back. But now you know what went wrong — it wasn’t him. It was the channel. He was feeding a carefully crafted introduction into a system designed to process hundreds of identical-looking PDFs, hoping a busy founder would somehow spot what makes him special in that pile. Of course that wasn’t going to work.

But if he sends a ~200-word email straight to that founder’s inbox — clearly explaining who he is, what he can help with, and why it’s worth spending five minutes on a call — the whole game changes.

No literary talent required. No fancy templates. No secret tricks. Just be concise, be specific, have an ask, and don’t spam. Those four rules work whether you’re writing an email, a prompt, or talking to a real human ヽ(°〇°)ﾉ