Placement preparation for engineering students: a semester-by-semester plan
Start placement preparation in second year, choose one direction by the end of it, and spend the next two years building proof for that direction: DSA and projects for software roles, core subjects for core and PSU jobs, SQL and Python for analytics. Atyant seniors who reached Amazon, Google, HPCL and ZS Associates followed that pattern. Their most common regrets were starting late and preparing for three things at once.
When to start placement preparation
In second year. A CSE senior who interned at Google started serious preparation in second year. Another, who got a FAANG internship off-campus, said their biggest regret was not starting internship preparation in second year. A Civil senior who joined HPCL through campus placement said they would start in fifth or sixth semester next time, with more mock interviews.
Preparation takes longer than most students plan for. One CSE senior prepared for 14 months before joining Amazon. A Chemical Engineering senior did it in about six months, but spent half of that time on mock interviews and revision. If you are already in final year, it is not too late, but focus on one target role instead of several.
A semester-by-semester placement plan
This plan combines what these seniors did with what they said they would change. If you can move a step earlier, do.
- Semesters 1 and 2: keep your CGPA steady, because many companies set a CGPA cutoff for who can take their test. Learn one programming language properly.
- Semesters 3 and 4: choose one direction, such as software, core, analytics or GATE. Start a daily routine for it: DSA problems for software, core subjects for core roles. Build your first project.
- Semester 5: build two or three projects you can explain end to end, write the first version of your resume and apply for summer internships. Ask seniors and alumni what the rounds at your target companies look like.
- Semester 6: do the internship. Add system design if you are aiming for software roles, or revise core subjects if you are aiming for core and PSU jobs. Start mock interviews.
- Semester 7: placement season. Practise aptitude and timed tests, prepare for each company's rounds and keep doing mock interviews. Apply off-campus at the same time instead of waiting for campus drives.
- Semester 8: keep going. A Mechanical senior was placed at MNGL, a GAIL and BPCL joint venture, through campus placements in eighth semester.
What placement rounds test
Most campus drives follow a similar sequence, though the details vary by company. Ask seniors who sat the same company's drive last year what each round looked like.
- Online assessment: aptitude and reasoning, plus coding problems for software roles or technical questions for core roles. It is timed, so practise under a timer.
- Group discussion or group task: common at core companies and PSUs. The Civil senior who joined HPCL researched HPCL's group task and interview before the drive.
- Technical interviews: DSA and your projects for software roles, core subjects for core roles. Expect questions on anything you wrote on your resume.
- HR interview: why this company, why this role, and whether you can explain your own choices clearly.
How to prepare for the aptitude round
The aptitude test is usually the first filter, and it is timed, so speed matters as much as knowing the method. Take one full timed mock test before you start studying. It shows which topics cost you the most time and marks.
Then go topic by topic: learn the concept, solve a set of questions on it, and move on only when you can solve them within the time limit. Go back to full timed mocks every week or two to check your speed.
- Quantitative aptitude: number systems, percentages, profit and loss, ratios, time and work, time and distance, permutations and combinations, and probability.
- Logical reasoning: series, seating arrangements, blood relations, syllogisms, coding-decoding and data interpretation.
- Verbal ability: reading comprehension, sentence correction and vocabulary.
Placement preparation for CSE and IT students
Pick one resource, such as LeetCode or GFG, and solve problems daily instead of trying to cover every topic. One senior who joined Amazon solved about 300 LeetCode problems grouped by pattern, from easy to hard. Keep a list of what you have solved and review it every week to find weak areas. Also revise the computer science subjects technical interviews ask about: OOPs, DBMS and SQL, operating systems and computer networks.
Start system design alongside DSA, not after it. Starting it late was the most common regret among the seniors who reached Amazon and Google. For projects, one or two full-stack projects or open-source contributions you can explain in detail count for more than many small tutorial projects.
Placement preparation for core branches
Core interviews test your subjects, not DSA. An Electrical senior placed in a core role at JSL focused on Power Systems, Control Systems and Machines, and recommends MATLAB and PLC projects. A Metallurgy senior who joined JSW Steel with no prior internships focused on Material Science and Thermodynamics, practised core interview questions and asked alumni what JSW looks for.
Decide early whether you are going core. Both of those seniors said generic coding preparation for CS roles cost them time they could have spent on core subjects. If you want analytics or software instead, the related guides below show how students from core branches made that switch.
Resume, projects and internships
Describe every project the same way: the problem, your approach, the tools you used and the result, with numbers where you have them. A resume without measurable outcomes reads like everyone else's.
Tailor the resume to each role. An Electrical senior who became a Graduate Engineer Trainee at JSW Motors built their resume around a PowerGrid internship and a leadership role in the college fest, and said not tailoring their applications was a mistake.
Mock interviews and communication
Knowing an answer is not the same as explaining it under pressure, and several seniors underestimated this. They fixed it by practising out loud with seniors and peers, talking through their thinking as they solved. The Chemical Engineering senior who joined Amazon spent the last three of six months of preparation mostly on mock interviews and revision.
If you have nobody to practise with, Atyant's AI mock interview builds questions from the job description and your resume and asks follow-ups when an answer is thin, the way a real interviewer would.
If campus placements don't work out
Campus is one route, not the only one. A VNIT CSE senior who did not get a big company on campus built a public GitHub portfolio, entered coding contests regularly, grew their LinkedIn network and landed a FAANG internship off-campus. A Mechanical senior reached ZS Associates by asking VNIT alumni on LinkedIn for referrals to off-campus roles.
Keep placements open even if you are preparing for GATE, CAT or another exam. A Mechanical senior kept their CGPA steady and was placed at MNGL through campus placements in eighth semester, after a management exam did not work out.
Mistakes seniors say to avoid
- Preparing for DSA, AI and GATE at the same time. An Electrical senior who later qualified GATE and joined Maruti Suzuki called this their biggest mistake.
- Trying to cover every DSA topic instead of mastering the commonly asked ones.
- Leaving system design and mock interviews until final year.
- Applying only through campus drives.
- Talking to seniors and alumni only after the rounds have started.
- Sending the same resume to every company.
Real journeys from Atyant seniors
CSE, VNIT Nagpur → SDE, Amazon
14 months of preparation
What worked: Solved about 300 LeetCode problems by pattern, studied system design and contributed to open source.
What they would change: Started system design late and tried to learn everything at once.
CSE, VNIT Nagpur → Software Engineer Intern, Google
Serious prep from second year
What worked: Built DSA depth and full-stack projects, entered coding contests and did mock interviews.
What they would change: Did not focus on system design or interview communication early.
Chemical, VNIT Nagpur → Amazon, Bengaluru
About 6 months
What worked: Learned Python and DSA basics, solved two or three problems daily and did mock interviews.
What they would change: Did not practise enough under time limits or study company-specific patterns early.
CSE, VNIT Nagpur → FAANG off-campus internship
Final year, after missing campus offers
What worked: Built a public GitHub portfolio, did coding contests regularly and grew a LinkedIn network.
What they would change: Waited until final year to focus on internships.
Civil, VNIT Nagpur → Project Engineer, HPCL
Final year, campus placement
What worked: Researched HPCL's group task and interview, revised core civil concepts and asked seniors about their rounds.
What they would change: Would start in fifth or sixth semester with more mock interviews.
Electrical, VNIT Nagpur → Graduate Engineer Trainee, JSW Motors
Final year
What worked: Built a resume around a PowerGrid internship and a leadership role in the college fest.
What they would change: Networked late and did not tailor applications.
Mechanical, VNIT Nagpur → Assistant Manager, MNGL (GAIL and BPCL JV)
Eighth semester
What worked: Kept CGPA steady and joined campus placements after a management exam did not work out.
What they would change: Did not talk to seniors or people at target companies early.
Mechanical, VNIT Nagpur → Data Analytics, ZS Associates
About 8 months, final year
What worked: Went Python, then SQL, then one real project, and asked VNIT alumni on LinkedIn for referrals to off-campus roles.
What they would change: Spent weeks trying every data-science tool at once and applied only to on-campus drives at first.
Frequently asked questions
When should I start placement preparation?
In second year if you can. Seniors who reached a Google internship and a FAANG internship started serious preparation in second year or wished they had, and starting late was the most common regret. Final-year students still get placed, but should focus on one target role.
How do I prepare for the aptitude test for placements?
Take one full timed mock test first to find your weak topics. Then study quantitative aptitude, logical reasoning and verbal ability one topic at a time, and go back to timed mocks every week or two. The test is timed, so speed matters as much as accuracy.
Is DSA enough for placements?
For software roles, DSA gets you through the online test and the first interviews. The seniors who reached Amazon and Google also had projects they could explain, system design preparation and practice explaining their thinking out loud. For core roles, core subjects matter more than DSA.
How do I prepare for placements in Mechanical, Electrical or another core branch?
Revise the core subjects your target companies ask about, practise core interview questions and ask alumni what each company looks for. An Electrical senior focused on Power Systems, Control Systems and Machines. A Metallurgy senior focused on Material Science and Thermodynamics and joined JSW Steel.
What if I don't get placed on campus?
Apply off-campus at the same time. Seniors got a FAANG internship and an analytics role at ZS Associates off-campus through a public GitHub portfolio, coding contests and referrals from alumni on LinkedIn. Placements also continue late in the season: one Mechanical senior was placed at MNGL in eighth semester.
Do I need a high CGPA for placements?
Many companies set a CGPA cutoff for who can take their test, so a steady CGPA keeps your options open. Beyond the cutoff, what most of these seniors credit is skills, projects and interview practice.