Chapter 02 — Week 14

The Cover Letter I Couldn’t Write

Sunday, April 5, 2026 · 10:42 PM · comeback/journal/2026-04-05.md

Two weeks since the layoff. I have written 47,000 lines of production Go in my career. I have written zero usable sentences about myself this week. I have a Google Doc open in another tab called cover_letter_draft_4.docx and the cursor is blinking on a paragraph that begins “I am a passionate.” I cannot type the next word. I have been unable to type the next word for nine hours.

§ 1 — The Stack Trace That Week

Metric	Value
Day	Layoff + 20
Severance remaining	14 weeks
Liquid runway	$61,000 (untouched)
Burn rate	$8,900/mo (also untouched, somehow)
Active agents	0
*Google Docs open titled some variant of `cover_letter_`**	7
Average time-to-cursor-paralysis after opening blank doc	3 minutes 14 seconds
Job applications submitted	2 (one to a job I do not want, one to a job that does not exist)
LinkedIn posts	0
Number of times I have read another engineer’s “I was laid off and now I’m humbled to announce…” post and felt physically sick	19
People who now know I was laid off	Linda. Dr. K. Hana (told her Thursday, she cried, I cried, neither of us let our parents hear).
People still being told I’m “on a project”	Both parents. The Caffè Vita barista.
Hours in coworking space	41 (cumulative)
Hours actually working in coworking space	unclear. 6? 9?

The most embarrassing entry on this table is “job applications submitted: 2.” It is embarrassing because two weeks earlier I had told Linda I would have ten applications out by end of Week 14. We had said this in bed on a Sunday night, in the soft conspiratorial voice spouses use when they want to feel like a team against a problem. Ten by Easter, I had said, and she had said okay, ten by Easter, and we had gone to sleep feeling, for the first time since Monday, slightly in control of the calendar.

I had two by Easter. One was for a Director of Platform Engineering role at a logistics company in Memphis that I had no intention of moving to. The other was for a “Founding Infrastructure Engineer” role at a five-person AI startup whose website was, on closer inspection, a single landing page that had been generated by an LLM and contained the phrase “we’re cooking” in three different sections.

I applied to the cooking startup at 11:47 PM on a Wednesday. I did not tell Linda.

§ 2 — What Linda Didn’t Know

What Linda didn’t know, in Week 14, was that I had been spending three to four hours every weekday sitting in a Google Doc called cover_letter_draft_4.docx, typing one sentence, deleting it, typing a different version of the same sentence, deleting it, then closing the laptop and opening it again forty-five minutes later to repeat the cycle.

She thought I was applying to jobs. I was not applying to jobs. I was, in a sense that I want to be very precise about, fighting a war with the cursor. The cursor was winning. I lost the war on Monday, lost it again on Tuesday, lost it on Wednesday with such totality that I drove to a different coworking space in Bellevue to lose it in fresh surroundings, and lost it again on Thursday.

The thing about a cover letter is that it requires you to write the sentence “I am the right person for this role because…” and then complete the sentence. I had spent fourteen years architecting systems where every component had an explicit, documented role. I had written runbooks. I had written design docs. I had written postmortems. I had written, in 2024, a 23-page internal RFC about why we should adopt circuit breakers in the v3 control plane, and the RFC had been adopted, and a section of it had been quoted in a senior engineer’s promotion packet (not mine).

I could not, on April 1, 2026, complete the sentence “I am the right person for this role because.”

The reason, I now understand, is that I had spent fourteen years constructing a professional identity that explicitly forbade me from finishing that sentence about myself in the first person, out loud, with confidence, without immediately undermining it. Every cover letter draft I wrote sounded like one of three things:

An apology for applying.
A LinkedIn-influencer caricature of myself written in the second-person passive voice.
A regurgitated job description with my pronouns swapped in.

None of them sounded like me. I knew none of them sounded like me. I sent two of them anyway, because Linda had said “ten by Easter” and I needed to put numbers on the board.

The thing she didn’t know — and that I am writing here — is that on Thursday, April 2, while she was at a UX conference in Portland for the day and Mason was at preschool, I sat at the kitchen counter for six hours and forty minutes and did not produce one sentence I would let any human read. I ate one bagel. I drank four espressos. I closed the laptop at 4:12 PM, picked up Mason at 4:30, made spaghetti, read him Pete the Cat, put him to bed, and at 9 PM when Linda FaceTimed from her hotel I told her I had “made progress on the Memphis application.” I had not opened the Memphis application. I had stared at the cursor for six hours and forty minutes.

I am writing this down because I want, six months from now, to remember that I was capable of lying to my wife about whether I had typed words on a screen. I do not want to be that person. I am not going to pretend, in a future version of this story, that the layoff “made me more honest” if I do not also record the week it made me less.

§ 3 — The Build in 4 Prompts

