The app transcribes the question, then suggests an approach and its complexity — so you have something to say before you start writing code.
Typical algorithm questions from technical rounds.
The kind of suggestion the app produces during a round.
Four things the suggestion gives you in a coding round.
The suggestion names the technique — sliding window, two pointers, BFS — and gives the time and space complexity, so you can state the trade-off before you start typing.
Answers are written to be spoken rather than read, so you can narrate while you work instead of going quiet.
One line when you only need the technique. A paragraph when you need to explain it. Four bullets when you want to scan. Switch mid-round.
If the app doesn't pick up a question — the interviewer talked through it, or the audio was unclear — Ctrl+Shift+A asks for an answer on the spot.
Things worth doing regardless of what the app suggests.
Input size, whether you can mutate the input, whether duplicates are possible. It buys thinking time, and interviewers mark it.
Say what each costs, pick one, and explain why. Going straight to code reads as guessing.
Walk an input through to its output before you run anything. It catches off-by-one errors before the interviewer does.
Ctrl+Shift+A gets you a suggestion without having to pause the conversation.