Harvey AI·Software Engineer·Onsite - System Design / Architecture
Jun 2026
System design round at Harvey AI for a software engineer role. The whole thing was one big question about building a file storage service from scratch, and they wanted you to go deep on basically everything: APIs, metadata, concurrency, scaling, security. Felt like a 45-minute gauntlet.
- Design a production-grade file storage service with addFile(path) and list(path) APIs, where each directory is capped at 5 entries and duplicate filenames are auto-renamed with OS-style suffixes. Walk through the full architecture including API layer, metadata service, and content store.
- What metadata schema and storage backend would you choose for this service, and why relational vs NoSQL?
- How do you handle large file uploads, and what changes when files are too big to buffer in memory?
- How would you handle consistency, failure scenarios, and rollback in this system?
- How would you scale this service? Talk through partitioning, sharding, and caching strategies.
- What observability, rate limiting, and quota enforcement would you build into this service?
- How would you approach security for this service, including authentication, authorization, path traversal protection, and encryption?
- Define the key SLIs and SLOs you'd set for this service.
“This is a beast of a question.” The rest of the author's notes on Software Engineer interview at Harvey AI, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post