The build, in Week 14, was the moment I gave up on Thursday night and asked Claude for help.

I did not want to ask Claude for help. The model had been a stranger I’d typed into at 1:34 AM the previous Tuesday. Asking it to help with my cover letter felt like asking a stranger you’d cried in front of once to also do your taxes. It felt cheap. It also felt — and this is the part I want to confess — like an admission that I could not do something a senior engineer should be able to do, which was write a paragraph about himself in his own voice without a piece of software helping.

I asked anyway. It was 9:47 PM Thursday, Linda was still in Portland, Mason was asleep, the cursor on cover_letter_draft_4.docx had blinked at me approximately 14,000 times that day. I opened a Claude Opus 4.7 conversation. Here is what I typed.

PROMPT 1 — Thursday 9:47 PM, the surrender prompt

I am trying to write a cover letter. I cannot. I have been trying for nine hours today. Every sentence I write sounds like either a LinkedIn influencer or an apologetic robot. Please do not write the cover letter for me. I do not want to send a cover letter you wrote. I want to figure out why I cannot write the first sentence.

The model’s response had two parts. The first part was useful and the second part was annoying. I am only going to share the useful part.

You may not be unable to write a cover letter. You may be unable to write a cover letter that sounds like you for a job that you don’t actually want. Are you applying to jobs you want, or are you applying to jobs you can defend to your spouse?

I closed my laptop. I stared at the wall for eleven minutes. The wall in our kitchen is painted “Repose Gray” because a previous owner had read a Joanna Gaines book in 2018 and we had not gotten around to repainting. The Repose Gray, on Thursday April 2 at 10:01 PM, became the most important wall in my life. The wall was correct. The model was correct. I had been trying to write cover letters for two jobs I did not want — Memphis and the Cooking Startup — because they were jobs whose existence I could defend at dinner.

I opened the laptop. I typed Prompt 2.

PROMPT 2 — Thursday 10:14 PM, the diagnostic prompt

Read loved.md (I’ll paste it). Based on what’s in there, generate three sentences that begin with “I want to spend my next three years working on…” — sentences that I, the person who wrote loved.md, could read out loud to my wife at the kitchen table without flinching. Do not be aspirational. Be diagnostic.

I pasted the file from Week 16. The model returned three sentences. The third one ruined me. I will tell you the third one.

I want to spend my next three years working on small, on-call infrastructure for teams that have to be up at 3 AM, where I am close enough to the operators to have dinner with them after we ship.

That sentence is not a job description. There is no job posting on LinkedIn that says “small, on-call infrastructure for teams that have to be up at 3 AM, where you are close enough to the operators to have dinner with them.” That sentence is a shape. I had been trying, for three weeks, to fit myself into the shape of jobs that already existed. The model’s gift, on Thursday April 2 at 10:14 PM, was to give me back the shape of the work I actually wanted, which did not yet exist as a job posting and might not ever exist as a job posting and might, eventually, have to be a thing I built for myself.

I typed Prompt 3.

PROMPT 3 — Thursday 10:38 PM, the voice-extraction prompt

Look at the language in loved.md. Don’t summarize it. Don’t paraphrase it. List the actual phrases I keep using — verbatim — that sound like me. I want to make a “voice file” so I stop writing cover letters that sound like a stranger.

The model gave me back a list of seventeen phrases. I will not share the whole list. Three of them, the ones I have used in every piece of professional writing I have done since:

“close enough to the operators to have dinner with them”
“the kind of system that respects the people who carry the pager”
“I would rather ship a smaller thing well than a larger thing politely”

I copied the list into a file called voice.md and committed it to comeback/. Commit 4a2e8b1. Commit message: voice file: phrases I will not let myself stop using.

I want to be clear about what happened here. The model did not write my cover letter. The model listened to me describe what I loved, then gave the description back to me in a form I could use. That is not authorship. That is the function a good editor performs at a small literary magazine in 1973. I am not going to thank an LLM for being a good editor; I am going to thank it for being available at 10:14 PM on a Thursday when my wife was in Portland and there was no human alive who could have done that work for me at that hour.

The fourth prompt, the one I am proudest of, came twenty minutes later.

PROMPT 4 — Thursday 11:02 PM, the un-do prompt

Now write me one cover letter using the voice in voice.md for a job posting I will paste below. But I want you to write it, then I want you to take out everything that does not sound like the voice file. Then I want you to take out two more sentences. The cover letter should be shorter than 200 words. I would rather be short than polite.

I pasted in a real job posting — a Series A startup that was hiring a “Principal Platform Engineer,” twelve people, run by a CTO who had written a blog post in 2024 that I’d bookmarked — and the model produced a 174-word cover letter. I read it. I changed two words. The opening sentence was: “I want to work somewhere small enough that the platform engineer eats dinner with the operators after a bad on-call week.” I did not write that sentence. I authored the conditions under which it could be generated. There is a difference. I will defend it for the rest of my life.

