Month 1 is not about applying for jobs. It is about building the minimum viable technical foundation that makes you worth calling back when you do apply. The most common fresher mistake is skipping this phase and applying immediately — resulting in failed aptitude tests, blank technical interviews, and zero shortlists.

🎯 The 3-Track Decision: Which Path Are You On?

Before learning anything, decide your track. Trying to learn everything simultaneously is the fastest way to learn nothing deeply enough to impress anyone.

• Track A — Software Development: Java or Python → Spring Boot or Django → MySQL → REST APIs → Git. Target: TCS, Infosys, Wipro developer roles, product startups.
• Track B — Testing / QA: Java or Python basics → Selenium → Manual testing concepts → JIRA → SQL. Target: Accenture testing roles, HCL, Wipro QA positions.
• Track C — Cloud / DevOps (Emerging 2026 Path): Linux basics → AWS Cloud Practitioner → Docker intro → Git. Target: HCL, Tech Mahindra cloud roles, fast-growing mid-size IT companies.

⏱️ Daily Schedule That Actually Works

• Morning (2 hours): New concept learning — follow one structured course (see free courses section below)
• Afternoon (1.5 hours): Coding practice — LeetCode, HackerRank, or building a mini-feature
• Evening (30 minutes): Review what you learned, push code to GitHub, read one IT industry article

Month 2 is where you convert your Month 1 knowledge into visible, shareable proof of skills. This is the single most underutilised phase in the average Indian fresher’s job search — and it’s the phase that separates candidates who get interview calls from those who don’t.

Recruiters cannot verify that you “know Java” from a resume bullet. They CAN verify that you built a working Java application and pushed it to GitHub with proper documentation. That’s the difference between a claim and evidence.

🔑 The Two-Project Minimum Rule

You need at least two complete, deployed projects on GitHub before you start applying. Not two tutorial-follow-alongs — two projects where you made independent design decisions, hit real errors and debugged them, and can explain every line of code you wrote.

💡 Project Ideas That Stand Out in 2026

• Track A — Dev: Job portal with search and filter, expense tracker with analytics dashboard, student management system with REST API, e-commerce backend with order tracking
• Track B — QA: Automated test suite for an existing public website (using Selenium), bug reporting tool with JIRA integration, test case management mini-application
• Track C — Cloud: Deploy a web app on AWS EC2 with auto-scaling, set up a CI/CD pipeline using GitHub Actions, create a serverless function with AWS Lambda and API Gateway

📝 Writing Your Resume Alongside Projects

Month 2 is also when you build your core resume — because your projects are your biggest asset and you should document them while the details are fresh. Follow the resume structure covered in our Silpa Careers Fresher Resume Guide and use each project as a rich, bullet-point-heavy section with measurable outcomes.

Month 3 is when you begin applying — but with a system, not a spray-and-pray approach. The single biggest mistake freshers make during this phase is applying to 100+ companies with one generic resume and then wondering why they never hear back.

🔢 The 10-10-10 Weekly Application Rule

Apply to exactly 30 positions per week, split across three tiers:

• 10 Tier-1 targets: Big IT companies (TCS, Infosys, Wipro, HCL, Accenture, Tech Mahindra) — through official career portals and off-campus drives. Lower hit rate but highest brand value if successful.
• 10 Tier-2 targets: Mid-size IT companies (Mphasis, Hexaware, Cognizant, LTIMindtree, Capgemini) — often faster hiring cycles and higher fresher-to-interview conversion rates.
• 10 Tier-3 targets: Startups, product companies, and local IT firms via LinkedIn, Unstop, and Internshala — best chance of getting real project experience that accelerates your career.

📋 Tailoring Each Application — The 15-Minute Rule

For every application, spend 15 minutes: read the job description carefully, adjust your resume summary to mention the specific role, reorder your skills to match the JD’s priority keywords, and personalise the first line of your cover email if one is required. This sounds like a lot — but 30 tailored applications a week convert far better than 100 copy-paste submissions.

📊 Track Everything in a Spreadsheet

Create a simple Google Sheet with columns: Company, Role, Date Applied, Platform Used, Resume Version, Status (Applied / Shortlisted / Rejected / Interview Scheduled), and Notes. This tracking system does three things: it prevents duplicate applications, it tells you which platforms are generating results, and it gives you psychological clarity — you can see your progress instead of feeling like you’re shouting into the void.

Month 4 is when applications start generating responses — and you need to be ready to convert shortlists into offers. Interview preparation runs parallel to applying from Month 3 onwards, but Month 4 is when you go deep on mock interviews and targeted technical revision.

🧠 Technical Interview Prep Plan

• OOPs (Week 13): Master all four pillars with code examples in your chosen language. Be able to explain abstract class vs interface, polymorphism types, and encapsulation — with live code if asked.
• DBMS + SQL (Week 13–14): Practice writing JOIN queries, subqueries, GROUP BY, and HAVING clauses from scratch. Revise normalization (1NF–3NF) with table examples. Understand ACID properties with the bank transfer example.
• OS + Networks (Week 14): Process vs Thread, Deadlock conditions, OSI model layers, TCP vs UDP — all with real analogies ready. Conceptual depth over memorised definitions.
• DSA Coding (Weeks 13–16 ongoing): 2 LeetCode problems daily — one Easy, one Medium. Focus on arrays, strings, hashmaps, linked lists, and trees. Time yourself to 25 minutes per problem.

Month 5 and 6 are where the majority of freshers either break through or burn out. You have been applying for 2–3 months. You may have had rejections, near-misses, or deafening silence. This section is specifically about how to keep going — productively, not desperately.

🔄 The Month 5 Review — Diagnose Before You Double Down

Before blindly increasing application volume, run a diagnostic. Look at your tracking spreadsheet and answer these questions honestly:

• Are you getting shortlists? If less than 5% of applications are generating responses, the problem is your resume or your application targeting — fix these before applying more.
• Are you getting interview calls but failing at aptitude? The problem is test preparation — spend a week exclusively on timed aptitude practice (PrepInsta, IndiaBix).
• Are you reaching HR but not getting offers? The problem is communication and HR preparation — do 3 more mock HR interviews this week before your next real one.
• Are you getting technical interviews but failing them? The problem is technical depth — identify the specific topic where you struggled and spend one week going 3 layers deep on that topic.

📈 New Actions to Add in Month 5–6

• Attend virtual job fairs: Naukri, LinkedIn, and Unstop regularly host virtual hiring events — register for all of them. Direct recruiter contact at these events bypasses the ATS layer entirely.
• Referrals: Reach out to seniors, alumni from your college, or LinkedIn connections who work at target companies. A referred application at TCS, Infosys, or Wipro moves through screening 3x faster than a portal application. Message them professionally — one specific ask, not a vague “please help me get a job.”
• Third-party recruiters: Register on iMocha, AMCAT, and eLitmus — these are third-party assessment platforms that forward your profile to partner companies when you score well. Many Indian IT companies source freshers exclusively through these platforms.
• Add one new certification: An AWS Cloud Practitioner or Google IT Support certificate completed in Month 5 adds a new keyword to your resume and signals continued learning momentum to recruiters.