Emails

📘 Learn Emails from zero

Start from the constraint. A job-search email is a request packet sent over a high-latency, lossy channel: a busy professional's inbox. The recipient triages dozens in seconds, and most get dropped. Your job is to make your packet survive triage and produce one action.

Analogy. Treat the inbox like an API endpoint with a tiny attention budget. The subject line is the request route the reader uses to decide whether to open at all; the introduction is the payload header stating who you are and why this call matters; the closing / call-to-action (CTA) is the single field you want filled. Everything else is overhead that raises the odds of a 4xx-style rejection (ignored or deleted). This maps onto the canonical three-part structure the book optimizes with AI: subject line → introduction → closing/sign-off.

Worked example. A backend role, and you share a mutual contact — so this is a referral email. Weak: "Dear Sir/Madam, I am writing to express my keen interest..." — no route, no reason, no ask. Strong: Subject (under ~60 chars, specific): Backend SWE referral via Priya Rao — quick question. Intro: name the referrer first ("Priya Rao on your team suggested I reach out"), then one line of relevance ("I built a payments service handling 5k req/s"). Closing: one explicit, low-friction CTA ("Would you be open to a 15-minute call this week?") and a sincere thanks. Two to three short paragraphs, one ask.

Where AI fits. Use ChatGPT to brainstorm subject lines, draft the intro/closing, and adjust tone ("make it more formal," "make it friendlier"). But you own the truth: replace every placeholder with a real, verifiable detail, proofread, and rewrite any robotic AI phrasing in your own voice. AI is a drafting accelerator, not a fact source.

Key insight: every job-search email must pass a 5-second test — a stranger can identify who you are, why you wrote, and the one action you want, without reading twice.

✨ Added by the guide to build intuition — not from the source course.

🎯 Guided practice

1. Easy — Fix the subject line. Draft subject is Hello; the body asks a recruiter for a status update on a submitted application. Reasoning: (a) the subject is the route the reader uses to triage, so it needs identity + purpose; (b) front-load the role and the action and keep it under ~60 characters so it isn't truncated on mobile; (c) result: Following up — Senior Data Engineer application (Req #4821). Pattern: a subject line is an index key — specific and self-describing so the reader can route it without opening.
2. Medium — Classify the type, then prompt AI with the canonical template. You want a 15-minute informational interview with a senior PM at a target company; no mutual contact. Reasoning: (1) classify: this is cold outreach in the informational-interview scenario, so the ask must stay small (time and advice), never "give me a job." (2) Fill the book's master email template — Purpose → Tone → Key Points → Call-to-Action — into a constrained prompt so the model can't drift: "Help me write a polite, concise email to [Name], a [Job Title] at [Company]. Introduce me as a [my current role] interested in [specific topic]. Reference their work on [specific launch I will name]. Ask if they'd be open to a 15-minute call or coffee chat for career advice. Tone: friendly yet professional, ~90 words, one clear CTA, no flattery clichés, no fabricated facts — leave bracketed placeholders for anything personal." (3) Then you verify and humanize: replace every [placeholder] with a real, true detail, proofread for grammar, and rewrite any formulaic AI phrasing in your own voice to dodge the "overuse of AI phrases" pitfall. Core pattern across both: classify the type → apply the canonical structure → make exactly one ask, with AI accelerating the draft and the human owning truth, tone, and personalization.

✨ Added by the guide — work these before the full problem set.