Harvey Backend Engineer interview questions

4 Backend Engineers have shared notes from their Harvey interviews, with the questions they were asked in each round. That is 7% of the 54 Harvey interview notes on Screna AI.

4 Backend Engineer interview notes

Harvey·Backend Engineer·Technical Phone Screen

Jul 2026
Interviewed for a backend role at Harvey and got two coding problems. Nothing too wild conceptually but both had more edge cases than I expected, and I don't think I handled them as cleanly as I should have.
  • Given a sentence and a list of tags, return only the tags that appear in the sentence as whole-word matches (case-insensitive). Partial matches don't count, so a tag like 'blue' should not match the word 'blueprint'.
  • Design and implement an in-memory file system that supports creating directories, listing contents, writing to files, and reading from files.

“The partial-word thing is where I fumbled a bit.”

View Post

Harvey·Backend Engineer·Onsite - Behavioral / Leadership

Jul 2026
Behavioral round at Harvey for a backend engineer role. Just one question but it had a lot of moving parts, basically a full conflict-resolution story they wanted unpacked in detail.
  • Tell me about a time you had to coordinate between two teams that were seriously at odds. What caused the conflict, how did you bring stakeholders together, what did you personally do, and what happened?

“This one required a real story with actual texture, not just 'we had a disagreement and resolved it.' They wanted to know what I personally did versus what the group did, which tripped me up a bit because my instinct was to say 'we' the whole time.”

View Post

Harvey·Backend Engineer·Onsite - System Design / Architecture

Jun 2026
Technical interview at Harvey for a backend role, one question but it had real teeth. You pick a project and basically defend every decision you made, including the ones you'd rather forget.
  • Pick a project you worked on and walk through the key technical decisions: why that architecture or stack, what alternatives you considered, what trade-offs you accepted, and what you'd change looking back.

“This one is sneakier than it sounds.”

View Post

Harvey·Backend Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Harvey for a backend role. The whole thing centered on building a secure document vault, which sounds straightforward until you get into the weeds on auth, chunked uploads, and integrity verification. Pretty thorough for a single question.
  • Design a secure cloud-based document vault where authenticated users can upload, store, and retrieve sensitive files with strict authorization controls.
  • How would you scale this system as the number of files and user traffic grows significantly?
  • How would you design the access control and permission model for this system?
  • How would you handle uploading very large files in this system?
  • When files are uploaded to object storage in chunks using presigned URLs, how do you verify that each chunk actually belongs to the intended file and was uploaded by the authorized user, rather than being arbitrary or malicious data?

“This was the anchor question for the whole session.”

View Post