Harvey frontend interviews almost always circle one product shape: an editable spreadsheet grid with formulas that reference other cells. Harvey.ai builds legal AI products, and the screen grades whether you can ship a dense, stateful UI under a hard timer.
This guide is built from 6 Harvey interview reports that FrontendLead members posted between July 2025 and October 2026, plus the 6 coding questions members have tagged with Harvey. You’ll get the stages, what each round grades, and a four-week plan that targets them. The exact prompts candidates were asked are in the members-only sections below.
The single biggest pattern: treat the phone screen as a race to a working grid, then a formula evaluator. Candidates who spent too long on styling or clarifying questions ran out of time before the formula follow-up.
By Shivam Bhalla · Updated
01Harvey frontend interview at a glance
- Aspect
- What to expect
- Timeline
- Often a few weeks; confirm with your recruiter
- Stages
- Recruiter or hiring manager screen, then a technical phone screen
- Signature topic
- Editable spreadsheet / grid with cell formulas
- Coding style
- Practical React or vanilla JS UI; minimal styling expected
- Company
- Harvey.ai – legal AI platform (not a generic “Harvey”)
- Languages
- JavaScript or TypeScript; React is common for the grid UI
- Levels seen
- Frontend, Senior, Staff, and full-stack screens share the same sheet theme
- Bar
- Finish the base grid fast; formula support decides the round
02The Harvey front end interview process
Harvey does not publish a detailed public frontend interview guide, so treat the stages below as the path members report. Confirm round count and editor setup with your recruiter.
- 1
Recruiter or hiring manager screen
30 to 45 minutesBackground, why Harvey, ownership stories, and tough feedback. Public reports outside our set also describe project ownership and curiosity outside your immediate scope. Have one legal-tech or AI-product reason ready, not a generic “I like startups” answer.
- 2
Technical phone screen
About 60 minutesLive coding focused on a spreadsheet-like grid. Expect a two-part structure: editable cells first, then formulas that read other cells. Interviewers often de-emphasize styling and semantics so you spend time on state and evaluation. Several members said the pace felt “implement ASAP” with little room to chat.
- 3
Later rounds
Varies by roleMember reports in this set concentrate on the screen. Full loops at AI companies often add design, code review, and behavioral rounds; confirm with your recruiter rather than assuming a fixed onsite shape.
- 4
Decision
Days to about a weekOne public write-up noted failing when later formula parts were unfinished. Budget time for the hardest follow-up, not a perfect first paint.
03Why Harvey keeps asking for a spreadsheet
Harvey ships dense document and knowledge workflows for legal teams. A grid with interdependent cells is a clean proxy for the skills that matter: controlled inputs, derived state, dependency graphs, and talking about production hardening after the happy path.
Interviewers want to see:
- A clear cell address model (column letter + row number)
- Edit UX that does not fight the user (focus, commit on blur or Enter)
- Formula parsing that pulls referenced cells and computes a result
- A short production-grade punch list at the end: cycles, invalid refs, recompute scope, accessibility
If your prep is only LeetCode arrays, you are practicing the wrong muscle for this screen.
04What “good enough” looks like in 60 minutes
Members who passed or nearly passed share a timing pattern. Aim for a usable grid in the first third of the slot, a working formula path in the second third, and a spoken production backlog in the last third.
- Minutes 0 to 15: cell addresses, controlled inputs, commit on blur or Enter, render a small fixed grid
- Minutes 15 to 40: detect
=formulas, resolve referenced cells, show computed values without losing raw text - Minutes 40 to 60: walk through cycles, invalid references, recompute scope, keyboard UX, and how you would test it
Do not invent a full Excel clone. Interviewers grade clarity of the model under time pressure. A small correct CONCAT or SUM path beats half-finished operator precedence with no UI.
Full-stack variants may push evaluation into setCell time instead of lazy getCell reads. Ask which they want in one sentence, then commit. Switching mid-implementation costs the round.
Members only
What the coding rounds actually test
5 real Harvey interview questions
Every prompt members reported, with the round, the level, and the follow-ups interviewers asked.
Members only
Real Harvey interview questions reported by candidates
6 real Harvey interview questions
Every prompt members reported, with the round, the level, and the follow-ups interviewers asked.
Members only
What Harvey system design interviewers dig into
4 real Harvey interview questions
Every prompt members reported, with the round, the level, and the follow-ups interviewers asked.
Members only
Worked example: formula cells without a full spreadsheet engine
The exact Harvey interview prompts
Every prompt members reported, with the round, the level, and the follow-ups interviewers asked.
09Behavioral and “why Harvey”
Harvey is a legal AI company. Interviewers expect a specific reason you care about that domain: document workflows, trust and citations, or shipping AI tools lawyers will actually use. Pair that with two project stories you can defend end to end.
Strong motivation answers name a concrete workflow (contract review, research memos, knowledge retrieval) and a product principle you care about, such as verifiability or latency when a lawyer is mid-call with a client. Weak answers stop at “AI is exciting.”
For project deep dives, pick work where you owned UI state complexity: interdependent forms, collaborative editors, or data-heavy grids. Map that story to the same muscles the spreadsheet screen tests.
Use FrontendLead’s behavioral questions for STAR practice on ownership, tough feedback, and discovering problems outside your lane.
10How the loop changes by level
Mid / E5-style
Working grid + one formulaGet editable cells and a single formula path working. Clear narration beats clever abstractions.
Senior
Speed and extensibilitySame theme, less forgiveness on time. Structure part 1 so part 2 is a small addition, not a rewrite.
Staff
Production talk after the demoExpect a sharper “what would you improve for production” segment: cycles, recompute, collaboration, a11y.
11A four-week Harvey prep plan
- 1
Week 1: Grid UI under a timer
CodingBuild a bare 10×10 editable grid twice in 25 minutes. Practice: Reactive Sum Sheet.
- 2
Week 2: Formulas and recompute
CodingAdd CONCAT and SUM-style formulas. Practice: Minimal Recompute Sheet and Formula Spreadsheet.
- 3
Week 3: Spreadsheet system design
DesignWhiteboard a sheet for 45 minutes: model, deps, virtualization. Use Design a Spreadsheet and the frontend system design framework.
- 4
Week 4: Mocks and stories
Loop rehearsalTwo timed sheet mocks. Write “why Harvey.ai” and two deep dives. Review behavioral questions and Harvey reports.
12Mistakes that sink Harvey candidates
- Polishing CSS first. Members said styling was de-emphasized; formulas were not.
- Over-clarifying. One senior candidate felt there was almost no room to ask questions; ship a baseline fast.
- Storing only displayed values. You need the raw formula string to round-trip edits.
- Ignoring cycles and invalid refs in the wrap-up. Even unfinished implementations can pass the talk track if you name the hard parts.
- Generic motivation. Harvey is legal AI; say why that product, not “AI is the future.”
13Harvey front end interview FAQ
How long is the Harvey frontend interview process?
Member reports focus on the technical screen after an initial call. End-to-end timing varies; ask your recruiter for the full loop for your role.
Does Harvey ask LeetCode questions for frontend roles?
Reported frontend screens center on a practical spreadsheet UI, not classic algorithm drills. Full-stack variants still stay on the sheet theme in our set.
Can I use React in the Harvey coding interview?
Yes. Several candidates built the grid in React. Vanilla inputs also work if your state model is clear.
What is the most common Harvey frontend coding topic?
An editable spreadsheet-style grid with formulas that reference other cells. Exact prompts are in the members-only sections above.
Is Harvey the same as other companies named Harvey?
This guide is about Harvey.ai, the legal AI company. Confirm the company domain on your recruiter email.
Where can I practice for Harvey?
Start with Minimal Recompute Sheet, Reactive Sum Sheet, and Design a Spreadsheet. Browse coding questions and behavioral questions.
