First-week job search: Build resume, target list, and tracker

By the Reach team · Updated October 22, 2026

Spend the first week building three things before you send volume: a resume you can defend, a short list of targets you can describe in one sentence, and a tracker. Then treat your first 20 applications as a calibration batch, not a sprint. In our experience, the search tends to keep the habits it starts with, good or bad.

Why the order matters

The usual advice is to apply fast because roles fill quickly. That is partly true, and it is why people open a job board on day one and start clicking. The cost shows up later. Applications sent with a generic resume and no record of what was sent are hard to learn from. You get silence, and silence tells you nothing about which part failed.

Sequencing fixes that. If the resume, the targeting, and the tracking are in place first, every application becomes a data point. If they are not, every application is just a lottery ticket you cannot trace.

There is also a mood effect. The first batch of responses, or the lack of them, sets your expectations for the whole search. Twenty applications that go out with a messy resume and vague targeting, followed by two weeks of nothing, can convince you the market is closed. Often the market is fine and the inputs were off. That conclusion is hard to undo once you have drawn it.

Days 1 and 2: decide what you are actually looking for

Write down the answer to three questions in plain sentences, not buzzwords.

• What title or titles? Pick one primary title and up to two adjacent ones. If your list has five unrelated titles, you do not have targets yet, you have a mood.
• What are the constraints? Location or remote, compensation floor, company size, industry exclusions, visa or start date issues. Decide these now, because every posting will tempt you to bend them.
• What would make you say no? A short list of dealbreakers saves you from spending an hour on an application you would later decline.

Then build a target list of companies, not just postings. Aim for a modest number you can actually research, something like 30 to 60, sorted into rough tiers: places you would be excited about, places that are solid, and places that are practice. The practice tier is real. It lets you run an interview loop before the one that matters.

If you cannot say your target in one sentence ("senior backend engineer at a Series B to D company, remote in US time zones"), applications will come out unfocused, and recruiters can tell.

Days 2 to 4: fix the resume once, properly

Most people tweak the resume for every posting before they have a solid base version. Do it in the other order. Build one strong master resume first, then tailor from it.

The master version

• One page if you have under roughly ten years of experience, two if more. Longer rarely helps.
• Each role leads with outcomes, not duties. "Responsible for the billing system" tells a reader little. "Rebuilt invoice reconciliation so month-end close stopped needing manual fixes" tells them something, as long as it is true.
• Use numbers only where you actually know them. If you do not have a defensible figure, describe the scope in words instead. An invented number will come up in an interview and it will not go well.
• Plain formatting. Single column, standard section names, no text in images. Applicant tracking systems parse plain files more reliably, and humans skim them faster.
• A headline or summary that matches your target title from day 1. If the top says one thing and your targets say another, fix whichever is wrong.

The tailoring rule

Decide in advance how much you will change per application. A workable rule: the summary line, the order of bullets, and the skills section may change. Employment history facts do not. This keeps tailoring to a few minutes and keeps you honest.

Have one other person read the master. A friend in the field is better, but anyone who will tell you what confused them is useful. Typos and unclear bullets are cheap to fix now and expensive once they are on forty submitted copies.

Days 3 to 5: set up tracking before there is anything to track

A spreadsheet is enough. The point is that it exists before the first application, because reconstructing a record from memory and email search is miserable and always incomplete.

The "next action date" column does the most work. A tracker that only records history is a diary. One that tells you what to do on Thursday is a tool.

Also set up a dedicated email folder or label, and a calendar habit of a short weekly review. Fifteen minutes on Friday looking at what moved and what stalled is enough.

Day 5 onward: the first 20 applications

Now apply, but with a different mindset. These first 20 are a calibration batch. You are testing whether your resume, your targeting, and your process produce responses, and you are watching for patterns early enough to correct them.

Some practical guidance:

1. Mix the tiers. Send a few practice-tier applications first, then solid, then save some excited-tier ones until you have seen how the first batch behaves. Burning your favorite company on a first draft resume is a common and avoidable mistake.
2. Read each posting fully. At this stage, careful beats fast. You are learning what the market means by your target title, and postings are the best free source for that.
3. Log as you go. Record the application in the tracker at the moment you submit it, not at the end of the day.
4. Review after about 15 to 20. Ask which applications produced any response at all, which tier they came from, and what they had in common. With a sample this small, treat it as a hint, not a conclusion.

What you are looking for is not a perfect response rate. It is whether something is clearly broken. If nearly nothing comes back from postings that match you well, the resume or the targeting needs another look. If you hear back mostly from roles you do not want, your headline may be pointing the wrong way. If you get interviews but no offers, the problem has moved downstream, and that is a different kind of problem to have.

Where automation fits, and where it does not

Tools that automate applications are useful for the repetitive parts: filling forms, tracking status, surfacing new postings. They are a poor fit for the first week, because they multiply whatever you feed them. A weak resume sent a hundred times is still a weak resume, only faster. If you do use one, Reach included, wait until the calibration batch has told you the basics work, and keep reading what goes out under your name. Automation also makes it easy to apply to roles you would never have chosen by hand, which dilutes your tracking data.

A rough plan for the week

Your pace may differ. A person with a recent, solid resume can compress days 2 to 4 into one. Someone returning after a long gap may need longer. The order is what matters, not the calendar.

Common ways this goes wrong

• Treating the tracker as optional. You will skip it on a busy day, and then it is useless.
• Tailoring too early. Customizing a resume that is not yet solid just spreads the flaws around.
• Applying only to dream roles first. You get one first impression per company, usually.
• Judging the market from five applications. Small samples are noisy. Wait for the batch.
• Skipping the constraints conversation. Unstated dealbreakers cost you time later, in interviews you did not want.

For more on what to do once the responses start arriving, see the rest of the Reach guides.