← Back to Directory

Harvey interview notes, page 3 of 6

Mid-sized

Most of these Harvey write-ups come from Software Engineers (46), then Backend Engineers (4) and Machine Learning Engineers (4). The most reported rounds are the technical phone screen (30), the system design round (17), the behavioral / leadership round (4) and the onsite coding round (2).

54 interview notes · updated Jul 2026

Harvey·Software Engineer·Technical Phone Screen

May 2026
Harvey SE interview, got a multi-part coding problem about building an in-memory spreadsheet from scratch. Three progressive parts, each adding complexity. Felt manageable until cycle detection showed up and I had to think harder than expected.
  • Design and implement an in-memory spreadsheet that supports cell labels like A1 and B10, with set_cell and get_cell methods. Start with plain integer storage, then add formula support (cell references and addition), then add cycle detection.

“Part 1 was basically a hashmap, took maybe five minutes.”

View Post

Harvey·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at HarveyAI focused on building something close to their actual product, which made it feel less abstract than most design interviews. The follow-ups got pretty deep into upload mechanics and security, more than I expected.
  • Design a document storage system similar to Harvey's core vault product. Focus especially on scaling and access control.
  • How would you handle very large file uploads in this system?
  • For each chunk uploaded to object storage, how do you verify it actually belongs to the user who initiated the upload and hasn't been tampered with?

“The fact that it was literally their own product made it a bit surreal.”

View Post

Harvey·Software Engineer·Onsite - System Design / Architecture

May 2026
HarveyAI engineering interview centered on a single deep project walkthrough, where they expect you to own the narrative but also be ready to defend every corner of your design on the spot.
  • Walk us through a project you owned end-to-end: the context, your specific role, the architecture, the key decisions and trade-offs, how you implemented it, what the outcome was, and what you took away from it.

“This is basically the whole interview.”

View Post

Harvey·Software Engineer·Onsite - Coding / Algorithms

May 2026
Coding round at HarveyAI for a Software Engineer role. The problem itself was interesting but the whole session was derailed by an interviewer who seemed completely checked out, and I ended up burning too much time just trying to get basic responses out of him.
  • Given a map of symbol expressions, compute the resolved value for each symbol using graph traversal.

“Classic DFS setup but with a wrinkle.”

View Post

Harvey·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at Harvey and got a spreadsheet engine problem. Pretty meaty for a single coding round, more design-y than I expected.
  • Design and implement a Spreadsheet class where cells can hold either integer literals or formula strings that sum cell references and literals. Support get and set operations, lazy or eager evaluation, and raise an error on cyclic dependencies without modifying existing state.

“The cycle detection part is what bit me.”

View Post

Harvey·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at HarveyAI and got a spreadsheet-style coding problem, reminded me of something I'd seen on LeetCode before. Pretty focused on data structure choices more than anything else.
  • Implement setCell and getCell functions for a spreadsheet. No formula support, just integer values. What data structure would you use?

“The interviewer kept pushing back on my first instinct and asked me to justify why I picked what I picked.”

View Post

Harvey·Software Engineer·Technical Phone Screen

May 2026
One coding question at HarveyAI for a Software Engineer role. Pretty straightforward once I cleared up a misunderstanding about scope, then walked through complexity at the end.
  • Solve the H-Index (citation count) problem.

“Misread it at first.”

View Post

Harvey·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Harvey AI for a software engineering role. The whole interview was basically one long question about file deduplication that kept branching into harder and harder territory. Walked out not totally sure how I did.
  • How would you determine whether two files have identical byte content, ignoring filesystem metadata? Design a hashing-based approach and extend it to large-scale deduplication across machines.

“This question had like seven sub-parts and I did not fully appreciate that until I was already three minutes into talking about SHA-256 vs MD5.”

View Post

Harvey·Software Engineer·Technical Phone Screen

May 2026
Got a coding question at Harvey AI for a software engineer role that was basically about string matching and annotation. Three parts, each building on the last, and the third part is where things got interesting.
  • Given an LLM output string and a list of source strings, design an algorithm to count how many times each source string appears in the LLM output. Then extend it to wrap every occurrence of a source in XML-style tags, handling overlapping matches correctly. Finally, modify the tagging so each tag includes annotations indicating which source indices matched at that position.

“The first part is basically substring frequency counting, fine.”

View Post

Harvey·Software Engineer·Onsite - Behavioral / Leadership

May 2026
HarveyAI software engineer interview included a project deep dive where behavioral questions were woven in, apparently tied to their internal company values.
  • Walk us through a project you worked on in depth, and be ready for follow-up questions about your decisions and behavior along the way.

“The tricky part is they don't just let you narrate the project.”

View Post