The Third-Year Timeline: A Month-by-Month Plan Before Placement Season
Most students start preparing for placements about two months too late and then compress a year of work into a panicked semester. This is what the third year looks like when it is planned properly — month by month, with what to drop.
The students who do well in placement season are almost never the ones who worked hardest during it. They are the ones for whom the season was a harvest rather than a scramble — people who arrived in August with a resume that was already true, projects already finished, and a preparation routine that had been running long enough to be boring.
The students who struggle are usually not less capable. They started in June, discovered that data structures take months rather than weeks, and tried to build a portfolio project in the same fortnight they were revising for aptitude tests. Both things came out thin.
The difference is almost entirely timing, and timing is the one input that is completely under your control in the third year. Here is a plan that spreads the work across twelve months instead of compressing it into two.
What placement season actually tests
Before the calendar, be clear about what you are preparing for, because it is a shorter list than students imagine and each item has a different lead time.
| What is tested | How long it takes to build | When it must be ready |
|---|---|---|
| Aptitude and reasoning | 6-10 weeks of light practice | Month 9 |
| Coding fundamentals and DSA | 6-9 months, slowly | Month 10 |
| One or two real projects | 2-3 months each | Month 9 |
| CS core subjects | 6-8 weeks of revision | Month 10 |
| Resume | A weekend, but only if the rest exists | Month 10 |
| Interview communication | Months of small exposure | Month 11 |
| An internship | Applied 6+ months ahead | Summer |
The lead times are the point. DSA and communication cannot be crammed; aptitude and CS revision can. That asymmetry tells you what to start early and what to leave until the end, and it is the skeleton of everything below.
Months 1-3 (the start of third year): build the base
The first three months are for the two things that take the longest and are the least urgent, which is precisely why they get postponed.
The first is programming fluency. Not competitive programming — fluency. One language you know well enough to stop looking things up: arrays, strings, maps, sorting, recursion. If solving a straightforward problem still involves searching for basic syntax, that is the gap to close before anything else. A slow, consistent hour a day for three months does this comfortably.
The second is one real project, started now and finished. Not a tutorial reproduction. Something with a user, a database, and a deployment, however small. It will take longer than you expect, which is exactly why it should start when nothing else is competing for your attention. Our guide on the final-year project that actually helps your placement sets out what separates a project that gets asked about from one that gets skipped.
Alongside those, do two small administrative things: create a clean GitHub profile and start using it properly, and write a one-page resume even though it is currently thin. The empty spaces on that page are the most honest to-do list you will get all year.
Months 4-6: depth, and the internship application
By now the base should be steady enough that you can add structure.
Move from fluency to actual data structures and algorithms, in a planned order rather than by random problem-picking. Arrays and strings, then hashing, then two pointers and sliding window, then stacks and queues, then trees, then graphs, then dynamic programming last. Volume matters far less than students believe; understanding a pattern well enough to recognise it in an unfamiliar problem is the entire skill. How much DSA is enough has the realistic version of this, including the point at which additional problems stop paying.
This is also the window where summer internship applications happen, and it closes earlier than most students realise. Applications for summer internships often run six months ahead. If you want an internship — and you do, because it is the strongest single line on a fresher resume — the applications go out now, not in April. If you have nothing to show yet, landing a first internship with zero experience is written for exactly this position.
Finish the project from months 1-3 in this window. Deploy it. Write a proper README. A project that exists on a live URL is worth several that exist only as repositories.
Months 7-8 (the summer): the highest-leverage weeks of the degree
Whatever you do with this summer is what your resume will mostly be made of.
The best version is an internship, even an unglamorous one, because it produces the two things nothing else does: a verifiable line of experience and a professional reference. If it goes well it can produce a great deal more, and how freshers actually convert a PPO explains what that conversion actually depends on.
If there is no internship, the second-best version is a serious build — a substantial project, an open-source contribution to a real repository, or freelance work for an actual client. Two months of undistracted time is more than most people get again for years. Squandering it and then explaining in October that you were unwell for the summer is a conversation I have too often. Open-source contributions from an average college is a good starting point if you want a path that does not depend on anyone hiring you first.
Whichever it is, keep a plain-text log of what you did each week. In September, when you sit down to write the resume, that log is the difference between accurate bullet points and vague ones.
Months 9-10: convert everything into a process
Now the compressible things start, and the tone changes from building to preparing.
Begin aptitude and reasoning practice — quantitative, logical, verbal — at a modest daily volume. Six to ten weeks is genuinely enough for most students, but only if it is continuous. Clearing the online assessment round covers what these tests actually look like now, including proctoring.
Revise CS core subjects: operating systems, databases, networks, and object-oriented concepts. Companies ask about these more than students expect and more than students prepare for, and a month of structured revision covers the ground.
Rewrite the resume properly, now that there is something to put in it. One page, evidence-first, with links that work. Rebuilding a fresher resume for callbacks is the detailed version — and it is worth doing before the placement cell asks for it, because that deadline always arrives sooner than announced.
Start being able to talk about your own work. Most students can build a project and cannot describe it, which costs them in interviews where the project round is the friendliest part of the process. Practise out loud, to a person.
Months 11-12: the season
By the time the season begins, the work should be maintenance rather than acquisition.
Keep the DSA practice going at a lower daily volume so the recall stays warm. Do mock interviews with actual humans — seniors, friends, a counsellor, anyone who will ask follow-up questions rather than nod. Prepare the behavioural round properly, because it is where offers get lost late; the HR round is not a formality explains how.
Then protect two things that nobody puts in a preparation plan: your sleep and your capacity to keep going after a rejection. The season is long, most people are rejected several times before an offer, and the students who do best in November are usually the ones who were still functioning in December. Our piece on protecting focus and mental energy during placement season is about this specifically, and it is not a soft topic.
How many hours a day does this actually take?
Less than students fear, and it is spread differently than they expect. The plan above is roughly ninety minutes a day for the first half of the year and two to three hours a day in the last four months, plus whatever your summer becomes.
That is achievable alongside a full semester, and it is achievable specifically because it is spread out. The same total effort compressed into the two months before the season is about seven hours a day on top of final-year coursework, which is why students who start late do not simply do less — they do worse work, in a state of exhaustion, and arrive at interviews already depleted.
A weekly shape that holds up over a year looks something like this: five weekdays of one focused hour on whatever the current priority is, one weekend session of three or four hours on the project, and one hour somewhere for the things that are easy to skip — reading job descriptions, updating the resume, talking to a senior who graduated last year.
Two rules make it stick. Keep the daily block at the same time so it stops requiring a decision, and never let the streak break twice in a row. Missing a day is normal; missing three is how a plan quietly ends in October.
Protect one non-negotiable: do not run this at the cost of your sleep or your semester results. A student who arrives at placement season with a burnt-out brain and two new backlogs has traded a strong asset for a weak one.
What if I am already in the middle of third year and behind?
Most students reading this will be, and the honest answer is that a compressed plan still works — but only if you cut something rather than doing everything badly.
Rank by lead time. What cannot be compressed comes first: coding fluency and DSA, and at least one finished project. What can be compressed comes later: aptitude, CS revision, the resume itself. If you have six months, that means DSA every day starting now, one project scoped small enough to actually finish, and aptitude deferred to the last two months.
Then drop things honestly. A student with six months cannot do a full DSA syllabus, three projects, two certifications, a hackathon, and daily aptitude practice. Attempting all of it produces a resume of half-finished items, which reads worse than a shorter list of complete ones. Certifications in particular are the most over-purchased item on the list — which certifications are actually worth it is worth reading before spending money on one.
The plan is not the point. Starting early enough that the plan is unnecessary is the point, and third year is when that is still available to you.
Not sure where you stand in the timeline? Talk to a Career Call counsellor. Tell us your month, your branch and what you have built so far, and we will tell you exactly what to start this week and what to leave alone.