Interview Q&A

Short answer: Unit testing involves testing the smallest parts of an application (units) independently to ensure they work correctly. It is important because it helps detect bugs early, improves code quality, supports refactoring, and provides documentation for expected behavior.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A good unit test is: Isolated: Tests one unit without external dependencies. Repeatable: Produces the same results every run. Fast: Executes quickly to allow frequent runs. Automated: Runs without manual intervention. Clear: Easy to understand and maintain. Independent: Does not depend on other tests.

Real-world example (ShopNest)

Arrange a cart with 2 items → Act Checkout() → Assert total and that payment was called once.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Focus on testing: Critical business logic. Edge cases and boundary conditions. Public methods and APIs. Error handling and exception paths. Code that is prone to bugs or complex.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Unit Testing: Tests individual units in isolation. Integration Testing: Tests interaction between multiple components or systems. Functional Testing: Tests end-to-end functionality from the user's perspective.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Challenges include: Managing external dependencies and state. Writing tests for legacy or tightly coupled code. Maintaining tests as code evolves. Ensuring tests are meaningful and not brittle. Balancing test coverage and development speed.

Real-world example (ShopNest)

ShopNest unit tests cover pricing and discount rules so a bad coupon change fails in CI before customers see it.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Eventual consistency is a consistency model used in distributed systems where updates to data will propagate and eventually become consistent across all nodes, but not necessarily immediately.

Explain a bit more

How it works: In an eventually consistent system, updates are made to a node and eventually, that update will be propagated to all other nodes. It allows for temporary inconsistencies, but ensures that the system will converge to a consistent state over time. Use cases: Suitable for systems that can tolerate a delay in consistency, like NoSQL databases (Cassandra, DynamoDB) and systems dealing with high availability and massive scale.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The DISTINCT keyword is used to return only unique values in the result set, removing any duplicate rows.

Example code

SELECT DISTINCT Country FROM Customers; This will return a list of unique countries from the Customers table.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The UNION operator combines the result sets of two or more SELECT queries into a single result set and removes duplicate records. All SELECT queries must have the same number of columns with compatible data types.

Example code

SELECT Name FROM Employees UNION SELECT Name FROM Customers;

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: CHAR: A fixed-length string data type. It always reserves the same amount of space regardless of the string's length. Use case: When the length of the string is known and consistent. VARCHAR: A variable-length string data type. It only uses as much space as needed to store the string. Use case: When the string length can vary.

Example code

CREATE TABLE Example ( fixed_char CHAR(10), variable_char VARCHAR(10) );

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The LIMIT clause is used to specify the number of records returned by a SELECT query. It is commonly used to restrict the number of rows, especially for pagination.

Example code

SELECT * FROM Employees LIMIT 5; This will return only the first 5 rows from the Employees table.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: NULL represents the absence of a value in a column. It is not the same as an empty string or zero. Handling NULL: To check for NULL, use IS NULL or IS NOT NULL. To handle NULL in queries, use COALESCE() (returns the first non-NULL value) or IFNULL().

Example code

SELECT Name, IFNULL(Salary, 0) FROM Employees;

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: And does not log individual row deletions.

Explain a bit more

Cannot be rolled back (in most databases). And does not log individual row deletions. Cannot be rolled back (in most databases). nd does not log individual row deletions. Cannot be rolled back (in most databases). Resets auto-increment counters. DELETE: Deletes rows based on a condition, and can be rolled back (if using transactions). Slower compared to TRUNCATE. DELETE FROM Employees WHERE Age < 18; -- Deletes only specific rows TRUNCATE TABLE Employees; -- Deletes all rows nd does not log individual row deletions. Cannot be rolled back (in most databases). Resets auto-increment counters. DELETE: Deletes rows based on a condition, and can be rolled back (if using transactions). Slower compared to TRUNCATE.

Example code

DELETE FROM Employees WHERE Age < 18; -- Deletes only specific rows TRUNCATE TABLE Employees; -- Deletes all rows

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: TRUNCATE: Deletes all rows in a table, but the table structure remains. It is faster and does not log individual row deletions. Cannot be rolled back (in most databases). Resets auto-increment counters. DELETE: Deletes rows based on a condition, and can be rolled back (if using transactions). Slower compared to TRUNCATE.

Example code

DELETE FROM Employees WHERE Age < 18; -- Deletes only specific rows TRUNCATE TABLE Employees; -- Deletes all rows

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: An Index is a database object that speeds up the retrieval of rows from a table by creating a data structure (often a B-tree). Indexes improve the performance of SELECT queries but can slow down INSERT, UPDATE, and DELETE operations.

