DEV Community: AI Utilities

I Tried ChatGPT to Fix My Resume. Here's Why It Missed the Point.

AI Utilities — Thu, 18 Jun 2026 03:23:31 +0000

Comparing https://resume.zoevera.com against https://chatgpt.com

And what a purpose-built ATS checker caught that GPT-4 didn't.

Let me be upfront: I use ChatGPT for everything. Code reviews, draft emails, explaining stack traces at 2am. It's genuinely useful. So
when I needed to tailor my resume for a senior backend role, my first instinct was to open a chat window.

That was three weeks ago. Here's what I learned.

What ChatGPT actually does well

Ask ChatGPT to "improve my resume" and it will:

Clean up passive voice ("responsible for" → "led")
Suggest stronger action verbs
Add structure and formatting consistency
Rewrite vague bullets into something that sounds more impressive

For general writing quality, it's genuinely good. If your resume reads like it was written by someone who hasn't slept in 48 hours, ChatGPT will fix that.

What ChatGPT fundamentally cannot do

Here's the problem: ChatGPT doesn't know what job you're applying for.

You can paste the job description into the prompt, sure. But there's no mechanism for it to:

Score your resume against that specific JD — it has no concept of a match percentage
Identify which keywords are present vs. missing — it will suggest improvements but won't systematically audit keyword coverage
Know how Applicant Tracking Systems parse text — it will rewrite content without knowing whether an ATS will ever see it

ATS filters work on keyword frequency and placement. A resume that reads beautifully to a human can score 40% on an ATS if the right
terms aren't in the right sections. ChatGPT optimizes for human readers. ATS systems are not human readers.

I ran a test. Same resume, same job description (Backend Engineer, Node.js/AWS stack). I gave ChatGPT the full JD and asked it to optimize my resume for ATS.

The output was well-written. It added "microservices" and "REST APIs" in a few places. But it missed:

"AWS Lambda" — mentioned 4 times in the JD, absent from my resume after the rewrite
"CI/CD pipeline" — appeared in the required skills section, never added
The Projects section — ChatGPT rewrote my experience bullets but left the Projects section untouched, which is where most of my relevant backend work lived

When I ran the same resume through resume.zoevera.com, it flagged all three gaps explicitly, with section-level attribution. The ATS
match score went from 54% to 81% after applying the suggested changes.

The core difference: diagnostic vs. generative

ChatGPT is a generative tool. It produces new text. It's very good at that.

An ATS checker is a diagnostic tool first. It measures the gap between your resume and a specific job description, then tells you exactly what's missing. The rewrite comes second — and it's grounded in what was actually identified as absent, not what the model thinks sounds better.

This distinction matters because:

ChatGPT hallucinates improvements. It will add metrics you never achieved ("improved system performance by 35%"), use terminology that
sounds right but wasn't in the JD, and rewrite bullets that didn't need rewriting while leaving critical gaps untouched. Every line needsfact-checking.

A purpose-built tool works from the actual gap. The keywords it adds are the ones the JD asked for. The sections it flags are the ones the ATS will score. The output is closer to submission-ready.

A practical workflow

These tools aren't mutually exclusive. The best result I got came from using both in sequence:

ATS checker first: identify the keyword gaps and get a scored rewrite that closes them
ChatGPT second: use it to polish tone, tighten sentences, and clean up anything that sounds mechanical

The ATS checker handles precision. ChatGPT handles prose quality. Neither does both well alone.

The cost argument

ChatGPT Plus is $20/month. If you're actively job searching, that's a fixed overhead whether you use it or not.

Most people search for jobs in windows — a few weeks of active applications, then nothing for months. A per-session model makes more
sense: pay when you need it, nothing when you don't. ZoeVera's pricing works that way — free analysis, one-time payment for the full
rewrite, no subscription.

For a developer audience specifically: if you're applying to 10–15 roles over two weeks, you're not optimizing resumes 365 days a year.
The math on a monthly subscription doesn't work.

What I'd actually recommend

If you just need better writing: ChatGPT is fine and you already have it
If you're applying to roles where ATS filtering is real (any company using Workday, Greenhouse, Lever, iCIMS): use a dedicated ATS checker first, then polish with ChatGPT
If you're a developer and haven't thought about this: your resume probably uses technical jargon that means something to you and nothing to an ATS keyword parser. "Built scalable backend" is not the same as "developed microservices architecture using Node.js and AWS ambda" — even if the underlying work is identical

