supio·Software Engineer·Technical Phone Screen
Jun 2026
Supio gave me a 60-minute live coding interview on a small LLM chat UI codebase, mixing bug fixes with feature work. Two bugs to squash, two features to add, all under the clock. Pretty practical format, less algorithmic grind and more 'can you actually read unfamiliar code fast.'
- The app throws an 'api key invalid' error when sending a message. How do you find and fix the root cause?
- Messages are being received from the API but the chat UI renders them as empty. What's going wrong and how do you fix it?
- Add a Clear button that resets the visible message history, the stored conversation context, and the overall chat state back to its initial empty state. The store already has a reset action available.
- Add a Stop button that cancels an in-flight streaming response and leaves whatever partial text was already rendered in place. Walk through your state management and cancellation approach.
“Went straight to the network tab and traced the request headers.” The rest of the author's notes on Software Engineer interview at supio, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post