What you will learn
- Set up a structured 30-day job search routine with weekly goals
- Use a job application tracker to manage applications, follow-ups, and pipeline stages
- Avoid the two failure modes: spray-and-pray (200 generic applications) and paralysis (0 applications)
Why this matters
The average Indian CS fresher's job search is chaotic: apply to 100 jobs on Naukri in one weekend, hear nothing, get demoralized, stop for a month, panic, repeat. A structured routine replaces anxiety with a system. Students who track their pipeline, send targeted applications, and follow up consistently get offers 2-3x faster than those who rely on mass-applying through portals.
The two failure modes
Failure mode 1: Spray-and-pray
Applying to 200 jobs on LinkedIn Easy Apply with the same generic resume. Result: 200 rejections and zero signal about what to improve.
Failure mode 2: Paralysis
Spending weeks "perfecting" your resume and portfolio, never actually applying. Result: zero applications, zero feedback, zero interviews.
The fix: A weekly routine that forces both quality (targeted applications) and quantity (a minimum number per week).
The weekly rhythm
Monday: Research (1 hour)
- Identify 10-15 job listings that match your skills
- Save them in your tracker (see below)
- For each, note: company name, role, team, required skills, application deadline, and one person at the company you could contact
Tuesday-Wednesday: Apply (2 hours total)
- Submit 5-8 targeted applications
- Tailor your resume header/summary to each role (not a full rewrite — adjust the top line and reorder projects)
- Write a 2-sentence cover note if the portal allows it
Thursday: Outreach (1 hour)
- Send 3-5 cold emails or LinkedIn DMs to people at your target companies
- Follow up on messages sent last week (one follow-up per person, max)
- Engage with 2-3 posts from people at target companies (meaningful comments, not "Great post!")
Friday: Skill + content (1 hour)
- Work on a project (keep GitHub active)
- Post one technical update on LinkedIn (a project milestone, a learning, a short write-up)
- Review any interview prep material for upcoming interviews
Weekend: Interview prep (as needed)
- Practice 2-3 behavioral questions using STAR-Lite
- Do 1-2 coding problems on LeetCode/Codeforces
- Review any company-specific material for upcoming interviews
The job application tracker
Use a spreadsheet (Google Sheets works fine). Here is the schema:
| Company | Role | Source | Date Applied | Status | Contact Person | Follow-up Date | Notes |
|---------|------|--------|-------------|--------|----------------|----------------|-------|
Status values:
- Saved — found the listing, haven't applied yet
- Applied — application submitted
- Referred — someone referred you internally
- Screen — recruiter screen scheduled/completed
- Technical — technical round scheduled/completed
- Behavioral — behavioral round scheduled/completed
- Offer — received an offer
- Rejected — received a rejection
- Ghosted — no response after 3+ weeks and 1 follow-up
Tracker rules:
- Update the tracker the same day you apply or receive a response
- Set a follow-up date for every application (2 weeks after applying)
- Review the tracker every Monday during your Research hour
- If an application has been in "Applied" status for 3 weeks with no response, move it to "Ghosted" and move on
30-day targets
| Week | Applications | Outreach messages | Interviews | Portfolio updates |
|---|---|---|---|---|
| Week 1 | 5-8 | 3-5 | 0 (pipeline is empty) | 1 GitHub commit |
| Week 2 | 5-8 | 3-5 | 0-1 (screens start) | 1 LinkedIn post |
| Week 3 | 5-8 | 3-5 | 1-3 (technical rounds) | 1 GitHub commit |
| Week 4 | 5-8 | 3-5 | 2-4 (deeper rounds) | Reflect + adjust |
After 30 days: review your pipeline. If you have 0 screens from 25+ applications, your resume needs work. If you get screens but fail technical rounds, increase coding practice. If you pass technical but fail behavioral, practice STAR-Lite. The tracker gives you data to diagnose the problem.
Where to find jobs (India, 2026)
High-signal sources:
- Company career pages directly — always check the source; job portals are often delayed
- LinkedIn Jobs — filter by date posted (last week), location, and experience level
- AngelList / Wellfound — best for startup roles
- Instahyre — recruiter-first platform; strong for product companies
- Cutshort — good for mid-stage startups
- Twitter/X — follow CTOs and engineering managers; many roles are posted there first
Low-signal sources (use sparingly):
- Naukri.com — volume is high but signal-to-noise ratio is low; use only for service companies
- Indeed — mostly non-tech or service company listings
- Random Telegram/WhatsApp "job groups" — high noise, many scams
Highest-signal source:
- Direct referrals — reach out to alumni, seniors, and connections at target companies. A referred application is 4-10x more likely to get a response.
Dealing with rejection and silence
The math of job searching
Expect a funnel like this:
- 30 applications → 8-10 recruiter screens → 4-5 technical interviews → 1-2 offers
This means 90-95% of your applications will result in rejection or silence. This is normal. It is not a reflection of your ability — it is the base rate of the process.
When you get rejected:
- Ask for feedback (politely): "Thank you for letting me know. If you're able to share any specific feedback on my interview, I'd really appreciate it for my improvement."
- Log it in your tracker with any feedback received
- Move to the next application — do not dwell
When you get ghosted:
- Send one follow-up after 2 weeks: "Hi [Name], following up on my application for [Role] submitted on [Date]. Still very interested — happy to provide any additional information."
- If no response after the follow-up, mark as "Ghosted" and move on
- Do not take it personally — companies ghost candidates constantly. It says nothing about you.
The mental game
- Set a daily time limit — job searching for 8 hours a day leads to burnout. 1-2 focused hours is enough.
- Track leading indicators, not just outcomes — "I sent 5 targeted applications this week" is a success metric you control. "I got an interview" depends on factors you cannot control.
- Batch rejections — check email/portals twice a day, not every 30 minutes. Constant checking creates anxiety.
- Maintain your routine — keep coding, keep building. The worst thing you can do during a job search is stop developing skills.
Quick quiz
Q: After 30 targeted applications over 4 weeks, you've received zero recruiter screens. What should you do?
How to explain it in an interview
"I run my job search like a project with weekly sprints. Every Monday I research roles, Tuesday-Wednesday I submit 5-8 targeted applications, Thursday I do outreach, and Friday I work on my portfolio. I track everything in a spreadsheet with status, follow-up dates, and notes. After 30 days, the data tells me exactly where my funnel is breaking — resume, technical, or behavioral — so I know what to improve."