Interview Q&A

Short answer: Mocking/stubbing replaces external dependencies like web services or message queues with controlled test doubles to isolate the parts under test and control external behavior without invoking real services.

Real-world example (ShopNest)

When testing ShopNest’s order service, mock IPaymentGateway so tests do not call Razorpay.

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: In-memory databases allow fast, isolated testing of data access code without a real database, making integration tests easier to run and maintain, but may lack certain behaviors of real databases (like relational constraints). Practical & Advanced Topics

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: Dependency Injection (DI) is a design pattern where dependencies are provided rather than created inside a class. DI makes testing easier by allowing tests to inject mock or fake implementations of dependencies, isolating the unit under test.

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: Stub: Provides predefined data to the test. Mock: Verifies that certain interactions happened. Fake: Has a working implementation, often simpler than production.

Real-world example (ShopNest)

When testing ShopNest’s order service, mock IPaymentGateway so tests do not call Razorpay.

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 concurrency issue that only appeared under load was caught by a combination of unit and integration tests with parallel execution. It was tricky to reproduce but testing helped identify race conditions.

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: I have implemented CI/CD pipelines integrating xUnit tests, automated database resets, and used mocking extensively to achieve reliable, fast test runs that provide immediate feedback.

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: The Assert class provides methods to verify conditions in tests, such as equality, truth, exceptions, or null values. It determines whether a test passes or fails based on these validations.

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: Mocking involves creating objects that simulate behavior and expectations to verify interactions. Spying records information about how real or partial objects are used, focusing on what happened rather than controlling behavior.

Real-world example (ShopNest)

When testing ShopNest’s order service, mock IPaymentGateway so tests do not call Razorpay.

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: Typically, I aim for at least 80% coverage on critical code paths, but focus more on meaningful coverage rather than just numbers. Coverage alone doesn’t guarantee quality.

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: 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.