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

15 results across 1 active filter

Page 1 of 1

Concept questionMedium~7 min

Choose Strategy, Adapter, and Decorator for real problems

Selects small structural and behavioral patterns from the problem being solved instead of pattern-name recognition.

.NETASP.NET Core

Concept questionMedium~7 min

Clean architecture dependency direction without ceremony

Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.

.NETASP.NET Core

Practice drill

Architecture scenarioHard~12 min

CQRS: when separate read and write models help

Applies CQRS proportionally, separating model responsibilities without assuming separate databases, messaging, or event sourcing.

.NETASP.NET Core

Concept questionEasy~5 min

Dependency injection versus the service locator pattern

Distinguishes explicit dependency injection from runtime service lookup and identifies the narrow framework boundaries where scoped resolution is legitimate.

.NETASP.NET Core

Concept questionMedium~7 min

Dependency inversion and the application composition root

Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.

.NETASP.NET Core

Architecture scenarioHard~12 min

Enforce boundaries inside a modular monolith

Turns a modular-monolith choice into enforceable code and data ownership rather than relying on folders and team discipline alone.

.NETASP.NET Core

Architecture scenarioHard~12 min

Evolve a legacy architecture in safe slices

Improves architecture through protected behavior, incremental boundaries, and measurable delivery instead of a risky all-at-once rewrite.

.NETASP.NET Core

Concept questionEasy~5 min

Interface segregation at application boundaries

Designs consumer-focused contracts that reduce accidental authority and coupling without producing meaningless one-method wrappers.

.NETASP.NET Core

Concept questionMedium~7 min

Liskov substitution and behavioral contracts

Explains substitutability through inputs, outputs, side effects, and failure behavior rather than inheritance syntax alone.

.NETASP.NET Core

Concept questionMedium~7 min

Open-closed principle with strategies instead of growing flags

Uses stable extension points for genuinely variable behavior while avoiding speculative abstractions and configuration-driven branching.

.NETASP.NET Core

Architecture scenarioHard~12 min

Place domain logic without anemic or bloated models

Places invariants and state transitions near the data they protect while keeping orchestration and infrastructure out of domain entities.

.NETASP.NET Core

Architecture scenarioHard~12 min

Repository pattern over EF Core: useful boundary or extra layer

Evaluates repositories by domain language, query ownership, and substitutability instead of treating them as a mandatory wrapper around DbSet.

.NETASP.NET Core

Concept questionMedium~7 min

Separate API, domain, and persistence models deliberately

Uses separate models where they protect contracts, invariants, or storage evolution while avoiding repetitive mapping with no boundary value.

.NETASP.NET Core

Concept questionMedium~7 min

Single responsibility and cohesive boundaries in real code

Applies single responsibility to reasons for change, cohesive behavior, and maintainable service boundaries instead of counting methods.

.NETASP.NET Core

Concept questionMedium~7 min

Vertical slices versus horizontal application layers

Chooses code organization from change locality, shared policy, and cross-cutting needs rather than adopting one folder structure universally.

.NETASP.NET Core