← Back to Directory

Hebbia

Small

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

3 interview notes · updated Jul 2026

Hebbia·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Hebbia for a software engineer role, focused entirely on building the backend for an LLM-powered chat product in a fintech context. Pretty meaty scope: streaming responses, multi-agent orchestration, tool calls, compliance concerns, the works. Left feeling like I covered the broad strokes but probably underdeveloped the failure handling section.
  • Design the backend for an LLM-powered chat product used in a financial-technology setting. Cover the architecture, main services, data model, request flow, scaling strategy, and failure handling. The frontend is a simple chat UI but your scope is the backend only.

“This is a big one.”

View Post

Hebbia·Software Engineer·Technical Phone Screen

May 2026
Coding round at Hebbia for a software engineer role. The whole thing was one extended problem that kept getting layers added on, which I didn't fully expect. Felt okay about the core part but the compressed snapshot extension tripped me up a bit.
  • Implement an LRU cache with fixed capacity that supports get and put operations, evicting the least recently used entry when full.
  • Write a snapshot function that returns the current cache contents in order from most to least recently used.
  • Extend the snapshot to support compressed output: group keys that share the same value, and clarify how ordering should be preserved across groups.

“Pretty standard stuff if you've seen it before.”

View Post

Hebbia·Software Engineer·Technical Phone Screen

Apr 2026
HebbiaAI software engineering interview that went straight into a meaty coding problem. It was a follow-up to standard Tic-Tac-Toe but with a lot more moving parts, and the design discussion around data layout took up more time than I expected.
  • Implement Ultimate Tic-Tac-Toe on a 9x9 grid structured as a 3x3 arrangement of 3x3 sub-boards. A move is represented as a tuple of sub-board coordinates, cell coordinates, and the player. A player claims a sub-board by getting three in a row within it, and the overall winner is whoever claims three sub-boards in a row on the outer grid. Discuss your data layout and how you'd detect wins incrementally at both levels.

“I started with the inner board logic since it's basically just regular TTT, but the nesting tripped me up more than I'd like to admit.”

View Post