Concept questionMedium~7 min

Interview question

What are boxing and unboxing in C#, and where can boxing appear unexpectedly when working with structs?

Boxing, unboxing, and interface calls on structs

Explains when a value is wrapped as an object, why unboxing is exact, and how generic APIs can avoid hidden allocations.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Boxing copies a value type into an object on the managed heap so it can be treated as object or as an interface it implements. Unboxing checks that the boxed value has the exact expected value type and copies the value out. For example, assigning an int to object boxes it, and casting that object back to int unboxes it. Casting a boxed int directly to long fails even though an ordinary numeric conversion from int to long is valid.

Full answer below

Practice focus

Boxing allocation, exact unboxing, interface dispatch, generics, nullable values, mutation of boxed copies, and measurement.

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
Boxing is easy to dismiss as old syntax, but it can still create allocations and copied state in generic-looking logging, formatting, interface, and collection code.
Boxing copies a value type into an object on the managed heap so it can be treated as object or as an interface it implements. Unboxing checks that the boxed value has the exact expected value type and copies the value out. For example, assigning an int to object boxes it, and casting that object back to int unboxes it. Casting a boxed int directly to long fails even though an ordinary numeric conversion from int to long is valid.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Boxing can appear when a struct is passed to an object parameter, stored in a non-generic collection, or used through an interface in a call site that cannot use constrained generic dispatch. The boxed object contains a copy, so mutating the boxed struct does not update the original local value. Generic collections such as List<int> and generic methods can preserve the concrete value type and usually avoid boxing. Interpolated string handlers and generic formatting APIs can also avoid allocations that older object-array formatting created, but I would verify the actual overload selected.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I treat boxing as a measured hot-path concern, not a reason to distort ordinary code. A few boxes in administrative logic are rarely important, while boxing per item in a high-volume parser, telemetry loop, or serializer can create visible allocation and GC pressure. I would use a profiler or BenchmarkDotNet to confirm the source, inspect interface and delegate conversions, and prefer constrained generic APIs where the call is performance-sensitive. Nullable value types have special boxing behavior: a null nullable boxes to null, while a populated nullable boxes the underlying value. Ref structs cannot be boxed at all because their lifetime cannot escape to the heap.

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

Describing boxing as only a type conversion and ignoring the copied boxed object.
Expecting a numeric widening conversion to happen during unboxing.
Replacing clear APIs with generics before confirming boxing matters.
Mutating a boxed struct and expecting the original value to change.

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

Details

Cannot name a realistic call site that can box a value.
Assumes every interface call on every struct always boxes in all generic contexts.
Claims unboxing returns a reference to the original local value.
Optimizes allocation without profiling the hot path.

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.

Why can a constrained generic call avoid boxing?
What happens when a nullable value type is boxed?
Why can a ref struct not be boxed?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Go deeper

Practice the next layer of the same subject.

Value and reference semantics

Opening drill

Concept questionMedium~7 min

Interview question

What are boxing and unboxing in C#, and where can boxing appear unexpectedly when working with structs?

Boxing, unboxing, and interface calls on structs

Explains when a value is wrapped as an object, why unboxing is exact, and how generic APIs can avoid hidden allocations.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Boxing allocation, exact unboxing, interface dispatch, generics, nullable values, mutation of boxed copies, and measurement.

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
Boxing is easy to dismiss as old syntax, but it can still create allocations and copied state in generic-looking logging, formatting, interface, and collection code.
Boxing copies a value type into an object on the managed heap so it can be treated as object or as an interface it implements. Unboxing checks that the boxed value has the exact expected value type and copies the value out. For example, assigning an int to object boxes it, and casting that object back to int unboxes it. Casting a boxed int directly to long fails even though an ordinary numeric conversion from int to long is valid.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Boxing can appear when a struct is passed to an object parameter, stored in a non-generic collection, or used through an interface in a call site that cannot use constrained generic dispatch. The boxed object contains a copy, so mutating the boxed struct does not update the original local value. Generic collections such as List<int> and generic methods can preserve the concrete value type and usually avoid boxing. Interpolated string handlers and generic formatting APIs can also avoid allocations that older object-array formatting created, but I would verify the actual overload selected.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I treat boxing as a measured hot-path concern, not a reason to distort ordinary code. A few boxes in administrative logic are rarely important, while boxing per item in a high-volume parser, telemetry loop, or serializer can create visible allocation and GC pressure. I would use a profiler or BenchmarkDotNet to confirm the source, inspect interface and delegate conversions, and prefer constrained generic APIs where the call is performance-sensitive. Nullable value types have special boxing behavior: a null nullable boxes to null, while a populated nullable boxes the underlying value. Ref structs cannot be boxed at all because their lifetime cannot escape to the heap.

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

Describing boxing as only a type conversion and ignoring the copied boxed object.
Expecting a numeric widening conversion to happen during unboxing.
Replacing clear APIs with generics before confirming boxing matters.
Mutating a boxed struct and expecting the original value to change.

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

Details

Cannot name a realistic call site that can box a value.
Assumes every interface call on every struct always boxes in all generic contexts.
Claims unboxing returns a reference to the original local value.
Optimizes allocation without profiling the hot path.

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.

Why can a constrained generic call avoid boxing?
What happens when a nullable value type is boxed?
Why can a ref struct not be boxed?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Go deeper

Practice the next layer of the same subject.

Value and reference semantics

What are boxing and unboxing in C#, and where can boxing appear unexpectedly when working with structs?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper

What are boxing and unboxing in C#, and where can boxing appear unexpectedly when working with structs?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper