Katkat

Company

Harvey interview questions

46 practice questions in the style of Harvey's interviews, covering Software Engineering Fundamentals, Coding & Algorithms, Behavioral & Leadership, System Design, ML System Design, Machine Learning.

Questions46

0 easy38 medium8 hard

Your progress0/46

Harvey interview questions by the numbers

Last updated

Katkat has 46 Harvey interview questions. The largest topics are Coding & Algorithms (35%), System Design (20%) and Software Engineering Fundamentals (17%). By difficulty: 83% medium and 17% hard. The most common round is Onsite (52%). Frequent concepts include System Design, Design, Information Retrieval and LLM.

Difficulty

  • Medium83% · 38
  • Hard17% · 8

Interview rounds

  • Onsite52% · 24
  • Technical Screen46% · 21
  • Other2% · 1

Roles

  • Software Engineer80% · 37
  • Backend Engineer9% · 4
  • Frontend Engineer4% · 2
  • Machine Learning Engineer4% · 2
  • AI Agent2% · 1

Frequent concepts

  • System Design11% · 5
  • Design9% · 4
  • Information Retrieval9% · 4
  • LLM9% · 4
  • RAG9% · 4
  • design7% · 3

Showing 31–46 of 46 results

  • This problem tests your ability to manage a directed graph of dependencies and implement a topological update mechanism to recompute spreadsheet cell values efficiently.

    HarveySoftware EngineerCoding & AlgorithmsTechnical Screen
  • Design an in-memory cursor-based text editor supporting character insertion, deletion, and cursor navigation with efficient time complexity.

    HarveySoftware EngineerCoding & AlgorithmsOnsite
  • Tests your ability to implement a thread-safe connection pool that manages connection lifecycles, blocking acquisition with timeouts, and resource reuse under concurrent access.

    HarveySoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to model cell dependencies using a directed graph, handle topological sorting for re-evaluation, and identify circular references.

    HarveyMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • Design an in-memory integer spreadsheet supporting cell assignments, additive formulas with nested references, and dynamic recalculation of acyclic dependency chains.

    HarveySoftware EngineerCoding & AlgorithmsTechnical Screen
  • This combined prompt evaluates string-processing and parsing skills for tag matching and design/implementation skills for an in-memory file system, measuring competencies in exact whole-word matching, case normalization, punctuation and duplicate handling, path parsing, hierarchical data structures, and file API behaviors.

    HarveyBackend EngineerCoding & AlgorithmsOnsite
  • Design an in-memory file system supporting directory creation, file creation with automated duplicate-name collision resolution, content retrieval, and directory listing.

    HarveySoftware EngineerCoding & AlgorithmsOnsite
  • Build an in-memory variable resolver for a CI configuration system in three stages: plain integer variables, expression variables that reference other variables, then cycle detection with recomputation limited to the affected dependents. Checks whether a candidate can grow a design incrementally, respect a correct computation order, and reason about a dependency graph under change.

    HarveySoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A three-part coding exercise: build a mini spreadsheet with set_cell and get_cell, add formulas that sum constants and cell references with values computed eagerly in set_cell, and detect and reject circular dependencies. It tests dependency graphs, ordered recomputation and cycle checks.

    HarveySoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Three behavioral questions from a hiring manager screen: a project you owned in the last year, tough feedback you received, and a time you discovered an important problem outside your immediate focus area. It tests ownership, coachability and judgment about raising issues beyond your own scope.

    HarveySoftware EngineerBehavioral & LeadershipTechnical Screen
  • This interview module assesses your technical ownership, architectural decision-making, and alignment with engineering core values such as velocity, rigor, and customer obsession.

    HarveySoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates conflict resolution, stakeholder alignment, cross-team communication, and leadership competencies in the context of engineering coordination, classified under Behavioral & Leadership for a backend engineer role.

    HarveyBackend EngineerBehavioral & LeadershipOnsite
  • Implement an in-memory spreadsheet class in three steps: set and get integer cell values, support formulas that reference other cells, and reject any write that would create a circular reference while leaving the sheet unchanged. It tests dependency tracking, update propagation and cycle detection.

    HarveySoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Build an in-memory spreadsheet class in three stages: integer cells with set_cell and get_cell, formula cells such as =B1+C1+1 with explicit handling of never-set cells and recomputation on every write, then cycle detection and recomputing only dependent cells. Tests incremental design, evaluation order and dependency graphs.

    HarveySoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design an in-memory spreadsheet formula engine supporting cell assignments, formula evaluation with dependencies, and cycle detection. The question tests directed graph modeling, topological invalidation, and cycle detection algorithms.

    HarveySoftware EngineerCoding & AlgorithmsTechnical Screen
  • An ML research discussion on training language-model agents for long-context, long-horizon tasks. It tests the training recipe from context extension through supervised trajectories to RL, the design of reproducible training environments, and reward design that resists reward hacking over long trajectories.

    HarveyMachine Learning EngineerMachine LearningOnsite

Harvey interview experiences

All 6 →
  • Patterns from Seventeen ReportsHarvey · Software Engineer · Onsite · Sep 2026

    The author summarizes 17 Harvey interview reports from March through September 2026. Technical screens reportedly centered on spreadsheet formulas or text highlighting, with attention to dependency cycles, evaluation timing, and whole-word matching. Onsite coding examples included an in-memory filesystem, expression evaluation, citation highlighting, and duplicate-file discovery with symbolic-lin…

  • Phone Screen Building an Excel set_cell/get_cell in Three ScopesHarvey · Software Engineer · Technical Screen · Sep 2026

    Another Excel set_cell and get_cell problem. It starts out really simple and then ramps up step by step, and time was still really tight while writing it. Scope 1 Implement a simple Excel. You need and In step one, set only takes numbers, no formulas, so I'd suggest getting through it fast and not wasting time. Scope 2 Step two adds the ability to set a formula, e.g. set_cell("A1", "=B1+C1+1") or…

  • Hiring Manager Screen, Then a Spreadsheet Tech Screen I Didn't FinishHarvey · Software Engineer · Technical Screen · Aug 2026
    Rejected

    I applied online and a recruiter reached out. First round was a hiring manager screen. They asked questions like: tell me about a project I owned in the last year tell me about tough feedback I received tell me about a time I discovered an important problem outside of my immediate focus area Second round was the technical screen. It was similar to the spreadsheet question you can find online, but…

  • Three Rounds and a Frustrating Empty OfficeHarvey · AI Agent · Onsite · Aug 2026
    Rejected

    It was a surreal onsite experience. I had practiced the phone-screen problem many times. It was the Google Sheets problem, and I finished it immediately. The recruiter told me about an hour later that I had passed, then arranged the onsite. There were three rounds. For system design, I was asked to design an agent that scores a file according to a set of rules and labels it qualified, acceptable,…

  • A File System Question and a Hard-to-Follow InterviewerHarvey · Software Engineer · Technical Screen · Sep 2025

    The file system question from 1point3acres. The writeup is here: a question that hasn't shown up on the forum before, basically a file system where you implement two functions: addFile(String path) — given a string like "path/to/somewhere/file.txt", store this file getFile(String path) — input "path/to/somewhere" returns file.text, input "path/to" returns the "somewhere" folder There wasn't reall…

More companies