The screening call
Most pipelines begin with a short call from a recruiter whose job is to filter volume, not to test depth. Expect ten to twenty minutes on your availability, notice period, current or last role, city and compensation range, with a couple of basic role questions. Answer crisply and consistently, because screening notes travel with your file, and a number misremembered here becomes an awkward question at the offer stage. If a detail is private or undecided, say so plainly rather than improvising. Before ending, confirm the interviewer’s name, which stage you have reached and the expected timeline for the next step. Keep your résumé open during the call, since being unable to match your own document is the most common way freshers fail this stage.
Assessments and written rounds
Many employers insert a test before any human speaks to you: aptitude or domain multiple-choice sets, an online coding task for technical roles, or a short written exercise for support and operations. The purpose is scale, reducing a pile of applications to a list worth interviewing. Preparation is mostly familiarisation with the format, the timer and the interface, which trip more candidates than the questions themselves. Do a handful of timed practice sets under exam conditions, because completion rate matters as much as correctness in many such tests. Read the instructions about calculator use, camera requirements and browser rules, since violating them fails the attempt automatically. When stuck, answer and move on, because partial progress beats blanks.
Technical and skill rounds
The core rounds are conversations that probe what you actually did. For technical roles, expect project walkthroughs, problem-solving on a shared document, and follow-up questions designed to check understanding rather than recall. For support, sales, retail or operations roles, expect scenario questions: how you handled an unhappy customer, a delay, a discrepancy. The reliable move in all of them is to narrate your real work precisely: the situation, your role in the team, the decision points, and what you would change now. Nobody expects a fresher to know everything, but they do expect honest reasoning from what you do know. Saying that you have not used something but would approach it a certain way is a good answer, not a confession.
The HR and managerial round
This round is not a formality; it tests whether the manager can work with you and whether your expectations match the job. Standard questions about why this role, your strengths and weaknesses, and conflicts you have handled reward specific stories over polished slogans. Have salary expectations ready and honest, grounded in the range the employer posted or that you know from the market, not in hope. Ask good questions back: what a typical week looks like, how performance is reviewed in the first few months, why the role is open. Interviewers read these as competence signals. In many companies the hiring manager’s impression here outweighs earlier scores, so arrive rested and treat it with technical-round seriousness.
After each round
After every round, do three small things. First, write down what was asked, within the hour, because memory decays and rounds often repeat question families, so your notes compound across attempts. Second, send nothing unless you were given a contact and a reason; unprompted follow-ups after a standard we-will-get-back-to-you line add no value and occasionally subtract it. Third, keep your pipeline running, because parallel processes steady your nerves and give you real leverage at the offer stage. If you are rejected, ask the recruiter politely what the deciding gap was. The answers cluster around the same few topics, and that cluster is precisely your next preparation plan.