Fresher hiring is not mysterious. It is a sequence of filters, each testing something slightly different, and each with a predictable failure mode.
Understanding the shape of the process tells you where to spend your preparation time. Most students over-prepare for the round that is easiest to pass and under-prepare for the one that decides the outcome.
The screen: can you be matched to the role?
The first filter is usually a human or a parser reading a resume against a list. It checks eligibility, graduation year, branch, sometimes a minimum percentage, and whether your skills resemble the job description.
What fails here: an unreadable resume, a missing graduation year, a portfolio link that does not open, or applying to a role whose eligibility you do not meet.
What helps: a single-column PDF, the exact role title, and evidence placed near the top. No amount of interview skill survives a screen you never pass.
The aptitude round: can you work quickly and accurately?
Quantitative aptitude, logical reasoning and verbal ability are common in campus and mass-hiring drives. The questions are not hard; the time limit is.
This round tests composure under time pressure more than intelligence. Practise with a timer, learn to skip a question early, and do not let one bad section ruin the rest.
The coding round: can you produce working logic?
Usually two to three problems in 60 to 90 minutes. The expected level varies enormously between organisations, so check the pattern from previous drives if it is published, or from students who have attended.
Preparation that transfers:
- Arrays, strings, hashing, sorting and searching until they are automatic.
- Reading the constraints before choosing an approach.
- Writing a brute-force solution first when you are stuck, then improving it.
- Testing with the provided examples and one edge case before submitting.
The technical interview: can you explain your thinking?
The coding round asks whether you can code. The technical interview asks whether you can reason with another person.
Expect questions on one or two of your projects, core computer-science fundamentals relevant to the role, and a problem you solve out loud. The interviewer is checking whether your resume is yours and whether you can be corrected.
What helps:
- A two-minute project explanation with a clear problem, approach and result.
- Honest answers about what you do not know.
- Thinking aloud instead of going silent.
- Asking a clarifying question before writing code.
What hurts: claiming a technology you cannot discuss, blaming teammates, or memorised answers that do not respond to the question asked.
The HR or managerial round: can you be managed?
This round is not a formality, and it is not primarily about “tell me about yourself”. It checks motivation, communication, reliability and fit with the team.
Prepare for: why this role, what you know about the organisation, how you handled a conflict or a missed deadline, and what you want to learn. Keep answers honest and specific. A rehearsed story with no detail is worse than a plain one with a real example.
What the process is really looking for
| Round | The real question |
|---|---|
| Screen | Can we match this person to the role quickly? |
| Aptitude | Do they stay accurate under pressure? |
| Coding | Can they produce working logic alone? |
| Technical | Can they reason and be corrected? |
| HR | Would we trust them with the team? |
Preparation that actually moves the needle
- Solve problems on a shared editor with someone watching. Silence feels different when observed.
- Write your two project explanations down and time them.
- Revise the fundamentals listed in the job description — not everything you have studied.
- Prepare three questions for each interviewer.
- Sleep before the drive. Tired candidates make avoidable errors in the aptitude round.
After the process
Ask for the timeline and the next step. If you are rejected, request feedback once — some organisations give it, many do not. Either way, write down the questions you could not answer and close the loop before the next drive.
A rejection is information about one process, on one day, with one panel. It is not a permanent classification.
The short version
Pass the screen with a readable resume, survive the aptitude round with timed practice, earn partial credit in coding, explain your projects honestly, and treat the HR round as a real assessment. That is the whole game.