Final-Year Campus Placement Prep: A Month-by-Month Timeline (2026)

The Calendar Nobody Shows You Until It Is Late

You are in final year. Someone in your class has a spreadsheet. Someone else is on their 300th LeetCode problem. Your TPO has said "placements are starting soon" three times without giving a date. Nobody has shown you the actual calendar.

Here it is, working backwards from the season instead of forwards from today.

One thing up front, because it matters more than any tip below: most tier-2 and tier-3 colleges start placement prep in August of final year, and that is late. Not fatal. Late. The big mass-recruiter windows open between August and November, and the things they test — aptitude, one language you actually know, basic data structures, a resume that is not embarrassing — take three to four months of steady work, not three weeks of panic before the drive.

If you are reading this in June, you have won something. If you are reading this in October, skip to the compressed plan near the end.

What the Season Actually Looks Like

Rough shape of a final year at a typical Indian engineering college. Your college will differ by a few weeks — ask your TPO for last year's drive list and dates. That single document is worth more than any advice here.

Two things to notice. First, the peak is short — often six to eight weeks. Second, the tail is long. Plenty of people from tier-2 and tier-3 colleges get their first job in February or later, off campus. That is a normal outcome, not a failure.

The Four Tracks You Are Running at Once

Final year is not one preparation. It is four, and they need different amounts of time.

1. Aptitude and verbal — quant, logical reasoning, English. Boring, finite, and the single biggest filter at mass recruiters. You can genuinely finish this one.
2. Coding — one language properly, plus arrays, strings, hashing, sorting, recursion, basic trees. For most service and mid-tier product companies that is the whole ask.
3. Core and projects — DBMS, OS, CN, OOP, plus two projects you can defend for fifteen minutes.
4. The paper and the talking — resume, LinkedIn, HR answers, mock interviews.

Aptitude is the one people postpone and then lose on. Coding is the one people over-invest in at the expense of the other three.

June and July: Build the Base Nobody Sees

This is the only stretch of final year where you have time and no deadline.

• Pick one language and commit. C++, Java or Python. Not all three. Whichever one the tests your campus runs will accept.
• Start aptitude now, 45 minutes a day, every day. Quant first — percentages, ratios, time-speed-distance, permutations, probability. It is school maths you have forgotten.
• Start one project that is not a tutorial clone. Something small that works end to end and whose design decisions you can explain.
• If you can get any internship — paid, unpaid, remote, two months with a local company — take it. On a fresher resume, one real internship outranks four certificates.

By end of July you want: the aptitude syllabus covered once, 60–80 coding problems done, one project deployed somewhere with a public link.

August: Aptitude Done, Resume Drafted

August is when eligibility lists get made. Two things get decided for you here that you cannot fix later.

• CGPA cutoffs. Many mass recruiters filter at 60% or a 6.0–7.0 CGPA, and a lot of them also require no active backlog at the time of the drive. If you have a backlog, clearing it is not a side quest this semester. It is the main quest.
• Documents. Aadhaar, PAN, marksheets from 10th onwards, passport photos, a clean PDF of each. Sounds trivial until a form closes at 11pm and your 12th marksheet is in your home town.

Prep work for August:

• Finish the aptitude syllabus once, then move to timed sectional tests. The real difficulty at mass recruiters is the clock, not the maths.
• Write the first draft of your resume. One page. It will be bad. That is fine, it is a draft.
• Register for the national tests that are open to everyone and not only to your campus. The TCS NQT is the obvious one — it runs outside the campus process and the score travels with you.

September: Coding Volume and the First Mocks

By now the drive calendar is real. September is where preparation turns into performance.

• Coding: steady daily volume on the patterns that actually show up — arrays, two pointers, strings, hashmaps, sorting, binary search, recursion, basic trees and graphs. Depth on twenty patterns beats one problem each from two hundred.
• Do your first mock interview this month, even though you will be bad at it. With a senior, a friend, anyone. The gap between knowing an answer and saying it out loud under pressure is the whole game, and it only closes with reps.
• Rewrite the resume properly. Projects above education if your projects are the stronger half. Links that actually open. No photo, no declaration, no "Objective".
• Fix your LinkedIn. It will be looked at. An empty profile reads worse than a plain one.

