Signals At The Whiteboard

More than one of these reads as strength to an interviewer. Select every behaviour that does.

A

Spending the first minutes writing thorough comments so the interviewer can follow the code without narration.

B

After the last line compiles in your head, stepping through a small case by hand and looking for off-by-one errors before saying anything.

C

Stating the complexity with its cause: "O(n log n), because I sort once and then make a single pass."

D

Paraphrasing the question back before touching the keyboard.

E

Asking about value format specifically: empty input, nulls, duplicates, negatives, extremes.

F

Announcing "done" the moment the final line is written, so the remaining time goes to the next question.