How ResumeBloom tailors your resume (Part 1): Most Resume Tailoring Agents Are Optimizing the Wrong Things

I fed the same work history into three resume tailoring tools and got back three documents that were nearly identical, not because my experience was consistent, but because each tool had independently arrived at the same wrong answer. "Spearheaded cross-functional initiatives." "Leveraged Kubernetes to orchestrate containerized deployments." "Reduced operational costs by 40%."

None of those things happened. The tools invented them because their training data taught them that this is what "good" resumes look like.

The unsettling part: each output scored well on the tool's own quality metrics. Keyword density was high. Action verbs were present. Quantified achievements were sprinkled throughout. By every internal measure, these were excellent resumes. But when I showed them to three recruiters, the reaction was unanimous, they felt generated. Not wrong, exactly. Just... not real.

I've spent the past several months running the same inputs through a dozen tools, comparing outputs side by side, and talking to recruiters about what makes them trust a document or discard it. The patterns are consistent, and they're not what the tools are optimizing for.

In this post, I'll walk through what I found when I stopped asking "does this resume score well?" and started asking "does this resume feel true?", and the five ways most tailoring agents fail that second test.

I started by checking the most obvious thing: keywords. That's where the first crack appeared.

Every tailoring tool I tested had some version of a keyword-matching score. Feed in a job description, get back a percentage. The logic is straightforward: a job description mentions Terraform eight times, so the agent dutifully works Terraform into every corner of the resume it can find. On the tool's internal scorecard, this looks like a win.

But I wasn't interested in the scorecard. I was interested in what happened when a human read the output.

So I showed the keyword-optimized resumes to recruiters and asked a simple question: "Does this person know Terraform?" The answer, across every recruiter I asked, was some version of "I can't tell." They weren't tallying mentions. They were asking a quieter, more instinctive question: does this person actually know what they're talking about?

There's a gap between claiming a skill and demonstrating it, and that gap is exactly where every tool I tested fell apart. Compare these two lines:

Experienced with Terraform, AWS, Kubernetes, Docker, and CI/CD.

Built AWS infrastructure with Terraform and automated deployments through GitHub Actions.

The first is a list of things someone wants you to believe. The second is a description of something that happened. One of them makes a recruiter feel something. The other makes them reach for the next resume.

Tailoring systems are great at the first kind of sentence. They're rarely built to produce the second. And once I understood that, I started wondering: if the tools are optimizing for the wrong signal on keywords, what else are they getting wrong?

So I looked at the numbers next. That's when things got worse.

Spend enough time with AI-generated resumes, and you start noticing that everything, somehow, improved by a suspiciously round percentage. Deployment time down 60%. Efficiency up 40%. Costs reduced by half.

The numbers aren't lies, exactly. They're more like unexamined truths. The system learned that quantified achievements perform well, because every resume guide on the internet says so, and then it applied that lesson everywhere, indiscriminately, until the resume started reading like a quarterly earnings call.

I tested this directly. I took a resume that contained one genuine, verifiable metric, "reduced build times from 12 minutes to 4 minutes by parallelizing test suites," and fed it through three tools. Two of them inflated it. One changed it to "reduced deployment time by 60%." Another added three entirely new metrics to bullet points that had originally contained none.

The problem isn't the numbers themselves. The problem is that recruiters immediately start asking questions that fabricated numbers can't answer. From what baseline? Over what timeframe? Was it actually your doing? Does it matter at the scale the company operates?

A concrete, modest claim survives that scrutiny. An inflated, unsupported one doesn't. And a resume full of the latter signals something, not competence, but the performance of competence.

At this point I had two failures on my hands: keyword optimization that didn't demonstrate knowledge, and metric generation that collapsed under questioning. But I still hadn't looked at the most basic element of all: the words themselves.

I tried a diagnostic I'd never seen anyone use: read only the verbs.

My favorite test, when I suspect AI involvement: ignore everything and read only the verbs.

Spearheaded. Leveraged. Orchestrated. Facilitated. Utilized.

Nobody talks like this about their own work. Engineers say they built something, fixed something, migrated something, stayed up until 2am because the pipeline was broken again. The AI verbs are trying to sound more professional and achieving the opposite, they strip the humanity out of the experience and replace it with the linguistic equivalent of stock photography.

