Interview Q&A

Short answer: Reduction means proving the business can run without you in fewer days. Combine manager sponsorship, documented KT, and optionally using accumulated leave or buyout. Target a specific last working day (LWD), not a vague “as soon as possible.”

Step-by-step approach

1. Calculate calendar days: 90 working days ≠ 90 calendar days—check if weekends/holidays count in your policy.
2. Identify low-risk period: post-release, between projects, or after major go-live.
3. Offer concrete KT: recordings, runbooks, shadow sessions, and access revocation checklist.
4. Ask HR about leave adjustment (paid leave during notice) vs buyout—policies differ by company.
5. Escalate politely if HR stalls: ask for policy reference and approval workflow in writing.
6. Keep performing normally—performance drops are a common reason managers block early release.

Real-world example

Ananya, QA lead at TCS with 90-day notice, wanted to join a Bangalore product startup in 70 days. She created Confluence pages for 40 test cases, paired a junior QA for 2 weeks, and proposed LWD after the UAT sign-off. Account manager agreed; HR reduced notice to 75 days and allowed 5 days of earned leave in the notice window.

Numbers & benchmarks

• Typical achievable reduction with good KT: 15–30 days off a 90-day notice.
• Leave during notice: many firms cap how many PTO days offset the notice period.

Mistakes to avoid

• Assuming all companies treat notice the same—MNC captives vs Indian service vs product differ widely.
• Going straight to HR bypassing your manager (manager can block silently).
• Using sick leave patterns to cut notice—can trigger compliance review.
• Sharing confidential client data in KT docs stored on personal drives.

If reduction is denied, ask: “What specific handover milestones would make a 60-day release acceptable?”

Short answer: Early release is a business decision, not a favor. You need manager + HR + sometimes client approval. Make it easy to say yes: low transition risk, no open escalations, and a replacement or clear backlog plan.

Step-by-step approach

1. Check if your project is in a critical phase—avoid requesting release during go-live week.
2. Identify who must approve: manager, HRBP, delivery head, sometimes client POC.
3. Submit resignation with professional tone; attach transition timeline.
4. Volunteer for overlap with your replacement or extended support calls (within policy).
5. If denied, ask for interim date review after milestone X is delivered.
6. Document all approvals—Relieving letter and experience letter dates must match LWD.

Real-world example

Vikram, DevOps engineer at Wipro, was on a 90-day notice. His pipeline work was automated; on-call was shared. He trained two teammates on Terraform modules and showed 30 days of clean incident history. Delivery manager approved 45-day release; client had no objection because KT was recorded.

What to say / email template

Talking point to manager:
"Our release is stable and documented. I propose LWD [date] after these 3 KT sessions. I can stay reachable on email for 2 weeks post-exit for critical questions if policy allows."

Mistakes to avoid

• Disengaging after resignation (“quiet quitting”)—guarantees denial.
• Demanding early release citing only personal reasons without handover plan.
• Accepting verbal OK without HR portal/email confirmation.
• Starting full-time work at the new company while still on old payroll—legal and tax risk.

Offer a 30-minute weekly KT call during part of your notice if the team is short-staffed—often unlocks flexibility.

Short answer: Sometimes yes—if your employment contract or HR policy allows notice buyout. You (or your new employer) pay compensation for unserved notice days, usually basic salary equivalent. Not all companies permit it; captives and banks often do not.

Step-by-step approach

1. Search offer letter for “notice buyout,” “payment in lieu of notice,” or “shortfall recovery.”
2. Ask HR explicitly: “Is buyout allowed for my band and account?”
3. Get the formula: basic only vs CTC vs fixed components—amounts vary hugely.
4. Negotiate with new employer: joining bonus or relocation can cover buyout cost.
5. Pay only after written approval and final settlement calculation from HR.
6. Keep receipts and F&F settlement sheet for tax and future employment verification.

Real-world example

Priya’s product company required 30-day join; her MNC had 60-day notice with buyout at 1 month basic (₹85,000). Flipkart added ₹1L joining bonus conditioned on start date. Priya paid buyout, joined on time, and claimed reimbursement per offer letter clause.

Numbers & benchmarks

• Buyout range: 0.5–3 months of basic/common salary depending on employer.
• Some firms allow new employer to pay directly to old HR—ask both sides.
• Recovery on absconding is often higher than voluntary buyout—never compare them equally.

Mistakes to avoid

• Assuming buyout is automatic—it is often discretionary.
• Paying buyout without formal HR letter (scams/fake HR requests—verify domain).
• Not clarifying if variable pay / bonus is forfeited on early exit.
• Skipping tax treatment discussion on buyout and F&F components.

