DEV Community: 思源

I built a Chrome extension to stop getting lost in 11,000 startups with real revenue

思源 — Mon, 28 Sep 2026 13:38:21 +0000

I spend a lot of evenings on TrustMRR looking for my next thing to build. It lists 11,000+ startups with verified revenue, which is exactly what you want when you're hunting for ideas that already make money.

It's also exactly how you lose an evening.

After a week I had three problems:

I couldn't remember what I'd already looked at. Every visit I scrolled past the same cards and re-read them.
I couldn't tell why a boring tool makes $3k a month. The card says MRR and a one-line description. It doesn't say who pays, why they pay, or where the customers come from.
The filters didn't stick, and I couldn't exclude categories. I never want to see mobile apps, but I can only pick categories to include, not hide the ones I don't want.

So I built a small Chrome extension for myself. It's called IdeaPanner (pan as in panning for gold).

What it does

Mark every card. Hover a startup and you get ✕ Pass · ☆ Later · ◎ Dig in · ✎ Note. Passed startups can be hidden on your next visit, so you only see what's new. The same buttons now also sit under the description on a startup's own page.

Explain. Click ? Explain and an AI writes a plain-language breakdown: what's going on in that market, what hurts, how the product makes money, where its customers come from, whether a solo founder could build it, and where you'd start if you copied it. It reads the startup's public TrustMRR profile, not just the card, so the answer is grounded in the actual numbers.

My list and Compare. Your Later / Dig in startups open in one panel with revenue, your note and the explanation side by side. Switch to Compare and they line up in a table: MRR now, pricing, customer channels, verdict, where to start. It also remembers the MRR on the day you marked something, so you can see what grew since.

Hide categories. Pick Mobile Apps (or anything else) and those cards disappear, and stay gone after a refresh.

Saved filters. Set up TrustMRR's filters once, save them under a name, restore them with one click.

A few things I learned building it

The site is a React app that re-renders a lot. My toolbar kept vanishing after hydration, and some pages use invisible 0×0 links laid over the visible card. The fix was to attach buttons to the visible card instead of the link, and re-attach whenever the page redraws.
Detail pages ship two layouts (mobile and desktop, one hidden with CSS). My first version happily inserted its buttons into the hidden one. Only pick elements that are actually rendered.
Free AI without a server is hard. Asking every new user to go get an API key kills the first click. The new version gives 10 free explanations a day through a tiny endpoint, and falls back to "add your own key" instead of a scary network error if that endpoint is down. Bring your own key (any OpenAI-compatible API) and requests go straight from your browser to that API.

Privacy

Marks, notes and filters live in your browser. No account, no analytics. The free trial sends the startup's public info to my server, which forwards it to the AI provider; it also sees a random install ID and your IP, used only for the daily limit. It only runs on trustmrr.com, and it's not affiliated with TrustMRR.

Try it

It's free: IdeaPanner on the Chrome Web Store. The version with Explain, Compare and Hide categories is in store review right now, so depending on when you read this you might still get the simpler first version.

If you browse TrustMRR too, I'd love to know what you filter on and what you wish the cards told you.

The Career-Change Resume Advice That Quietly Breaks ATS Parsing

思源 — Sun, 27 Sep 2026 07:44:04 +0000

Two sets of advice, both mainstream, both correct in their own lane, and almost nobody reads them on the same day. Here is what actually happens when you follow the first one.

If you search for how to format a career-change resume, the answer comes back fast and it is remarkably consistent: use a functional or hybrid format. Lead with a skills section. Push employment history down, because your old job titles are working against you. Indeed says it, ResumeGenius says it, half the career-change template libraries are built around it.

If you search instead for how to format a resume to pass an ATS, you get the opposite: single column, standard section headings, reverse-chronological, dates on everything. Functional resumes get named specifically as a parsing risk.

This contradiction is not a secret — Jobscan publishes articles on both sides of it. What is genuinely broken is the reader's path. Somebody changing careers searches career change resume format, gets the functional answer, downloads a template, and is done. There is no reason for them to go and search ats resume format afterwards. The conflict is real, it is documented, and it is completely invisible from where they are standing.

So rather than quote either side, we built both versions of the same resume and ran them through our own parser.

The test

One fictional career changer: a high school science teacher moving into corporate L&D. Seven achievement bullets, each with real numbers in it. Then four documents containing the same seven bullets, word for word:

A — reverse-chronological. Standard: summary, WORK EXPERIENCE with two roles and date ranges, education, skills list.
B — functional. The textbook career-change build: the same bullets regrouped under three skill headings at the top, then a WORK HISTORY section listing the two employers with no dates.
C — functional, with two fixes. Identical to B, except the section is renamed WORK EXPERIENCE and the date ranges are put back next to each employer. Skills still lead the page.
D — functional, poured into a two-column template. The same content as B, laid out with a skills sidebar — which is what most downloadable career-change templates actually look like.

Scores from our ATS checker, run with no job description attached so nothing but structure is being measured:

Same seven bullets, four layouts

Before: A — reverse-chronological: 100
B — functional: 93
D — functional, two-column template: 83

After: C — functional with standard heading + dates restored: 100

The headline number says the mainstream career-change advice costs 7 points. The more useful number is C.

Skills-first is not the problem

This is the finding we did not expect, and it changes the advice. Version C leads with skills exactly the way every career-change guide tells you to, and it scores the same as the plain reverse-chronological resume: 100.

The entire 7-point gap in version B came from two checks, neither of which has anything to do with putting skills at the top:

The section heading. B calls it WORK HISTORY. The parser looks for a recognised employment heading — Work Experience, Professional Experience, Employment — and Work History was not on the list, so the check came back warn: missing experience section. A resume with two jobs on it registered as having no employment section at all.
The dates. A had 4 parseable date ranges; B had 2, and both of those were on the education entries. The job entries had none, because dropping them is the whole point of a functional layout. That is the field a system uses to compute how long you have worked.

Put the heading back and put the dates back, and the penalty disappears without moving the skills section. The advice is not wrong about what to emphasise. It is wrong about what you have to give up to emphasise it.

What this test can and cannot prove

Our checker is a deterministic rule engine reading plain text — it verifies the things that are checkable as text facts: can the contact details be found, do the section headings match known names, are the date ranges in a parseable form, is the layout single-column. What it cannot tell you is whether a commercial parser correctly attributes a given bullet to a given employer. In a functional resume the achievements sit under Leadership rather than under a job, so the link between the accomplishment and where it happened is gone from the document itself — no parser can recover information that was never written down. That is the strongest claim you'll see made about functional resumes, and it is the one part of this we could not measure first-hand. Treat it as reasoning, not as a number.

The two-column template is the bigger loss

Version D is byte-for-byte the same text as B — only the layout changed — and it scored 83. One check drove the whole difference: 26% of the lines registered as multi-column, a hard fail. So the sidebar on its own costs 10 points, more than the functional structure's 7.

This matters because of how career-change advice gets delivered in practice. The article says "use a hybrid format," and immediately below it there is a template gallery. The templates are designed to make a skills sidebar look good on a page. When that file is converted to text, the sidebar and the main column interleave, and the tidy visual grid becomes lines with two unrelated fragments stuck together.

You are not choosing a format at that point. You are choosing a layout that happens to carry a format with it, and the layout costs more than the format does.

What to do instead: a format that satisfies both sets of advice

The two camps only conflict if you accept the template's version of "functional." Build it by hand and you can take the emphasis without the parsing cost. Five rules, all verified above:

Single column. No exceptions. No sidebars, no tables, no text boxes, no two-column skills grid. This is the largest single penalty in the test and the easiest to avoid.
Lead with a skills or core-competencies section if you want to. It costs nothing measurable. For a career changer it is genuinely the right call, because the first thing a reader sees should not be a job title from an industry they are not hiring for.
Keep a real employment section, and call it Work Experience. Not Work History, not Career Journey, not Where I've Been. The heading is how a parser finds the block at all; a creative one costs you the entire section.
Put date ranges on every role, in a boring format: Aug 2019 - Present, 2018 - 2019. Gaps are a smaller problem than being unreadable. A gap gets asked about in a conversation; an unparseable work history doesn't get to one.
Keep at least one or two achievement bullets under each job, even if your best material is grouped up top. This is what preserves the link between the accomplishment and the employer — the thing a purely functional layout throws away.

That document is what most guides mean by "hybrid," but the name is doing a lot of work and the templates sold under it frequently violate rules 1, 3 and 4. Build it from the rules, not from the label.

The part the format cannot fix

Formatting is the cheap half of a career-change resume and it is where the advice piles up, probably because it is easy to write about. The expensive half is that your bullets are written in the vocabulary of the industry you are leaving.

Teacher moving into corporate L&D

Before: Designed a year-long chemistry curriculum adopted by 46 teachers across 9 schools.

After: Built a year-long training program adopted by 46 instructors across 9 sites, replacing three separate legacy programs.