October and November: Peak Season, Zero Prep Time

During peak weeks you are not preparing any more. You are executing. Assume drives eat your evenings and some of your attendance.

• Apply to everything you are eligible for, including companies you consider beneath you. The first offer is not the last offer, and having one in hand changes how you interview everywhere else. Campus rules on accepting and freezing vary wildly — read your college's policy before the first drive, not after you clear one.
• After every rejection, write down which round you lost in. Aptitude? Coding? Technical? HR? Three data points and you will know exactly what to fix.
• Revise core subjects in short passes between drives. DBMS normalisation, joins, indexes. OS scheduling, deadlock, paging. CN layers, TCP vs UDP. OOP's four pillars with an example from your own project.
• Sleep. You cannot clear a 9am aptitude test on four hours of sleep, and every year people lose exactly that way.

December and January: The Second Wave

If you are placed, this is when you start choosing instead of accepting. If you are not placed, this is the most important stretch of your year and also the one where people quietly give up.

• Mid-size companies and startups recruit later and hire in smaller batches. They lean less on aptitude cutoffs and more on what you can build. Your projects matter more here than your CGPA does.
• Start the off-campus track properly now. Company career pages, LinkedIn job posts, startup job boards, and referrals. The seniors who graduated one and two years ago are your most under-used asset — they remember being where you are, and most of their companies pay them a referral bonus for it.
• Keep sitting for campus drives. Second-wave drives are less crowded.

February to May: The Long Tail

Campus goes quiet. Hiring does not stop; it moves off campus.

• Treat the hunt like a course with fixed hours. A block every weekday, a target number of applications, and a tracker with company, date, role, status and contact person.
• Apply early. A job post that is two days old has a very different competition profile from one that is two hours old.
• Keep building. A final-semester project that is deployed and used by ten real people is a better interview story than most internships.
• If you graduate unplaced, that is common and recoverable. Off-campus hiring runs all year. The people who suffer most are the ones who stop applying in June out of embarrassment.

If You Are Reading This in October With Nothing Done

The compressed version. Six weeks, no fat.

1. Weeks 1–2: Aptitude only, two hours a day, timed. Resume written and shown to two people. Documents scanned.
2. Weeks 3–4: Coding, one language, the twenty core patterns. One project made presentable with a working README.
3. Weeks 5–6: Core subjects in fast passes. Four mock interviews. Apply to every eligible drive plus every open national test.

You will not become a top-tier candidate in six weeks. You will become an eligible one who does not freeze, and that clears more rounds than you would expect.

What the Numbers Look Like, Honestly

Fresher salary figures in India in 2026, given as bands, not quotes. What you get depends on the company, the role and the city.

• Large IT services mass recruitment: roughly ₹3.5–4.5 LPA, with higher tracks for candidates who clear the advanced test
• Mid-size product companies and funded startups: roughly ₹6–12 LPA
• Top product companies and premium tracks at large firms: ₹15 LPA and up, with far fewer seats and a much harder process

Anyone quoting you a precise "average fresher package" is selling something. Ask your own seniors what they actually signed. That is the only number that reflects your college and your market.

What to Do This Week

Pick the three that apply to you and do them before Sunday.

1. Get last year's drive list and dates from your TPO. Put the months in your phone calendar.
2. Check your eligibility honestly — CGPA, backlogs, gap years. If there is a backlog, plan the clearance now.
3. Start aptitude today, 45 minutes, even if the season is months away.
4. Write the ugly first draft of your one-page resume.
5. Message three seniors from your branch who graduated in the last two years and ask what their process actually looked like.

When the off-campus stretch begins and you are applying every day, the bottleneck stops being ambition and becomes time — writing a tailored mail for each role takes ten minutes you do not have. That narrow problem is what JobApplyAI was built for, and the free tier is enough to see whether it helps you.

The calendar above is not motivational. It is just the shape of the year. Most people lose to the calendar, not to the competition.