I sent the cover letter at 11:43 PM Thursday. I told Linda about it on Friday at the airport when she landed. I got a response from the CTO twelve days later. I’ll write about that response in Week 6.

§ 4 — The Bug I Won’t Forget

The bug is cover_letter_draft_4.docx.

It was a bug because I had treated cover-letter-writing as a productivity problem. I am not writing fast enough. I need to write more drafts. I need a better template. I need to schedule three hours every morning to draft. I had brought to the cover-letter task the same instincts I brought to debugging a slow database query: more iterations, more variations, narrower scope, A/B test the openings.

The cover letter was not a productivity problem. The cover letter was a self-knowledge problem dressed up in a productivity costume. I could not finish the sentence “I am the right person for this role because” not because I was a slow writer but because I did not yet know which roles I was the right person for, and I had been hiding the not-knowing under hours of cursor-blinking I could later describe as “working on it.”

The bug, more precisely: I had spent fourteen years operating in a system (Atlas Cloud) that decided for me what the right roles were. I had been very good at being slotted into roles. I had no muscle for picking them. The layoff had taken away the slotting machine, and I had reached for the same machine in the form of a job board, and the job board was doing the slotting badly, and I had concluded that I was bad at cover letters.

I want to record, for the record, that the Repose Gray wall in our kitchen taught me more about my own career on Thursday April 2 at 10:01 PM than any career counselor ever has. The wall did not have advice. The wall just sat there while I sat in front of it for eleven minutes. The wall is, as far as I can tell, the most under-rated career-development tool in the modern American home.

§ 5 — The Boundary I Wrote Into the Agent

There is no agent yet, but the boundary was written this week, in plain English, in comeback/RULES.md, commit 9b3c7e2, message rules file: things I will not let the model do for me.

The Voice Rule

I will not let Claude — or any other model — write a sentence under my name that I would not say out loud to a person, in my own voice, without flinching.

Test: read the sentence aloud, in the kitchen, to Linda or to the wall. If I flinch, the sentence is not mine. Cut it. The model can produce a hundred sentences. I will keep the three that pass the kitchen test.

This rule, more than any other, has shaped every email, every LinkedIn post, every prospect outreach, every contract paragraph I have shipped under my name in the four months since. It is the reason I have not become — despite using AI at every step of this comeback — one of those people who post threads that begin “Most engineers don’t realize this, but…” I cannot read that sentence in my own voice without flinching. So the model does not get to write it for me. So I do not become the kind of person who would have written it.

The funny part — the dark-funny part, since you asked for some — is that I am taking dictation from a wall and a 5-year-old’s bedtime book and a chatbot, and the result is the most “in my own voice” writing I have ever done. Fourteen years of writing design docs in committee at Atlas Cloud, all of them edited by review chains of eight people, produced a body of work that sounds like it was written by no one. Three weeks of sitting alone with Claude and a Repose Gray wall has produced, on this page, the first sentences in my career that sound like me.

I do not know what to do with that. I am writing it down anyway.

§ 6 — What Compounded

voice.md.

The file has, as of tonight, twenty-three entries. Most weeks I add one or two. Some entries are phrases I want to use. Some are phrases I will never let myself use again. The file is sorted in two sections: MINE and NOT MINE. The NOT MINE section includes “thrilled to share,” “blessed and grateful,” “passionate about leveraging,” “I’d love to learn more,” “synergy,” “personal brand,” “thought leader,” “unlock,” “10x,” “deep dive,” “circle back,” “low-hanging fruit,” “in the weeds,” “swing by,” “let’s chat,” and (added Thursday 10:48 PM) “passionate.”

The MINE section is shorter. It will always be shorter. That is the point.

Every email, every cover letter, every LinkedIn post, every prospect outreach since Thursday April 2 has been written through voice.md. The Hermes outbound agent I will install in Week 6 has voice.md loaded into its system prompt. The OpenClaw memory layer I will install in Week 4 (after Week 0, you’ll see what I mean) tags every prospect note with which entries from voice.md I used. The custom MCP server I will write in Week +4 has, as one of its tools, a voice_check(sentence) function that returns FAIL if the sentence contains any phrase from the NOT MINE list.

What compounded, in Week 14, is the file I am most proud of building in fourteen years of building software. It is twenty-three lines of plain text. It is the foundation under everything that follows.

If you are reading this in your Week 14 — staring at your own blank Google Doc, your own Repose Gray wall — please make voice.md before you make the next cover letter draft. The file does not have to be long. Two phrases that sound like you and three phrases that don’t, written down once, will do more for the rest of your job search than seven more drafts of cover_letter_draft_4.docx.

The cover letter comes later. The voice comes first.

— Daniel, Sunday Week 14, 10:42 PM, kitchen counter, Linda asleep, Repose Gray wall on my left, fan still wobbling.