Harvey Software Engineer Interview Guide

Our candidates report a process that can feel oddly detached from Harvey’s own domain. In one experience, the recruiter reached out based on a tech-company signal on LinkedIn, but the candidate’s actual legal-tech background never really got explored, even though it was directly relevant. That pattern matters: Harvey appears to care less about a deeply tailored conversation up front and more about moving through a standardized screening script. We’ve seen that create friction for candidates who expect their niche experience to be recognized and used as evidence of fit.

A recurring theme is the lack of contextual follow-up. The only memorable question in this account was, “What was your stack score?” — a signal that the team may be using shorthand metrics or internal benchmarks rather than digging into the substance of a candidate’s work. We’d pay close attention to that because it suggests Harvey is looking for quick comparability, not a long narrative. The non-obvious risk here is assuming your background will speak for itself; in this process, it may not be surfaced at all unless it maps cleanly to the company’s pre-set filters.

What stands out most is the impression of checkbox evaluation over real discovery. Multiple candidates would likely read this as a warning that the early conversation may be shallow, scripted, and light on resume-based context. For Harvey, that means candidates who can’t translate their experience into the exact signals the team is already tracking may leave without ever being meaningfully understood.