Reason through complexity and approach — no coding required.
This is a spoken, conceptual discussion, not a live-coding exercise. You explain your reasoning out loud — concepts, tradeoffs, and "what would happen and why" — while the interviewer follows up and pushes on anything vague or surface-level.
Can you explain what Big-O notation actually measures, and what it deliberately ignores?
Can you describe how you'd approach finding whether an array contains a pair of numbers that sum to a target value, and what the time complexity of your approach would be?
Can you explain the difference between depth-first and breadth-first traversal, and when you'd choose one over the other?
Can you explain how quicksort works at a high level, and what its worst-case time complexity is and why?
Can you explain what makes a problem a good candidate for dynamic programming?
Can you explain what a base case is in recursion, and what happens if you get it wrong?
Can you explain the tradeoffs between using an array versus a linked list for a given problem?
Walk me through how you approach a problem you've never seen before — what's your process before you start coding?
These are a few examples — each real session pulls 5 questions at random from a larger pool across every category above, so repeat sessions won't repeat the same set.
5 free interviews every month, any track, no card required.