Interview Q&A

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: Start with gratitude, then move to value: explain why you are excited about the role and why your impact justifies a better package. A post-offer negotiation works best when your ask is anchored in market data and your recent outcomes. Keep the tone collaborative so HR sees you as a long-term hire, not a short-term transaction.

Why this matters in Salary Negotiation

This is easiest to do in the first 24 to 48 hours after offer release, before background checks and onboarding steps begin.

Step-by-step approach

1. Thank HR for the offer and confirm you are seriously interested in joining.
2. Benchmark compensation for your exact role, location, and experience using at least three credible sources.
3. Prepare a one-page value brief with 3 achievements tied to revenue, cost, reliability, or delivery speed.
4. Share a clear expected range instead of one rigid number, and mention your ideal fixed-pay mix.
5. Discuss negotiable components like joining bonus, retention bonus, ESOP vesting, or appraisal cycle.
6. Close by asking when you can expect a revised offer so the process does not lose momentum.

Real-world example

Priya received an SDE-2 offer from Flipkart while working at TCS. She thanked the recruiter first, then shared numbers showing she reduced production incidents by 38% and cut API latency by 120 ms in her current role. Rahul, now at Razorpay, helped her present a range rather than a single demand. Flipkart revised her CTC upward and improved the fixed component, and Priya accepted confidently.

Numbers & benchmarks

• A practical negotiation range is usually 8% to 15% wide.
• For most professionals, keeping variable pay under 20% improves monthly cash-flow stability.
• A 24 to 48 hour response window after offer receipt is usually ideal for renegotiation.

Mistakes to avoid

• Jumping directly to money without first signaling interest in the role.
• Quoting random social-media salary figures with no role/location context.
• Using emotional language like "I deserve this" instead of evidence-based outcomes.
• Waiting until the joining date is near and creating unnecessary urgency.

Ask once, ask clearly, and support it with proof.

Short answer: A reasonable increase is one that reflects both market rate and your capability uplift. The right number depends on role criticality, tech stack rarity, and whether you are moving from support to core product ownership. Evaluate total compensation quality, not just percentage hike.

Step-by-step approach

1. Identify whether your move is lateral, step-up, or domain switch; each has different hike expectations.
2. Compare current responsibilities against target JD to estimate scope premium.
3. Benchmark at least 8 to 10 active job postings with disclosed ranges when available.
4. Separate fixed pay, variable pay, and benefits before concluding what is reasonable.
5. Stress-test offer sustainability by calculating post-tax take-home and annual volatility.
6. Choose only offers that improve both pay and learning trajectory.

Real-world example

Karthik worked in support engineering at Infosys and got an SRE role interview at Swiggy. His first instinct was to ask for 30%, but the role required incident leadership and automation ownership across teams. Neha from PhonePe helped him benchmark similar roles in Bengaluru and identify a better range. He negotiated a 47% increase with stronger fixed pay and still met company budget expectations.

Numbers & benchmarks

• Lateral switches often settle around 20% to 40%.
• Role-upgrade switches can move into 35% to 60% if demand is high.
• If variable pay is above 25%, verify historical payout before valuing it fully.

Mistakes to avoid

• Using one percentage rule for every type of role change.
• Counting retention bonus as guaranteed annual income.
• Ignoring city-level compensation differences while comparing offers.
• Choosing highest CTC even when role quality is weak.

Reasonable means market-aligned and sustainable for both sides.

Short answer: Freshers can negotiate, but the strategy is different: prove readiness, not tenure. If you have internships, strong projects, or competition wins, use them to justify a modest but meaningful revision. Focus on fixed pay and learning runway rather than only CTC headline.

Step-by-step approach

1. List practical signals of readiness: internships, open-source contributions, hackathon wins, or deployed apps.
2. Research entry-level pay ranges for your stack in your target city.
3. Ask for clarity on probation conversion, training timeline, and first review cycle.
4. Request a realistic improvement in fixed pay if total CTC cannot move much.
5. Negotiate onboarding support such as relocation assistance if applicable.
6. Confirm all terms in writing before signing the offer.

Real-world example