Phrase to new employer: “My notice buyout is approximately ₹X—can we align joining bonus or one-time payment to offset this?”

Short answer: Email HR after your manager agrees in principle. Be factual: current notice, requested LWD, business justification (handover complete), and attach transition plan. HR responds to process and risk, not urgency alone.

Step-by-step approach

1. Never cold-email HR without manager alignment—get verbal or Teams approval first.
2. Use official HR ticket/portal if your company has one (TCS/Infosys often require this).
3. Include: employee ID, resignation date, contractual notice, requested LWD, manager name.
4. Attach KT checklist and confirmation that access/assets will be returned on LWD.
5. Ask for response timeline: “Kindly confirm by [date] so I can coordinate with the new employer.”
6. If rejected, request written reason citing policy clause for future reference.

Real-world example

Rahul’s manager agreed on Teams to support 60-day release. Rahul opened an HR ticket with screenshot of project KT completion and manager’s email. HR approved in 3 business days and updated LWD in the separation portal—avoiding confusion at full & final settlement.

What to say / email template

Dear HR Team,

I submitted resignation on [date]. Contractual notice period: 90 days (LWD [date]).

With manager [Name]’s support, I request LWD [new date] based on completed handover (KT doc attached, manager approval email attached).

Please confirm approval or advise additional steps.

Employee ID: ___
Regards, ___

Mistakes to avoid

• Emotional language or comparing yourself to others who “got 15 days.”
• Copying only HR without manager—request gets stuck or rejected.
• Missing attachments—HR will delay for “incomplete submission.”
• Calling HR daily—polite follow-up every 3–5 business days is enough.

Subject line that works: “Notice period reduction request — [Name] — [Emp ID] — Manager approved”

Short answer: A 90-day notice is not bad for your career—it is common in Indian IT services. What hurts growth is unplanned exits, burning bridges, or long gaps while serving notice without upskilling. Product companies know service-sector notice norms.

Why this matters in Notice Period

Recruiters ask about notice on the first call. Transparency + early release plan beats hiding your situation.

Step-by-step approach

1. Disclose notice length early in interviews—surprises at offer stage kill deals.
2. Use notice period to finish certifications, portfolio updates, and system design prep.
3. Avoid negative posts about long notice on LinkedIn—frame as “standard for my current employer.”
4. Track release approvals weekly so offers do not expire.
5. If stuck 90 days, negotiate partial remote or learning time with manager.
6. Build relationships during notice—references matter for senior roles.

Real-world example

Ananya served full 90 days at Cognizant but used evenings for Azure certification and mock interviews. She joined Zoho with a clear story: “I honored commitment, automated handover, and upskilled.” Interviewers valued reliability over speed.

Mistakes to avoid

• Believing only 15-day notice companies are “good”—many strong firms accept 90 with planning.
• Going idle during notice—recruiters notice skill rust in later rounds.
• Accepting counter-offers without fixing why you wanted to leave.
• Letting frustration show in team meetings during long notice.

Follow-up questions you may get

• “Can you join in 30 days?” — Explain actual notice + KT plan + possible buyout.
• “Why is your notice so long?” — Industry norm for service co; not a performance issue.

Growth comes from skills and outcomes, not notice length alone—use the window deliberately.

Short answer: Resign in person or video call to your manager first, then submit formal email to HR the same day. Stay positive, give adequate notice, and focus on handover—not grievances. Professional exits protect references and future background checks.

Step-by-step approach

1. Choose timing: avoid peak release week unless unavoidable; give manager heads-up privately.
2. Prepare resignation letter/email before the conversation.
3. Thank manager for growth; state last working day per contract.
4. Ask about handover expectations and exit formalities (assets, access, exit interview).
5. Inform HR via official channel; complete separation portal steps.
6. Remain productive; do not download client data or solicit colleagues to leave.

Real-world example

Neha met her manager on Monday morning, explained she accepted a product role, and shared a 2-week handover outline. She submitted HR resignation by noon, completed exit checklist, and received a positive experience letter mentioning “professional conduct during transition.”

Mistakes to avoid

• Resigning by email without speaking to manager first.
• Using resignation to negotiate salary unless you will genuinely stay.
• Telling teammates before manager—news travels and erodes trust.
• Deleting code or docs out of frustration—can be grounds for legal action.

Toolliyo resources

• Update resume before exit interviews
• More career Q&A

