A 30-Day Placement Preparation Plan for Freshers
A realistic 4-week placement preparation plan for freshers: aptitude, coding, core subjects, resume and HR answers, with a daily routine for each week.
Placement season tends to arrive faster than expected. If you have about a month before your first drive, a plan helps you cover the essentials without burning out on one topic.
This plan assumes 3 to 4 hours a day alongside college. Adjust it to the companies you're targeting: service companies tend to focus on aptitude, basic coding and communication, while product companies go deeper into data structures and problem solving. Check the test pattern of each company you're applying to, because it changes from year to year.
How placement drives usually work
Most campus and off-campus drives for freshers have some version of these rounds:
- Online assessment: aptitude (quantitative, logical reasoning, verbal), and often a coding section.
- Technical interview: your projects, a programming language, core subjects (OOP, DBMS, operating systems, networks) and sometimes live coding.
- HR or managerial interview: communication, attitude and fit.
The plan below covers all three, so no round catches you unprepared.
A daily routine
| Time | What to do |
|---|---|
| 45 to 60 min | Aptitude: one topic, then a timed set of questions |
| 60 to 90 min | Coding: one concept, then 2 or 3 problems |
| 45 min | Core subject or your main language |
| 15 to 20 min | Speaking practice: one HR question out loud |
Keep one day a week lighter for revision and a mock test. Consistency matters more than long weekend sessions.
Week 1: Foundations
- Aptitude: percentages, profit and loss, ratio and proportion, averages. These appear in many other topics too, so start here.
- Coding: pick one language and stay with it. Revise arrays, strings, loops and functions. Solve easy problems: reverse a string, find duplicates, check a palindrome, count character frequencies.
- Core: OOP concepts (classes, inheritance, polymorphism, encapsulation) with one example each in your language.
- Resume: finish a one-page resume this week, so you can start applying. Our guide on writing a fresher resume with no experience walks through it.
Week 2: Speed and patterns
- Aptitude: time and work, time-speed-distance, simple and compound interest. Learn the shortcut methods; for example, the LCM method for time and work removes most fraction arithmetic.
- Coding: hashing (maps and sets), two pointers and sliding window. These patterns solve a large share of easy and medium array problems.
- Core: DBMS: keys, normalisation, and SQL queries with
JOIN,GROUP BYand subqueries. See SQL joins explained with examples. - Logical reasoning: number series, coding-decoding, blood relations, seating arrangement.
Week 3: Interview depth
- Coding: recursion, sorting and binary search, plus basic linked list and stack problems. Practise explaining your approach out loud before you code.
- Your language in depth: if you're applying for web roles, JavaScript questions on closures, scope, promises and the event loop are very common. Try the event loop output questions.
- Projects: for each project on your resume, prepare a two-minute explanation: the problem, your role, the tech you used and why, one challenge and how you solved it.
- Core: operating system basics (processes vs threads, deadlock, memory management) and networking basics (HTTP, TCP vs UDP, what happens when you type a URL).
Week 4: Mock tests and HR
- Mock tests: take at least two full-length timed aptitude tests. Afterwards, spend as much time reviewing mistakes as you spent on the test.
- Mock interviews: ask a friend or senior to interview you for 30 minutes, covering your projects and two coding problems.
- HR answers: prepare "Tell me about yourself", strengths and weaknesses, "Why should we hire you?" and "Where do you see yourself in five years?". Start with how to answer "Tell me about yourself" as a fresher.
- Company research: for each company you're interviewing with, know what it does, its main products or clients, and why you want to join.
On the day of the test or interview
- Check your device, internet connection, camera and the test link a day before an online test.
- Keep your resume, ID and any documents the company asked for ready.
- In the interview, it's fine to take a few seconds to think, and to say "I'm not sure, but here's how I'd approach it".
- After each interview, write down the questions you were asked. They're the best guide for your next one.
Make the plan your own
No plan fits everyone. If you're already strong at coding, shift time to aptitude; if communication is your weak spot, do the speaking practice every day. What matters is covering every round, practising under time limits, and reviewing your mistakes.
You can read free answered questions on JavaScript, React, SQL, DSA, aptitude and HR on our free interview questions pages.