Guides › Placements
6-Month Placement Preparation Plan (Month by Month)
A realistic 6-month plan for campus placements: DSA, aptitude, CS fundamentals, projects, resume and mock interviews — with weekly targets.
Six months is enough time to go from "I know some C/Java" to "I can clear an online assessment and hold my own in a technical interview" — if you spend it on the right things in the right order. This plan assumes about 2–3 hours a day on weekdays and a little more on weekends, alongside college.
Already in your final semester with less time? Follow the same order, but compress months 1–2 into three weeks and drop the "nice to have" items.
Turn this plan into days: enter your placement date and daily hours in the Study Planner and it builds a day-by-day schedule — DSA problems, aptitude, CS subjects and SQL — that you can tick off every day.
The plan at a glance
| Month | Main focus | Side track | You should be able to… |
|---|---|---|---|
| 1 | One language + basics of DSA | Aptitude: arithmetic | Write loops, functions and array code without looking things up |
| 2 | Arrays, strings, hashing, recursion | Aptitude: reasoning | Solve most Easy problems in 20 minutes |
| 3 | Linked lists, stacks, queues, trees | SQL + DBMS | Solve Easy problems fast and many Mediums |
| 4 | Graphs, greedy, dynamic programming | OS + networks | Recognise the pattern behind a Medium problem |
| 5 | Project + resume | Mock tests every week | Explain your project end to end |
| 6 | Mock interviews + revision | Company-specific practice | Walk into interviews calm |
Month 1 — pick one language and get fluent
Choose C++, Java or Python and stay with it. Interviewers do not care which one; switching languages halfway is what costs you time.
- Learn input/output, conditionals, loops, functions, arrays and strings properly.
- Learn your language's standard library:
vector/map/setin C++,ArrayList/HashMapin Java,list/dict/setin Python. - Understand time complexity — why a nested loop over
nitems is O(n²) and why that matters whennis 10⁵. - Solve the first 30–40 problems of the Codify DSA Sheet (basics and patterns).
Aptitude side track: percentages, profit and loss, simple and compound interest, ratios and averages. Do 15 questions a day in aptitude practice.
Month 2 — the core of DSA
This is the month that decides most online assessments.
- Arrays: prefix sums, two pointers, sliding window, sorting-based tricks.
- Strings: frequency counting, palindromes, anagrams, basic pattern matching.
- Hashing: "have I seen this before?" in O(1) — the most useful single idea in DSA.
- Recursion and backtracking: subsets, permutations, N-Queens style problems.
- Binary search: on sorted arrays first, then "binary search on the answer".
Target 60–80 problems this month. If you are stuck for more than 30–40 minutes, read the hint, then the approach, and re-solve it the next day without help.
Aptitude side track: number series, coding–decoding, directions, blood relations, seating and ranking.
Month 3 — data structures
- Linked lists (reversal, cycle detection, merging), stacks (next greater element, valid brackets), queues and deques.
- Trees: traversals, height, diameter, lowest common ancestor, binary search trees.
- Heaps / priority queues: top-K problems, merging sorted lists.
Side track — SQL and DBMS. Almost every service company and many product companies ask SQL. Learn SELECT, WHERE, GROUP BY, HAVING, joins and subqueries, then practise on the SQL practice problems until joins feel natural. On the theory side: normalisation, keys, transactions and ACID, indexing — the DBMS notes cover each with worked examples, and the Top 50 DBMS and Top 50 SQL questions are your revision list.
Month 4 — graphs and dynamic programming
- Graphs: BFS, DFS, connected components, topological sort, shortest paths (Dijkstra), union–find.
- Greedy: interval scheduling, activity selection, and why greedy sometimes fails.
- Dynamic programming: start with 1D (climbing stairs, house robber), then 2D (grid paths, LCS, knapsack). Always write the recursive solution first, then add memoisation.
Side track: operating systems (processes vs threads, scheduling, deadlock, paging) and computer networks (OSI/TCP-IP layers, TCP vs UDP, what happens when you type a URL). The CS Fundamentals roadmap lists exactly what to cover; for revision use the solved-example notes on CPU scheduling, deadlocks, paging and TCP/IP, and the Top 50 OS questions.
Month 5 — one solid project and your resume
One well-understood project beats three tutorial clones.
- Build something with a real user flow: login, a database, a few screens. A MERN or Spring Boot app is ideal. Pick one from Projects (each has a step-by-step guide) — projects by role tells you which suits the job you want.
- Deploy it and put the live link on your resume.
- Be ready to answer: Why this design? What was the hardest bug? What would you change with more time?
Write your resume this month (see our fresher resume guide) and tidy your LinkedIn and GitHub. Start taking one timed aptitude mock every week in the mock test and one weekly contest for coding speed.
Month 6 — mock interviews and revision
- Do at least 5 mock interviews with friends or seniors. Explaining your thinking out loud is a separate skill from solving problems. On days nobody is free, use the AI mock interview — voice mode even scores your pace and filler words.
- Play a few Code Battles each week: racing another coder on the same problem is the closest practice to a timed online assessment.
- Revise with spaced repetition: interview flashcards for theory, and re-solve the problems you marked as hard.
- Read the HR side too — 20 HR questions and how to answer them.
- Before each company's test, look up its recent pattern and do 2–3 timed practice papers. Company guides: TCS NQT, Infosys, Wipro, Accenture, Cognizant — and how the whole campus process works.
How to track progress
Every Sunday, write down three numbers: problems solved this week, your mock test score, and the topic you are weakest at. Next week, spend the first two days on that weakest topic. Your dashboard streak and XP make this easy to see at a glance.
Common mistakes
- Watching instead of solving. A two-hour video feels productive; 45 minutes on one problem actually is.
- Skipping aptitude because "it's easy". Many students who code well get filtered out in the aptitude round.
- Collecting resources. One problem sheet, one playlist per subject, one roadmap — then execute.
- No revision. If you solved a problem once three months ago, you probably cannot solve it today. Re-solve.
Six months goes quickly. Start today with the Placement Preparation roadmap and tick off the first topic.
More guides
- How to Use Codify: A 7-Day Start Plan — New here? Pick a roadmap, make a study plan, start the DSA sheet, revise with notes, practise for placements and test yourself — one step a day, then a daily routine.
- Infosys Preparation Guide: Online Test, Pseudocode and Interview — Roles (SE, DSE, SP), what each section of the Infosys online test checks, how to crack pseudocode and reasoning, a 4-week plan and the interview.
- Wipro Elite NLTH Preparation: Aptitude, Essay and Coding — The Wipro fresher test round by round — quant, logical and verbal, the written essay, two coding problems — plus a 3-week plan and interview tips.
- Accenture Preparation Guide: Cognitive, Technical, Coding and Communication — Every Accenture round explained — cognitive, MS Office/networking/cloud technical MCQs, pseudocode, coding and the spoken-English test — with a 4-week plan.