Same fact, same numbers, nothing invented — only the nouns changed to ones the hiring side searches for. No format decision does this for you, and a beautifully parseable resume in the wrong vocabulary still loses. The step-by-step version of this rewrite is a separate procedure, and what to actually put on a career-change resume covers the content side.

One thing not to do while translating: do not translate the numbers. "46 teachers" becoming "46 instructors" is fine. "46" becoming "50+" is not.

Check yours in two minutes

The four checks that produced every point of difference above are ones you can run on your own file right now: is the employment heading a standard one, does every role carry a parseable date range, is the layout genuinely single-column, and can the parser find your contact details.

Paste your resume text and see the same report we ran here — section headings, date ranges, column layout, contact details, and keyword coverage against a posting. No sign-up, nothing uploaded, it runs in your browser. Run a free ATS check

There is also a low-tech version that costs nothing: open your resume, select all, copy, and paste it into a plain text editor. What you see is roughly what the parser sees. If the skills sidebar has merged into your job descriptions, or your dates have wandered off from the roles they belong to, you have found your problem without needing a score at all.

One caution on scores in general, including ours: a high number means the machine can read what you are claiming. It does not mean the claim is strong. Our functional version and our chronological version had identical 73% keyword coverage against the same job posting — because they contain the same words. Structure decides whether you get read. It does not decide whether you get hired. Most rejections attributed to the ATS are parsing failures, and that is exactly the part this is worth fixing for.

FAQ

What is the best resume format for a career change?

A single-column resume that opens with a skills or core-competencies section and still keeps a dated, reverse-chronological employment section below it. In our test that structure scored the same as a plain chronological resume — 100 — so you get the emphasis for free. What costs you is the version that renames the employment section and drops the dates, which scored 93, and the two-column template, which scored 83.

Do ATS systems actually reject functional resumes?

An ATS does not reject anything; it parses your resume into database fields that a recruiter then searches and reads. A functional resume does not get thrown out — it gets stored with a weaker employment record, because the dates and the achievement-to-employer links were never in the document. The practical risk is a recruiter opening a profile where the work history looks thin or undated, which is also why recruiters report finding the format suspicious.

Should I use a hybrid or combination resume format?

Yes, if "hybrid" means skills at the top plus a complete dated employment section underneath. That is the version that passed every check in our test. Be careful with templates sold under the label: many of them ship a two-column layout and an undated work-history block, which are precisely the two things that cost points.

Will leaving dates off hide my career gap?

It hides it from a human skim for about ten seconds, and it does not hide it from anyone who is looking, because a missing timeline is itself the signal. Meanwhile it removes a field the system uses to compute your years of experience. A gap you can explain in one sentence is a much smaller problem than a work history nothing can date.

Is a two-column resume bad for ATS?

It is the single most expensive formatting choice we measured. Holding the text constant and only moving the skills into a sidebar cost 10 points, against 7 for the functional structure itself; together they took a 100 down to 83. The failure mode is mechanical: when the file is converted to text, the sidebar and the main column interleave line by line, so unrelated fragments end up on the same line. Copy your own resume into a plain text editor and you will see it immediately.

How many pages should a career-change resume be?

The same as any other resume — one page under roughly ten years of experience, two beyond that. Career changers sometimes stretch to two pages to make room for the extra skills section, which is the wrong trade: the fix is cutting bullets from the industry you are leaving, not adding length. The one-page versus two-page question goes into where the line actually sits.

Originally published on ResuHive.

We Ran 6 Popular Open-Source Resume Templates Through an ATS Parser. One Lost Every Digit.

思源 — Fri, 25 Sep 2026 07:08:30 +0000

The usual advice is that two columns break ATS parsing. We measured it instead of repeating it, and that is not what broke.

Almost every resume guide tells you the same two things: never use two columns, and never let a parser see anything fancy. Both claims get repeated far more often than they get tested. So we took six open-source resume templates — the ones developers actually fork on GitHub — and pushed each one through the same PDF text extraction that runs when someone uploads a resume to this site.

The result contradicted the advice. Two columns parsed fine. Character encoding is what destroyed a resume.

What we tested, and how

Six PDFs, all from repositories with an explicit open-source licence. Text was extracted with the same library and the same call the site's uploader uses — not a better parser picked to make a point, because that measures the parser instead of the template. The extracted text then went through the same rule set behind our free ATS check.

Finding 1: one template loses every single digit

The Chinese edition of Deedy produced 1,709 characters of extracted text containing zero Arabic numerals. Not a low count — none. Every other file in the set returned between 69 and 453.

What that means in practice is that a parser reading this resume sees no graduation years, no employment dates, no metrics. The text comes out looking like this:

Lines as the parser actually received them

.-. where a date range should be · (总计万访客，万阅读量) · (+ 关注者) · 超过⾏ — the gaps are where digits were. These are copied verbatim from the extraction; we are not reconstructing what the original numbers were, only showing that they are gone.

The numbers are visibly there when you open the PDF. They simply are not in the text layer, so anything reading the file programmatically never receives them. Every quantified achievement in that resume — the exact thing every guide tells you to add — is invisible to the machine.

Finding 2: the same file mangles its own Chinese characters

Sixty-nine characters in that same extraction are not the characters they appear to be. They are Kangxi radicals — a separate Unicode block that renders almost identically but is a different code point. The candidate's surname comes out as ⾼ (U+2F98, a radical) rather than 高 (U+9AD8, the character). 工程 comes out as ⼯程.

Why this matters more than it looks

Keyword matching is exact-match at this level. A recruiter searching their system for 软件工程 will not match a resume that technically says ⼯程. The resume looks perfect to a human and is invisible to a search.

Finding 3: two columns did not break anything

This is the part that contradicts the standard advice. The English Deedy template is a narrow-left, wide-right two-column layout, and it passed every layout-related check: email extracted, phone extracted, contact details found in the opening lines, and zero lines flagged as scrambled column bleed.

The two-column warning is not baseless — columns implemented as untagged tables or text boxes genuinely do interleave when flattened to text. But a two-column layout is not automatically that. What we measured says the failure mode lives in how the file encodes text, not in how many columns you can see.

One result we threw out

The run initially flagged the zheyuye template for a missing phone number. It is not a defect. That template ships 13xxx-xxx-xxx as a deliberate placeholder in its sample content — there is no phone number to find. Reporting it as a template flaw would have meant counting someone's placeholder as a bug, so it is excluded from the conclusions.

We are mentioning a discarded result on purpose. A measurement you can only see the successful half of is not a measurement.

What to actually do about it

Open your own PDF and select the text with your cursor, then paste it somewhere plain. What lands in the clipboard is roughly what a parser receives.
Check the numbers specifically. Dates and metrics are the first things to disappear, and they are the hardest to notice missing.
If your characters or digits vanish, the fix is the font embedding, not the layout. Re-export with fonts fully embedded, or switch the export path entirely.
Do not rebuild a two-column resume into one column on the strength of the columns alone. Test it first — it may already be fine.

Reproducing this

The measurement script is in the repository as scripts/ats-template-audit.ts, and the source, licence and commit of every template is recorded alongside the files. Run it and you should get this table back. If you do not, this article is out of date and the script is right.

Want to see what a parser gets from your own resume? — Run the free ATS check

Originally published at resuhive.com.

Nursing Cover Letter: What Nurse Managers Actually Read

思源 — Thu, 24 Sep 2026 00:54:16 +0000

A nursing cover letter is not read the way a general one is. It usually passes a recruiter screening for license and certifications first, and only then reaches a nurse manager who is staffing a specific unit on specific shifts.

Most advice for nursing cover letters is the same advice given to everyone else with the word nurse inserted. It tells you to show passion for patient care, which every applicant does, and skips the three things that decide whether your letter gets past the first screen.

Those three things are credentials, unit fit and availability. They are concrete, they are checkable, and they are the reason a nursing letter is structurally different from a marketing one.

Two readers, in this order

Understanding the sequence explains almost every rule below.

Reader	Spends	Checking for
Recruiter / HR screen	Under a minute	Active license and state, required certifications, experience in the posted specialty, shift and start date
Nurse manager	Longer, if you survive	Whether you can carry the unit's patient load, how you behave in a specific clinical situation, whether you will still be there in a year

Who reads a nursing application, in what order, and what each one is checking for.

The recruiter is not evaluating your writing. They are matching fields. If your RN license, your specialty and your availability are not findable in a few seconds, the letter fails at a stage that has nothing to do with how well it is written.

Put the credentials above the fold

Licenses and certifications belong in the first four lines, not in a closing paragraph and not only on the resume. The screen that reads for them often does not open the resume first.

The opening: name the unit, not the hospital

"I am excited to apply for a nursing position at your hospital" tells the reader nothing they did not already know, and it reads identically to the other two hundred letters in the queue.

Opening lines

❌ I am writing to express my strong interest in the Registered Nurse position at your esteemed hospital. I am a compassionate and dedicated nurse with a passion for patient care.

✅ RN, licensed in Ohio (compact), BLS and ACLS current, two years on a 32-bed med-surg floor at a 1:6 ratio. I am applying for the night-shift RN opening on your step-down unit and can start within three weeks of an offer.

