Salary & Closing
For Indian IT services and GCC support hiring, the HR round is a formality that people lose marks on by improvising. Prepare it.
The three questions
| Question | What they want |
|---|---|
| Expected CTC? | A number you can justify, with room to move |
| Notice period? | How soon you can start |
| Why are you leaving / why this role? | Whether you'll bounce |
You are in your final year with no job. Your notice period is immediate, and saying so plainly removes an entire round of negotiation. Do not invent a serving notice period you do not have.
Salary — how to answer
Three rules:
- Give a range, not a point. "I'm looking in the range of X to Y, depending on the overall package" keeps you in the conversation.
- Anchor to the JD, not to your previous number. You have no previous number — this is your first role.
- Know the components. CTC includes base, variable, PF, gratuity and sometimes a retention bonus. Ask about the split if the offer surprises you.
Saying a number with no basis either anchors you low or disqualifies you. A range framed around the role is always safer.
What research before you go
- Search the role title plus your city on job portals for posted ranges.
- Check Glassdoor for the company's support band.
- Ask the recruiter directly — "what is the band for this role?" is a normal question and they are expected to answer it.
If pressed for a single number
"I'm flexible depending on the overall package. Could you share the band for the role? I'd rather aim accurately than leave you guessing."
That is a professional answer, not a dodge.
"Why are you leaving?"
For a student, this becomes "why this role?":
"I've been running my own Linux infrastructure — deployment, systemd services, monitoring, and troubleshooting failures as they happen — and I've enjoyed the operational side more than building products. This role is that work professionally: real users, real incidents, and a team I can learn from. I've been closing the gaps for the Windows and networking side by building a lab."
It uses evidence, shows self-awareness, and explains why you will stay.
"What are your weaknesses?"
Give one real weakness that you have an action attached to. Never "I'm a perfectionist" — it signals you did not think.
"My Windows Server and Active Directory experience was theoretical until this year. I've since built a domain controller in a home lab with OU structure, delegated permissions and Group Policies, and I've been practising troubleshooting scenarios weekly. It's the gap I'm actively closing, and it's why this role fits."
"Where do you see yourself in 3 years?"
"Starting in L1/L2 desktop support, I want to get to L3 — deeper into Active Directory, Windows Server and networking — and eventually into infrastructure engineering. I'd like to be the person on the team others escalate to."
Shows ambition that is consistent with the role, not a flight risk.
Questions YOU should ask
Asking nothing reads as no interest. Have three ready.
| Question | Why it is good |
|---|---|
| "What does a typical day look like for this role?" | Shows you want the work, not just the offer. |
| "What's the split between L1 and L2 work?" | Establishes where you sit. |
| "How is the team structured, and who do I escalate to?" | Practical and professional. |
| "What does on-call or shift work involve?" | Critical for support roles. |
| "What's the training budget or certification support?" | Signals long-term intent. |
| "Why is the role open?" | Genuinely useful, and rarely asked. |
Support roles often have rotational or 24×7 on-call. Discovering that after accepting is how people end up unhappy within a quarter.
After the interview
- Send a short thank-you email restating your interest and one detail you genuinely found interesting.
- Note every question you were asked. The second round repeats them.
- If they ask for a technical take-home, complete it carefully and on time.
Final checklist
You're ready
Start at the beginning, work the modules in order, and build the lab. The lab is the part that makes everything else credible.