Module 05 · Job-Search Automation
Capstone: Your 30-Day Job Application Sprint Plan
Open lesson + course map
On this lesson
Course outline
Module 1 · Your AI Job-Search Toolkit
Module 2 · Resume Engineering
Module 3 · LinkedIn as a Lead Engine
Module 4 · Interview Preparation With AI
A 30-day job application sprint is a fixed period for using your resume, LinkedIn profile, outreach messages, interview stories, and application tracker as one system. It replaces random bursts of applying with planned work you can review.
By the end, you will have a complete job-hunt kit, a day-by-day calendar, a small dashboard, and decision rules for changing the plan without inventing experience or exhausting yourself.
// concept
Assemble the Five-Part Job-Hunt Kit
Create one private folder named Job-Sprint-YYYY-MM on your device or in a storage account only you control. Add these five parts:
| Part | Minimum capstone evidence | File name |
|---|---|---|
| Resume | One truthful master resume and at least two role-specific variants | Resume_Master.pdf, Resume_Marketing.pdf |
| Final headline, About section, skills, and accurate dates | LinkedIn_Profile_Copy.md | |
| Outreach | Three researched message templates and one polite follow-up | Outreach_Templates.md |
| Interview bank | Six real STAR stories plus the mock-interviewer prompt | STAR_Bank.md, Mock_Interview.md |
| Pipeline | Live tracker with role, company, source, variant, date, stage, next action, and notes | Application_Tracker |
Remove placeholders, confirm dates and links, and ensure every claim is verifiable from a manager, teacher, client, or project record. A missing qualification becomes a learning task, not a resume bullet.
Edit the master resume only when a verified fact changes. Save each tailored copy as YYYY-MM-DD_Company_Role.pdf and record that file name in the tracker.
// concept
Set Weekly Targets and Quality Caps
Targets cover the whole search, not just application clicks. The sample limits below are workload caps, not hiring benchmarks.
| Week | Main purpose | Tailored applications | Outreach | Visible proof | Interview work | Review decision |
|---|---|---|---|---|---|---|
| 1 | Calibrate two role lanes and test the kit | Up to 6 | 3 researched messages | 1 useful LinkedIn post | 2 mock sessions | Which role lane produced relevant replies or clearer fit? |
| 2 | Repeat the stronger search patterns | Up to 8 | 4 researched messages | 1 project or learning post | 2 mock sessions | Are weak applications failing the fit check before submission? |
| 3 | Improve the weakest pipeline stage | Up to 8 | 4 researched messages | 1 thoughtful industry post | 2 mock sessions | Change one input only: targeting, evidence, outreach, or interview practice. |
| 4 | Follow up, close loops, and document learning | Up to 6 | Follow up once where appropriate | Optional update post | 2 mock sessions | Keep, revise, or stop each tactic for the next sprint. |
Use these quality-over-quantity caps:
- Maximum two tailored applications on an application day, logged and checked before the next application block.
- Send one new outreach message per person and one brief follow-up after five to seven days, then stop.
- No application unless the tracker contains a source URL, closing date if stated, selected resume variant, and next action.
- Cap tailoring at 45 focused minutes per vacancy. Log
Not applying — evidence gapwhen a required qualification is genuinely missing. - Keep one no-search day weekly. Alerts may collect opportunities without requiring an immediate response.
// concept
Build the 30-Day Calendar and Dashboard
Copy this into your phone calendar or spreadsheet. Replace Lane A and Lane B with specific targets such as Junior Data Analyst — Pakistan and Remote Reporting Analyst.
Day 01 Audit all five kit parts; define Lane A and Lane B.
Day 02 Create two saved searches and alerts; shortlist only.
Day 03 Tailor and submit up to 2 Lane A applications; log both.
Day 04 Research 3 people; send 1 specific outreach message.
Day 05 Tailor and submit up to 2 Lane B applications; log both.
Day 06 Run mock interview; revise 1 weak STAR story.
Day 07 Review dashboard; take no application action.
Day 08 Process alerts; reject poor-fit roles with a reason.
Day 09 Submit up to 2 applications in the stronger-fit lane.
Day 10 Send up to 2 researched outreach messages.
Day 11 Publish 1 sample-free, truthful project/learning post.
Day 12 Submit up to 2 applications; schedule next actions.
Day 13 Run mock interview; practise two follow-up questions.
Day 14 Review dashboard; take a no-search evening.
Day 15 Check stale applications; close or schedule follow-up.
Day 16 Submit up to 2 applications using the best variant.
Day 17 Send 1 first follow-up; stop after this bump.
Day 18 Improve the weakest portfolio or evidence link.
Day 19 Submit up to 2 applications only if fit check passes.
Day 20 Run mock interview from a live target job post.
Day 21 Review dashboard; choose exactly 1 process change.
Day 22 Process fresh alerts and company career pages.
Day 23 Submit up to 2 applications with the chosen change.
Day 24 Send up to 2 researched outreach messages.
Day 25 Submit up to 2 applications; verify every attachment.
Day 26 Practise salary and availability scripts aloud.
Day 27 Follow up once on eligible Week 3 conversations.
Day 28 Review dashboard; no new applications.
Day 29 Close stale rows; archive files; note lessons learned.
Day 30 Score the capstone; design the next 30-day sprint.In the tracker, add a Dashboard sheet. Assume Stage is column F and Date Applied is column E. These Google Sheets formulas count your own activity; they do not compare you with other applicants.
Applications sent: =COUNTIF(Tracker!F2:F,"Applied")+COUNTIF(Tracker!F2:F,"Screen")+COUNTIF(Tracker!F2:F,"Interview")+COUNTIF(Tracker!F2:F,"Offer")
Screens: =COUNTIF(Tracker!F2:F,"Screen")
Interviews: =COUNTIF(Tracker!F2:F,"Interview")
Offers: =COUNTIF(Tracker!F2:F,"Offer")
Closed/Rejected: =COUNTIF(Tracker!F2:F,"Closed")
Missing action: =COUNTIFS(Tracker!F2:F,"<>Closed",Tracker!G2:G,"")Add rows for Lane A, Lane B, Resume variant, and Source, then filter during review. With a small personal sample, inspect individual rows instead of treating percentages as market statistics.
// concept
Write Decision Rules Before Results Arrive
Put these rules beside the dashboard and apply them only during weekly review:
| Signal in your tracker | Decision for the next week |
|---|---|
| More than two saved roles fail the same required skill | Pause that lane for one session; build or verify evidence before applying again. |
| Applications have no response yet | Keep tracking; audit fit and attachments, but do not claim the resume is the cause. |
| Screens occur but interviews do not | Review screening answers, availability, and role fit; practise that stage rather than mass-applying. |
| Interviews occur but answers become vague | Add the missed competency to the STAR bank and run a focused mock round. |
| Outreach receives a useful reply | Preserve the specific research step that made the message relevant; do not copy the message blindly. |
| Two planned work blocks are missed from fatigue or other duties | Reduce the next week's volume by 25% and keep the no-search day. |
Change one variable per week. Altering the target role, resume ordering, outreach style, and volume together makes the review inconclusive.
// worked_example
Worked Example
This is a fictional sample, not a result claim. Areeba, a Lahore fresh graduate, has verified university projects in Excel reporting and survey analysis. Her first plan says: Apply to 10 jobs daily, message every hiring manager, and rewrite the resume for anything available.
She replaces that plan with two role lanes, a daily cap of two applications, three Week 1 outreach messages, and two mock sessions. She records the resume variant for each row and rejects roles requiring production SQL experience she lacks.
After Week 1, her sample tracker has six applications, three outreach messages, two mock sessions, and no response yet. She reviews only redacted rows:
You are reviewing my seven-day job-search process, not predicting hiring results.
Inputs:
- Planned actions: [paste Week 1 row]
- Completed counts: [paste dashboard counts]
- Redacted application rows: [remove names, email, phone, address, CNIC]
- Notes from mock interviews: [paste notes]
Return four headings:
1. Completed versus missed actions
2. Evidence of process friction, quoting the relevant row
3. Three possible changes, each tied to evidence
4. One recommended change for Week 2
Rules: Do not invent recruiter opinions, market benchmarks, or reasons for silence.
Do not diagnose my worth or guarantee an outcome. Mark insufficient evidence clearly.A realistic sample response says there is insufficient evidence to explain silence. It flags two missing next-action dates and weak mock answers about survey cleaning, then recommends one focused STAR story—not more applications.
Areeba fixes the rows and schedules STAR practice on Day 13. The decision now cites observable evidence without guessing why employers have not replied.
// failure_cases
Failure Cases to Diagnose
6 cases to diagnose
The calendar is only application days.
Restore sourcing, outreach, interview practice, and review.
Every alert becomes an application.
The tracker shows roles with unmet required qualifications. Add a fit gate and log honest non-application reasons.
Targets become minimum quotas.
Treat table figures as maximum workload caps and stop when quality drops.
The dashboard counts stages inconsistently.
One row says
HR Call, anotherScreening, and formulas miss both. Use one controlled stage list throughout the tracker.AI explains silence as if it interviewed the recruiter.
Delete invented causal claims and ask only for patterns supported by redacted rows and your own notes.
Weekly reviews change everything.
Record one process change and hold other controls steady for a week.
// pakistan_angle
Pakistan Angle
Run separate local and remote lanes. A Karachi or Lahore onsite role may ask about relocation or notice period; a remote role may ask about time-zone overlap, contractor status, and payment method. Research current ranges instead of inventing PKR figures, and verify USD-to-PKR conversion at decision time. Search LinkedIn, Rozee.pk, Mustakbil, and employers' career pages; never pay an “application fee” or send CNIC scans through unsolicited WhatsApp.
Plan around load-shedding, mobile data, and shared devices. Save vacancies and resumes locally, then schedule attachment-heavy submissions for a stable connection. Redact CNIC, home address, phone numbers, references' details, and private WhatsApp chats before using an AI service. Use Urdu or Roman Urdu for networking only when appropriate; follow the job post's language for the application.
// hands_on
Hands-On Exercise
6 steps
Build and run the first seven days of your own 30-day sprint.
Create the private sprint folder and add the five kit parts. Open each file and remove placeholders or unverifiable claims.
Name two role lanes and create one saved search or company-career-page routine for each. LinkedIn's current interface allows alerts from a search; confirm the current steps on its official help page.
Copy the calendar into your tool. Set dates, no-search time, application caps, and two mock-interview appointments.
Create the dashboard formulas and controlled stage list in your tracker. Add live applications only; do not manufacture sample outcomes in the live sheet.
Copy the decision rules beside the dashboard. Adjust workload numbers to your available time while preserving quality caps.
Complete Days 1–7, then run the redacted review prompt. Record one Week 2 change and the tracker evidence behind it. “Done” means a reviewer can find each submitted resume, see all 30 days, reproduce the dashboard counts, and explain the single Week 2 change.
// completion_rubric
Completion Rubric
6 checks — tick as you verify
// sources
Sources
// check_yourself
Check yourself
4 questions · answers and options are taken word-for-word from this course
1 / 4 · diagnose
Your work shows this failure mode: “The calendar is only application days.” What does the lesson tell you to do about it?