The ATS doesn't know what you meant. It only knows what you wrote.

Tested against a real Backend Engineer job description. Tools used: ChatGPT GPT-4o, https://resume.zoevera.com. June 2026.

The Resume That Almost Cost Me Everything (And What I Wish Someone Had Told Me Sooner)

AI Utilities — Sat, 06 Jun 2026 14:59:39 +0000

Article inspired by https://resume.zoevera.com

A letter to every financial professional who has ever felt invisible in a hiring process they were more than qualified for.

— -
There is a particular kind of silence that follows when you send out
application after application and hear nothing back. Not a rejection. Not “we went with someone else.” Just silence. As though you never existed at all.

If you have lived that silence, I want you to know something before we go any further: the problem is almost never you. I have spent a great deal of time sitting with people who are extraordinary at what they do, people who have owned P&L statements worth tens of millions, who have led teams through consolidations and statutory audits and board-level reporting cycles that would make most people’s heads spin and they cannot get a callback. Not because they lack the skill. Not because they lack the experience. But because the first reader of their resume is not a human being.

It is a machine. And the machine does not care how good you are.

— -
The Truth About How Financial Manager Roles Are Filled Today

Here is what the hiring process looks like at most mid-size and enterprise companies right now. A job description is written. It is loaded into an Applicant Tracking System: Workday, Greenhouse, iCIMS, SAP SuccessFactors and that system is given a list of terms to screen for. Then your resume lands in that system, and before any recruiter ever lays eyes on it, software assigns it a match score.
Below a certain threshold, typically 70 percent, your application is filtered out automatically.

Seventy percent. And you never know.

What the system is scanning for is not the depth of your wisdom or the quality of your leadership. It is looking for specific vocabulary. It is looking for “FP&A” and “variance analysis” and “SAP FI/CO” — not just “SAP.” It is looking for “EBITDA,” “working capital,” “rolling forecast,” “DCF analysis.” It is looking for your qualification written two ways: “CIMA” and “Chartered Institute of Management Accountants,” because some systems index the acronym and some index the full name, and if yours only has one, you may score half of what you should.

This is not a fair system. But it is the system. And you deserve to know how it works.

— -
What a 27% Match Resume Looks Like

Let me show you something that will change how you look at your resume forever.

A financial manager applies for a role. Her experience is real and substantial. She has managed budgets. She has overseen reporting cycles. She has been responsible for financial systems across multiple business units.

Her resume says: “Managed budgets and oversaw financial reporting across the business.”

ATS match score: 27%.

The same experience, rewritten with the vocabulary the system is trained to find:

“Owned £85M annual budget across 6 cost centres, delivering monthly management accounts, board reporting packs, and KPI dashboards aligned to IFRS standards using SAP FI/CO and Power BI.”

ATS match score: 83%.

Same person. Same experience. Two completely different outcomes.
This is what I mean when I say the problem is almost never you. The problem is that nobody taught us that the language of achievement and the language of ATS screening are two different dialects — and to get through the door, you need to speak both.

— -
The Words That Open Doors for Financial Managers

If your resume is going out for Financial Manager, Finance Manager, or Head of Finance roles right now, here is the vocabulary that ATS systems at these companies are trained to find. Not as a checklist to mindlessly stuff into a document — but as a mirror. Do the words in your resume reflect the full scope Same person. Same experience. Two completely different outcomes.

ATS match score: 83%.

Same person. Same experience. Two completely different outcomes.

This is what I mean when I say the problem is almost never you. The problem is that nobody taught us that the language of achievement and the language of ATS screening are two different dialects — and to get through the door, you need to speak both.

— -
The Words That Open Doors for Financial Managers

If your resume is going out for Financial Manager, Finance Manager, or Head of Finance roles right now, here is the vocabulary that ATS systems at these companies are trained to find. Not as a checklist to mindlessly stuff into a document but as a mirror. Do the words in your resume reflect the full scope of what you actually do?
In financial planning and analysis: FP&A, financial modeling, three-way model, DCF analysis, NPV, IRR, rolling forecast, variance analysis, cash flow management, EBITDA.

In reporting and compliance: Management accounts, statutory accounts,
consolidation, board reporting, IFRS, UK GAAP, US GAAP, KPI dashboards.