You can be firm and kind: “This was a hard decision; I want to make the transition smooth for the team.”

Short answer: Keep it short: intent to resign, last working day per policy, gratitude, and offer to support handover. Do not include reasons for leaving, complaints, or new employer name unless required.

Step-by-step approach

1. Address manager and HR (or use company resignation template).
2. State: “I hereby resign from my position as [title], effective [resignation date].”
3. Mention contractual notice and proposed LWD.
4. Thank the organization; offer KT support.
5. Sign with full name, employee ID, contact.
6. Attach formal letter PDF if HR requires it.

Real-world example

Arjun sent a 6-line email after a manager call. HR accepted immediately; no back-and-forth because dates matched policy and tone was neutral. His F&F processed on time.

What to say / email template

Subject: Resignation — [Your Full Name] — [Employee ID]

Dear [Manager Name] and HR Team,

Please accept this email as formal notice of my resignation from the position of [Job Title], effective [Resignation Date].

As per my employment terms, my notice period is [X days/weeks], and my expected last working day is [LWD], subject to company policy and handover completion.

I am grateful for the opportunities here and will do my best to ensure a smooth transition, including documentation and knowledge transfer.

Please advise on exit formalities and asset return.

Sincerely,
[Full Name]
[Employee ID]
[Phone]

Mistakes to avoid

• Writing a novel about why you hate the job.
• Naming the new company and salary—creates unnecessary friction.
• Wrong LWD math—HR will ask you to resubmit and delay process.
• Sending from personal email instead of corporate account.

Save a PDF copy—needed for visa, loans, and future verification.

Short answer: If your contract specifies notice and you resign voluntarily, the employer can require you to serve it or pay buyout if allowed. They generally cannot force unpaid labor beyond contract, but absconding triggers recovery clauses and legal risk.

Why this matters in Notice Period

Indian employment law is contract-driven. IT industry norms are strong but not above written terms.

Step-by-step approach

1. Re-read appointment letter, bond (if any), and separation policy.
2. Understand consequences of not serving: salary hold, experience letter delay, negative verification.
3. If employer denies release without cause, escalate to HRBP with documented KT proof.
4. Consult labor lawyer only for clear violations (harassment, withheld salary illegally)—rare for standard notice disputes.
5. Never stop working without formal acceptance of absconding consequences.
6. Negotiate buyout or partial serve if full 90 days is impossible for new offer.

Real-world example

A developer’s manager refused early release despite empty backlog. HR cited policy: full 60 days or buyout. He chose buyout funded by new employer rather than absconding—avoided blacklist on background verification vendors used by top product firms.

Numbers & benchmarks

• Background verification failures on notice absconding can delay offers 2–8 weeks.
• Recovery claims: typically basic salary for unserved days plus statutory adjustments.

Mistakes to avoid

• Assuming “I can leave anytime” in at-will myths—India is not US at-will for most IT contracts.
• Absconding to join startup—many vendors flag “did not serve notice.”
• Threatening legal action without grounds—burns references.
• Ignoring garden leave instructions while working elsewhere.

If stuck, serve professionally—your reputation outlasts one long notice.

Short answer: Leaving without notice (absconding) usually triggers salary forfeiture, negative or delayed experience letter, recovery notices, and failed background checks. Some employers mark “not eligible for rehire.” New employers may revoke offers if verification fails.

Step-by-step approach

1. Calculate total cost: recovery letter + legal fees + offer loss vs buyout cost.
2. Contact old HR to negotiate settlement—even after leaving—some accept buyout late.
3. Document any harassment or illegal withholding if that forced exit (seek legal advice).
4. Prepare honest explanation for future employers—avoid lying on verification forms.
5. Complete PF/gratuity transfer separately—absconding complicates but does not always block PF.
6. Rebuild trust with strong references from other managers/clients if possible.

Real-world example

Karthik absconded from a service firm after 20 days of 90-day notice to join a startup. BGV failed; startup withdrew offer. He paid settlement after 6 months, got experience letter, and re-applied—lost a year of seniority progression. Buyout would have cost less than career damage.

Mistakes to avoid

• Believing small companies “do not check” notice history—they use third-party BGV.
• Ignoring recovery emails—accumulates interest and legal escalation in some cases.
• Using fake experience letters—criminal fraud risk.
• Assuming new employer will always protect you—they protect their hiring compliance first.

Follow-up questions you may get

• “Why did you leave abruptly?” — Own mistake, explain settlement, emphasize reliability since then.

Almost always cheaper and safer to negotiate buyout or serve partial notice than to abscond.