Example code

CREATE INDEX idx_employee_name ON Employees(Name);

Real-world example (ShopNest)

ShopNest adds an index on Orders(CustomerId, CreatedAt) because “my recent orders” is queried constantly.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The ACID properties ensure reliable processing of database transactions:

Real-world example (ShopNest)

Checkout wraps stock decrement + order insert in a transaction so you never sell stock you do not have.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

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: Your hike target should be based on market demand, not only your current CTC. If your skill set is niche or revenue-linked, you can justify a stronger jump than a standard lateral move. Always decide a target, an acceptable minimum, and a walk-away number before interviews close.

Step-by-step approach

1. Map your role to market bands for your city and years of experience.
2. Classify your skills into common, in-demand, and scarce to estimate pricing power.
3. Set three numbers: aspirational, fair, and minimum acceptable compensation.
4. Adjust expected hike if the new role has bigger scope, team ownership, or on-call complexity.
5. Calculate real take-home after variable pay, tax impact, and benefits breakdown.
6. Use this line in discussion: "Based on scope and market benchmarks, I am targeting this range."

Real-world example

Ananya, a backend engineer at Infosys, got interview calls from Zoho and Freshworks. She realized one role included architecture ownership and weekend release responsibility, so she increased her expected hike ask. Vikram reviewed her compensation sheet and helped her compare fixed pay versus variable components. She negotiated a stronger final number at Zoho with better in-hand salary and accepted.

What to say / email template

Hi [Recruiter Name], thank you for the offer details. Based on current market compensation for this scope and my recent outcomes in [domain], I am targeting a total CTC in the range of [X]-[Y], with stronger fixed pay preference. I am very interested in joining and would appreciate if we can review the offer once.

Numbers & benchmarks

• Many India job switches close in the 25% to 55% hike range depending on skill demand.
• For high-demand domains, candidates sometimes negotiate 60%+ with strong proof of impact.
• Keep at least 10% buffer between target and minimum acceptable number.

Mistakes to avoid

• Copying a friend's hike expectation without considering your own role maturity.
• Ignoring hidden deductions and overestimating actual monthly in-hand.
• Asking too low early in process and getting anchored below market.
• Not revising expectations when scope significantly increases.

Decide your walk-away number before negotiation starts.

Short answer: Treat HR as a partner who must balance budget, internal parity, and candidate closure timelines. When you understand these constraints, your ask becomes easier to approve. Lead with business outcomes and role fit, then discuss compensation structure logically.

Step-by-step approach

1. Ask HR how compensation is split across fixed, variable, bonus, and long-term benefits.
2. Position your request around role scope, risk ownership, and measurable delivery record.
3. Use a calm, data-backed narrative instead of competitive pressure language.
4. Negotiate sequence: fixed pay first, then one-time bonuses, then review timeline.
5. If numbers are frozen, request an early performance review clause in writing.
6. Confirm final details by email to avoid misalignment before offer acceptance.

Real-world example

Neha was interviewing for a platform lead role at Razorpay while employed at Flipkart. Instead of saying "another company is paying more," she explained that she would own migration risk and 24x7 availability for critical services. Arjun from Zoho helped her rewrite her talking points around business continuity and release stability. HR could not change total CTC much, but increased fixed pay and added a 6-month review commitment, which Neha accepted.

Mistakes to avoid

• Speaking aggressively and turning negotiation into confrontation.
• Skipping structure details and focusing only on total CTC headline.
• Assuming HR can always revise numbers without policy limits.
• Accepting verbal promises without written confirmation.

Follow-up questions you may get

• If HR says the budget is frozen, ask: "Can we agree on a written review checkpoint after 6 months based on defined KPIs?"

Negotiate in layers: fixed, bonus, then review cycle.

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: To negotiate a higher CTC, you must demonstrate higher expected impact. Recruiters can stretch budgets when they can justify your value to hiring managers and finance. Build your case around outcomes, not effort or tenure.

Step-by-step approach

1. Translate your last two years of work into business metrics and decision-level talking points.
2. Highlight risk areas in the new role where your experience reduces failure probability.
3. Offer two compensation structures, for example higher fixed or lower fixed plus joining bonus.
4. Ask politely whether there is room in band based on interview feedback quality.
5. Use competing opportunities carefully as context, not as threats.
6. Request a written revised breakdown before final confirmation.

Real-world example

Meera interviewed at CRED for a senior Android role while working at Freshworks. She prepared a scorecard showing app crash-rate reduction, payment success uplift, and release turnaround improvements from her past projects. The recruiter said the band was tight, so Meera offered two structure options. CRED approved a higher CTC with a better fixed portion and a joining bonus to close quickly.

