← Back to Directory

Sesame

Small

Screna has 5 Sesame interview write-ups. The most reported round is the technical phone screen (3).

5 interview notes · updated Jul 2026

Sesame·Software Engineer·Onsite - System Design / Architecture

Jul 2026
System design round at Sesame for a software engineer role. The whole session was basically one big networking question dressed up as a product feature, which I wasn't fully expecting.
  • Design a TCP-based chat server where multiple clients can connect, messages get broadcast to all other clients, and the server handles clients joining and leaving without crashing. Walk through your concurrency model, how you'd frame messages on the byte stream, and how you'd do a clean shutdown.

“I started with thread-per-connection because it's the obvious answer, but they pushed back pretty fast on what happens at 10k clients.”

View Post

Sesame·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Sesame had me design a full voice chatbot pipeline from scratch, end-to-end, which sounds like a fun problem until you realize how many moving parts they actually expect you to cover in one session.
  • Design a voice chatbot system end-to-end, covering speech-to-text, intent and dialog understanding, state management, response generation, text-to-speech, and audio streaming back to the user. Also address latency budgets per stage, barge-in and interruption handling, scaling for concurrent calls, and observability.

“This is a beast of a question and I did not pace myself well.”

View Post

Sesame·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Sesame AI asked me to implement a ring buffer from scratch, which sounds like a straightforward systems question until you're actually in the middle of it trying to remember which pointer tracks what. Solid technical screen, nothing behavioral, just code and follow-ups.
  • Implement a circular buffer with a fixed byte capacity. It should support writing bytes (returning how many were written), reading up to N bytes from the front, and reporting how many bytes are currently available. Use head, tail, and size pointers with modulo arithmetic for wraparound, handle edge cases like a full buffer and reading past what's available, and briefly discuss thread safety.

“I got the basic structure down pretty quickly, head/tail/size, modulo on writes and reads.”

View Post

Sesame·Software Engineer·Technical Phone Screen

May 2026
Sesame software engineering interview that went deep into low-level systems design pretty fast. The core problem was about an in-memory filesystem backed by fixed-size node arrays, and it escalated into a broader design conversation I wasn't fully ready for.
  • You have an in-memory filesystem stored as a list of fixed-size nodes, where each node is a fixed-size character array. Implement a print method that correctly traverses these nodes and outputs the full stored content.
  • How do you handle file boundaries when files can start or end in the middle of a node, or span across multiple nodes?
  • How would you generalize this design to support read and write operations, not just printing?

“The example they gave was two nodes like ['a','b','c','d','e','f','g','h'] and ['i','j','k','l','m','n','o','p'] so the output should be the full concatenated string.”

View Post

Sesame·Software Engineer·Technical Phone Screen

Apr 2026
Got a technical phone screen for a software engineering role at Sesame AI that was basically one meaty design question the whole time. The problem was interesting but the O(1) constraint with bounded memory made it trickier than it looked on the surface.
  • Design a StreamingMetrics class that ingests ASR (speech recognition) events, each containing a user ID and word count, and tracks the user with the longest transcribed sentence and the total number of unique users. The constructor takes a lookback window size limiting how many recent events are kept in memory. The ingest method must run in O(1) time and memory must stay bounded.

“This one took me a minute to even parse.”

View Post