One resume for forty jobs is why you are not hearing back

Paste the posting. See the terms that requisition is indexed on, which ones you already carry, and which of your bullets is the right home for the rest.

Sending the same document to every opening is efficient for you and useless to the system reading it. Requisitions are indexed on the language of the posting, and two roles with the same title frequently share almost none of it. A resume that matches at 40% is competing against ones that match at 80%, and the difference is usually vocabulary rather than ability.

The work is genuinely small once you can see it: three or four bullets rewritten, one headline changed, two skills added that were always true and never written down. What takes the time is knowing which three bullets, which is the part this does for you.

In short

  • Terms ranked core / preferred / nice-to-have
  • Match rate recalculated as you edit
  • Tailoring never claims experience you do not have
  • Each application keeps its own version and score
Priya Raghunathan
Senior Backend Engineer, distributed systems and payments
priya.r@hey.com · +1 (415) 555-0142 · Oakland, CA · linkedin.com/in/priyaraghunathan · github.com/priyar · priyar.dev
Summary

Backend engineer with eight years on high-throughput payment infrastructure. Took a ledger service from 400 to 9,000 writes per second without a consistency regression, and led the migration that moved 42 million accounts off a single Postgres primary. Comfortable owning a system end to end: schema design, rollout, the pager.

Experience
Senior Backend Engineer, Northwind Payments · Remote (Oakland, CA)Mar 2022 – Present
Rebuilt the double-entry ledger on an append-only event store, lifting sustained throughput from 400 to 9,200 writes per second while keeping balance reconciliation exact.
Led the shard migration of 42M accounts off a single Postgres primary across six weeks with zero customer-visible downtime and no rollback.
Cut p99 settlement latency 71% (2.4s to 690ms) by replacing synchronous fan-out with a batched outbox consumer.
Mentored four engineers; two were promoted to senior within eighteen months.
Backend Engineer, Cartogram · San Francisco, CAJun 2019 – Feb 2022
Designed the tenancy model behind the enterprise tier, which closed $3.1M in ARR that had been blocked on data isolation.
Reduced infrastructure spend 34% ($780K annualised) by moving cold tiles to object storage behind a signed-URL cache.
Wrote the incident review process still used company-wide; mean time to resolution fell from 4.1 hours to 52 minutes.
Software Engineer, Helix Robotics · Berkeley, CAAug 2017 – May 2019
Built the telemetry pipeline ingesting 1.2TB per day from 3,400 field units, replacing a batch job that ran twelve hours behind.
Shipped the fleet-diagnostics API consumed by every downstream team and by two customer integrations.
Skills
Languages: Go, TypeScript, Python, SQL
Infrastructure: Kubernetes, Kafka, Postgres, Terraform, AWS
Practices: Distributed systems, Event sourcing, Observability, Incident command
Education
B.S. Electrical Engineering & Computer Science, University of California, Berkeley · Berkeley, CAAug 2013 – May 2017
Grade: 3.8/4.0

How it works

  1. 01

    Paste the job description

    The whole thing, including the responsibilities nobody reads. Requirements and responsibilities are indexed differently and both matter.

  2. 02

    See what it is indexed on

    Terms are pulled out and ranked core, preferred or nice-to-have, then split into what your document already carries and what it is missing.

  3. 03

    Tailor, or place them yourself

    One click rewrites the most relevant bullets to carry the missing terms honestly, or you can see which bullet each term belongs in and write it yourself.

It will not put words in your mouth

Tailoring rewrites bullets you already have to use the posting's vocabulary where it genuinely applies. If a term describes something you have never done, it stays in the missing list with a note, rather than appearing in a bullet you cannot defend.

This is the line that matters. Keyword stuffing gets you into an interview you then fail, which is worse than not getting it. You have burned the company, the recruiter and a week.

One version per application

Every tailored resume is saved as its own document with its own score, its own keyword report and its own notes on where you sent it. When they call three weeks later, you can open the exact version they read.

That is the real argument for unlimited documents, and it is why the free plan's single resume is the limit people hit first.

Questions

Keyword targeting questions

How many keywords should I match?

Core terms are the ones that matter, so aim to carry all of them honestly. Preferred terms are worth adding where true. Nobody needs a perfect match, and a document stuffed to 100% reads as a document stuffed to 100%.

Where should keywords go?

Inside the bullet describing the work you used them on, plus the headline for the job title itself. A skills list at the bottom is the weakest possible placement, though it is better than nothing.

Does this work for non-English postings?

Yes. Extraction works on the language of the posting, and documents can be translated while keeping the structure intact.