Interview Q&A

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

[ApiController]

[Route("api/[controller]")]

public class EmployeeController : ControllerBase
{

[HttpGet("{id}")]

public IActionResult Get(int id)
{
return Ok(new { Id = id, Name = "Sandeep" });
}
}

Key Characteristics:

• Lightweight
• JSON support by default
• Built-in dependency injection

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

lso document assumptions clearly in Jira or Confluence, so if changes come later, we know

what to revisit.

Decision-Making & Problem Solving –

Interview Questions + Sample

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

Answer: simply be moved forward to the tip of the other branch without creating a new merge commit.

What interviewers expect

• A clear definition tied to Version Control in Git & GitHub projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Git & GitHub application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Git & GitHub architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Answer: common ancestor to determine how to combine changes, potentially creating a new merge commit. Long Answers:

What interviewers expect

• A clear definition tied to Version Control in Git & GitHub projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Git & GitHub application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Git & GitHub architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

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:

What interviewers expect

• A clear definition tied to Version Control in Git & GitHub projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Git & GitHub application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Git & GitHub architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.