Practice C# interview answers on value and reference semantics, equality, LINQ execution, async and cancellation with a changing-query example. Start with the question, explain the mechanism, and then state an assumption or tradeoff. The scenarios below are original practice examples, not questions supplied by an employer.
How do value and reference semantics affect assignment?
A value-type assignment copies the value, while a reference-type assignment copies a reference to an object. A copied value can itself contain references, so 'copy' does not necessarily mean a deep copy of every object it mentions. Explain the concrete fields in your example. Avoid treating stack versus heap as a universal shortcut for semantics; the observable assignment and mutation behavior is what the question needs.
How should you explain equality?
Distinguish identity from the equality contract of the type. Two references can identify the same object, while two different objects may compare equal under a value-based rule. Explain which fields define equality and whether they can change. If the type is used in a hash-based collection, its hash behavior must agree with equality. A business identifier may be a safer key than an entire mutable object.
When does a LINQ query execute?
Many operations over an enumerable use deferred execution, so enumeration can read the source later. Materializing with an operation such as ToList creates a result at that point, but it does not necessarily deeply clone the contained objects. Explain the source and provider: a database-backed query introduces additional translation and execution considerations. Repeated enumeration may repeat work or produce different observations when the source changes.
What does await change about a method?
It allows asynchronous work to be composed without blocking the current thread for the entire wait in the usual I/O case. It does not make every operation run on another thread. Describe how the returned task represents completion and how exceptions are observed. Explain why an unawaited operation can outlive the scope or leave an error unobserved by the caller who expected the work to finish.
How should cancellation be handled?
Cancellation is cooperative: pass the appropriate token to operations that support it and respond to the request at suitable boundaries. Define what happens if part of a business operation already completed. Stopping a wait is not the same as undoing a committed change. Explain cleanup and the response contract, then test cancellation before work, during waiting and after a result is available.
Worked example
Original example: create a deferred query selecting active users, then add a newly active user to the source before enumerating. Depending on the source and operation, the later enumeration can include the new record. If the requirement is a snapshot of membership at creation time, materialize at the correct point.
Now mutate a user's display name after materialization. A list of references may still show the changed name. Explain the difference between copying list membership and copying each object's state. That distinction prevents a simplistic 'ToList makes everything immutable' answer.
Practice plan
Predict results for assigning a reference, copying a value containing a reference and materializing a LINQ query. Write down the expected observation before running the example. Then explain a cancellation scenario in which a completed database update cannot simply be undone by canceling the caller's token.
Use Cluegent during preparation to review your own answer: ask for one incorrect assumption and one follow-up question, then respond again without suggestions. Check current plans before choosing a subscription. Follow the employer's rules during the actual interview.
Sources checked
These official references support the guide. Product details and technical documentation can change; check the linked source for current information.
Where Cluegent helps
Cluegent supports permitted live workflows with transcript context, typed prompts, screenshot-aware answers, resume context, custom response behavior, quick action buttons, and a private desktop overlay. It is most useful when you already understand the subject and need help staying structured under pressure.
Frequently asked questions
Does ToList make a deep copy?
It materializes a list of the results. Reference-type elements can still refer to the original objects unless you explicitly copy their state.
Does await always create a new thread?
No. Explain the operation being awaited and distinguish asynchronous waiting from scheduling CPU work on another thread.