← Back to Directory

Baseten

Small

Screna has 3 Baseten interview write-ups. The most reported round is the system design round (2).

3 interview notes · updated Jun 2026

Baseten·Software Engineer·Onsite - System Design / Architecture

May 2026
Follow-up system design question at Baseten, focused on correctness verification for a parallel S3 chunk downloader. Pretty deep dive into checksums and testing strategy, felt more like a design review than a typical interview.
  • After building a parallel S3 chunk downloader, how do you verify that every chunk arrived correctly and that the reassembled file actually matches what the server has?
  • If a chunk checksum or the final file size doesn't match what you expected, do you retry or fail fast, and what drives that decision?
  • How would you unit and integration test this downloader, specifically around chunk failures and reassembly correctness?

“This is where I started rambling a bit.”

View Post

Baseten·Software Engineer·Technical Phone Screen

May 2026
Baseten gave me a systems-flavored coding round that was less about grinding leetcode and more about actually thinking through concurrency and failure modes. The starter code was functional but single-threaded, and the job was to make it real.
  • You're given a sequential file downloader that fetches chunks one at a time. Refactor it to download chunks in parallel while keeping correctness: bounded concurrency, proper in-order assembly, per-chunk retries, fail-fast on unrecoverable errors, and graceful cancellation.
  • How do chunk size and concurrency level interact to affect overall download throughput, and what are the tradeoffs?

“This one took me a minute to scope properly.”

View Post

Baseten·Software Engineer·Onsite - System Design / Architecture

Mar 2026
System design round at Baseten for a software engineering role. The whole thing was basically one giant prompt about building a CI/CD platform from scratch, which sounds manageable until you realize how many sub-problems are hiding inside it.
  • Design a CI/CD platform for engineering teams. Walk through pipeline definition, source control integration, build and test infrastructure, artifact storage, deployment strategies, secret management, observability, and access control.
  • How would you ensure isolation between tenants in a shared build agent pool?
  • How do you guarantee reproducible builds in a CI/CD system?
  • How would you design the observability layer for individual pipeline runs, covering logs, metrics, and traces?
  • Walk me through how you'd implement queueing fairness across multiple engineering teams sharing the same build infrastructure.

“This is a monster of a question.”

View Post