The second version is not warmer. It answers, in one sentence, every field the recruiter screen is looking for — and it does it before the reader has decided whether to keep reading.

Note what it does not say: nothing about compassion, dedication or a lifelong calling. Those claims are unfalsifiable and every applicant makes them, so they carry no information. The specifics do the work those adjectives were trying to do.

Ratios and acuity are the most underused detail in nursing letters

"Two years of med-surg experience" could describe wildly different jobs. A nurse manager reads it and still does not know whether you can handle their floor.

Patient ratio — 1:4 and 1:8 are different professions on a bad night
Unit size and type — 32-bed med-surg, 12-bed ICU, 20-bed step-down
Acuity — trauma level, vent-dependent patients, post-op day one, telemetry
Charge or preceptor time — even a few shifts counts, and almost nobody mentions it
EHR — Epic, Cerner and Meditech are a real onboarding cost, and naming yours removes it

Generic experience → readable experience

❌ I have extensive experience providing high-quality care to a diverse patient population in a fast-paced environment.

✅ On a 32-bed med-surg floor at 1:6, I carried a full assignment of post-op day-one and telemetry patients, precepted four new grads over eighteen months, and charted in Epic.

"Fast-paced environment" is what people write when they have not translated the job into numbers. The numbers are already in your head — the unit size, the ratio, the shift. Write those down and the paragraph writes itself.

If you are a new graduate nurse

The most common mistake in a new grad nursing cover letter is apologising for the thing that is not actually missing. You have clinical hours. They were supervised, they were real patients, and most new grads describe them as if they were observation.

Name the rotations by unit and hours. "Nine weeks on a 24-bed med-surg unit, 180 clinical hours" is evidence. "Completed clinical rotations" is not.
Pick one patient situation and describe what you did. Not the outcome — what you did, in order. This is the paragraph a nurse manager remembers.
State your NCLEX status honestly and precisely. "NCLEX-RN scheduled for 14 October" is far better than silence, which reads as not yet passed and not willing to say so.
Say which unit you want and why, in clinical terms. "I want to start in med-surg because I want the assessment reps before specialising" shows judgement. "I am open to any unit" shows none.

Externships and tech hours count

If you worked as a PCT, CNA or nurse extern, that is paid clinical experience in a real unit — put it in the letter. New grads routinely leave it out because it was not an RN role, which is exactly backwards: it is the part that proves you can do the work at 3am.

Availability is a qualification, and most letters omit it

Hospital postings exist because a specific hole in a schedule needs filling. A letter that does not mention shift, weekend availability or start date forces the recruiter to find out by phone — and with a stack of applications, the ones that already answered get called first.

One sentence near the end is enough: shift you are applying for, weekend and holiday availability if the posting asks, and the earliest date you could start after credentialing.

The formatting part that quietly loses letters

Large hospital systems run applications through Workday, Taleo or iCIMS. Two consequences follow, and both are avoidable.

The letter is often pasted into a plain text box, not uploaded. Anything that depends on layout — columns, a header block, a table of certifications — collapses. Write it so it survives as plain text.
Credentials get parsed as strings. Write them the way the posting writes them. If the posting says BLS, do not write Basic Life Support only; include the abbreviation the system is matching against.

This is the same class of quiet failure covered in why ATS filters your resume — the document looks perfect on your screen and arrives as something else.

A structure that works

Line 1–2: license and state, key certifications, years and specialty, the exact role you are applying for.
Paragraph 2: the unit you worked on in numbers — size, ratio, acuity, EHR — and one thing you did that a manager would recognise.
Paragraph 3: why this unit at this hospital, in clinical terms. One specific fact about them that is not from the homepage banner.
Closing: shift, availability, start date. Then stop.

One page. If you are padding, the letter is not too short — it is missing numbers, and padding will not supply them.

Common questions

Do nursing jobs even require a cover letter?

Often it is optional. Write one when the posting asks, when you are a new grad, when you are changing specialty, or when something on your resume needs one sentence of context — a gap, a relocation, a short stay. If you would only be restating the resume, skipping it costs little.

How long should a nursing cover letter be?

Three or four short paragraphs, well under one page. The recruiter screen is under a minute and the nurse manager is reading between shifts.

Should I mention why I left my last unit?

Only if the resume raises the question — a stay under a year, or a gap. One neutral clause is enough. Do not explain at length, and do not criticise the previous employer; in nursing, the manager reading your letter may well know them.

Is it different for travel or agency roles?

The weighting changes. Licensure across states, the speed you can be credentialed, and how fast you take a full assignment with no orientation matter more than long-term fit. Lead with the compact license and the shortest realistic start date.

What about other healthcare roles?

The credential-first structure holds across clinical hiring, but the specifics differ — see healthcare cover letters for medical assistant, allied health and non-nursing clinical roles.

Cover Letter vs Resume: What Each One Is Allowed to Say

思源 — Wed, 23 Sep 2026 11:07:45 +0000

Most explanations of this difference stop at "a resume is a list and a cover letter is a narrative," which is true and completely useless when you are staring at a blank page.

The useful version of the distinction is about what each document is allowed to claim. A resume can only state what happened. A cover letter is the one place you can say why it happened, or why the obvious reading of your resume is wrong.

That is why a letter which simply restates the resume in sentences is worse than no letter: it spends the reader's attention on information they already had, and it uses up the only slot where the resume's open questions could have been answered.

The actual division of labour

	Resume	Cover letter
Answers	What you have done	Why it adds up to this job
Read by	A parser first, then a human scanning	A human, only if they are already interested
Tense of the claim	Past and factual	Past facts used to support a forward-looking claim
Can explain a gap?	No — it can only show one	Yes, in one sentence
Can say what you want next?	Only through a summary line	Yes, and it is the main reason to write one
Length	One to two pages	Three or four short paragraphs
Optional?	Never	Often — and that is fine

What each document can and cannot do. The right-hand column is where most applicants lose the letter.

The one-sentence test

If every sentence in your cover letter could be deleted without the reader losing anything they could not get from the resume, the letter is not doing its job. That is not a style problem — it means the letter has no content of its own.

What only the cover letter can do

There are exactly four jobs. A letter that does none of them is the kind that gets skipped.

Explain a choice the resume can only show. A gap, a short stay, a relocation, a step down in title, a switch of field. The resume makes the reader guess; one neutral sentence removes the guess.
Connect two things that do not look connected. Your last job and this posting, when the titles do not match. This is the whole job of a career-change letter.
Show judgement about their problem. One specific, non-obvious observation about the role or the company, and what you would do about it. This cannot exist on a resume.
State what you want next. A resume implies direction; a letter can say it outright, which matters most when your history points somewhere else.

Restating vs adding

❌ As you can see from my resume, I have five years of experience in digital marketing, where I managed campaigns and analysed performance data.

✅ My last two years were mostly paid acquisition, which is not what this role is. The reason I am applying anyway: the retention work in your posting is what I moved into at Brightline in March, and it is the part I want to keep doing.

The first sentence is a link to the resume. The second is information the resume could not carry — and it answers the question the reader was about to ask.

CV vs cover letter (and CV vs resume)

Two different questions get tangled here, so take them separately.

CV vs cover letter — these are not alternatives. The CV is the record of what you have done; the cover letter is the argument. You may be asked for both, and if so they are doing the two different jobs described above.
CV vs resume — this one is regional. In the UK, Ireland, most of Europe, Australia, New Zealand, India and much of Africa, "CV" simply means what Americans call a resume: one to two pages, tailored. In the US and Canada, a CV is a long academic record — publications, grants, teaching, conference talks — used for academic, research and some medical roles, and it is not length-limited.

Write what the posting calls it

If a US posting asks for a CV and the role is not academic, it almost always means a resume. Send the tailored one-to-two-page document, and do not send a fifteen-page publication list to a software company because the form said CV.

When you genuinely do not need a letter

The honest answer is: more often than the internet admits. Skip it when all of the following are true.

The posting says optional, or there is no field for it
Your resume already matches the posting closely, with no gap or switch to explain
You have nothing specific to say about this employer that is not on their homepage

In that situation a letter would be filler, and filler is a weak signal, not a neutral one. Conversely, write one whenever the resume raises a question you would rather answer than have guessed at — that is the single most reliable rule in this whole comparison.

If you write both, do not let them repeat

The most common failure is not contradiction — it is duplication. A practical sequence that prevents it:

Finish the resume first, tailored to the posting.
Read it as a stranger and write down the questions it raises. Usually there are one or two, and they are obvious.
Write the letter to answer those, plus one observation about the employer.
Delete every sentence in the letter whose content is already on the resume. If the letter survives at three paragraphs, it was worth sending.

Step four is where the value is. It also explains why the phrases everyone uses — "as you can see from my resume," "I am confident I would be a great fit" — are the first to go: see the nine cover letter phrases to replace.

Common questions

Should the cover letter repeat my resume's keywords?

