How to run a two-week job search sprint

Most job searches fail from lack of focus rather than lack of effort. People apply in bursts, lose track of what they sent, and never learn which approach worked. A sprint fixes that by compressing the search into two weeks with clear daily targets and a review at the end.

Days 1–2: set the target

Write down three to five job titles, the locations or remote setup you will accept, and a minimum salary. Then pull ten postings that match and read them side by side. The requirements that appear in most of them are your target keywords; the ones that appear in none can be cut from your resume.

Days 3–4: build the base documents

Create one base resume that matches the common requirements and one cover letter skeleton with a strong opening result. Run both through a scanner against two of the postings and fix anything below 70. You will tailor from this base for every application, so it is worth an extra hour here.

Days 5–9: apply in batches

Set a daily target — ten tailored applications is realistic if you use automation for the tailoring. Apply in the morning when postings are fresh, then spend the afternoon on outreach: one message per application to someone at the company, a recruiter or a hiring manager. Log everything in a tracker with the date, documents used and status.

• Morning: match and apply to new postings.
• Afternoon: outreach and follow-ups on last week's applications.
• End of day: update the tracker and note anything you learned.

Day 10: review

Count applications, replies, screens and interviews. If replies are under 10%, the problem is targeting or the resume; revisit the keyword list. If screens are not converting to interviews, practise the screening call answers. Then plan the next sprint with those fixes in place.

Two weeks is enough to test a hypothesis about what the market wants from you. Several sprints, each adjusted from the last, beat an open-ended search every time.