Concept questionEasy~5 minC# OOP & Type Design Essentials / 9 of 15

Interview question

How do C# access modifiers help design a maintainable API, and when would you choose internal or protected over public?

Access modifiers and assembly boundaries in C#

Uses public, internal, protected, private, and protected internal deliberately to control API surface and inheritance exposure.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I expose the smallest access surface that supports the intended callers. Private keeps implementation inside the declaring type. Internal exposes a type or member only within the assembly, which is useful for implementation components that several classes share but consumers should not call. Protected is for a deliberate inheritance contract, while public is for supported consumers rather than merely making tests or wiring convenient.

Full answer below

Practice focus

Public APIs, assembly boundaries, private state, protected extension points, internal implementation, friend assemblies, and compatibility.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Access modifiers define who may depend on a member. I expose the smallest surface that supports intended use because every public or protected member becomes harder to change safely.
I expose the smallest access surface that supports the intended callers. Private keeps implementation inside the declaring type. Internal exposes a type or member only within the assembly, which is useful for implementation components that several classes share but consumers should not call. Protected is for a deliberate inheritance contract, while public is for supported consumers rather than merely making tests or wiring convenient.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Protected internal allows access from the same assembly or derived types elsewhere, while private protected restricts access to derived types in the same assembly. Those combinations are uncommon and should have a clear extension reason. Tests can use public behavior, live in the same assembly, or use InternalsVisibleTo carefully. Changing production APIs only to enable tests is usually the wrong trade.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I treat public and protected surface as a versioned contract, especially in shared libraries. Binary and source compatibility can be affected by removing, renaming, sealing, or changing members. Internal boundaries also help architecture by preventing consumers from reaching implementation types even when they share a repository. I review accidental public types in packages and keep extension points few, documented, and tested. Reflection and serializers may still access non-public members, so access modifiers are design controls rather than a security boundary.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Making members public to simplify testing.
Using protected for arbitrary code reuse.
Treating internal as a security boundary.
Exposing implementation classes from a library.

Red flagsCandidateSigns the object design is fragileSignals that an interviewer may treat as risky.Open details

Details

Most types in a package are public without consumers.
Derived classes depend on many protected fields.
A minor release removes public members casually.
Reflection assumptions are undocumented.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What is the difference between internal and protected?
When is InternalsVisibleTo acceptable?
Why is protected part of the API contract?

Continue the section

Next in C# OOP & Type Design Essentials: Object construction

Step 10 of 15

Choose constructors, static factories, and builders

Opening drill

Concept questionEasy~5 minC# OOP & Type Design Essentials / 9 of 15

Interview question

How do C# access modifiers help design a maintainable API, and when would you choose internal or protected over public?

Access modifiers and assembly boundaries in C#

Uses public, internal, protected, private, and protected internal deliberately to control API surface and inheritance exposure.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Public APIs, assembly boundaries, private state, protected extension points, internal implementation, friend assemblies, and compatibility.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Access modifiers define who may depend on a member. I expose the smallest surface that supports intended use because every public or protected member becomes harder to change safely.
I expose the smallest access surface that supports the intended callers. Private keeps implementation inside the declaring type. Internal exposes a type or member only within the assembly, which is useful for implementation components that several classes share but consumers should not call. Protected is for a deliberate inheritance contract, while public is for supported consumers rather than merely making tests or wiring convenient.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Protected internal allows access from the same assembly or derived types elsewhere, while private protected restricts access to derived types in the same assembly. Those combinations are uncommon and should have a clear extension reason. Tests can use public behavior, live in the same assembly, or use InternalsVisibleTo carefully. Changing production APIs only to enable tests is usually the wrong trade.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I treat public and protected surface as a versioned contract, especially in shared libraries. Binary and source compatibility can be affected by removing, renaming, sealing, or changing members. Internal boundaries also help architecture by preventing consumers from reaching implementation types even when they share a repository. I review accidental public types in packages and keep extension points few, documented, and tested. Reflection and serializers may still access non-public members, so access modifiers are design controls rather than a security boundary.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Making members public to simplify testing.
Using protected for arbitrary code reuse.
Treating internal as a security boundary.
Exposing implementation classes from a library.

Red flagsCandidateSigns the object design is fragileSignals that an interviewer may treat as risky.Open details

Details

Most types in a package are public without consumers.
Derived classes depend on many protected fields.
A minor release removes public members casually.
Reflection assumptions are undocumented.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What is the difference between internal and protected?
When is InternalsVisibleTo acceptable?
Why is protected part of the API contract?

Continue the section

Next in C# OOP & Type Design Essentials: Object construction

Step 10 of 15

Choose constructors, static factories, and builders

How do C# access modifiers help design a maintainable API, and when would you choose internal or protected over public?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

How do C# access modifiers help design a maintainable API, and when would you choose internal or protected over public?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section