Candidates prepare one interview and attend two. The technical and HR rounds evaluate different risks the company is pricing — knowing each round’s real question changes how you prepare and perform.
Technical round: “Can you do the work — and think?”
The interviewer is pricing your trainability: fundamentals + reasoning under pressure. Expect:
- Your resume, deeply — projects line by line (“why this stack?”, “what breaks at scale?”). Every bullet is a question you invited (defensible projects shine here).
- Core subjects — DSA basics, OOP, DBMS/SQL, OS/networks fundamentals per role (question banks).
- Live problem-solving — where thinking aloud matters more than perfect answers: state assumptions, try structure, accept hints gracefully. “I don’t know X, but I’d reason it as…” scores; bluffing detonates.
HR round: “Should we hire this person?”
Not a formality — HR prices fit, reliability and joining risk. Expect behavioral questions (STAR stories), why-this-company (research shows or its absence shows), relocation/shift flexibility (answer honestly — misdeclaring surfaces at offer time), strengths/weaknesses (real weakness + improvement motion), and your questions to them (have two — role growth, training structure).
The preparation split
- Technical (larger share): daily DSA, project defence prep, core-subject revision per the JD.
- HR (small but non-zero): 4-5 STAR stories rehearsed aloud, company research (15 min), honest answers pre-decided on location/bond questions (know the terms).
Both rounds share one meta-rule: composure reads as competence. Pauses to think are professional; panic-filling silence isn’t. Treat each round as its own game and you’ll stop losing winnable interviews at the last table.