Ananya, a final-year student from Pune, got an offer from Infosys and another from a product startup in Chennai. She showed her internship results, including a dashboard feature adopted by 2,000 internal users. Vikram from Razorpay suggested she ask for a better fixed component and an early performance review. The startup increased fixed pay and offered a 6-month review milestone, which she accepted.

Numbers & benchmarks

• Even a 5% to 12% revision at fresher stage compounds strongly over 2 to 3 years.
• A 6-month review clause can be more valuable than a one-time sign-on bonus.
• If relocation is required, request clear relocation reimbursement limits upfront.

Mistakes to avoid

• Assuming freshers cannot negotiate at all.
• Asking for unrealistic jumps without portfolio proof.
• Ignoring probation terms and review timing.
• Selecting offer only by brand name without role quality.

As a fresher, negotiate with proof and humility.

Short answer: Email negotiation should be crisp, evidence-led, and respectful of timeline. A strong mail includes appreciation, rationale, expected range, and a clear next step. Keep it short enough to read in one screen but specific enough to approve.

Step-by-step approach

1. Use a precise subject line such as "Offer Discussion - [Your Name]".
2. Open with appreciation and confirm your interest in accepting the role.
3. Add 2 to 3 quantified reasons that support your revised expectation.
4. Mention your expected range and preferred structure in one clear paragraph.
5. Request a timeline for response and keep availability open for a call.
6. If no reply in two business days, send one professional follow-up.

Real-world example

Neha got an offer from Infosys while finishing interviews with two other firms. Instead of negotiating on chat, she sent a concise email with three impact metrics from her previous role at CRED and a realistic range. Arjun from Razorpay helped her remove emotional phrases and keep the message business-focused. HR replied the same day, revised the fixed pay, and closed the offer quickly.

What to say / email template

Hi [HR Name],

Thank you for sharing the offer. I am genuinely excited about this opportunity and would like to discuss compensation once before final acceptance.

Based on role scope and my recent outcomes in [domain] (for example: [metric 1], [metric 2], [metric 3]), I am targeting a CTC range of [X]-[Y], with preference for a stronger fixed component.

If feasible, please let me know whether we can review this. I am available for a quick call today/tomorrow.

Regards,
[Your Name]

Mistakes to avoid

• Writing long emotional mails without concrete evidence.
• Sending multiple reminders in a short span and appearing impatient.
• Using aggressive phrases like "final offer or I walk away."
• Forgetting to mention continued interest in joining.

One clear email beats five vague follow-ups.

Short answer: An ATS-friendly resume is simple, keyword-aligned, and evidence-based. Use plain formatting so systems can parse sections correctly, then make each bullet prove measurable impact. If ATS can read it and a recruiter can scan it in 20 seconds, you are on the right track.

Step-by-step approach

1. Use a single-column layout with standard headings like Summary, Skills, Experience, and Projects.
2. Extract required keywords from JD and incorporate them naturally in skills and bullets.
3. Rewrite every bullet as Action + Context + Result with numbers where possible.
4. Remove tables, icons, and text boxes that often break ATS parsing.
5. Keep file as PDF or DOCX only if the job portal specifically supports it.
6. Run a final ATS score check and human readability review before applying.

Real-world example

Priya applied to 40 roles from TCS and got almost no callbacks. Rahul from Razorpay reviewed her resume and found heavy design formatting with missing backend keywords. She rebuilt it into a clean one-column format with impact metrics for latency and uptime improvements. Callback rate improved within two weeks.

Mistakes to avoid

• Using visually rich templates that ATS cannot parse properly.
• Stuffing keywords unnaturally and reducing readability.
• Listing responsibilities without measurable outcomes.
• Submitting same resume to all roles without adaptation.

Toolliyo resources

• Resume Builder
• ATS Rewriter

Readable by machine first, impressive to human next.

Short answer: A professional summary should state role identity, core strengths, and business impact in 3 to 4 lines. It is not an objective statement or motivational quote. Think of it as your positioning headline for recruiter skimming.

Step-by-step approach

1. Start with your role + years of experience + core domain in one sentence.
2. Add 2 key strengths aligned to target job requirements.
3. Include one measurable achievement that supports credibility.
4. Mention preferred scope, for example product backend or ML platform work.
5. Keep total length under 70 words for readability.
6. Customize summary slightly for each major role type you apply to.

