Say plainly that hiring is slow right now

Job searching in this market takes longer and hurts more than it did a few years ago. Roles get more applicants per posting, some processes stall for weeks without an update, and a strong candidate can still hear nothing back. None of that means something is wrong with you. It means the odds changed, and the way most people respond to worse odds, applying to more jobs faster, usually makes the problem worse instead of better.

A recruiter reading two hundred applications for one opening is not reading carefully. They are scanning for a reason to say no, because saying no to most people is the only way to get through the pile. A generic application gives them that reason immediately: nothing on the page connects to the specific job in front of them. Volume competes against volume. A distinct, well aimed application competes against almost nothing.

Stop applying to everything that is remotely close

Bulk applying feels productive because the number of applications sent goes up every day. It rarely produces a proportional number of real conversations, because a resume written to be technically true for thirty different roles is optimized to offend no one and excite no one. Reviewers can tell within a few seconds when a document was aimed at the job title and not at the job.

Pick one or two openings that actually fit where you want to go next, not just what you are qualified to do. Put the hours you would have spent on the other twenty applications into those one or two instead. This is uncomfortable because it feels like giving up options, but a search with five careless applications and one careful one usually loses to a search with two careful applications and nothing else.

  • A role you are qualified for is not the same as a role you actually want.
  • If you cannot say why this company in one honest sentence, that is a sign to slow down, not to send faster.
  • Two applications you can defend in an interview beat twenty you would struggle to explain.

Build the resume around the role, not the other way around

A tailored resume is not a find and replace of the company name at the top. Read the posting closely and identify the two or three responsibilities that matter most for that team, then rebuild your bullet points so the most relevant work is what a reader sees first. Cut or shrink the experience that has nothing to do with this job, even if it was meaningful work. A resume is a pitch for one specific role, not a full record of your career.

Use the language the posting uses when it honestly describes what you did. If they call it incident response and you call it firefighting, say incident response. This is not about keyword stuffing; it is about making the match obvious to someone reading quickly. If you have to stretch the truth to make the language fit, that is useful information too: the role may not be as close a match as it looked.

Write a cover letter with an actual reason behind it

Most cover letters restate the resume in sentence form and end with a line about being a great fit. That is not a reason, and reviewers read enough of them to recognize the pattern instantly. A real reason is specific: a product you have used and have an opinion about, a technical problem the company has talked about publicly that you have also wrestled with, a person whose work at that company you have followed, or a stage of growth you want to be part of and can explain why.

The story does not need to be dramatic. It needs to be true and specific enough that it could not be copied into a letter for a different company without editing. If your explanation for wanting the job would work unchanged for three other companies in the same industry, it is not yet a reason, it is a category. Keep narrowing it until it only fits this one.

Try to connect with the job and the company before you hit submit

Where you can, talk to someone before the application goes in, not only after. A short, respectful message to someone on the team, a comment on something they built, or a question about how they approach a problem you care about turns you from a resume in a pile into a person who was already curious about the work. This is not about asking for a favor. It is about arriving with context that makes the eventual application easier to write and easier to believe.

This step is exactly why applying to fewer roles matters. Real outreach does not scale to fifty companies a week. It scales to the one or two you actually care about, which is the same short list the earlier sections are pointing you toward.

Why I am writing this down

This is not advice from the sidelines. I have been through slow, demoralizing searches myself, sent out the same recycled resume before I learned better, and rebuilt the approach in this article over several rounds of applying, and later, of reading other people's applications from the other side of the table. That combination is what convinced me the fix was never more applications. It was fewer, argued properly.

I am currently writing a longer book built around that experience: the searches that went nowhere, what actually changed the outcome, and the fuller version of everything in this article. It covers more ground than one page can hold, and it is still in progress. Until it is finished, this is the short version.

Treat every application as a small, honest bet: this company, this role, this reason, argued as well as you can argue it. Fewer bets, made with real conviction, hold up better than a hundred made in a hurry.

← Back to articlesDiscuss an engineering challenge ↗