Sending another twenty applications feels like work. It is often a way to avoid looking at the twenty you already sent. The useful week starts with a count of where those rows stopped, and only then with a decision about what to change.
Handshake’s note on what 2025 taught the early-career market, published 2 January 2026, puts a scale on the pile. For the class of 2026, the platform saw 23 applications per full-time job. The class of 2025 figure was 20.8. The class of 2023 figure was 11. Full-time postings were down 15 percent year over year. Those are platform counts. They describe how crowded a typical full-time opening looked on Handshake. They do not describe your chance on the next form you open.
A ratio like 23 to 1 is easy to misuse. It is an average across many employers, majors, and cities. A student who applies to twelve roles that match a confirmed skill, and a student who applies to sixty roles with a resume that could belong to anyone, are both inside that average. The number is a reason to keep a funnel. It is a poor reason to decide that effort is pointless, and a poor reason to decide that sixty more forms will fix a resume that never produces a screen.
Four stages, and nothing fancier
Open the list you already have. Mark four stages you can verify from your own records.
Applied means you submitted the materials the posting asked for, on a date you can point to. Screened means a person or a scheduled step wrote back: a recruiter note, an online assessment invitation, a request for times. Interviewed means a conversation happened, including a one-way video if you completed it. Offered means you have a written offer, or a written rejection of an offer you can name. A portal word you do not understand stays in a notes column. It does not get promoted to a stage.
Count the rows in each stage for the last month, and for the term. If you have forty applications, two screens, and no interviews, the leak is between submit and screen. Another forty applications with the same resume repeats the leak. If you have eight interviews and no offers, the resume is already doing the job it can do. The next hour belongs to the stories you tell in the room, which is a different task from rewriting bullet points.
@randomrecruiter put a version of that split in a public post on 25 November 2025. No interviews, in that recruiter’s telling, means change the resume. Interviews that do not become offers mean work on interviewing. The post is one person’s advice from hiring work. It is not a study. The split is still a clean way to stop treating every silence as the same problem.
A large number from one thread is still one thread
A public thread on r/cscareerquestions in May 2026 shared a diagram of 589 applications and one offer. The author described about four years of experience, so this is not a student story. Treat every count in that thread as claimed by the person who posted it. Do not import 589 as a target, a warning label, or a fact about computer science graduates.
What the thread is good for is the shape. A single person can send a very large number of applications and still have almost no movement past the first stage. Volume did not, in that account, turn into a wide interview funnel. If your own sheet already shows the same shape at a smaller scale, adding rows will not teach you something the sheet does not already say.
Keep other people’s totals out of your tracker. Your columns are applied, screened, interviewed, offered, and the date of the last thing you know. Someone else’s Sankey is a story you can read once. It is not a cell in your spreadsheet.
What to change when a stage is thin
If the screen stage is thin, stop and read five of the postings you already applied to. For each one, write the required skill in the posting’s words and the line on your resume that shows it. If you cannot point at a line, that application was a guess. Close those rows in your own list so they stop counting as active work. For the postings where a line does exist, make that line the first line a reader hits, using the posting’s noun for the skill. Then send a smaller batch, and count again in two weeks.
If the interview stage is thin, you do not have a volume problem. You have a conversation problem. Write down the questions you were actually asked. Practice one example for each, from work you did. A second resume pass can wait until you have heard the same objection twice.
If offers are thin after several final rounds, ask what changed between the conversation and the decision, in one note, and then look at whether the roles were ones you could take. A role that requires work authorization you do not have can sit in “interviewed” and never become an offer. That row should have been labeled before you prepared.
Handshake’s 15 percent drop in full-time postings is a reason the funnel feels slower than it did for the class of 2023, when the same source put the load at 11 applications per job. Slower is not a personal verdict. It does mean a week spent only on new forms, with no look at the earlier rows, is a week that ignores the part of the market you can actually see: your own stages.
A week that has a number in it
Give the funnel a budget. One example that fits a class schedule: review every open row on Monday, revise one resume against one posting on Tuesday, send at most five new applications on Wednesday, and leave Thursday for a person you already know who can speak to the work. Friday is for the count. If Wednesday’s five do not change the screen count over the next two weeks, the next Wednesday is a revision day. Leave the new forms unsent.
The budget is arbitrary on purpose. Twenty-three applications per job is a platform average. Five in a week is a number you can finish while you are in class. The point of the smaller number is that you still have time to read the posting and to record the stage. A week of forty sends and no updated sheet is how a funnel becomes a feeling.
When you review, separate the rows by outcome you can see. Silence after a week is not yet a stage. Silence after the date someone promised is a fact you can write down, and it belongs in the same sheet. Do not let a stale portal status talk you into a sixth email. The sheet’s job is to show you the next different action. A more precise worry is not a next action.
How Flightpath helps
Flightpath keeps this count in the applications tracker. A role moves from saved to applied to interview to offer, which is the funnel in four words you set yourself. The weekly check-in puts that list back in front of you, next to the plan for this year, so a new batch of postings does not bury the stage that is already thin.
You pin a posting and see the gaps against facts you have confirmed. If the screen stage is the leak, the gap list is the resume problem. If the interview stage is the leak, the tracker date is the thing to prepare for, and a draft follow-up waits until you approve the exact text. Nothing is sent on its own. A role you cannot take stays labeled, and it is not ranked above a role you can take. The national ratio stays off the page. Your rows stay on it.