A 12-week placement preparation plan for tier-2 and tier-3 college students

If your college doesn't get many top companies, placement preparation can feel unfair. Fewer companies visit, seniors give conflicting advice, and most "roadmaps" online assume you have six months and a lot of free time.

This plan assumes you have about two hours a day for twelve weeks. It won't promise you a package. Nobody honest can. It will make you clearly better prepared than you are today, with proof to show for it.

How most fresher hiring works

Details differ by company, but the usual pattern for freshers is:

1. An online test. Aptitude, logical reasoning, verbal ability, and often one to three coding questions.
2. Technical interviews. Your projects, programming basics, data structures, databases, and sometimes a problem to solve live.
3. An HR round. Communication, motivation and fit.

So the plan trains all three, every week, instead of finishing DSA first and panicking about aptitude later.

The daily two hours

• 45 minutes: data structures and algorithms (DSA) and coding practice.
• 30 minutes: aptitude and reasoning.
• 45 minutes: your project, or résumé and interview work in later weeks.

Pick one language for coding questions (Python, Java or C++) and stick to it.

Weeks 1–4: foundations

• DSA: complexity (Big-O), arrays, strings, hashing. Solve 3–5 easy problems a day and write down the pattern behind each one.
• Aptitude: percentages, ratios, time and work, number series. Practise timed sets; speed matters in online tests.
• Project: start one project you'll be proud to explain (see our project ideas). Get the smallest working version online by the end of week 2.
• GitHub: clean up your profile (our checklist).

Weeks 5–8: core skills

• DSA: two pointers, sliding window, recursion, sorting and binary search, linked lists, stacks and queues. Move to medium problems.
• CS basics: revise the questions interviewers ask freshers most: OOP concepts, DBMS (keys, joins, normalisation, transactions), operating systems (processes, threads, deadlocks) and computer networks basics.
• SQL: write real queries every week (joins, group by, subqueries). Many tests include SQL.
• Project: add one feature a week, with a README update and a few tests.

Weeks 9–12: interview mode

• DSA: trees, heaps, graphs (BFS, DFS) and the basics of dynamic programming. Mix in timed mock tests twice a week.
• Résumé: one page. Put projects with links above "skills" lists. For each project, one line on what it does and one on what you did, with a number where honest ("handles 200 bookings in the test data", not invented user counts).
• Mock interviews: explain your project out loud in three minutes; answer "why did you choose X?" for every major decision. Practise with a friend and swap roles.
• HR answers: prepare honest answers to "tell me about yourself", "why this company", and "a time you solved a problem".

Make the work visible

A recruiter can't see your practice, but they can see your GitHub. Keep your practice solutions in a repository with clear folder names, and keep your project's commit history steady across the twelve weeks. Steady, explained work is hard to fake, and it's what separates you from everyone who only lists "DSA" on their résumé.

If you fall behind

You will miss days. Everyone does. Don't restart the plan; continue from where you are and drop the lowest-value item for that week, usually extra problems. Consistency beats intensity.

Doing this alone is hard

Our DSA for Placements course follows the same order: twelve weeks, a quiz every week and a problem set scored automatically against hidden tests, with a schedule built around the time you actually have.