60 applications, three replies
Before Applyr existed, I spent a stretch of one summer applying to backend engineering roles. I had the experience. I had the projects. I tailored the summary line on top of my resume for each company, changed a word here and there, and sent it out. Sixty-something applications. Three replies. Two of those were auto-generated rejections that arrived within an hour of me hitting submit — fast enough that no human had opened the file.
I assumed, like most people do, that the resume itself wasn't good enough. So I rewrote it. New template, tighter bullets, a friend in recruiting gave it a read and said it looked strong. Same result. The silence didn't change.
The thing that finally explained it
What actually changed my mind was a conversation with someone who'd worked inside a mid-size company's hiring pipeline. I described what I was doing — same resume, small tweaks per role — and she asked to see it next to a job posting I'd applied to. She pulled up the requirements list and started reading down it out loud: "Kubernetes." Not on my resume — I'd written "container orchestration" instead, because that's how I actually thought about the work. "CI/CD." I'd written "automated deployment pipelines." Same skill, described in words that meant nothing to whatever was scanning the resume before a person ever saw it.
That was the moment it stopped being a "polish your resume" problem and became a "you're speaking a different language than the filter" problem. I wasn't under-qualified. I was unreadable to the system standing between me and a human.
What that actually cost me
Here's the number that stuck with me: of those 60 applications, I estimated later — based on going back through the job postings and comparing them against my resume's actual wording — that I was a genuine, honest match for at least 15 of them. Not a stretch, not wishful thinking. Roles where my real experience lined up with what they were asking for. I heard back from three. The other twelve weren't rejections of my ability. They were resumes that never got read, because the words didn't line up with what a script was scanning for.
That gap — between being qualified and being legible to the system doing the first pass — is the entire reason Applyr exists.
Why I built it as a Chrome extension, not just another checker
The first version of what became Applyr was a script I wrote for myself: paste resume, paste job description, get back a list of words that were missing. It worked, but it was still a manual step I had to remember to do, on a separate tab, for every single application — and after application 20 in an evening, the thing I actually skip is the step that requires effort. That's true for everyone, not just me.
So the extension exists specifically to remove that friction: it reads the job posting in the tab you're already looking at, scores your resume against it right there, and shows you what's missing without a copy-paste round trip. The web app does the deeper work — tailoring the resume itself, generating clean exports — but the extension is the part that makes checking a match effortless enough that you'll actually do it every time, not just the first time.
What I'd tell the version of myself sending those 60 applications
Not "write a better resume." The resume was fine. What I needed was a way to see, before hitting submit, whether the words on the page matched the words the job description used — the same comparison that recruiter did for me by hand, in five minutes, that I could have been doing myself the whole time if I'd known to look for it.
That's the whole product, honestly. Check your resume against a real job posting free at Applyr — the same gap-finding conversation, minus needing a friend who happens to work in recruiting.