Roadmap › 7. Interview Questions & Career › Step 60
₹
Career Gaps, Job Changes & Salary Negotiation
Explaining career gaps, layoffs, frequent job changes, domain/tech switches and freelancing; understanding CTC and offers (India and Taiwan), researching market pay, answering expected-salary questions, negotiating, counter-offers, offer comparison and resignation etiquette.
You know 0 of 15Open a question, read the answer, then tap “✓ I know this”.
15 of 15 questions match the filters.
Interview priority:★ Must know High priority — asked in almost every interview, learn firstMedium asked regularlyLow good to know
1.I see a gap of a year in your resume. Can you explain it?
In short: Answer in three parts: reason, activity, readiness.
- Example: "My role was affected by a restructuring in early 2025.
- I used the time to deepen my skills — I completed the AZ-204 certification and built a full-stack project with ASP.NET Core, React and Azure that's on my GitHub — and I also did a three-month freelance contract building APIs for a logistics client.
- I'm now fully ready and looking for a long-term role where I can contribute from day one." Keep it calm, factual and short, then move on.
2.What is your expected salary?
In short: Give a researched range tied to the role: "For a senior .NET developer role with Azure responsibilities in Pune, market data and my experience put my expectation at ₹22–25 lakhs fixed.
- I'm open to discussing the full package, including variable pay and growth." If it's very early, you can ask to learn more about the role first, but don't avoid answering entirely if they insist.
3.What is your current CTC and why do you expect a big hike?
In short: State your current CTC honestly with its breakup (fixed vs variable).
- Justify the expectation with market value, expanded responsibilities in the new role, skills you bring (e.g. cloud, leadership), and competing offers if real.
- Example: "My current CTC is ₹12 LPA, of which ₹10.5 is fixed.
- My current salary is below the market median because I've been with the company since joining as a fresher, while my responsibilities have grown to leading a module and owning CI/CD.
- The market range for this role is ₹18–22 LPA, which is the basis for my expectation."
4.Why did you change jobs so frequently?
In short: Explain briefly and show a positive pattern: "My first role was a 10-month contract;
- the second company shut down its India development centre;
- since then I've been at my current company for three years and grown from developer to module lead.
- Now I'm looking for a long-term role where I can grow into a technical lead." Emphasise what you learned and your intention to stay.
5.Are you open to negotiation on the salary you mentioned?
In short: "Yes, I'm flexible within reason.
- The role and growth matter to me as much as the number.
- If the fixed component needs to be lower, components like a joining bonus, a performance review after six months, or equity could balance it." This shows flexibility without abandoning your target.
6.You were laid off. Was it because of performance?
In short: "No — it was part of a company-wide restructuring that affected about 20% of the engineering team after a client contract ended.
- My last review rated me 'exceeds expectations', and my manager is happy to give a reference.
- I've stayed active since — I completed a certification and built a project with the latest .NET." Only say this if it's true; offer references.
7.How do you justify switching from support/testing to development?
In short: Show evidence, not just interest: "In my support role I wrote C# tools and SQL scripts that automated incident triage, saving about 10 hours a week.
- Over the last year I built two applications with ASP.NET Core and React (on GitHub), completed a .NET certification, and contributed bug fixes to our internal product with my lead's approval.
- My production-support background helps me write more reliable, debuggable code."
8.We can offer only 15% above your current salary. Will you accept?
In short: Respond politely and with data: "Thank you.
- I'm keen on this role.
- However, a 15% increase puts the offer below the market range for this position, and below another offer I'm considering.
- Would there be flexibility to reach ₹X fixed, or to add a joining bonus and a salary review after six months?" If they can't move and you still want the job, decide based on the whole picture;
- if not, decline gracefully.
9.Do you have other offers?
In short: Be honest.
- If yes: "Yes, I have one offer from a product company and I'm in final rounds with another.
- This role is my preferred option because of the team and the Azure work, so I'd like to see if we can align on the package." Don't invent offers — companies sometimes ask for proof, and it damages trust.
- If no: "I'm in process with a couple of companies, but this role is a strong fit for me."
10.What is your notice period, and will you be able to join early?
In short: "My notice period is 90 days.
- My company allows a buyout of up to 45 days, so I could join in about 45–60 days.
- If the buyout amount is a concern, would you be able to support it?" Be accurate — commitments you can't keep damage trust.
11.How would you respond to a counter-offer from your current employer?
In short: Thank them, and evaluate against the reasons you wanted to leave — growth, technology, team, location — not only the money.
- If those reasons remain, decline respectfully: "I appreciate the offer and everything I've learned here, but I've decided to take this new role for the learning opportunity.
- I'll make sure the handover is smooth." If you accept a counter-offer, inform the new employer immediately and courteously.
12.You receive a written offer below your expectation, but you really want the job. What do you do?
In short: Express enthusiasm and ask for time to review.
- Calculate the in-hand amount and compare with market data and your walk-away number.
- Then make one well-justified request covering the specific gap, and offer alternatives (joining bonus, earlier appraisal, a higher designation, a relocation allowance, remote days).
- If they can't move, decide consciously: accept if the role's learning, brand or stability is worth it, or politely decline.
- Either way, get the final terms in writing.
13.Background verification shows a mismatch in your previous employment dates. What should you do?
In short: Contact HR immediately and explain transparently — for example, the resume used the project start date while the official joining date was a month later, or a notice period was shortened.
- Provide documents (offer and relieving letters, payslips, PF/UAN service history).
- Small honest discrepancies can usually be resolved; deliberate misrepresentation usually leads to offer withdrawal.
- Prevent it by using official dates on your resume.
14.You were freelancing for two years. The interviewer worries you won't fit into a team. How do you answer?
In short: "Freelancing taught me to own outcomes end to end — requirements, delivery, deployment and support — and to communicate directly with clients.
- I also worked in teams on most projects: for example, with a client's in-house developers using Git and pull requests, and with designers and QA.
- I'm moving to full-time because I want deeper long-term product ownership and to grow with a team.
- I've closed my freelance engagements, so there's no conflict of interest."
15.An HR person asks for your expected salary before the technical rounds, and the posting has no range. What do you say?
In short: Try to learn the band first: "Could you share the budgeted range for this role?
- That will help me give a meaningful answer." If they insist, give a researched range with a qualifier: "Based on what I understand about the role and the market for senior .NET engineers in this city, I'm looking at ₹24–28 lakhs fixed, depending on the responsibilities and total package." Avoid a single low number that anchors the whole negotiation.