What to say / email template

I am very positive about this role. Based on interview scope and the outcomes I have delivered in similar responsibilities, is there flexibility to move the offer closer to [target range]? I am open to discussing structure options to make this workable.

Mistakes to avoid

• Talking only about years of experience without impact numbers.
• Demanding max band despite average interview performance.
• Overusing external offers as pressure in every conversation.
• Forgetting to verify if ESOP value is real or only projected.

Give alternatives; flexibility increases approval probability.

Short answer: A convincing justification links your compensation ask to measurable business value and future scope. Replace statements like "I worked hard" with clear evidence such as uptime, cost savings, delivery speed, or customer impact. Decision-makers approve hikes faster when your story is quantifiable and role-aligned.

Step-by-step approach

1. Build a value dossier with metrics from at least 3 projects you led or stabilized.
2. Connect each metric to one business outcome, such as revenue protection or support cost reduction.
3. Show benchmark parity by comparing your role-level compensation with market data.
4. Present your ask as a fair correction, not an emotional demand.
5. Suggest a timeline for decision and offer to share additional details if needed.
6. If immediate raise is not possible, negotiate milestone-linked revision checkpoints.

Real-world example

Arjun at Zoho wanted a correction after taking on architecture ownership that was previously handled by two senior engineers. He documented migration completion, outage reduction, and faster release cycles over six months. Priya from TCS reviewed his note and advised him to align metrics with team-level business outcomes. HR approved a staged hike with a confirmed review in the next appraisal cycle.

Mistakes to avoid

• Making comparisons with colleagues instead of market and role expectations.
• Using generic adjectives like "excellent" without hard evidence.
• Submitting a hike request without showing expanded responsibility.
• Escalating emotionally when manager asks for data.

Your best argument is a measurable before-versus-after story.

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: Experienced candidates are evaluated on ownership depth, not just technical skills. Your negotiation should show that you can de-risk delivery, mentor teams, and improve business outcomes quickly. The stronger your leadership evidence, the more room you have to negotiate compensation structure.

Step-by-step approach

1. Summarize your last 3 years in terms of scope, team influence, and measurable impact.
2. Show examples where you handled ambiguity, incidents, or cross-team delivery risk.
3. Ask how success is measured in the first 90 days and align compensation discussion to that scope.
4. Negotiate fixed pay and variable payout conditions separately.
5. Discuss long-term wealth components like ESOP vesting schedule and liquidity history.
6. Lock in notice buyout support or joining flexibility if that affects your decision.

Real-world example

Vikram, a senior engineer at HCL, interviewed for a staff role at PhonePe. He highlighted how he mentored 11 engineers and reduced release rollback incidents by 41% across two quarters. Neha from Flipkart helped him frame this as leadership leverage rather than only coding output. PhonePe revised his package with better fixed pay, a buyout component, and clearer bonus terms.

Mistakes to avoid

• Discussing compensation before understanding role expectations fully.
• Ignoring payout conditions attached to variable components.
• Undervaluing managerial and mentoring impact in negotiation conversations.
• Not calculating opportunity cost of notice period overlap.

Follow-up questions you may get

• After final round, ask for compensation review only after receiving positive interview feedback signals.

For experienced roles, negotiate based on scope leverage.

Short answer: You can share current salary selectively, but do not let it become the only anchor. Redirect the conversation toward market value and role scope so your future compensation reflects the new responsibility. If disclosure is mandatory by policy, share accurate numbers with full breakup context.

Step-by-step approach

1. Ask politely whether current salary disclosure is mandatory for this hiring process.
2. If asked, share complete structure: fixed, variable, bonus, and one-time payouts.
3. Immediately re-anchor discussion on expected range tied to new role scope.
4. Explain differences between current role complexity and upcoming role expectations.
5. Avoid inflating numbers; any mismatch can fail background checks later.
6. Document disclosure and expected range clearly over email.

Real-world example

Rahul was interviewing at Swiggy while working at TCS and was asked to share current compensation early. He provided the exact breakup and clarified that a large part was one-time retention payout, not recurring income. Karthik from Zoho advised him to pivot the discussion to the new platform ownership scope. The recruiter accepted his reasoning and evaluated him against role band, not his old fixed salary.

Mistakes to avoid

• Sharing only total CTC and hiding non-recurring components.
• Refusing abruptly without understanding recruiter policy constraints.
• Inflating numbers and risking verification failure.
• Letting old salary become permanent anchor for new role.

Disclose honestly, then re-anchor to market and scope.

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.