Weekly review and decision rules
One hour every Sunday. Look at the numbers, find the one bottleneck, and change one thing for the coming week.
The tracker
One sheet with three tabs: Pipeline (every company and person), Weekly numbers (applications, referral asks, proof messages, replies, screening calls, technical rounds, final rounds, offers) and Interview log.
Follow up once after 5 working days and once more after 10. Then stop.
Read the funnel
| Symptom | Diagnosis | Change |
|---|---|---|
| Few replies to about 60 weekly attempts | Proof or message problem | Rewrite the outreach message. Check every link again. Run the ATS check. Shift hours from job boards to referrals and proof messages. |
| Replies but few screening calls | Targeting problem | Narrow to startups in your project’s domain that use React or Next.js. |
| Screening calls but you fail technical rounds | Skill gap | Double machine coding time. Add paid mocks with working engineers (Topmate or Preplaced, roughly ₹500 to ₹1,500 each). |
| You pass technical but fail the project deep-dive | Ownership gap | Build a feature live without AI every week until you’re fluent. |
| Final rounds but no offer | Communication | Mock HR rounds. Practise the pitch and the gap answer until they sound natural. |
Decision rules
- Day 14: fewer than 3 screening calls means your proof or messaging is broken, not your skill. Fix that before adding volume.
- Day 30: at least one open-source pull request merged or in review. If not, cut other work until it is.
- Day 45 with no offer: widen the net to paid internships of 3 to 6 months with a conversion clause (stipend at least ₹15,000 to ₹20,000 a month), junior QA-automation or support-engineer roles at product companies where you can move into development, and services-company walk-in drives.
- Runway checkpoint: before you start, write down the date your savings run out, minus a safety margin. If there’s no offer by then, continue the same system from home rather than spending your savings on the hostel. Bengaluru is worth it for meetups and in-person rounds. It is not worth debt.
Calendar slowdowns
Hiring slows around Dussehra, Diwali week, and the second half of December. Use those weeks for machine coding, a lightning talk and follow-ups. Silence then is normal.
If you have a mentor or senior friend
Ask for exactly this, about 2 to 3 hours a week: a Sunday funnel review, a midweek live mock (alternate defend-the-code and machine coding), referrals and introductions from their network, and in week 1, a click-through of every link on your resume.
What not to do
- Don’t learn a new framework, language or cloud platform during the search.
- Don’t start a new big project. Deepen, deploy and defend the ones you have.
- Don’t spend more than a day on portfolio design, or collect certificates.
- Don’t mass Easy Apply. Every application gets a person contacted.
- Don’t pay anyone for a job.
- Don’t work 7 days a week. Burnout by week 4 kills more job searches than lack of skill.