I Was Mass-Applying to Jobs. Then I Let AI Write My Cover Letters.

The Sunday Night Ritual

It was 11 PM on a Sunday. I had 14 tabs open — all job postings — and a Google Doc titled "Cover Letter FINAL v3 (real final).docx". Sound familiar?

I'd been at it for three weeks. Copy the company name. Swap out the framework. Change "passionate about React" to "passionate about Vue". Hit send. Repeat. I was applying to 10-15 jobs a day and hearing back from exactly zero of them.

The worst part wasn't the silence. It was knowing that every cover letter I sent was the same bland paragraph wearing a different hat. Recruiters could smell it. I could smell it. But what else was I supposed to do — write a heartfelt, unique letter for every single listing?

The Breaking Point

The moment I almost gave up was a Wednesday afternoon. I got a rejection from a company I actually cared about. A startup building developer tools — right in my wheelhouse. I'd spent 45 minutes on that cover letter. Mentioned their recent blog post. Talked about their open-source library. Still got the "we've decided to move forward with other candidates" email.

I stared at my screen and thought: I have six real projects on GitHub. I've contributed to open source. I've built things people actually use. But none of that shows up in a cover letter that starts with "Dear Hiring Manager, I am writing to express my interest in..."

That's when I realized the problem. My cover letters talked about what I wanted. They never showed what I'd actually done.

What If My Code Could Speak for Me?

I'd been building Flynner partly out of my own frustration, and one feature kept nagging at me: what if we could generate cover letters that were actually grounded in a developer's real work? Not generic templates with blanks to fill in, but letters that pull from your GitHub projects, your commit history, the technologies you've actually shipped with.

So we built it. And the first time I used it on my own job search, I felt something I hadn't felt in weeks: I wasn't embarrassed to hit send.

The letter opened by connecting my open-source monitoring dashboard to the company's focus on observability tooling. It mentioned specific technologies from my repos that matched their stack. It didn't say "I'm a fast learner" — it said "I built a real-time WebSocket pipeline in the same framework your team maintains."

It was still my story. The AI just knew how to tell it.

What Actually Changed

I want to be honest here — AI cover letters aren't magic. I didn't suddenly get offers from every company. But three things shifted almost immediately:

I stopped dreading applications. The worst part of job hunting is the soul-crushing repetition. When each letter takes 30 seconds to generate instead of 30 minutes to agonize over, you actually have energy left to research companies, prep for interviews, and — you know — live your life.

My response rate went up. Not overnight, but noticeably. Within two weeks I had three first-round interviews scheduled. The previous month I'd had one. The letters felt specific enough that recruiters actually referenced them in calls. One said, "I liked that you mentioned your experience with our GraphQL setup." The AI had pulled that connection from my projects. I wouldn't have thought to make it.

I applied to fewer jobs, but better ones. When you're mass-applying, you throw spaghetti at the wall. When each application feels tailored, you get pickier about where you apply. That sounds counterintuitive, but it means you spend more time on companies you actually want to work at — and it shows.

The Part Nobody Talks About

Here's what I wish someone had told me earlier: the cover letter isn't really about convincing someone you're qualified. Your resume does that. The cover letter is about making a human connection in 200 words — showing the person reading it that you've thought about their company, not just any company.

That's exactly what generic templates fail at. And paradoxically, it's what AI does well — when it has real data to work with. Your GitHub is full of real decisions, real trade-offs, real problem-solving. An AI that can read your repos and connect them to a job description isn't making things up. It's finding the story that was already there.

You still need to review it. Edit it. Make it sound like you. But you're editing a solid draft instead of staring at a blank page.

A Typical Tuesday Now

These days my job search looks different. I spend my morning coffee browsing listings on Flynner, filtered by my stack and salary range. When I find something interesting, I read about the company, check out their engineering blog, maybe look at their open-source repos.

Then I generate a cover letter. It takes about a minute. I read through it, tweak a sentence or two, sometimes add a personal note about why I'm genuinely interested. I submit it and move on with my day.

No more 14-tab Sunday nights. No more "FINAL v3 (real final)" documents. No more sending the same letter to 15 companies and hoping nobody notices.

I apply to maybe 3-4 jobs a week now. I hear back from most of them.

Try It Yourself

If you're in the middle of a job search and you're exhausted by the application grind, I get it. I was there. The trick isn't to work harder — it's to let the work you've already done speak louder.

Sign up for Flynner, connect your GitHub, and generate your first AI cover letter in under a minute. It's free to start, and honestly, just seeing your projects translated into a compelling narrative might change how you think about your own experience.

Your code already tells a great story. You just need a better way to share it.