Short answer: To crack a campus placement interview, prepare for each round separately. Practise aptitude for the online test. Revise your core subject and one programming language for the technical round, and be ready to explain every project on your resume line by line. For the HR round, prepare short, true stories using the STAR method. Do at least two mock interviews before the drive, and research the company the night before.
This guide is for final-year students and recent graduates facing campus or pool-campus drives for software roles. It covers what each round tests, a two-week preparation plan and the ten habits that interviewers notice most. For help beyond campus drives, see ASTI’s placement assistance and career support.
What each round of a campus drive tests
Most campus drives for software roles follow a similar sequence, although every company sets its own process. Read the company’s drive notice carefully, because it usually lists the rounds.
| Round | What it tests | How to prepare |
|---|---|---|
| Online assessment | Aptitude, logical reasoning, verbal ability and often coding questions | Timed practice tests every day. Learn the common question types, not just the answers |
| Group discussion (some companies) | Communication, listening and teamwork | Practise speaking for 60 seconds on a topic and letting others finish before you respond |
| Technical interview | Programming basics, data structures, databases, your projects | Revise one language deeply, write code on paper, and rehearse explaining your projects |
| HR interview | Attitude, fit, honesty, willingness to relocate or work shifts | Prepare true stories with the STAR method and research the company |
A two-week preparation plan
- Days 1–3: Audit your resume. Remove anything you cannot explain in detail. For each project, write down the problem, your role, the tools you used, one difficulty and what you learned.
- Days 4–7: Fix the technical basics. Choose one language, such as Java, Python or C#. Revise OOP concepts, arrays and strings, basic SQL queries and joins, and the fundamentals of your branch subject.
- Days 8–10: Aptitude speed. Take one timed test a day and review every wrong answer. Speed comes from recognising question types.
- Days 11–12: Mock interviews. Ask a trainer, senior or friend to interview you, and record it if you can. Watch for filler words, long answers and weak project explanations.
- Days 13–14: Company research and rest. Read the company’s website, products and recent news. Prepare two questions to ask. Sleep well before the drive.
Ten tips interviewers notice
1. Know your resume better than anyone
Interviewers usually pick a line from your resume and go deeper. If you list SQL, expect to write a join. If you list a project, expect to be asked why you chose its design.
2. Explain projects in a fixed structure
Use problem, approach, your contribution, result and what you would improve. This keeps answers short and shows clear thinking.
3. Use the STAR method for HR questions
Describe the Situation, the Task, the Action you took and the Result. One real example is better than a general claim like “I am a team player”.
4. Think aloud in coding questions
Say what you are trying before you write code. Interviewers often care about your approach as much as the final answer, and thinking aloud lets them help you when you are stuck.
5. Prepare a 45-second introduction
Cover your degree, your strongest technical skill, one project and why you want this role. Do not repeat your whole resume.
6. Research the company
Know what the company does, who its customers are and which technologies the role uses. It helps you answer “Why do you want to join us?” honestly.
7. Be honest about what you don’t know
Saying “I haven’t used that yet, but this is how I would approach it” is better than guessing. Interviewers usually notice bluffing quickly.
8. Show you can learn
Mention a technology you taught yourself, a certification you are working towards or a course you completed, and what you built with it.
9. Ask one or two good questions
Ask about the training for freshers, the team’s technology stack or what success looks like in the first six months. Avoid asking only about salary in the first round.
10. Follow up professionally
If you have the recruiter’s email, send a short thank-you note the same day. Keep it to three or four lines.
Common mistakes
- Listing tools on your resume that you have only watched videos about
- Memorising answers word for word, which sounds unnatural under pressure
- Giving very long answers. Aim for one to two minutes, then stop
- Skipping aptitude practice because you are “good at coding”, which can end your drive at round one
How ASTI helps you prepare
Every ASTI course includes career support: resume building, LinkedIn profile help, mock technical and HR interviews with feedback, and interview preparation linked to the course projects. Learn more on the Placements page, or compare tracks in which software course to choose. Placement assistance does not guarantee a job. Hiring decisions are made by employers.
Frequently asked questions
How many rounds are there in a campus placement?
It depends on the company. Software roles commonly have an online assessment, one or two technical interviews and an HR interview. Some companies add a group discussion.
Which programming language should I prepare for campus interviews?
Choose the one you know best and prepare it deeply. Companies usually let you code in a common language such as Java, Python, C++ or C#.
What if I have no internship?
Build one or two projects you can explain in depth and put them on GitHub. A well-explained project often carries more weight than a short internship you cannot discuss.
How do I answer “Tell me about yourself”?
Give a 45-second answer covering your degree, your strongest skill, one project and why you want the role.
I didn’t get placed on campus. What now?
Many graduates are hired through off-campus drives and job portals. Keep improving one job-ready skill, build a project and apply consistently. A structured course with interview practice can help, but no course can guarantee a job.