Harvey AI Interview Questions
Reconstructed from 85 verified candidate reports across 9 questions. Mar 2025 – Aug 2026.
This page is a live view of every Harvey AI interview question AceOffer has indexed — pulled from real candidate reports, not invented from job descriptions or one founder’s memory. Every question shows how many times it’s been reported and when it was last seen. The catalog gets a refresh pass every month.
Key facts
- •9 distinct Harvey AI interview questions indexed
- •85 candidate reports across the catalog
- •Most reported: RAG Citation / Text Matching and Tagging — 23× (last seen August 2026)
- •Reports span Mar 2025 – Aug 2026
- •Refreshed monthly · last updated August 2026
Browse Harvey AI interviews by topic
The Harvey AI loop, from candidate reports
Harvey's loop is unusually predictable, and the reports say so directly: twelve of the fifty threads in this corpus describe the question they got as 地里的老题 — the known one from the forum. The phone screen (店面/电面) is a single coding question drawn from a small rotating set, most often the citation/text-matching problem or the spreadsheet cell-and-formula problem, on CoderPad for about an hour. The onsite (昂赛) adds a system design round that is almost always either Google Drive-style file storage with access control or a RAG pipeline — RAG being, as one report puts it, 他们家的基本盘 — plus a project deep dive and a values-based behavioral round. The hiring-manager round is a full hour on one past project, and reports describe it as genuinely selective on domain fit rather than a formality.
What does Harvey AI ask in each interview round?
Harvey AI interviews span 4 distinct round types, broken down below. Counts reflect distinct questions per round, not number of times asked. Frequencies on individual question cards show how many candidates reported getting that specific question.
60 minute design rounds. Interviewers push hard on the specific dimension their team cares about (storage at scale, real-time fan-out, multi-tenancy).
Which Harvey AI interview questions come up most?
These are the Harvey AIquestions reported most across the loops we’ve indexed, sorted by candidate-report frequency.
| Question | Round | Reported | Last seen |
|---|---|---|---|
| RAG Citation / Text Matching and Tagging | Coding | 23× | August 2026 |
| Spreadsheet / Excel Cell Get and Set with Formula and Cycle Detection | Coding | 16× | August 2026 |
| Google Drive / File Storage System Design with ACL | System Design | 11× | July 2026 |
| Project Deep Dive | Tech Deep Dive | 10× | August 2026 |
| Harvey Values / Behavioral | Behavioral | 10× | July 2026 |
| File System Implementation | Coding | 7× | June 2026 |
| RAG System Design | System Design | 5× | July 2026 |
| Past Project Experience Deep Dive (HM) | Behavioral | 2× | May 2026 |
| Design Mint / Payment Scheduling System | System Design | 1× | September 2025 |
The full index is below, or browse the Harvey AI catalog →
Every Harvey AIinterview question we’ve indexed
All 9, grouped by round and sorted by how often candidates reported them. Each links to the question, its reported follow-up count, and when it was last seen.
Coding (3)
- RAG Citation / Text Matching and Tagging — reported 23×, last seen August 2026
- Spreadsheet / Excel Cell Get and Set with Formula and Cycle Detection — reported 16×, last seen August 2026
- File System Implementation — reported 7×, last seen June 2026
System Design (3)
- Google Drive / File Storage System Design with ACL — reported 11×, last seen July 2026
- RAG System Design — reported 5×, last seen July 2026
- Design Mint / Payment Scheduling System — reported 1×, last seen September 2025
Behavioral (2)
- Harvey Values / Behavioral — reported 10×, last seen July 2026
- Past Project Experience Deep Dive (HM) — reported 2×, last seen May 2026
Tech Deep Dive (1)
- Project Deep Dive — reported 10×, last seen August 2026
Read two Harvey AI questions free
Full problem statements, candidate-reported follow-ups, and walkthroughs. No signup needed.
The most-reported Harvey question by a wide margin, and the one the phone screen most often draws. Three progressive parts: count word-level matches of each source phrase in a model output, wrap the matched spans in <yellow> tags with overlapping and adjacent matches merged into one block, then append citation indices sorted by how often each source appears across the whole text. Interviewers correct candidates who count citation frequency per-highlight instead of globally.
The system design round that shows up in nearly every Harvey onsite report, sometimes framed as a PDF-only “Data Room”. Listing, upload/download, sharing, and access control, with the follow-ups converging on two things candidates lose the round on: organization-level ACL for sharing with thousands of users, and the unusual probe one candidate quoted verbatim — how do you verify that each chunk uploaded to S3 is actually yours.
Harvey’s other system design, described in one report as 他们家的基本盘 — their bread and butter. The reports carry an unusually specific failure mode: candidates prepare LLM and RAG internals, then lose the round on the crawler and the distributed-systems layer. One candidate was strong in every other round and failed on exactly that; another says outright to focus on crawler scale-up.
- •On the file-storage design: separate the metadata store from the blob store early, then raise chunking for large files before the interviewer asks — passers volunteer it, failures wait to be prompted
- •On the file-storage design: cover organization- and group-level ACL, not just user-level sharing, and be ready to explain how a pre-signed URL is scoped so chunk ownership can be verified
- •On the RAG design: walk the whole pipeline — crawler, chunking, embedding, vector store, retrieval, generation, evaluation — and treat crawler scalability as a first-class dimension rather than an afterthought
- •On the behavioral round: prepare three to five tight STAR stories mapped to Harvey's published values in advance, and keep them short in the 30-minute format so you cover breadth
- •On the hiring-manager round: pick a project that is genuinely domain-relevant to the team, and lead with why and what you traded off rather than waiting to be probed
- •Read the prompt HR sends before the design round — reports say it is detailed enough to tailor preparation around
- •Over-indexing on LLM and RAG internals while neglecting web-crawler scalability — one candidate was strong in every other round and failed system design on exactly this
- •Designing only user-level ACL on the file-storage question, with no answer for organization-level sharing at scale
- •Spending so long on requirements clarification that the deep-dive portion gets squeezed — a repeated cause of running out of time
- •Treating the RAG question as a pure ML problem rather than a distributed-systems one
- •Bringing generic STAR stories that were never mapped to Harvey's specific values, or burning the 30-minute behavioral on a single story
- •Choosing a hiring-manager project that sounds relevant but has no depth under probing — reports describe the HM losing interest quickly
Get the full Harvey AI catalog
Every question. Every candidate-reported follow-up. The mistakes that sink people, and what passers do instead. Monthly refresh.