Some overlap is natural and fine, because both documents are about the same job. Deliberately stuffing the letter with keywords is not worth it — the letter is usually read by a person after the resume has already passed the parsing stage, which is where keywords actually matter. That stage is covered in why ATS filters your resume.

Which one do recruiters read first?

The resume, in almost every case, and often the letter never gets opened at all. That is an argument for making the letter short and front-loaded, not for skipping it when it has something to say.

Can the cover letter be in the email body?

Yes, and when you are emailing a person directly it is usually better — an attachment is one more click. Keep the resume as an attachment. If you are applying through a portal, follow the form.

Does a cover letter help if the job has hundreds of applicants?

It helps less at the screening stage, where volume forces field-matching, and more at the shortlist stage, where a human is choosing between candidates who all look similar on paper. That is precisely when "why this job, and what I would do about your problem" is the deciding information.

Why does your resume keep getting filtered by ATS? 5 common reasons

思源 — Tue, 22 Sep 2026 13:56:36 +0000

An applicant tracking system is not a robot deciding whether you're good enough. It's a database with a search box. Once you understand that, most "ATS tricks" stop being mysterious.

Almost every mid-size and large employer runs applications through an applicant tracking system (ATS) — Greenhouse, Lever, Workday, Taleo, and so on. A lot of advice online treats these systems as an AI gatekeeper that scores you out of 100 and bins you if you fall short. That is not really how they work, and believing it leads people to do strange things, like stuffing white keyword text into the margins.

What an ATS actually does is more boring and more fixable: it parses your file into structured fields — name, employer, title, dates, skills — and stores them so a recruiter can search and filter. When your resume gets "filtered out," it usually means one of two things happened. Either the parse went wrong and your experience never made it into the database correctly, or it parsed fine but you didn't use the words the recruiter searched for.

1. Your layout confuses the parser

This is the single most common technical failure, and it is invisible to you. Your resume looks perfect in a PDF viewer. The parser sees something else entirely.

The usual culprits:

Text inside images. A resume exported as an image, or with your name in a graphic header, parses as an empty document.
Tables used for layout. Some parsers read tables cell by cell in the wrong order, interleaving your job titles with your dates.
Text boxes and multi-column layouts. A two-column design can parse as one scrambled column, mixing your skills list into the middle of a job description.
Headers and footers. Contact details placed in the actual header/footer region of a document are sometimes skipped entirely — which is how people end up with no phone number in the system.
Uncommon fonts or heavy glyph substitution, which can turn accented characters and bullets into question marks.

How to check this yourself in 30 seconds

Open your resume PDF, select all the text, copy it, and paste it into a plain text editor. What you see is roughly what the parser sees. If sections are out of order, words are glued together, or your contact line has vanished, that is your problem — and no amount of keyword tuning will fix it.

2. Your section headings are creative

Parsers look for conventional headings to decide where one section ends and the next begins. "Where I've Worked" and "My Journey" read nicely to a human and mean nothing to a parser expecting Experience, Education, or Skills.

This one costs you a lot for very little creative upside. Use standard headings. Spend your originality on the content underneath them.

3. Your dates and titles are formatted inconsistently

Employment dates are one of the fields recruiters filter on most often — years of experience, current employment, gaps. If your date formats vary between entries ("2021-2023" in one, "March 2021 – Present" in another, "'21–'23" in a third), some entries will parse and others won't.

Pick one format and use it everywhere. Mar 2021 – Present is unambiguous and parses reliably. Same principle for job titles: put the title and the employer on their own clearly separated lines, not merged into a single sentence.

4. You're missing the words the recruiter is searching for

This is the real "keyword" issue, and it's less sinister than it sounds. A recruiter filling a Kubernetes role searches for "Kubernetes." If your resume says "container orchestration" but never the product name, you don't appear in that search. You weren't rejected — you were never retrieved.

The fix is not to paste the job description into your resume. It's to check whether the specific nouns in the posting — tools, platforms, certifications, methodologies — appear anywhere in your resume in a way that's actually true of you.

Same experience, different retrievability

❌ Managed our container infrastructure and deployment pipeline, improving release reliability.

✅ Managed Kubernetes infrastructure and the CI/CD pipeline (Jenkins, Docker), cutting failed releases by [X%].

Note what changed and what didn't. The work is identical. The second version just names the tools, which makes it findable — and adds a metric slot, which makes it persuasive to the human who eventually reads it.

Don't fake it

Only add a keyword if you can defend it in an interview. Listing a technology you've never touched gets you retrieved into a conversation you will immediately lose. Keyword coverage is about not under-selling what you did do, not about claiming what you didn't.

5. You're applying with one resume for everything

A generic resume is optimized for no particular search. If you're applying to backend roles, data engineering roles, and platform roles with the same document, it is probably a weak match for all three, because each of those recruiters is filtering on a different vocabulary.

You don't need to rewrite from scratch each time. In practice, tailoring means: adjust the summary line to name the target role, reorder your skills so the relevant ones lead, and make sure the two or three central nouns from the posting appear in your experience bullets where they're genuinely true.

Paste a job description and your resume to see which of its keywords you're actually covering — and which ones you're missing.

What actually matters, in order

If you only fix a few things, fix them in this order:

Make sure it parses. Do the copy-paste test. A beautiful resume that parses as gibberish is worth less than a plain one that parses cleanly.
Use standard section headings and consistent date formats. Cheap to fix, disproportionately costly to get wrong.
Name the specific tools and terms from the posting that are genuinely true of you.
Then, and only then, worry about design. Once it parses correctly, a clean single-column layout is enough. Nobody has ever been hired because of a resume's colour scheme.

One thing ATS advice usually gets wrong

You'll see claims that ATS systems auto-reject the overwhelming majority of resumes with a specific score. Treat those numbers with suspicion — they're widely repeated and rarely sourced, and different systems behave very differently. Some knock out applications on hard requirements like work authorisation. Many do no automatic rejection at all and simply rank and filter for a human.

The practical takeaway doesn't change either way: your resume needs to survive parsing and show up in the right searches. Both are within your control, and neither requires gaming anything.

The 60-second self-introduction that actually works

思源 — Fri, 18 Sep 2026 06:12:01 +0000

It is the only interview question you can be certain you'll be asked. Most people answer it by narrating their resume from the top, which throws away the one moment where you get to choose what the conversation is about.

"Tell me about yourself" is not an information request. The interviewer has your resume open in the other window. They are not sitting there hoping to learn where you went to university.

What they're doing is three things at once: starting the conversation somewhere easy, checking whether you can explain your own work coherently, and listening for a reason to believe you fit this role. The third one is the part that's actually being scored, and it's the part most answers never touch.

There's a mechanical reason to take this seriously. Interviewers follow up on what you just said — it's the only material they have. Whatever you spend your opening minute on becomes the agenda for the next ten. Spend it on your dissertation and you will spend the next stretch discussing your dissertation. You are choosing the topic, so choose deliberately.

The structure: present → relevant past → why this role

Three beats, in this order. The order matters more than the wording, because it front-loads the thing the interviewer can use.

Present — about 15 seconds

Start with what you are now, in one sentence: current title, the kind of work, one detail of scope. Scope is what stops it being generic — "I'm a product designer" is a category, "I'm a product designer on a payments team, mostly working on the checkout flow" is a person.

If you're between jobs, frame it around what you do, not what you're missing. "I'm a supply chain analyst — I spent four years at a mid-size retailer and I'm looking for my next role" is complete. Do not apologise for a gap in your first sentence. You've handed the interviewer the objection before they'd even thought of it.

Relevant past — about 30 seconds

This is where the answer usually collapses, because people turn it into a chronology. It is not a chronology. It's a selection. Pick one or two things from your history that make the case for this particular job and skip everything else — including things you're proud of, including your longest role if it isn't the relevant one.

The test for each sentence: if the interviewer replied "and that matters here because…?", do you have an answer? If not, cut the sentence. You have about four sentences total, so each one has to be earning its place.

Why this role — about 15 seconds

Close by connecting your past to their opening, out loud and explicitly. This is the sentence most candidates leave out, apparently assuming the connection is obvious. It isn't, and an interviewer who has to construct your argument for you often doesn't bother.

One clause of real specificity does more here than a paragraph of enthusiasm. "You're building the analytics function out from scratch, and that early stage was the part I liked most in my last role" says something. "I've always admired your company's innovative culture" says you read the homepage.

The first sentence sets the agenda

❌ So, I grew up in Manchester, did my A-levels there, then went to university in Leeds and studied business, and after graduating I wasn't really sure what I wanted to do, so…

✅ I'm an operations analyst — for the last three years I've worked on demand forecasting, which is the part of this role that made me apply.

On length

Don't estimate this from the page — read your draft aloud with a timer and find out how long your own version of a minute is. Almost everyone runs longer out loud than they expect, because you add words in the room that aren't in the draft. Write to about 70 seconds in practice and you'll land near 60 in the interview.

Worked example 1: changing industries

Situation: eight years in retail operations, applying for an operations manager role at a logistics software company. The risk is being filed as "retail person" in the first ten seconds and never getting out of that box.