In systems and platforms: SAP FI/CO, Oracle Financials, Hyperion, Anaplan, Workday Finance, NetSuite, TM1/Cognos, Power BI, Tableau, Advanced Excel, VBA, SQL.

In qualifications: Write both forms. ACA and “Associate Chartered Accountant.” CIMA and “Chartered Institute of Management Accountants.” ACCA and “Association of Chartered Certified Accountants.” CPA. CFA.

In strategic scope: P&L ownership, cost centre management, business partnering, commercial finance, M&A due diligence, capital allocation, investor relations, working capital optimization.

If you are doing this work and not naming it precisely, the system cannot find you. And the recruiter never gets the chance to.

— -
A Deeper Failure Nobody Talks About

Here is the subtler version of this problem — the one that hits the most experienced finance professionals hardest.

The more senior you become, the more comfortable you get describing your work in outcome language. You led the business. You influenced strategy. You drove efficiency. This is accurate. This is even impressive, in conversation.

But outcome language without professional vocabulary underneath it will score low on every ATS built for finance roles. A system scanning for “commercial finance” or “business partnering” will not find those concepts inside phrases like “worked closely with senior leadership to support business decisions.”

The machine is literal. Describe your role in the exact terminology of your

profession, then layer the outcomes and metrics on top. Not one or the other but both.

And the metrics matter more than most people realize. Budget size. Team headcount. Efficiency percentages. Cost reduction in pounds or dollars. An ATS is not the only reader when a human recruiter does see your resume, they are scanning in approximately six seconds. Numbers stop the eye in a way that sentences cannot.

— -
What This Means for You

You do not need to reinvent yourself. You do not need to exaggerate or inflate or become someone you are not.
You need to look at your resume and ask: does this document speak the same language as the roles I am applying for? Not just in spirit. In precise vocabulary.

There are tools that can run this analysis for you — taking your resume, taking the job description, and showing you exactly which phrases are present and which are missing. What score you would receive. Where the gap is. The best ones go further and show you how to close it not with generic advice, but with rewritten bullets that carry the specific terminology your target roles require.
I am not here to sell you anything. I am here to tell you that this gap between experience and expression is real, it is solvable, and it is not a reflection of your worth.

— -
The Final Thing I Want You to Hear

Job searching at the financial manager level is an act of sustained courage.

You are putting yourself out there, repeatedly, against a process that was not designed with you in mind. The silence you feel after an application is not a verdict on your career. It is a vocabulary problem. A formatting problem. A keyword problem.

And those are the most fixable problems in the world.

Go back to your resume tonight. Read it the way a machine would literally, precisely, without context or inference. Ask yourself: if I were an algorithm scanning for “variance analysis” or “SAP FI/CO” or “P&L ownership,” would I find them here?

If the answer is no or if you are not sure that is where to start.
Your experience is real. Your qualifications are real. Now let your resume speak the language that gets them seen.

— -
If you want to see exactly how your financial manager resume scores against a live job description and which specific phrases are keeping you below the ATS threshold tools like https://resume.zoevera.com run this analysis in under a minute and show you the precise keyword gaps line by line.

Your resume says "K8s." The job description says "Kubernetes." The ATS marks it as missing.

AI Utilities — Fri, 05 Jun 2026 04:17:37 +0000

A senior engineer with five years of production experience ships a resume. React, TypeScript, AWS, Kubernetes: all of it real, all of it daily. Strong GitHub. Clean system design instincts. Applying for roles they're genuinely qualified for.

No callback. Not from one company. From seven.

The engineering hiring process has a layer most developers never think about. Before your resume reaches an engineering manager, before any human reads a single line, it runs through an Applicant Tracking System. The ATS doesn't evaluate your architecture decisions or your GitHub commit history. It compares strings in your resume against strings in the job description. Exact strings.

This is where strong candidates disappear.

The failure mode is invisible because it looks like a match when it isn't. You wrote "K8s" because that's how your team refers to it. The job description says "Kubernetes." The ATS scores you as missing Kubernetes experience. You wrote "built distributed backend services." The JD says "microservices architecture, gRPC." Zero overlap, zero score.

It gets worse. If you've been writing "CI/CD pipelines" but the posting specifies "GitHub Actions" and "Terraform" separately, the ATS may score you as missing both, even if GitHub Actions is the tool you used to build the pipeline you described. The system doesn't infer. It matches.