Real-world example

Karthik’s resume opened with a vague line: "Seeking challenging opportunities." Isha from PhonePe helped him rewrite the summary to mention backend expertise, payment-domain experience, and latency improvement outcomes. Recruiters could now understand his profile in seconds. He started receiving more relevant interview calls.

Mistakes to avoid

• Using generic objective lines with no role signal.
• Writing a 150-word paragraph that no recruiter reads.
• Adding personal adjectives without proof.
• Forgetting to align summary with target job type.

Your summary should answer: who are you, what can you deliver?

Short answer: No-experience resumes should highlight projects, internships, coursework relevance, and problem-solving evidence. Recruiters know you are entry-level; they want proof that you can execute and learn quickly. A focused project-first resume can outperform a generic fresher template.

Step-by-step approach

1. Open with a clear summary of target role and relevant technical stack.
2. Prioritize academic or personal projects with measurable outcomes.
3. Add internships, hackathons, open-source work, or freelancing if available.
4. Keep skills limited to tools you can explain confidently in interviews.
5. Include links to GitHub, portfolio, and deployed demos.
6. Tailor project keywords to each role before applying.

Real-world example

Ananya was a fresher from Hyderabad with no full-time work history. Vikram from Infosys helped her place projects above education and add measurable outcomes for each build. She added GitHub links and one deployed app demo in her resume header. Her profile started receiving internship-to-full-time callbacks.

Mistakes to avoid

• Leaving project section vague with no outcomes.
• Adding every class assignment as if it were production work.
• Listing advanced skills without practical proof.
• Ignoring portfolio links in resume.

For freshers, projects are your experience.

Short answer: Tailoring means changing emphasis, not inventing experience. Mirror the job language, prioritize relevant achievements, and remove distracting content. A targeted resume dramatically improves ATS match and recruiter response rate.

Step-by-step approach

1. Read JD carefully and mark required skills, domain context, and responsibility keywords.
2. Reorder experience bullets so most relevant impact appears first.
3. Swap project examples to match target role expectations.
4. Adjust summary line to reflect role title and domain focus.
5. Update skills section to emphasize directly relevant tools.
6. Run a quick ATS keyword-gap check before submitting.

Real-world example

Meera used one generic resume for all roles while applying from Infosys. Rohit from Freshworks showed her how to create two versions: backend-heavy and data-heavy. She reordered bullets and projects based on each JD instead of rewriting from scratch. Her interviews became more relevant and conversion improved.

Mistakes to avoid

• Copy-pasting JD words without matching evidence.
• Changing everything and losing profile authenticity.
• Keeping irrelevant projects at top due to personal preference.
• Sending same resume to fundamentally different role types.

Toolliyo resources

• Resume Builder
• ATS Rewriter

Tailor emphasis, never fabricate experience.

Short answer: Work & Office decisions become easier when you prepare evidence, propose options, and communicate clearly. A structured approach reduces uncertainty and leads to better outcomes. Keep your plan practical and well documented from start to finish.

Step-by-step approach

1. Define your target outcome and constraints before taking action.
2. Collect relevant data points from policy, market, and stakeholder inputs.
3. Build a practical execution plan with milestones and fallback options.
4. Communicate clearly and confirm all decisions in writing.
5. Review results and refine your approach for the next cycle.

Real-world example

Priya was working at TCS and needed to handle this situation: how to ask for work from home. She prepared a clear plan with timelines, ownership, and expected outcomes before speaking to HR and her manager. Rahul, who had recently moved to Razorpay, reviewed her approach and helped her tighten the messaging with measurable results. Within a few weeks, Priya achieved a better career outcome while preserving strong professional relationships.

What to say / email template

Hi [Name],

I would like to discuss [topic] and propose an option that supports both team continuity and my career timeline.
I have prepared a practical plan with ownership, dates, and transition support.

Proposed plan:
- [Point 1]
- [Point 2]
- [Point 3]

Please let me know if we can finalize this by [date]. Thank you for your support.

Mistakes to avoid

