You have roughly three months before placement activity becomes serious, with three gates to clear: aptitude, coding and interviews. A vague plan usually collapses when classes, projects and missed days interfere.
This schedule orders those streams and gives you weekly hours, checkpoints and a recovery rule. A useful plan must survive one bad Tuesday.
What the 90 days must deliver
Companies commonly filter candidates through an aptitude assessment, a coding round, then technical and HR interviews. Processes vary, but those abilities remain central, so the plan strengthens them in that order.
Aim for 25 to 30 focused hours weekly: three to four hours around weekday classes, with longer weekend blocks for mocks, review and project explanations. Count only deliberate work, not a lecture playing while you scroll.
A sustainable 25-hour week beats a brief 50-hour burst. By Day 90, you should be able to:
clear timed aptitude sets with controlled accuracy;
solve common easy and medium coding patterns and explain your approach;
answer core CS questions in DBMS, OS, networks and OOP;
present your projects and behavioural examples clearly;
track applications without starting each assessment from zero.
The stream split across three phases
The allocation shifts as your immediate bottleneck changes.
Phase | Main streams | Weekly allocation | Planned total |
|---|---|---|---|
Days 1 to 30 | Aptitude and coding foundations | 10 hours aptitude, 10 coding, 5 CS fundamentals | 25 hours |
Days 31 to 60 | DSA depth and CS subjects | 15 hours DSA, 8 CS, 4 aptitude maintenance | 27 hours |
Days 61 to 90 | Interviews, revision and applications | 10 hours mocks and interview prep, 8 revision, 6 applications | 24 hours plus 1 flexible catch-up hour |
The sums are 25, 27 and 24 hours. Phase three adds one flexible catch-up hour while leaving room for a company assessment.
Give each day one main block and one smaller maintenance block to reduce context switching without losing continuity.
A typical weekday can use 90 to 120 minutes for the main stream and 45 to 60 minutes for maintenance, with the remaining time for review. Reserve longer weekend sessions for a timed mock and its analysis. Keep the phase proportions even when your exact college timetable differs.
Phase 1, Days 1 to 30: clear aptitude and warm up coding
Rotate quantitative aptitude on Monday and Thursday, reasoning on Tuesday and Friday, and verbal ability on Wednesday. Use Saturday for a mixed timed test and Sunday for review or catch-up.
The aptitude for placements guide supplies the section order. About 8,000 published aptitude questions in the KnowledgeGate bank provide practice, but useful review matters more than volume. After each timed set, classify misses as concept, calculation, reading or time pressure.
Choose C++, Java or Python for the full phase. Switching languages repeatedly wastes problem-solving time. Review syntax only as needed, then practise arrays, strings, hashing and two-pointer patterns.
Target two or three easy-to-medium problems a day. For each problem:
restate the input, output and constraints;
write a direct approach before optimising;
test edge cases by hand;
code and measure the result;
record the pattern if you needed help.
Keep five weekly hours for compact OOP, DBMS, OS and networks notes rather than a complete subject pass. These notes become recall sheets in later phases.
At Day 30, clear a full aptitude mock comfortably under relevant test conditions. Then solve an easy array or string problem in under 20 minutes, including a spoken explanation and edge-case checks.
Phase 2, Days 31 to 60: DSA depth and CS subjects
DSA now receives the largest share. Move through linked lists, stacks and queues, trees and BSTs, recursion, sorting and searching, then graph and dynamic-programming basics. Give each topic a few days instead of touching a new label every session.
Aim for two medium problems daily. When stuck, identify the reusable decision, such as when a hash map removes a nested loop, two pointers preserve an invariant, or overlapping subproblems make dynamic programming useful. Do not memorise final code.
Run one CS subject focus each week:
DBMS: normalization, keys, joins, indexing and transaction basics;
Operating systems: processes, scheduling, synchronization, deadlocks and memory;
Computer networks: OSI and TCP/IP, addressing, transport and common protocols;
OOP: encapsulation, abstraction, inheritance and polymorphism with code examples.
In short recall sessions across the week, close your notes and explain five common questions aloud. Interview answers must be retrieved and expressed, not merely recognised.
At Day 60, solve most medium questions from covered patterns, although an unfamiliar hard problem may still stop you. Also explain five common topics from each CS subject without notes and handle one follow-up on each.
Phase 3, Days 61 to 90: interviews, revision and applications
Schedule two or three weekly mocks: one live DSA session while talking through code, one rapid-fire CS fundamentals round, and one HR, resume or project discussion.
Record exactly where each answer broke and fix it within that week. "Weak in OS" is vague; "could not distinguish starvation from deadlock" is actionable.
Stop expanding the syllabus around Day 75. During the final two weeks, re-solve flagged coding problems without looking at old code, review CS one-pagers, rehearse project stories and repeat timed assessments. Revision should now dominate new learning.
Applications run in parallel. Track role, source, date, stage, next action and test requirement across both on-campus and off-campus routes. The Placement Preparation category collects wider material, while the coding round strategy guide gives an online-round plan.
Before a scheduled company assessment, check its stages in your tracker and use the final preparation session for the relevant pattern. Do not abandon the broader phase plan for every new opening.
By Day 90, have a clean resume, concise explanations for every project, revised DSA patterns, clear CS fundamentals and no forgotten application action.
The recovery rule for missed days
A missed day is not a failed plan. Never miss twice: resume exactly where you stopped, without doubling the next day's load as punishment and creating two weak sessions.
Protect phase checkpoints and flex daily tasks. If a week slips, shorten the lowest-value maintenance work, not the main DSA block or scheduled mock. That may mean a shorter verbal drill or combining tracker cleanup with applications.
Keep Sunday light enough to absorb spillover. A catch-up block is planned slack, not evidence that the schedule failed. If nothing slipped, use it to retest errors or rest.
After several missed days, choose the next phase checkpoint, list only its required tasks and schedule the first two sessions. Do not rewrite all 90 days while anxious.
Your 90-day plan on one page and the short version
Days 1 to 30 build aptitude and coding foundations. Days 31 to 60 deepen DSA and the four interview subjects. Days 61 to 90 turn that knowledge into mock performance, revision and active applications. Run the plan at about 25 to 30 hours a week, and use the never-miss-twice rule when life interrupts it.
For an end-to-end CS base, use the Zero to Hero complete CS course as the structured learning spine. Keep the aptitude bank and the two linked placement guides as weekly practice surfaces. The order matters: build, test, review, then repeat until interview day feels like another scheduled checkpoint rather than a surprise.
