Your 6-Month Step-by-Step Plan for Campus Placements

Six months is enough for most campus placement drives, if you spend those months in the right order.

Most students treat aptitude, coding, and interview prep as three parallel tracks. Companies test them in a sequence. Preparation that mirrors the sequence is faster and more effective than preparation that runs all three in parallel from day one.

The six-month timeline at a glance

Months	Focus	Key deliverable
1 and 2	Aptitude, verbal, logical reasoning	Full mock-test baseline in all three sections
3 and 4	Coding, domain skills, one real project	GitHub repository with a working project
5	Resume, mock interviews, group discussion	One-page resume that holds up under scrutiny
6	Company-specific research and interview mode	Tailored prep for two to three target companies

The plan below covers each phase in detail. Start by reading the whole plan before starting any one phase, because the deliverable from each phase feeds directly into the next.

The Right Sequence: Why Order Matters

Campus recruitment follows a predictable funnel. The online aptitude test comes first and eliminates the largest group. A coding or technical round follows, narrowing the field further. The interview is last, by which point the field is small.

Prepare in that order. Aptitude skills build fastest when they are the only focus. Adding coding too early splits attention before the conceptual basics are solid. Interview skills only become useful once there is something concrete to discuss: a project, a verified test score, a resume that reflects actual preparation.

One practical calibration before starting: IT service companies share a common eligibility floor, while product companies and core engineering firms set their own criteria. Knowing which tier you are targeting shapes how you allocate weeks 9 through 16. The IT jobs for freshers guide has a breakdown of the four company tiers and their eligibility requirements and CTC bands, which is useful before committing to a preparation order.

Months 1 and 2: Aptitude and Verbal Reasoning

Every company at campus, from TCS to core engineering firms to consulting, tests aptitude. The topics are consistent: quantitative reasoning (time and work, percentages, ratios, data interpretation), logical reasoning (blood relations, coding-decoding, syllogisms, number series), and verbal ability (reading comprehension, sentence correction, para-jumbles).

The common mistake is starting with full-length mock tests before covering the concepts. Mocks measure readiness. They don’t build it. A student who takes a mock test in week 1 and scores below average learns only that they scored below average. The same student who covers quantitative concepts systematically for four weeks, then takes a mock, learns which chapters still need work.

Week-by-week structure for months 1 and 2

• Week 1 to 2: Quantitative aptitude only. One chapter per day. No timed drills yet. The goal is conceptual clarity before speed.
• Week 3 to 4: Add logical reasoning. Continue quant with chapter-end exercises timed at 1.5 times the expected pace.
• Week 5 to 6: Add verbal ability. Run mixed short drills of 20 questions in 25 minutes every other day.
• Week 7 to 8: Full-length mock tests, three per week. Review every wrong answer. Spend the final week on your two weakest sub-sections.

How to use mock tests effectively

A mock test only improves performance when the review takes longer than the test itself. For each wrong answer: identify whether it was a concept gap, a calculation error, or a time-management problem. Each root cause has a different fix. Concept gaps need more chapter practice. Calculation errors need drill repetition. Time issues need timed sprints at the question level.

The aptitude preparation guide for engineering placements breaks this into section-wise topic lists with practice question sets for each major assessor platform, including AMCAT, eLitmus, and CoCubes.

Months 3 and 4: Coding, Technical Skills, and Projects

Coding rounds in 2026 typically run 60 to 90 minutes with two or three problems at easy to medium difficulty. For service-tier companies, one clean solution with correct output beats two half-finished attempts.

What to build in months 3 and 4

• Week 9 to 12: Fundamentals. Arrays, strings, two-pointer and sliding window patterns, hashmaps, and basic recursion. Write every solution from scratch in one language. Python and Java are the most commonly tested. Solve at least three easy-level problems per day before moving to medium.
• Week 13 to 14: One real project. Not a tutorial clone. Not a certificate. Something that solves a problem you can explain in 90 seconds: a budget tracker, a web scraper, a simple recommendation system, a campus event notifier. Push it to GitHub with a clean README describing the problem, the approach, and how to run it.
• Week 15 to 16: Domain depth. CSE students: data structures and algorithms, especially trees, graphs, and dynamic programming basics. ECE and EEE students: add digital systems, C programming, or embedded basics alongside DSA. Core engineering branches often have domain-specific technical rounds with circuit analysis, thermodynamics, or materials questions.

AI skills in 2026: what actually matters for placements

