← Back to Directory

Nash AI

Small

Screna has 3 Nash AI interview write-ups. The most reported round is the onsite coding round (1).

3 interview notes · updated Jun 2026

Nash AI·Software Engineer·Technical Phone Screen

May 2026
Nash AI asked me to build a fully playable Minesweeper game from scratch in a single coding session. Pretty involved for a phone screen, but it was actually kind of fun once I got into it.
  • Implement a Minesweeper game class that takes width, height, and number of mines as constructor arguments. It should randomly place mines on initialization, support a click(x, y) method that loses the game on a mine, reveals a numbered cell directly, or flood-fills all connected zero cells and their neighboring numbered cells if the clicked cell has no adjacent mines. Include a console-based visualization so someone can actually play it.

“The flood-fill part is where I spent most of my time.”

View Post

Nash AI·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Nash AI system design round focused entirely on a real-time delivery tracking platform. The scope was broad and the interviewer clearly wanted depth on every layer, not just a high-level sketch.
  • Design a scalable, fault-tolerant system for tracking deliveries in real time, where third-party services handle the actual delivery. Your design should cover how status updates get ingested, how async task processing works, idempotency for duplicate events, retry logic with backoff, storage decisions for current state versus event history, and how you'd scale the read path for status queries.

“This one sprawled fast.”

View Post

Nash AI·Software Engineer·Onsite - Coding / Algorithms

Mar 2026
Nash AI had me do a take-home first, then a live coding round where I walked through my own solution and got asked to extend it on the spot. The batch mode extension was where things got interesting and a little stressful.
  • Walk us through your take-home solution and explain the design decisions you made.
  • Extend your solution to support batch mode, processing many inputs in a single invocation instead of one at a time.
  • How does the batch processing path differ from the single-item or streaming path, and what tradeoffs does that introduce?

“I'd rehearsed this in my head but stumbled a bit when they started asking why I'd structured things a certain way.”

View Post