← Back to Directory

Twitch

Large Enterprises

Screna has 6 Twitch interview write-ups. The most reported round is the technical phone screen (4).

6 interview notes · updated Jun 2026

Twitch·Software Engineer·Online Assessment (OA)

Jun 2026
Twitch's online assessment for this software engineer role was a two-hour session with a single object-oriented design problem and no automated test cases. You had to manually verify your output matched the examples exactly, whitespace and all. Oddly refreshing compared to the usual LeetCode grind, but also way more stressful when you're not sure if your newlines are right.
  • Design and implement an object-oriented solution to a multi-part problem, where your output must match the provided examples exactly in format, whitespace, and line breaks. No automated test cases are provided.

“The no-test-cases thing sounds fine until you realize you're basically your own QA team for two hours.”

View Post

Twitch·Software Engineer·Technical Phone Screen

Jun 2026
Twitch software engineer interview that centered on a classic game design problem with some teeth in the follow-ups. The base question felt approachable but the class design discussion and extensibility stuff is where they really wanted to see how you think.
  • Design and implement a Rock-Paper-Scissors game for two players, then extend it to support a streak-based bonus points system and a tie-break mechanism that guarantees a definite winner.
  • How would you redesign the class structure to support more than two players or additional move types beyond the standard three?

“Started fine with the basic game loop but the streak multiplier tripped me up a bit.”

View Post

Twitch·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Twitch for a software engineer role, basically one meaty question about a hard problem and how you worked through it. Felt more like a conversation than an interrogation, but the follow-up probing caught me off guard.
  • Tell me about a hard problem you faced at work, how you solved it, and what you took away from it. Walk through the situation, what made it difficult, what you tried (including things that didn't work), the outcome, and what you'd carry forward.

“I structured it as situation-action-result and thought I was doing fine until the interviewer started digging into the failed attempts.”

View Post

Twitch·Software Engineer·Technical Phone Screen

May 2026
Twitch coding screen for a software engineer role. The problem was a billing simulation, cleaner than it sounds but the edge cases snuck up on me.
  • A notification service bills users based on hourly usage over a 24-hour period. The first N notifications per hour are free; anything above that threshold is charged at a fixed per-notification rate. Given an array of 24 per-hour counts, return the total daily cost and a length-24 array showing the charge for each individual hour.

“Seemed straightforward at first glance.”

View Post

Twitch·Software Engineer·Technical Phone Screen

May 2026
Twitch SWE interview focused on a graph/indexing problem around channel recommendations. The follow-up discussion about BFS was conceptual only, which was a relief, but the core problem had more depth than I expected going in.
  • You have a map of channels to their followers. Given a target channel, find all other channels that share at least one follower with it. Walk through both a naive approach and a more efficient one using an inverted index.
  • How would you extend this to find 'similar' channels that are k hops away using BFS? No code needed, just talk through the approach.

“Started with the obvious nested loop thing, comparing the target's follower set against every other channel's followers.”

View Post

Twitch·Software Engineer·Technical Phone Screen

Apr 2026
Twitch SWE interview that leaned heavily on systems thinking. The main coding problem was LRU cache, which felt straightforward until they kept pushing on the concurrency angle and I realized I'd only half-prepared for that part.
  • Implement an LRU cache with get and put operations, both running in O(1) average time.
  • How would you extend that LRU cache to handle concurrent access from multiple threads safely? Walk through different locking strategies and the tradeoffs between them.

“I knew this one cold.”

View Post