I've spent the last eight years in retail operations — most recently I ran fulfilment for a 40-store chain, so I owned inventory accuracy, the warehouse team, and the systems connecting the two. The part I ended up specialising in was software rollouts. We replaced our warehouse management system two years ago and I led the pilot, the training and the cutover across all 40 sites, which took [X months] and touched every person in the operation.

That project is genuinely why I'm sitting here. I spent it on calls with the vendor's implementation team thinking I'd rather be on their side of the table — the problems were more interesting, and I could see where the product was making our lives harder in ways their team couldn't see from the outside. So I'm looking to move into logistics software in a role where the operational background is an asset rather than something I'm leaving behind. That's what caught my eye about this one: you're hiring an ops manager who has actually run a warehouse, not just built software for one.

Look at what the structure is doing. Eight years of retail get one sentence — enough to establish credibility, not enough to define him. The middle picks exactly one thread, the system rollout, because that thread is the bridge to the new industry. Everything else in eight years is left out.

The last section does two jobs. It names the fit explicitly instead of hoping the interviewer infers it, and it volunteers the motivation before anyone asks "so why are you leaving retail?" Answering the obvious objection on your own terms is much better than answering it defensively twenty minutes later.

Worked example 2: new graduate

Situation: final-year statistics student applying for a junior data analyst role at a healthcare company. The risk is that with nothing but coursework, the answer turns into a list of modules.

I finished a statistics degree in June, and the part I got most invested in was messy real-world data rather than clean problem sets. My final project was with the university's transport office — they had three years of bike-share data nobody had opened, and I built the cleaning pipeline and a dashboard showing which docking stations ran empty and when. They moved two stations this year based on it.

Alongside that I did a six-month part-time placement at a small insurance broker, which was mostly SQL and a lot of explaining numbers to people who don't like numbers — and it turned out I quite enjoy that second part. So I'm looking for a first analyst role somewhere the analysis actually gets used for something rather than filed. This one sits inside the clinical operations team rather than a central data function, which is specifically why I applied for it and not the general graduate scheme.

No module list. No grade. Two concrete things — one project, one placement — and both are described by what happened, not what was studied. "They moved two stations this year based on it" is worth more than any coursework summary, because it's an outcome outside the university.

The last sentence does something small and effective: it names a specific detail from the job posting. It's proof of attention that costs one clause and is very hard to fake.

Four ways this goes wrong

Reciting the resume top to bottom. They already have it. You're spending your best minute reading them a document they can read faster themselves, and chronology forces you to give your least relevant job the same airtime as your most relevant one.
Starting at birth. Hometown, school, degree, first job, second job. By the time you reach anything that bears on this role, the minute is gone and so is the interviewer's attention. Start from now and go backwards only as far as your argument needs.
Running four minutes. The most common failure by a distance. Nobody will interrupt you — they'll just stop listening, and you'll have spent your goodwill before question two. If you notice you're well past a minute, land the plane: finish the sentence, add your "why this role" line, stop. Silence afterwards is fine. Let them ask.
Rehearsing until it's recited. Memorising word for word gives you a flat delivery and no recovery path — lose your place and you have nothing. Learn the three beats and the two or three facts inside each, then say it aloud six or eight times, slightly differently every time.

There's a clean diagnostic for over-rehearsal: can you be interrupted? If a follow-up question halfway through derails you completely, you've memorised a speech instead of learning an argument. A good self-introduction survives being interrupted at any point, because you know what you're claiming and why.

💡 Shameless but relevant: we built a tool that generates a tailored self-introduction — plus the follow-up questions you're most likely to get — from your resume and the job description, so you can practise against the follow-ups instead of just the opener: Prepare for my interview →

Recruiter screen vs hiring manager

Same three beats, different emphasis, because the two people are trying to establish different things.

A recruiter is usually checking you against a shortlist of hard facts: level, location, notice period, salary range, and whether you can describe your work to someone who isn't in your field. So strip the jargon. No internal system names, no acronyms only your last company used. Say your level plainly, and make the "why this role" line about the job as advertised, since that's the version they know. If there's an obvious logistical question — you're relocating, you have a three-month notice period — answering it inside your minute saves everyone a round of email.

A hiring manager already knows the domain. They're listening for whether you think about the work the way their team does. This is where you go one layer deeper: name the actual tools, the actual scale, the specific hard problem you dealt with. Keep the present sentence shorter to buy room for it. And make the closing line about their team or product specifically rather than the company brand — you're now talking to the person who owns the problem.

If you've already given the story to two people at the same company, assume it was passed along. Don't repeat it verbatim in the final round; shift the emphasis to whatever the earlier conversations suggested they're unsure about.

Build yours in twenty minutes

Write the last sentence first — the "why this role" line. If you can't write it honestly, that's useful information about the application, not a writing problem.
Pick the one or two past items that support it. Everything else in your career comes out. This is the hard step and it's the whole exercise.
Write the present sentence: what you are now, the kind of work, one detail of scope.
Read it aloud with a timer. Cut until it lands under 70 seconds. Cut adverbs first, then whole sentences.
Say it once to another person. The parts you stumble over are usually the parts you don't quite believe, and those are the parts to rewrite.

Twenty minutes of work covers every interview you have this month, with only the final sentence swapped each time. It is the highest-return preparation available, precisely because it's the one question you know is coming.

This post was originally published on ResuHive.

How to Tailor a Resume to a Job Description in 20 Minutes

思源 — Wed, 16 Sep 2026 05:44:45 +0000

Most advice on this stops at "find the keywords and put them in," which is true, useless, and the reason people either burn an evening per application or give up and send the same file to everything.

Tailoring a resume means selecting and rewording experience you already have so it lines up with one posting's priorities. It is not writing a new resume, and it is not adding things you haven't done. Done properly it touches four parts of the document and leaves everything else alone — which is why it takes twenty minutes rather than an evening.