I ran this verb-only test across twenty AI-tailored resumes and twenty human-written ones. The difference was immediate. The human resumes used verbs like built, fixed, migrated, debugged, rewrote, shipped. The AI resumes used spearheaded, orchestrated, leveraged, facilitated, championed. There was almost no overlap.

Recruiter notice. Maybe not consciously, but they notice. The resume stops sounding like a person and starts sounding like a press release, and somewhere in the back of the mind, trust quietly exits the room.

Three failures now: keywords, metrics, language. Each one was a different surface symptom. But I started to suspect they all pointed to the same underlying problem, something structural, something about how these systems think about a resume as a whole rather than as a collection of parts.

That suspicion led me to the flaw I find most interesting: the coherence problem.

Picture a resume where the Skills section lists Terraform, Kubernetes, and AWS. Then you read through the Experience section, three jobs, eight bullet points each, and Terraform never comes up again. Not once. No project used it. No migration involved it. Just a word sitting alone in a list, disconnected from everything else.

I started checking for this pattern systematically. I'd take a tailored resume, extract every skill from the Skills section, then search for each one in the Experience bullets. Across a sample of thirty AI-tailored resumes, roughly 40% of listed skills never appeared in any experience bullet point. They were ghosts, claimed but never demonstrated.

That's the fingerprint of a system that optimizes sections in isolation. The Skills optimizer sees a job description keyword and adds it to the list. The Experience optimizer works on bullet points independently. Neither module knows what the other is doing.

Human experience doesn't work that way. When you actually use something, it leaves traces throughout your story. A technology appears in a project. That project connects to an outcome. The outcome reflects back on the skill. Real resumes have this internal gravity, things pull toward each other because the underlying experience is coherent.

Many tailoring systems produce documents that are locally optimized and globally incoherent. Every section looks fine on its own. The whole thing, read as a narrative, feels assembled rather than lived.

Four failures, all pointing in the same direction. But there was one more thing bothering me, something about the very definition of what these tools were trying to do.

At that point I realized the industry had settled on a definition of "tailoring" that I think is just wrong.

Tailoring, as most tools practice it, means making a resume resemble the job description. More shared vocabulary. Higher surface-level similarity. A better score on whatever ATS is being gamed.

But recruiters already have the job description. They wrote it, or their colleague did. What they're actually looking for is something the job description can't contain: a reason why this particular person is worth a conversation.

That's not about keyword density. It's about clarity. About making relevant experience easy to find and easy to trust.

The best-tailored resumes I've come across don't have the most keywords, the most metrics, or the most impressive language. They just make it obvious, quickly, why the candidate belongs in the room. And that's a fundamentally different optimization target than anything the current generation of tools is built to pursue.

All five failures converge on the same thing: credibility is harder to generate than keywords.

There's a quality to the resumes I find most convincing that I keep coming back to. They feel hard to fake.

Not because they're long or elaborate. Because they contain things that require real knowledge to produce, specific decisions, honest trade-offs, the texture of actual work. You can tell that whoever wrote this built the thing they're describing because they mention the part that was annoying.

That's the actual challenge for these agents. Generating keywords is a solved problem. Generating credibility, the sense that someone was genuinely there, is not. And every failure I found, from keyword stuffing to fabricated metrics to inhuman verbs to structural incoherence to the wrong definition of tailoring, is a different manifestation of the same gap.

---

So where does that leave us?

Probably in an uncomfortable middle ground. AI tailoring tools are genuinely useful for the mechanical parts, restructuring, reformatting, catching what's missing relative to a job description. That's real value, and pretending otherwise would be dishonest.

But the moment a tool starts writing your experience rather than clarifying it, something important gets lost. The resume stops being a record of what you did and becomes a projection of what the algorithm thinks an employer wants to hear. Those two things can look identical on screen and feel completely different to the person reading them.

The most useful frame I've found: treat tailoring as editing, not generation. You bring the substance. The tool helps with the signal. The moment that relationship inverts, the moment the tool is doing more authoring than you are, the resume stops being yours in any meaningful sense, and recruiters can usually tell.

The question I'm left with, and the one I'll take up in Part 2, is whether it's possible to build a tailoring system that optimizes for credibility instead of keyword density. Whether you can teach an agent to clarify experience rather than fabricate it. I don't know the answer yet. But I know the five things it would have to get right.

---

If you want a more grounded, practitioner-level take on what actually goes into a strong resume, format, structure, the decisions that matter before any AI gets involved, the r/resumes community has a surprisingly thorough wiki guide worth reading alongside anything automated tools produce.