Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Guides

Loading

Aporeon

Technical interview practice, from one developer to another.

Guides About Editorial standards Support Privacy Terms Refund policy

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

12 results across 1 active filter

Page 1 of 1

Behavioral questionMedium~8 min

Balance quality and delivery pressure

Builds a story about protecting quality while still making practical delivery decisions.

Behavioral questionMedium~8 min

Choose a simple solution over a clever one

Builds a story about resisting unnecessary complexity and choosing maintainable design.

Behavioral questionMedium~8 min

Communicate technical risk to non-technical stakeholders

Builds a story about explaining engineering risk in business terms without hiding uncertainty.

Behavioral questionMedium~8 min

Handle conflicting priorities

Builds a story about making competing work visible and helping the team choose intentionally.

Behavioral questionMedium~8 min

Handle vague requirements and discover scope

Builds a story about turning unclear requirements into a scoped, testable plan without overbuilding.

Behavioral questionHard~10 min

Improve a messy codebase without a rewrite

Builds a story about improving code quality incrementally while still delivering product value.

Behavioral questionMedium~8 min

Improve team process without heavy process

Builds a story about improving team workflow with lightweight, useful process changes.

Behavioral questionMedium~8 min

Make a technical trade-off under a deadline

Builds a story about choosing a pragmatic technical path under time pressure while preserving future safety.

Behavioral questionMedium~8 min

Miss an estimate and reset expectations

Builds a story about handling a missed estimate transparently and recovering with a realistic plan.

Behavioral questionHard~10 min

Push back on a risky requirement

Builds a story about challenging a risky requirement while staying constructive and product-oriented.

Behavioral questionHard~10 min

Resolve a cross-team dependency blocking delivery

Shows how to unblock delivery across team boundaries without hiding risk, blaming another team, or creating an unsafe shortcut.

Behavioral questionMedium~8 min

Tell me about a project you owned end to end

Builds a concrete story about owning a feature from requirements through release, verification, and follow-up.