Below is the whole procedure, the part every other guide skips (what to do about a requirement you genuinely don't have), and a way to verify you actually hit the mark before you send it.

First you need a master resume

Never tailor from the last version you sent. Every pass deletes a bullet, and six applications later you are editing a resume that has quietly lost half your career. Keep one long file — every job, every bullet, every number, three pages, ugly — and cut a copy down for each application.

Building it costs an hour, once. Every tailoring pass after that is deleting and reordering instead of remembering.

Everything goes in, including the jobs and projects you would normally cut for length. You cannot select from material you never wrote down.
The numbers live here. Write down the real figures while you still remember them: headcount, budget, latency, churn, ticket volume, class size. Reconstructing them eighteen months later is how people end up guessing, and guessed numbers come apart in an interview.
Keep two or three phrasings of your strongest bullets. The same piece of work reads differently to a team hiring for delivery speed and a team hiring for reliability.

Step 1: Find the five things the posting is actually screening for (5 minutes)

Read the posting twice. You are looking for repetition and position, not for a complete inventory of nouns.

Anything that appears in both the responsibilities and the requirements sections. Those two lists are often written at different times by different people. Whatever survived both is the real job.
The first two bullets of each section. The order is rarely random — it usually reflects what the hiring manager said first when someone asked them what they needed.
Named things: tools, methods, certifications, systems, regulations. Looker, HIPAA, Kubernetes, SOC 2, QBRs. These are the words a recruiter types into the search box.
Required versus preferred. "Preferred" is negotiable and should not consume any of your four edits.
Write the five down on one line. If you cannot get to five, the posting is generic and there is nothing here to aim at — see the last section.

Most of the words in a job description are not keywords

When I built the keyword extractor behind our free ATS checker, the thing that decided whether the output was useful was not the matching — it was the discard list. Telling someone they are missing Kubernetes is something they can act on. Telling them they are missing experience, strong, proven, collaborate, solutions or senior makes the whole report look broken, and one line of noise is enough to make a reader distrust the rest of it. Real keywords tend to have a shape: an all-caps acronym (SQL, AWS), a name with punctuation in it (Node.js, CI/CD, C++), a capitalized proper noun sitting mid-sentence. Adjectives and abstract nouns almost never qualify.

Step 2: Change four things, and leave the rest alone

This is the step that turns an hour into twenty minutes. Four places carry nearly all of the signal:

The summary line at the top. Two sentences, rewritten to name the thing this posting is about. Highest-leverage edit in the document and it takes three minutes.
The skills list. Same skills, reordered so the ones the posting named come first — and the ones it never mentions fall off the end.
The top three bullets of your most relevant role. Not all of them. Three. People read down a page and stop.
The order of items inside each section. Projects, skills, bullets within a role: put the matching one first. Reordering costs nothing and changes what gets read.

Everything below is off limits, and keeping it off limits is what makes the twenty minutes possible:

Job titles, employers and dates. These get verified. Adjusting them is not tailoring.
The numbers. A metric that shifts to suit the posting was never a metric.
Anything you could not talk about for five minutes. If it survives onto the resume you have to defend it in the room.
The lower half of the page — education, certifications, the roles from eight years ago. Almost nobody's decision turns on them, and that is exactly where tailoring time goes to die.

Step 3: Rewrite the top bullets in their words, not yours

The facts stay identical. What changes is which fact leads and which verb carries it.

A posting that repeats "onboarding" and "renewals"

❌ Before: Managed 40 enterprise accounts, including escalations, quarterly business reviews, renewals and onboarding for new logos.

✅ After: Onboarded 40 enterprise accounts and owned their renewals; ran quarterly business reviews and handled escalations.

Nothing was invented. Onboarding and renewals were already in that sentence — they were third and fourth in a list of four, sitting behind two things this particular posting never mentions.

The summary line, before and after reading the posting

❌ Before: Results-driven customer success professional with 6 years of experience building strong relationships and driving growth.

✅ After: Customer success manager, 6 years in enterprise SaaS — most of it onboarding and renewing accounts in the 200-to-2,000-employee range.

The first version fits every customer success posting written this year, which is another way of saying it fits none of them. The second is harder to write and much harder to skim past.

One prerequisite: if the bullets are weak before you start — responsibilities rather than outcomes — fix that first. Tailoring a vague bullet produces a vague bullet with better vocabulary. The rules for writing achievements cover that step, and there are annotated resume examples if you would rather work backwards from a finished one.

What to do about a requirement you genuinely don't have

Every guide on this topic skips the case people are actually in. You have three honest options and one bad one.

Name the adjacent thing, concretely. They asked for Looker and you have Tableau. Write the Tableau line specifically enough that a human reads "this person builds dashboards" — because that is the thing being screened for, and the tool itself is a week of learning.
Handle the gap somewhere a person is reading. A cover letter or the first five minutes of a call is where a missing requirement gets discussed. A resume is a filter; the gap does not belong on it.
Decide it is a real gap and move on. If four of their five are missing, a better-worded resume is not the thing standing between you and the job.
❌ Listing it anyway. This is the one that gets people into rooms they cannot survive. Our own checker says it in one line under the keyword panel: only add what's true — keyword stuffing is easy to spot in an interview.

The posting asks for Looker; you have used Tableau

❌ Before: Proficient in Looker, Tableau, Power BI and SQL.

✅ After: SQL and Tableau — built and still maintain the weekly retention dashboard the sales team runs their pipeline reviews on.

The second version does not claim Looker. It makes the Looker requirement feel like a formality, which is the most you can honestly do with it.

Step 4: Check the coverage before you send

You have just spent twenty minutes editing on the basis of what you believe the posting emphasised. Re-reading your own resume is a bad way to verify that, because you already know what you meant by every line.

Put the posting and your resume text side by side and get the list of terms that appear in one and not the other. Treat coverage as a proofreading step, not a score.

Paste your resume text and the posting: you get keyword coverage, the specific terms you're missing, and whether a parser can even find your contact details and dates. No sign-up, nothing uploaded — it runs in your browser. — Run a free ATS check

What to do with the result: a missing term you genuinely have is an editing miss, so fix it. A missing term you do not have is information, not a task. And a high coverage number does not mean you are a strong candidate — it means the machine can tell what you are claiming. The reasons resumes get filtered are mostly parsing failures, not keyword failures, and no amount of tailoring fixes a resume the parser cannot read.

Using ChatGPT or Claude to tailor: one prompt, three failure modes

A large share of the searches around this topic now include "ChatGPT" or "prompt", and the honest answer is that a model is very good at one half of this job and dangerous at the other. It can read a posting faster and more evenly than you can. It cannot supply your facts.

The prompt that doesn't blow up

Paste the posting, then your resume, then this: Use only facts that appear in my resume. Do not add, infer or estimate anything. (1) List the requirements this posting repeats or puts first. (2) For each one, quote the line in my resume that already covers it. (3) List the requirements that nothing in my resume covers — do not write bullets for these. (4) Rewrite only the lines from step 2, keeping every number, date, title and employer exactly as written. Step 3 is what makes it worth running. It tells you where your real gaps are instead of papering over them, which is the opposite of what a model does when left to its own devices.

It invents numbers. Hand it a bullet with no figure in it and you will get back "improved efficiency by 30%". Nobody measured that. Delete every number you did not personally supply.
It edits things you did not ask it to touch. Titles get "clarified", dates get reformatted, an entire bullet quietly disappears. Compare the output against your master resume line by line rather than skimming it.
It over-matches. Tell it to use the posting's language and it will use all of the posting's language — three bullets in a row starting with the same verb, the company's internal jargon showing up in a job you held four years ago. That reads as a template, which is the thing you were trying to avoid.

It is the same boundary as using AI on a cover letter: a capable editor and an unreliable witness.

When not to bother

Tailoring every application is a comfortable way to feel productive while applying to jobs you will not get. Three cases where the hour is better spent elsewhere:

The posting is generic. No named tools, no specifics, responsibilities lifted from a job-family template. There is nothing to aim at — send the master-resume cut and move on.
You came in through a referral. A person is already carrying your resume past the filter. Spend the time on what you will say to them.
You are sending thirty applications a week. Then volume is the problem, not wording. Eight tailored applications beat thirty untailored ones and you get your evenings back.

And the honest limit on all of this: tailoring changes which of your real qualifications a reader sees first. It does not change whether you have them.

FAQ

How long should it take to tailor a resume to a job description?

About twenty minutes per application once a master resume exists, plus the one-time hour to build that file. If it is taking an hour every time, you are rewriting instead of selecting — or you are editing the last version you sent instead of starting from the master.

Is tailoring a CV to a job description different from tailoring a resume?

For the one-to-two page industry CV used in the UK, Ireland and much of Europe, no — same procedure, same four edits. An academic CV is a different document: it is a complete record rather than a pitch, so you tailor the cover letter and the research statement instead of pruning the publication list.

How many keywords from the job description should I include?

Do not count them. Counting is how people end up with a skills section they cannot defend. Cover the terms that are genuinely true of you, get each one into a bullet where it is doing work rather than sitting in a list, and stop there.

Can I use ChatGPT to tailor my resume to a job description?

Yes for reading the posting, for finding which of your existing bullets already covers each requirement, and for rewording those bullets. No for writing bullets about requirements you do not cover — that is exactly where it invents facts. Tell it explicitly not to add anything that is not already in your resume, then check the output for numbers you never gave it.

Does a tailored resume actually get past the ATS?

An applicant tracking system does not reject you. It parses your resume into a database that a recruiter then searches. Tailoring helps because it puts the terms they will search for into your document in a form the parser can read. It does not help at all if the parser cannot read the document in the first place, which is a separate and more common problem.

Originally published at resuhive.com.

Should You Use AI for Your Cover Letter? Where the Line Is

思源 — Mon, 14 Sep 2026 06:00:41 +0000

Almost every guide on this lands in the same place: "AI is a starting point, not the finish line." True, and useless — it never says which parts you're supposed to finish.

Short answer: use AI for structure and pressure-testing, not for the claims. The parts of a cover letter that persuade are the parts only you can supply — a specific number, a specific project, a specific reason this company and not the twenty others. AI cannot invent those, and when it tries, it produces the exact sentences that get letters skimmed and dropped.

That sounds like the same advice as everyone else until you make it testable. So here is the test, and then the specific places AI helps and hurts.

First, the question everyone actually has: can they tell?

This is the wrong thing to worry about, and the reason is worth understanding because it changes what you should do.

AI-text detectors are unreliable in both directions. They flag human writing as machine-written and clear machine text as human, and the people running them know it. Very few hiring teams are running your cover letter through one, and the ones that do can't trust the result.

The real risk isn't detection — it's sameness

A recruiter reading forty applications for one role doesn't need a detector. They notice that letters 6, 19, and 33 make the same three points in the same order with the same enthusiastic register. No single letter looks fake. The set looks identical. That's what costs you, and no amount of "make it undetectable" fixes it.

So stop optimizing for not getting caught and start optimizing for not being interchangeable. Those pull in completely different directions: the first one makes you rewrite words, the second one makes you add facts.

The one-minute test

Take the draft — AI-written or not — and highlight every sentence that could appear, word for word, in a stranger's cover letter for a different job. Not the badly written sentences. The transferable ones.

A fully AI-generated letter usually comes back almost entirely highlighted. That is the whole problem, visible in about a minute. It's the same test that catches human clichés — I wrote it up with nine worked examples in cover letter phrases to replace — and AI just produces them faster and more fluently.

Typical AI first draft vs. what survives the test

❌ Before: I am excited to apply for the Product Designer role at Northwind. With my strong background in user-centered design and my passion for creating intuitive experiences, I am confident I would be a valuable addition to your team.

✅ After: Your onboarding flow asks for company size before it asks what the user wants to do — I redesigned almost exactly that sequence at Brightline last year and cut drop-off on step two by a third.

The second version is not better writing. It is the same writing with a fact in it. AI could have produced that sentence structure; it could not have produced the fact.

Where AI genuinely helps

Three jobs it does well, all of them structural rather than substantive:

Pulling requirements out of the job description. Paste the posting and ask what it is actually screening for, ranked. This is fast, accurate, and boring — exactly what you want a machine doing.
Reordering what you already wrote. Give it your five bullet facts and ask which order makes the strongest case for this specific posting. It is good at this and you are worse at it, because you are too close to your own history.
Cutting. "Take this to 200 words without removing any specific number or project name." That constraint is the whole trick — it forces the hedges and adjectives out and leaves the evidence in.

Notice that none of these ask AI to know anything about you. You supply the facts; it handles arrangement, compression, and reading the posting closely.

Where it gets you rejected

Inventing achievements. Ask for an impressive letter with thin input and you will get numbers you cannot defend. Same failure mode as AI resume rewriting — the invented line is always the one they ask about.
Guessing at the company. "I admire your commitment to innovation" means the model had nothing to work with. If you cannot name something specific about them, do not let a sentence pretend you can.
Register drift. Left alone, most models write a register warmer and more formal than how the company writes. Read the job posting's own tone and match it.
The em-dash-and-triads voice. Not a moral problem — a sameness problem. Three-part lists and heavy em-dashes turn up in every letter in the pile.

Prompts that produce usable drafts

The difference between a usable draft and a discardable one is almost entirely in how much raw material you hand over. These work because they front-load your facts and constrain the output:

Extract first: "Here's the job posting. List the five things this role is actually screening for, in priority order, quoting the line each one comes from."
Then supply evidence: "Here are six things I've done, with numbers. Map each to the requirements above and tell me which two make the strongest case — and which of my six are irrelevant here."
Then draft, constrained: "Write a 220-word cover letter using only the facts I gave you. No adjectives about my character. No sentence that could appear in someone else's letter. Open with the company-specific observation I wrote, not with my name or the role title."
Then attack it: "Highlight every sentence in this draft that could appear unchanged in a different applicant's letter for a different job." — this one is the most useful prompt on the list.

Same model, same job, different prompt

❌ Before: Write me a cover letter for a product designer role at Northwind. Make it sound enthusiastic and professional.

✅ After: Job posting below. My facts: cut onboarding drop-off 31% at Brightline; ran design system for 4 engineers;
noticed Northwind asks company size before intent on step one.
Write 220 words using ONLY these facts. No adjectives about my character.
No sentence that could appear in another applicant's letter. Open with the Northwind observation.

The instruction that changes the output most

"Use only the facts I gave you." Without it the model fills gaps with plausible-sounding invention, and you end up proofreading for lies instead of editing for strength.

A workflow that takes about twenty minutes

Spend five minutes writing raw facts — numbers, project names, one thing you noticed about the company. Ugly bullets are fine. This step is not optional and AI cannot do it.
Have AI extract what the posting screens for, and map your facts against it.
Have it draft under the constraints above.
Run the highlight test. Replace every highlighted sentence with a fact or delete it.
Read it aloud once. Anything you would not say out loud to a person, cut.

Step 1 is where the letter is actually won, and it is the step people skip because it is the only part that feels like work.

If you'd rather not assemble the prompt chain yourself, our cover letter tool runs this shape — job posting in, your real experience mapped against it, no invented claims. — Try the cover letter tool

FAQ

Is it dishonest to use AI for a cover letter?

Using it to arrange and compress your own facts is no different from using a spellchecker or asking a friend to read a draft. Using it to generate achievements you did not have is dishonest — not because a machine wrote it, but because the claim is false. The line is the claims, not the tool.

Are free AI cover letter generators good enough?

The model quality is rarely the limiting factor — your input is. A free tool fed six specific facts beats an expensive one fed a job title. Judge a generator by how much it asks you for, not by what it promises: anything that produces a letter from just a role and a company name is producing a letter about nobody.

Why does Reddit tell me AI cover letters don't work?

Because the letters people complain about are the fully-generated kind, which are transferable start to finish — and that criticism is correct. The disagreement isn't really about AI. It's about whether you did step 1.

Should I disclose that I used AI?

Not unless the employer asks, and some now do — a few applications include an explicit question about it. If asked, answer straight: you used it to structure and tighten your own material. That answer is easy to give when it's true, which is another reason to keep the claims yours.

Originally published at resuhive.com.

How Much Should You Prepare for an Interview? A Time Budget

思源 — Thu, 10 Sep 2026 09:07:50 +0000

The usual answer is "five to ten hours." It is not wrong, and it is not useful, because it never says what those hours are spent on — so people fill them with the easiest activity available, which is reading the company's About page a fourth time.

The number is the wrong thing to ask about. Most of what makes you good in an interview is prepared once and reused for every interview after it. Once you separate the one-time work from the per-interview work, the question stops being "how many hours" and becomes "which hours, and in what order."

Here is the budget I'd defend, what each block buys you, and the honest signal that you're done.

The budget: about five hours, split two ways

Split everything into reusable (do it once, use it for every interview this year) and per-interview (has to be redone for each company). Almost everyone gets this backwards and redoes the reusable part from scratch every time.

Six stories — 90 min — REUSABLE. Write six things you actually did, each with the situation, what you specifically decided, and how it came out with a number attached. Six covers most behavioural questions because interviewers ask the same six themes: conflict, failure, ownership, ambiguity, influence, and something you shipped. You write these once.
Your own resume, out loud — 30 min — REUSABLE. Read every line and answer "what would I say if they asked about this?" The lines you stumble on are the ones they will pick, because they are the vague ones.
The posting, closely — 45 min — per interview. Not skimmed. Write down the five things it is actually screening for and which of your six stories maps to each. Gaps you find here are what you prepare for; gaps you find in the room are what you lose to.
The company, specifically — 60 min — per interview. Not the About page. What did they ship in the last six months, what are they hiring for besides this role, and how do they write when they aren't marketing? Changelogs, engineering blogs, and job postings for other teams are worth more than the homepage.
Your questions for them — 30 min — half reusable. Three that show you read the posting, two that you actually want answered. The second kind matters more and is harder to fake.
One out-loud run — 30 min — per interview. Say your opening answer to a wall or a webcam. This is the step everyone skips and it is where the real errors show up.

The reusable half is why interview four is easier than interview one

Two of the six blocks — your stories and your resume walkthrough — are done once, then lightly re-cut per role. That is about two hours of one-time work. After that, each additional interview costs roughly two and a half hours, not five to ten. People who claim interviews get easier are not more confident; they are just no longer redoing the reusable part.

The six stories, in more detail

This is the highest-leverage block, so it is worth being specific about what a finished one looks like. The failure mode is writing a summary instead of a story:

A prepared story vs. a summary of a job

❌ Before: I led the migration of our billing system and it went well. It was challenging but I learned a lot about working with stakeholders.

✅ After: Billing was on a service two people understood and one had left. I argued for migrating in four slices instead of one cutover — slower, but each slice was reversible. Slice two broke invoices for about 40 accounts; because it was reversible we rolled back in under an hour and shipped it again two days later. Total migration took nine weeks against a six-week estimate, and we never had a billing outage longer than an hour.

The second one is not longer because it is padded. It is longer because it contains a decision you made, a thing that went wrong, and numbers. Those three are what the interviewer is listening for, and none of them can be improvised convincingly.

It is the same standard that makes a resume line credible rather than decorative — the action verbs piece has the written version of this test.

If you have one day, not one week

This is the actual situation for most people, and "five to ten hours" is useless advice at 9pm the night before. Ninety minutes, in this order:

30 min — three stories, not six. Ownership, failure, and something you shipped. Written down, with numbers.
20 min — the posting. The five things it screens for, mapped to those three stories.
20 min — the company. Their last two announcements and one specific observation you can say out loud.
10 min — two questions you actually want answered.
10 min — say your opening answer out loud once. Do not skip this one to buy more reading time; reading has sharply diminishing returns and speaking has almost none.

Ninety focused minutes beats six unfocused hours, and it comfortably beats the most common alternative, which is re-reading the company homepage until it is time to sleep badly.

The day of

Do not learn anything new. Anything you add in the last two hours competes for recall with material you actually rehearsed.
Re-read your six stories once, then close the document.
Say your 60-second introduction out loud once. If you have not built one, that is the highest-value fifteen minutes available to you — see the 60-second self-introduction.
Check logistics 90 minutes early, not 15. Link, room, name of the person, backup phone number.
Have your resume open in a tab. They will reference it and you should be looking at the same document they are.

Where AI actually helps, and where it wastes your time

Useful for two things specifically: pulling the real requirements out of a posting, and being an opponent. It is close to useless as an answer generator, for the same reason it is a bad cover letter writer — it cannot supply your facts, and answers built from invented facts collapse on the first follow-up question.

✅ "Here's the posting. What are the five things this role is screening for, in priority order?"
✅ "Here's my story about the billing migration. Ask me the three hardest follow-up questions an interviewer would ask." — this is the best use, by a distance
✅ "Which of these six stories is weakest for this specific role, and what is missing from it?"
❌ "Write me an answer to 'tell me about yourself.'" — you will memorise something that isn't yours and it will sound like it

If you want the opponent part without building the prompt chain, our interview prep tool generates role-specific questions and follow-ups from the actual job description. — Try interview prep

How to tell you're done

Preparation has sharply diminishing returns and no natural stopping point, which is why anxious people keep going all night and arrive worse than they were at hour three. Three signals that you have crossed the line:

You can tell all six stories out loud without notes, roughly two minutes each. Not word-perfect — word-perfect is worse.
You can name one specific thing about the company that is not on their homepage.
You are re-reading rather than producing. The moment your prep turns into rereading things you already wrote, you are done. Stop.

Over-preparation has a real cost

A rehearsed-to-the-word answer sounds rehearsed, and interviewers discount it — the same way a cover letter full of transferable sentences reads as a template. Prepare the material, not the wording. You want to know the story cold and choose the sentences in the room.

FAQ

Is five to ten hours per interview right?

For your first interview of a job search, roughly yes — but about two of those hours are one-time work. From the second interview on, two to three focused hours is realistic, and more than that is usually rereading rather than preparing.

How many interview questions should I prepare answers for?

None, in the sense of scripted answers. Six stories cover far more ground than twenty memorised answers, because interviewers ask the same handful of themes in endlessly different wordings. Prepare material that can be re-cut on the spot rather than answers that only fit the exact question you imagined.

What if I genuinely had no time to prepare?

Do the 90-minute version above, and if you have less than that, do the first item only: three stories with numbers, written down. Walking in with three real stories beats walking in having read the entire website.

Does preparing make me sound scripted?

Preparing the wording does. Preparing the material does the opposite — it frees you to listen to the actual question instead of scrambling for content while they are still talking. If you feel scripted, you rehearsed sentences when you should have rehearsed facts.

Originally published at resuhive.com.

9 Cover Letter Phrases to Replace (and What to Say Instead)

思源 — Tue, 08 Sep 2026 03:58:45 +0000

Most cover letter advice tells you what to cut. That's the easy half. The useful half is knowing what to put in the space where the cliché used to be.

Every phrase below is grammatically fine. That is exactly why they survive draft after draft — nothing about them looks wrong. The problem is that each one occupies the space where a specific claim about you should be, and the person reading has seen all nine before.

One test catches every case: could this sentence appear, word for word, in a stranger's cover letter? If it could, it isn't doing any work. Below is each phrase, why it fails, and the sentence to write instead.

1. "I am writing to apply for the [role] position"

The reader already knows. The subject line said it, the application form said it, and your resume is attached to the same email. Your first sentence is the most valuable line in the letter, and this one spends it confirming something nobody was unsure about.

Opening line

❌ Before: I am writing to apply for the Marketing Coordinator position at Northwind.

✅ After: Northwind's newsletter grew from 4,000 to 22,000 subscribers last year. I spent the last two years running that exact motion at a team about your size.

The rule: open with something that could only be written about this company by this applicant. If your opening line works for any employer, it works for none of them.

2. "Dear Sir or Madam" / "To Whom It May Concern"

Both read as a form letter, and "To Whom It May Concern" adds a faint suggestion that it may not concern anyone in particular. In most cases the name is findable in under two minutes.

The job posting itself — hiring managers often sign the description
LinkedIn: the "posted by" line on the job, or the team page
The company's about/team page
The signature on any email you have already received from them

Greeting

❌ Before: To Whom It May Concern,

✅ After: Dear Priya Raman,

— or, when the name genuinely isn't findable —

Dear Northwind Design Team,

Don't guess the honorific

If you have a name but aren't certain how the person is addressed, use the full name — "Dear Alex Chen,". It is always safe, and it is never the thing that costs you the interview. Guessing wrong is.

3. "I am confident that I would be a great fit"

This is the phrase people search for a replacement to most often, and the honest answer is: usually nothing. "I am confident," "I believe," "I feel" are hedges. They sit in front of a claim and quietly weaken it. Delete the hedge and the same sentence gets stronger — and shorter.

Dropping the hedge

❌ Before: I am confident that I have the skills needed to succeed in this role.

✅ After: I have shipped three design systems, two of them for teams smaller than yours.

Notice what happened: removing "I am confident that" forced the sentence to name something real. That is the actual value of cutting hedges — they are where vague claims hide.

4. Starting every sentence with "I"

The fix is not a list of synonyms for "I." It is changing what the sentence is about. "I am X" pushes you into claiming; making the work or the result the subject pushes you into showing.

Changing the subject of the sentence

❌ Before: I am experienced with leading teams and setting goals. I am also comfortable with ambiguity.

✅ After: Leading a four-person team at Brightline is where I learned to set quarterly goals that survive contact with a changing roadmap.

A practical limit: no more than two paragraphs in a row starting with "I." You do not need to eliminate the word — a cover letter is about you — you need to stop opening with it on autopilot.

5. "I am a hard worker / team player / detail-oriented"

Nobody has ever written "I am careless and difficult to work with." A claim that no applicant would ever contradict carries no information. These words are not wrong about you — they are simply unreadable as evidence.

Trait → evidence

❌ Before: I am detail-oriented and highly organized.

✅ After: I owned the release checklist for a 200-page docs site. We shipped 14 releases last year without a single broken link in production.

You never have to claim the trait. Give the evidence and let the reader arrive at it — they will trust their own conclusion far more than your adjective.

6. "I would be a great fit for your company culture"

Fit is the reader's conclusion to draw, not yours to assert. And "culture" without a specific referent signals that you read the careers page and nothing else.

Generic fit → specific fit

❌ Before: I would be a great fit for your company culture and values.

✅ After: You've written about keeping support and engineering in the same standup. That's the setup where I've done my best work — most of what I fixed at Brightline came from sitting in on support triage.

7. "As you can see from my resume…"

This asks the reader to go do the work in another document, and it spends a sentence on something they can already see. The cover letter's whole advantage is that it can carry what the resume structurally cannot: context, motive, and the story behind a line item.

Pointing at the resume → adding to it

❌ Before: As you can see from my resume, I have five years of experience in customer support.

✅ After: My resume lists five years in support ops. What it doesn't show is that three of those years I was the only person on call for a product running 24/7 — which is where I learned to write documentation nobody has to ask about.

8. "Thank you for your time and consideration"

This one is harmless, which is the trap. It is the last thing the reader sees, and it says nothing. Politeness is not the problem — spending your closing line on it is.

Closing line

❌ Before: Thank you for your time and consideration. I look forward to hearing from you.

✅ After: If it's useful, I can send a short breakdown of how I'd approach the first 90 days on your onboarding flow. Either way, thanks for reading.

The closing should either propose a next step or leave one concrete thing in the reader's head. It can still be polite while doing that.

9. "Sincerely," — and the alternatives that actually differ

"Sincerely" is not a mistake. It is neutral and slightly formal, and it will never be the reason you didn't get the interview. But if you want the sign-off to match the letter's register, these are the ones that genuinely read differently:

Best regards — safe default, slightly warmer than "Sincerely"
Best — normal for tech, startups, and anywhere the job post used contractions
Thank you — good when your closing line actually asked for something
Kind regards — common in the UK, Ireland, Australia, NZ; reads slightly formal in the US
Yours faithfully — British formal, and only when you opened with "Dear Sir or Madam" — which, per #2, you shouldn't have

Avoid Cheers unless the company's own writing is that casual, and avoid Warmly for a first contact with a stranger.

The one-minute check that catches all nine

Read your letter and highlight every sentence that could appear unchanged in a stranger's application. Not sentences that are badly written — sentences that are transferable. Then look at how much of the page is highlighted.

The threshold

If more than about a third of the letter is highlighted, it isn't a letter about you yet — it's a template with your name at the top. Every highlighted sentence is a slot where a specific fact could go instead.

A second pass that takes ten seconds: read only the first word of every sentence, top to bottom. If it goes "I, I, I, My, I," you have a subject problem, not a vocabulary problem — see #4.

Once the letter is doing its job, make sure the resume behind it parses cleanly — the strongest cover letter in the world can't rescue a file an ATS reads as gibberish. — Run a free ATS check

FAQ

What goes in a cover letter that isn't already on the resume?

Motive and context. Why this company rather than the twenty others hiring for the same title, what a line on your resume actually involved, and how you think about the problem the role exists to solve. If your letter only restates the resume in paragraph form, that is the real reason it feels hard to write.

What if the application doesn't ask for a cover letter?

If there is a free-text field, use it — four or five sentences built on the principles above beat a blank box. If there is no field at all, don't force one into the resume PDF; put the strongest specific line in your resume summary instead.

Can I reuse one cover letter across applications?

You can reuse the structure. You cannot reuse the specifics, and the specifics are the whole point — a reused letter is by definition made of transferable sentences, which is what the check above is designed to catch. In practice the opening line, the fit paragraph, and the closing ask are rewritten every time; the middle evidence paragraphs mostly hold.

How long should it be?

Under one page, and shorter is normal now — roughly 200 to 350 words, three or four short paragraphs. Length is not what makes a letter persuasive; the ratio of specific to transferable sentences is.

Originally published at resuhive.com.