Interview Q&A

Short answer: bstract Class Meaning Provides base behavior with shared implementation Represents IS-A inheritance relationship public abstract class PaymentBase { public void Log() => Console.WriteLine("Payment logged"); public abstract void Pay(decimal amount); } Summary Interface = Capability bstract Class = Shared Base Behavior bstract Class Meaning Provides base… behavior with shared implementation Represents IS-A inheritance…

Explain a bit more

relationship public abstract class PaymentBase { public void Log() => Console.WriteLine("Payment logged"); public abstract void Pay(decimal amount); } Summary Interface = Capability bstract Class = Shared Base Behavior

Real-world example (ShopNest)

Answer with: definition → one ShopNest-style story → trade-off → how you would verify it in production.

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: [ApiController] [Route("api/[controller]")] public class EmployeeController : ControllerBase { [HttpGet("{id}")] public IActionResult Get(int id)

Example code

{
return Ok(new { Id = id, Name = "Sandeep" });
}
} Key Characteristics: Lightweight JSON support by default Built-in dependency injection

Real-world example (ShopNest)

Answer with: definition → one ShopNest-style story → trade-off → how you would verify it in production.

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 never start development on vague requirements.

Explain a bit more

I request a quick sync with the stakeholder or BA to clarify the business goal. If things are still evolving, I build with feature toggles or keep the architecture flexible (e.g., config-driven logic or modular components). I also document assumptions clearly in Jira or Confluence, so if changes come later, we know what to revisit. Decision-Making & Problem Solving – Interview Questions + Sample Answers

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 never start development on vague requirements.

Explain a bit more

I request a quick sync with the stakeholder or BA to clarify the business goal. If things are still evolving, I build with feature toggles or keep the architecture flexible (e.g., config-driven logic or modular components). I also document assumptions clearly in Jira or Confluence, so if changes come later, we know what to revisit. Decision-Making & Problem Solving – Interview Questions + Sample

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: simply be moved forward to the tip of the other branch without creating a new merge commit.

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

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: common ancestor to determine how to combine changes, potentially creating a new merge commit. Long Answers:

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

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 merge that involves the two branch tips and their common ancestor to determine how to combine changes, potentially creating a new merge commit. Long Answers:

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

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.