The Standard Three-Round Shape
Across all three companies the loop is broadly the same, even though the names differ (TCS NQT, Infosys HackWithInfy / standard drive, Wipro Elite NTH):
- Round 1 — Online assessment: quantitative aptitude, logical reasoning, verbal ability, and usually a coding or pseudocode section
- Round 2 — Technical interview: your resume, one language in depth, DBMS/SQL basics, and your final-year project
- Round 3 — HR interview: relocation, bond/service agreement, shift flexibility, salary expectation, and why this company
- Some drives merge rounds 2 and 3 into a single panel, especially for off-campus hiring
Round 1 — The Aptitude Filter
This is a pure filter, and most rejections happen here. It is also the most trainable round in the entire process because the question types repeat year after year.
- Quantitative: percentages, ratios, time & work, time-speed-distance, profit & loss, averages, number system
- Logical: series, blood relations, seating arrangement, syllogisms, data interpretation
- Verbal: reading comprehension, error spotting, sentence completion, para-jumbles
- Coding: one or two problems, typically arrays, strings, or simple pattern printing
- Speed matters more than difficulty — the questions are not hard, but the clock is tight
Round 2 — The Technical Interview
For a fresher, the technical round is mostly a depth check on things you claimed on your resume. Panels are explicitly told not to reject on missing knowledge alone, but on the inability to reason.
- Pick ONE language and know it properly — panels respect depth over a list of five languages
- OOP concepts with a real example, not a textbook definition
- SQL: joins, group by, and writing a query on the spot
- DBMS: normalisation, keys, ACID — expect to be asked to apply, not define
- Your project: architecture, your specific contribution, what you'd do differently
- Basic data structures: arrays, linked lists, stacks, and their time complexity
Round 3 — HR, and the Questions That Actually Decide It
Candidates under-prepare this round because it 'feels easy'. In services hiring the HR round is a genuine screen — it is where availability, attitude and communication get tested.
- 'Are you open to relocation?' — a hesitant yes reads worse than a clear no
- 'Are you comfortable with night shifts / client time zones?'
- 'Why IT services and not a product company?' — answer honestly, do not insult the question
- 'Where do you see yourself in 3 years?' — connect it to the company's delivery model
- Service agreement and notice period questions — know the terms before you walk in
- Communication is being actively assessed. Fluency in English matters in this round specifically.
What Actually Differentiates Candidates Here
Everyone in the room has similar marks and similar projects. The differentiators are narrower than you think:
- Clear spoken English under mild pressure — this is the most common silent rejection reason
- One project you can explain in depth for ten minutes without notes
- Not freezing on 'I don't know' — saying how you'd find out is an acceptable answer
- Genuine, specific reasons for choosing that company
- Consistency between your resume and what you say out loud
Common Interview Questions & Answers
Q1. Why do you want to join an IT services company rather than a product company?
I want breadth early in my career. In services I'll work across multiple clients, domains and tech stacks in my first few years, which helps me find out what I actually want to specialise in. I also value the structured training — I'd rather learn on a strong process foundation than pick things up ad hoc. Long term I want to move into a specialist role, and this gives me the exposure to choose it deliberately.
Do not pretend it is your dream company. Honest, specific reasoning beats flattery.
Q2. Tell me about your final-year project.
Structure it as problem → your specific role → stack → outcome → what you'd change. Spend the most time on your own contribution and be precise about what you personally built versus what a teammate built. Finish with one honest limitation and how you would address it now — that single sentence signals engineering maturity more than any feature list.
Panels ask follow-ups on the part you sound least confident about. Know your weakest module best.
Q3. Are you willing to relocate anywhere in India?
If the answer is yes, say a clean yes without qualifiers. If you have a genuine constraint, state it once, clearly, with the reason, and then state what you CAN do — 'I have a family care commitment in Pune for the next year, after which I'm fully flexible.' Hedging is worse than either answer.
Vague answers here are read as a flight risk, which is the main thing services HR is screening for.
Q4. You have a 3-year service agreement. Are you comfortable with that?
Know the actual terms — duration and bond amount — before the interview, then answer directly. If you're comfortable, say so and briefly say why the stability suits your plans. If you have concerns, ask a factual clarifying question rather than expressing reluctance.
Read the offer terms yourself. Candidates who ask basic factual questions about their own bond look unprepared.
Common Mistakes to Avoid
Treating the aptitude round as easy and running out of time
Listing five programming languages and being shallow in all of them
Rehearsed HR answers that sound identical to every other candidate's
Being visibly reluctant about relocation or shifts and hoping it won't be noticed
Not being able to explain a project that is on your own resume
Expert Tips
Time yourself on aptitude — sectional timing is what actually eliminates people
Practise the technical round out loud; explaining OOP verbally is harder than writing it
Have one clear, specific reason for each company you are applying to
Work on spoken fluency deliberately — in this process it is a scored dimension, not a soft skill
Pre-Interview Checklist
6 itemsFrequently Asked Questions
Is the interview pattern the same every year?
The structure is stable, but the specific sections and question mix change between drives and years. Always check the current official assessment pattern published for your drive rather than relying on an older candidate's account.
How important is English fluency in these interviews?
Very. Services companies place freshers in client-facing and offshore-delivery roles, so communication is assessed in both the technical and HR rounds. It is one of the most common reasons for rejection among otherwise technically sound candidates.
Can I get selected with a backlog or a lower percentage?
Eligibility criteria are set per drive and are published officially. Check the specific drive's criteria — they vary by company, year and role, and unofficial information is frequently out of date.
Ready to ace your next interview?
Practice with SpeakWell AI. Upload your resume → get resume-based questions → practice with AI interviewers → improve communication → track progress → get instant AI feedback.