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

9 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

Change a technical decision after new evidence

Demonstrates technical humility by changing direction when measurements invalidate an earlier decision.

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

Follow up after an incident to prevent repeats

Builds a story about turning an incident into regression guards, observability, and process improvement.

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 questionHard~10 min

Influence a decision without formal authority

Builds a concrete story about earning alignment through evidence, listening, and a low-risk path rather than positional power.

Behavioral questionMedium~8 min

Learn unfamiliar technology quickly

Builds a story about learning a new technology in a structured way and applying it safely.

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 questionHard~10 min

Take ownership after a production bug

Builds a story about taking responsibility for a production bug, mitigating impact, and preventing recurrence.