• Acting without understanding policy, market context, or role expectations.
• Using generic claims instead of measurable evidence and concrete examples.
• Delaying communication and creating last-minute pressure for stakeholders.
• Skipping rehearsal, which causes weak delivery during interviews or negotiations.

Capture major decisions in writing to avoid confusion and future disputes.

Short answer: Work & Office decisions become easier when you prepare evidence, propose options, and communicate clearly. A structured approach reduces uncertainty and leads to better outcomes. Keep your plan practical and well documented from start to finish.

Step-by-step approach

1. Define your target outcome and constraints before taking action.
2. Collect relevant data points from policy, market, and stakeholder inputs.
3. Build a practical execution plan with milestones and fallback options.
4. Communicate clearly and confirm all decisions in writing.
5. Review results and refine your approach for the next cycle.

Real-world example

Karan was working at Razorpay and needed to handle this situation: how to improve productivity at work. She prepared a clear plan with timelines, ownership, and expected outcomes before speaking to HR and her manager. Isha, who had recently moved to PhonePe, reviewed her approach and helped her tighten the messaging with measurable results. Within a few weeks, Karan achieved a better career outcome while preserving strong professional relationships.

Mistakes to avoid

• Acting without understanding policy, market context, or role expectations.
• Using generic claims instead of measurable evidence and concrete examples.
• Delaying communication and creating last-minute pressure for stakeholders.
• Skipping rehearsal, which causes weak delivery during interviews or negotiations.

Capture major decisions in writing to avoid confusion and future disputes.

Short answer: Work & Office decisions become easier when you prepare evidence, propose options, and communicate clearly. A structured approach reduces uncertainty and leads to better outcomes. Keep your plan practical and well documented from start to finish.

Step-by-step approach

1. Define your target outcome and constraints before taking action.
2. Collect relevant data points from policy, market, and stakeholder inputs.
3. Build a practical execution plan with milestones and fallback options.
4. Communicate clearly and confirm all decisions in writing.
5. Review results and refine your approach for the next cycle.

Real-world example

Ananya was working at PhonePe and needed to handle this situation: how to ask for a promotion. She prepared a clear plan with timelines, ownership, and expected outcomes before speaking to HR and her manager. Vikram, who had recently moved to Infosys, reviewed her approach and helped her tighten the messaging with measurable results. Within a few weeks, Ananya achieved a better career outcome while preserving strong professional relationships.

What to say / email template

Hi [Name],

I would like to discuss [topic] and propose an option that supports both team continuity and my career timeline.
I have prepared a practical plan with ownership, dates, and transition support.

Proposed plan:
- [Point 1]
- [Point 2]
- [Point 3]

Please let me know if we can finalize this by [date]. Thank you for your support.

Mistakes to avoid

• Acting without understanding policy, market context, or role expectations.
• Using generic claims instead of measurable evidence and concrete examples.
• Delaying communication and creating last-minute pressure for stakeholders.
• Skipping rehearsal, which causes weak delivery during interviews or negotiations.

Capture major decisions in writing to avoid confusion and future disputes.

Short answer: Work & Office decisions become easier when you prepare evidence, propose options, and communicate clearly. A structured approach reduces uncertainty and leads to better outcomes. Keep your plan practical and well documented from start to finish.

Step-by-step approach

1. Define your target outcome and constraints before taking action.
2. Collect relevant data points from policy, market, and stakeholder inputs.
3. Build a practical execution plan with milestones and fallback options.
4. Communicate clearly and confirm all decisions in writing.
5. Review results and refine your approach for the next cycle.

Real-world example

Meera was working at Infosys and needed to handle this situation: how to become a high performer. She prepared a clear plan with timelines, ownership, and expected outcomes before speaking to HR and her manager. Rohit, who had recently moved to Freshworks, reviewed her approach and helped her tighten the messaging with measurable results. Within a few weeks, Meera achieved a better career outcome while preserving strong professional relationships.

Mistakes to avoid

• Acting without understanding policy, market context, or role expectations.
• Using generic claims instead of measurable evidence and concrete examples.
• Delaying communication and creating last-minute pressure for stakeholders.
• Skipping rehearsal, which causes weak delivery during interviews or negotiations.

Capture major decisions in writing to avoid confusion and future disputes.