The complete ATS keyword breakdown for software engineers shows the exact terms these systems scan for across the stack: not just language names but framework versions, observability tools like Datadog and OpenTelemetry, testing frameworks like Pytest and Playwright and cloud specifics like DynamoDB versus generic "NoSQL." Every category where a vague description costs you a keyword match.

The practical fix is mechanical, not creative. For every role you apply to: open the job description, find the exact technology names and make sure your resume uses those exact strings. "Kubernetes (K8s)" covers both. "GitHub Actions" and "Terraform" as separate entries score higher than "CI/CD pipelines" as a single line. Quantified outcomes such as "reduced deploy time by 60%," "99.9% uptime across distributed system" satisfy both the ATS keyword check and the human reader who sees the resume next.

Single-column formatting matters too. Markdown tables, multi-column layouts, and code blocks break ATS parsers at a surprising number of companies still running older systems. Plain text, standard section headers, no graphics.

If you want to know exactly which keywords your current resume is missing against a specific job description, not in general but for that exact role https://resume.zoevera.com runs the comparison and shows your match score, the missing terms and a rewrite that incorporates them. The first analysis is free with no signup.

The ATS doesn't know you built that distributed system. Your resume has to say so in its own language.

Inspired by https://resume.zoevera.com/ats-resume-tips-software-engineer

Why Your Resume Gets Rejected Before Anyone Reads It

AI Utilities — Sun, 12 Apr 2026 21:32:12 +0000

You spent hours on your resume. You tailored the bullet points, quantified your impact, and made sure every project had a strong
result. Then you applied to forty jobs and heard back from three.

It's not your experience. It's the filter between your resume and a human.

How ATS Works (And Why Engineers Underestimate It)

Applicant Tracking Systems — ATS — are the software gatekeepers that every major tech company uses to handle the volume of

applications they receive. At companies like Google, Amazon, or any mid-size SaaS startup, hundreds of people apply for a single
engineering role. ATS software scans each resume before a recruiter ever opens one, ranking candidates by keyword match and

filtering out anyone who falls below a threshold.

The problem is that ATS systems match literally. If the job posting says "Kubernetes" and your resume says "K8s," that's a miss.
If the job says "RESTful APIs" and you wrote "REST services," that's another miss. Small inconsistencies stack up — and the ATS
drops your resume before a hiring manager ever sees your name.

What Most Software Engineers Get Wrong

The most common mistake is treating the resume as a general document. A general resume might score 40–50% against a specific job
description. That rarely clears the threshold.

The engineers who consistently land interviews write targeted resumes. They read the job posting carefully, mirror the exact

language, and make sure every major skill from the posting appears somewhere in their resume — in context, not just as a keyword
dump.

The second mistake is formatting. Columns, tables, icons, and multi-section layouts break ATS parsers. The resume looks great as
a PDF but gets scrambled when the system tries to extract text from it. Plain single-column formatting is not boring — it's
smart.

The third mistake is omitting scope. "Built a CI/CD pipeline" is weaker than "Built a CI/CD pipeline using GitHub Actions,

reducing deployment time from 45 minutes to 8 minutes." ATS picks up on the tool names. Hiring managers remember the number.

How to Actually Fix It

The manual version of this process is tedious: read the job description, highlight every technical term, check your resume line
by line, rewrite bullets, repeat for every application. Most people skip it because it takes too long.

The faster version is to use an AI resume tool that does this analysis automatically. Paste your resume and the job description,
and within seconds you get a match score, a list of keywords you're missing, and a rewritten version of your resume with those
gaps filled in.

Resume Match Bot at resume.zoevera.com does exactly this. It scans your resume against any software engineering job posting,

shows you the keywords that are costing you interviews, and generates an ATS-optimized version you can download and submit
immediately. The initial analysis is free — no account required.

The Bottom Line

The engineering job market is competitive, but the gap between a resume that gets filtered out and one that lands interviews is
often smaller than people think. It's not about rewriting your whole career story. It's about making sure the right words appear
in the right places — so the system passes you through to the human who can actually say yes.

Check your resume match score free at https://resume.zoevera.com/why-resume-not-getting-interviews — paste your resume and any job description to see your score in under
30 seconds.