In FY26, AI-skilled graduates made up 60% of TCS’s fresher hires per TCS CHRO Sudeep Kunnumal, up from 10 to 15% three years earlier. This doesn’t mean every student needs a trained ML model in their project. It means knowing what AI tools can and cannot do is now expected, not impressive.

For most placement rounds, “AI skills” means being able to describe what a language model does, explain why a recommendation system uses collaborative filtering, or show a project that uses an API. Deep ML research is not what service-company interviewers are checking. The 2026 AI roadmap for Indian engineering students covers which AI skills appear in actual placement rounds and which are overhyped.

Month 5: Resume, Mock Rounds, and Soft Skills

Month 5 is when resume work makes sense, not month 1. By this point you have a test baseline, a project on GitHub, and technical skills you can actually defend in an interview. A resume written before that has nothing real on it. The common pattern of polishing a resume in month 1 is preparation theatre, not preparation.

Resume in 2026

One page for freshers. Every line should be something you can discuss for 90 seconds. Avoid listing tools you have only watched tutorials on. Real project experience outweighs a list of 15 technologies you nominally know.

For specifics on which skills to include and how to phrase technical achievements without padding, the top skills to put in your resume guide covers a section-by-section breakdown with ATS formatting rules for common applicant tracking systems used by IT recruiters.

Mock interviews

Run at least four mock interviews with a peer or senior, not solo practice in a mirror. Feedback from someone listening changes what you catch about your own answers. Record at least two sessions if possible. Watching yourself answer questions reveals habits that feel invisible in the moment.

The standard fresher interview covers three areas: your resume (any line on it is fair game), a coding or technical problem at medium difficulty, and HR questions about motivation and fit. Practise all three zones, not just the coding section most students over-index on.

Group discussions

Group discussions are tested by a smaller set of companies but weigh disproportionately in hiring decisions at the firms that use them. The skill is structured contribution, not volume. Two well-supported points in eight minutes outperform five rushed ones. Listen actively, build on what someone said, and support your point with a specific example or fact.

Soft-skills work belongs in month 5 rather than spread across all six months. Focused blocks produce faster improvement than persistent low-level background awareness.

Month 6: Company Research and Interview Mode

By month 6 the general preparation is complete. The remaining work is company-specific, and it differs for every company.

What company research means in practice

• Download past papers and mock series for the specific platform the company uses: AMCAT, Mettl, HirePro, or the company’s own test. Platform familiarity affects speed on test day. Knowing where the clock appears and how to navigate between sections saves two to three minutes in a 60-minute test.
• Attend pre-placement talks. These are not formalities. Companies often hint at what changed in their test pattern or which skills the interviewer will weigh most.
• Research the actual role. Know the difference between TCS Ninja and TCS Digital: the test pattern, the first-year onboarding track, and the work content are all different. Applying to both without understanding the difference is a missed opportunity to tailor preparation.
• Prepare two or three projects or experiences you can speak to in depth, tailored to the company’s focus area.
• Check logistics: registration deadlines, round sequences, and document requirements. Missed registration windows close doors before any preparation matters.

Interview mode in the final two weeks

By week 23 or 24, stop adding new topics. Review and rehearse what you already know. Confidence through repetition is the goal, not last-minute expansion.

Service-company interviews typically run 30 to 45 minutes. The structure is usually a brief HR opening, one or two technical questions from your resume, one coding or domain problem, and standard HR questions about strengths, future plans, and why the company. Know your resume well enough to speak for three minutes about any line on it without referring to the paper.

After the Campus Window

Missing the campus season because of backlogs, eligibility issues, or a college with few company visits is not the end of the road.

AMCAT is accepted by over 500 companies for direct off-campus applications. eLitmus and CoCubes cover a different but overlapping set of firms. The aptitude and coding work from this six-month plan transfers directly to those assessments. No preparation is wasted.

Many companies also run pool campuses and off-campus drives between January and March each year. Some specifically target students from colleges with smaller placement cells. Tracking company career pages and staying in contact with placement coordinators opens those doors.

The certification route is a third option for students who want to signal skills independent of their campus outcome. Platforms that award credentials for completed, reviewed projects carry more weight than completion certificates for video courses.

The preparation above is the campus-placement version of a more general skill set: aptitude, coding, communication, and domain knowledge. That skill set opens the same doors on the off-campus side.

---

If months 3 and 4 are where you are adding an AI project to your portfolio, TinkerLLM gives you a live LLM sandbox to run real experiments at ₹299, which is less than most mock-test subscriptions and directly adds a working AI project to your portfolio before month 5 resume day.