Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Topics

Loading

Aporeon

Technical interview practice, from one developer to another.

About Privacy Terms

Drills

Pick a focused question that fits your time, stack, and interview goal.

How much time do you have?

Show one-drill sessions you can finish now.

Search

Track

Practice style

Level

More filters1

Topic

Technology

Tech stack

Skill area

7 results across 1 active filter

Page 1 of 1

Debugging scenarioMedium~10 min

How can event subscriptions cause memory leaks in .NET?

Shows how publisher-to-subscriber references can retain objects and how to clean up event-based lifetimes.

Architecture scenarioHard~12 min

How would you design a memory-safe background batch job?

Covers chunking, bounded concurrency, scoped dependencies, progress, retries, and avoiding full-dataset memory spikes.

.NETASP.NET CoreC#

Practice drill

Concept questionMedium~7 min

IHttpClientFactory, handler lifetime, DNS, and socket reuse

Explains how IHttpClientFactory separates short-lived clients from pooled handlers and how concurrency, DNS, resilience, and DI lifetimes still require judgment.

.NETASP.NET Core

Comparison questionMedium~7 min

When do you use IDisposable instead of a finalizer in .NET?

Distinguishes deterministic cleanup from finalization and explains resource ownership in normal application code.

Concept questionMedium~7 min

When is IAsyncDisposable useful in .NET?

Explains asynchronous cleanup for resources whose shutdown path needs async work, such as flushing or closing remote connections.

Concept questionHard~9 min

When would you use Span, Memory, or ArrayPool in .NET?

Introduces lower-level allocation tools while emphasizing measurement, ownership, and safe usage.

.NETASP.NET CoreC#

Code reviewHard~12 min

Why is it risky for a singleton to capture scoped services or request data?

Reviews a captive scoped dependency as both a lifetime and concurrency bug, then replaces it with explicit per-operation scopes and minimal immutable work data.