← Back to Directory

Harvey

Small

Most of these Harvey write-ups come from Software Engineers (32), then Machine Learning Engineers (2). The most reported rounds are the technical phone screen (20), the system design round (9), the behavioral / leadership round (2) and the hiring manager screen (1).

34 interview notes · updated Jun 2026

Harvey·Software Engineer·Technical Phone Screen

Jun 2026
Coding round at HarveyAI for a software engineer role. One problem: build a connection pool. The db.query layer was already stubbed out so you just had to get acquire and release working correctly.
  • Implement a database connection pool with acquire and release methods. Assume db.query is already mocked.

“Scoped-down version of what could easily spiral into a full system design problem.”

View Post

Harvey·Software Engineer·Technical Phone Screen

Jun 2026
This was a technical screen for a Software Engineer role at HarveyAI focused on a string processing problem involving interval merging and text annotation. Pretty algorithmic for what I expected, but the problem was well-defined at least.
  • Given a body of text and a list of source strings, wrap every exact-match occurrence of any source string in the text with highlight tags. Overlapping or adjacent matches should be merged into a single span rather than producing nested tags.

“The merging part is what gets you.”

View Post

Harvey·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Values round at Harvey for a software engineering role. They asked behavioral questions tied directly to the three values listed on their public website, so you can at least prep in advance if you know where to look.
  • Share an experience that reflects one of Harvey's core company values.

“They go through each of the three values on their published values page and ask for a real example from your past.”

View Post

Harvey·Software Engineer·Technical Phone Screen

Jun 2026
Coding round at HarveyAI where the whole problem was building an in-memory file system from scratch. Pretty classic LC-style problem but the edge cases in path parsing tripped me up more than I expected.
  • Design and implement an in-memory file system that supports ls(path), mkdir(path), addContentToFile(path, content), and readContentFromFile(path).

“I jumped straight into coding the trie node structure without talking through the design first, which I regret.”

View Post

Harvey·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at HarveyAI focused almost entirely on building a Google Drive-like service, with a heavy lean toward the access control layer. Solid depth required, and the permission propagation piece in particular took more time than I expected.
  • Design the file and folder data model for a cloud storage service, including how parent-child hierarchy works and how permissions are inherited down the tree.
  • Walk through the sharing model: what permission roles exist (owner, editor, commenter, viewer), and how do you support sharing by user, group, link, and domain?
  • How do you handle permission propagation when a parent folder's ACL changes? What happens to children that have explicit permission overrides?
  • How would you design the access check system to work at low latency and scale? Think about denormalized caches and relationship-tuple approaches.
  • What would an audit logging system look like for this service? What events do you capture, and how do you store and query them?
  • Briefly cover how you'd handle file storage, client sync, and conflict resolution.

“I started with a basic node table with a parent_id pointer and felt pretty good about it.”

View Post

Harvey·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
HarveyAI's project round had one question per company value, which sounds manageable until you realize you have to actually know what their values are and have real answers ready for each one.
  • For each of HarveyAI's company values, describe a time your work or behavior reflected that value.

“One question per value sounds clean in theory but it's basically a gauntlet if you haven't mapped your experience to their specific values beforehand.”

View Post

Harvey·Software Engineer·Technical Phone Screen

Jun 2026
One question, pretty standard coding round for HarveyAI. Misread the problem setup at first but got corrected early and recovered fine.
  • Solve the H-index (citation count) problem, where citation counts are tracked globally across all papers.

“Tripped up immediately because I assumed the counts were local per some subset.”

View Post

Harvey·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at HarveyAI for a software engineer role. The interviewer pushed way deeper than I expected on two specific areas, file uploads and access control, and I came out of it feeling like I'd only half-answered both.
  • Design the file upload flow for a Google Drive-like system, including chunking, resumable uploads, deduplication, and how you separate metadata storage from blob storage.
  • How would you design the access control system for a cloud storage product, covering user and group sharing, link-based permissions, folder inheritance, and ACL checks at scale?

“I started with the happy path, client uploads a file, server stores it, done.”

View Post

Harvey·Software Engineer·Technical Phone Screen

Jun 2026
Coding round at HarveyAI for a software engineer role. The problem was a spreadsheet cell dependency thing, conceptually close to a well-known OpenAI question, and I almost finished but ran out of time one line short.
  • Design a spreadsheet system where cells can depend on other cells, and reads must be O(1).

“I was one line away from finishing.”

View Post

Harvey·Software Engineer·Technical Phone Screen

May 2026
Did a technical phone screen for a Software Engineer role at HarveyAI. One coding question, finished fast, then sat through some awkward small talk for the rest of the slot.
  • Design and implement a file system.

“Recognized it immediately from the forums so I was able to move pretty quickly.”

View Post

Harvey interview FAQ

What rounds are in the Harvey interview?

Candidates most often report a technical phone screen (20 write-ups), a system design round (9), a behavioral / leadership round (2) and a hiring manager screen (1).

What does the Harvey technical phone screen cover?

Across 20 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (20 questions), System Design (16) and Technical Trade-offs (14).