Placements · Roadmap
A 12-week placement preparation plan for final-year students
21 Nov 2026 · By Akshay, software engineer, India
A realistic week-by-week plan for campus placements: DSA patterns, core subjects, aptitude, one solid project, your resume and mock interviews, in about 3 hours a day.
Most students don’t struggle in placements because they aren’t smart enough. They struggle because they prepare in random order: a bit of DSA, a video on DBMS, a panic week of aptitude before the first test. This plan fixes the order. It assumes about 3 hours a day, six days a week, for 12 weeks.
The shape of a day
| Time | What |
|---|---|
| 90 min | DSA: one pattern, 3–4 problems |
| 45 min | A core subject or your project (alternate days) |
| 30 min | Aptitude: one topic, one timed set |
| 15 min | Revision: yesterday’s mistakes, flashcards |
On the seventh day, rest, or catch up on whatever slipped.
Weeks 1–2: foundations
- Pick one language for coding rounds (C++, Java or Python) and stop switching.
- DSA basics: arrays, strings, hashing, sorting, binary search. Solve easy problems until the syntax stops slowing you down.
- Aptitude: percentages, ratios, time and work.
- Choose your project (see below) and set it up.
Weeks 3–6: the core patterns
- DSA: two pointers, sliding window, recursion and backtracking, linked lists, stacks and queues, then trees.
- Core subjects: DBMS and SQL first (normalisation, indexes, transactions, joins), a favourite in campus rounds; then OOP.
- Aptitude: profit and loss, time–speed–distance, permutations and probability, plus a logical reasoning set every week.
- Project: build the main features. Commit every day.
- End of week 6: write your resume. One page, with your project and real numbers.
Weeks 7–10: depth and speed
- DSA: graphs (BFS, DFS, shortest paths), heaps, and dynamic programming (1D first, then 2D). Do a timed contest every weekend.
- Core subjects: Operating Systems (processes and threads, scheduling, deadlocks, memory and paging), then Computer Networks (the layers, TCP vs UDP, what happens when you type a URL).
- Aptitude: full timed sections in the pattern of the companies on your list.
- Project: deploy it, so it has a live link, and write a short README: what it does and how you built it.
Weeks 11–12: interviews
- Two mock interviews a week: one coding, one on core subjects and your project. Think aloud.
- Revise your mistakes list, not everything.
- Prepare your HR answers: tell me about yourself, why this company, a problem you solved.
- Take full-length practice tests for your target companies.
One project, done properly
One finished, deployed project you can explain line by line beats five half-built ones. Build something real (a placement tracker, an expense splitter, a booking system) and be ready for: why this design, what breaks at scale, what would you change.
Track it
Tick things off as you go. It’s the difference between “I studied a lot” and “I covered everything”. This plan as a checklist puts real dates on every week and saves your ticks on your phone, with a Google Calendar reminder for the daily 3 hours. Meanwhile, practise with our interview questions and code-reading drills, and learn JavaScript properly with Inside JavaScript.
Free lessons with videos, code-reading drills and interview questions.