You know the scroll. A layoff post. Another layoff post. Then a role that actually sounds like you, and the line underneath it: 1,000+ applicants.

And something in your chest quietly closes the tab.

If you're job hunting in tech right now, whether you were laid off, you're trying to leave before it happens to you, or you're trying to get in for the first time, that number is doing a lot of damage. So let's look at what it actually counts, and where your energy goes further.

I've been on both sides of that number

I've been laid off twice. The first time was April 2023. On a Friday, we were told we'd find out by 9am the following Friday whether we were affected. I really loved that job, so I kept refreshing my email until the answer showed up. I was on the list.

The second time was Halloween 2024. That July I'd moved from Arizona to Sydney and kept my US job, on the condition that I kept working the same hours I always had. So my workday started in the middle of the night. I opened my laptop for a 3am shift, typed my password about five times in a sleepy haze, and then saw it: computer locked, check your email for more info. The email said my role had been eliminated. Everyone outside the US was asleep when the announcement went out.

I've also sat on the other side of the table for close to 100 interviews, as the person deciding who moves forward. So I'm not going to tell you the number doesn't matter. I'm going to tell you it isn't the number you think it is.

What "1,000+ applicants" actually counts

• Often it's clicks, not applications. When a listing sends you to the company's own careers site, LinkedIn can't see whether you finished. Recruiters have pointed out for years that the count on those posts tracks people who clicked apply, including everyone who clicked, met a 40-minute application portal, and left. LinkedIn doesn't publish exactly how it counts, so treat the number as a mood, not a headcount.
• One-click applying makes applying nearly free. When it takes one tap, a lot of people tap. A real share of any pile is the same résumé sent to everything, including roles it doesn't come close to.
• The count only goes up. It doesn't know the team already has a shortlist, or that some of the pile applied from places the role can't hire in.

It wasn't always this stacked. The piles I saw before 2022 were noticeably smaller. But every time I've hired, before and since, the pile was big and the group of people who clearly showed they could do this specific job was small. You're not competing with a thousand people. You're competing with the handful who made it obvious.

Make it obvious on the page

Most of the time your résumé isn't being thrown out by a robot. It's being read by a person, quickly, between meetings. Three things help that person most.

• Evidence, not duties. "Responsible for customer escalations" tells me what was in your job description. "Cut the escalation backlog from 300 to 40 in six weeks by rebuilding how tickets were triaged" tells me what changed because you were there. (That one's an illustrative example, not a real résumé.) The first is a duty. The second is a receipt.
• A page that's easy to read. Clear headings, consistent dates, real white space, one accent color at most. Your résumé doesn't need to be prettier. It needs to be easier to skim.
• A top third that does the heavy lifting. Two or three lines that say what you do, what you're strongest at, and the kind of role you're going for. Write it for this kind of role, not every kind.

Apply to fewer jobs, on purpose

Sending applications to everything feels productive because the number goes up. But fifty generic applications usually lose to ten where you rewrote the summary and the top few bullets to match what the listing actually asks for.

• Read the listing for the problem, not just the keywords. What's broken that they're hiring someone to fix? Put your closest receipt for that problem near the top.
• Don't wait on any one application. Replies, rejections included, can take a few weeks to show up. Keep the next few moving instead of refreshing your inbox for the last one.
• Pick a weekly number you can actually sustain. Five good applications a week beats thirty you resent.

Find a person, not just a portal

A thousand applications land in the same inbox. A short note to a real person doesn't. You don't need to become a networking person. You need two or three sentences you're not embarrassed to send.

The worst case is silence, and silence is what the portal was already giving you. It's always a no if you don't ask.

When you get the interview, be clear before you're impressive

• Answer first. Say the answer in one sentence, then tell the story. Interviewers relax when they know where you're going.
• Tell stories in three beats. The setup, what you did, and what changed because you did it. Most people spend most of their time on the setup. Spend it on what you did.
• Treat "tell me about yourself" as a pitch, not a biography. What you do now, the thread that runs through your experience, and why this role is the next step. If your answer opens with "well, I'm married and I love going to concerts," that's a dating profile, not an interview.
• Have a calm answer ready for the layoff or the gap. Short, factual, no apology: "My role was eliminated in a company-wide layoff in [month]. Since then I've [what you've been doing]. I'm looking for [what this role is]." Then stop talking. The pause is fine.

Trying to get into tech?

The listings with the scariest numbers tend to be the obvious titles. Operations, support, trust and safety, program management, and vendor management all hire people who came from somewhere else, because the work runs on judgment, communication, and keeping things from falling over. If you've run a busy restaurant shift, you've done a version of incident management. Your job is to translate it. I wrote more about those roles in tech jobs that don't need code.

The part that isn't a tactic

This market is a numbers game you didn't choose. The silence feels personal and almost never is. A rejection from a pile of a thousand isn't a verdict on you. It's mostly math.

And if you're doing this around a job you still have, kids who still need dinner, or both, give the search edges. A set time, a set number, and a hard stop. Job hunting will take whatever you give it. Don't give it everything.

If you want the longer version

Everything above comes out of three guides I wrote because I kept having the same conversations. receipts. is about the words: turning what you've done into evidence for a résumé or a promotion case. itemized. is about the page those words sit on, so it's easy for software and people to read. And statement. is for the interview itself, when you need clear answers while your brain is buffering. Each one stands on its own, so start with whichever part is giving you the most trouble.

If you'd rather start free, my interview prep kit has a story bank you can fill in tonight.

Where are you in your search right now? Tell me. I'm curious.