Company
Harvey
Annual salary
$231k – $340k/yr
Location
San Francisco, CA
Listed
22d ago
- Experience:
- 5+ years
- Workplace:
- Hubs are San Francisco, New York City, and Toronto, and Chicago is also an option. Relocation help is available for the right candidate. For an exceptional OfficeJS engineer (for example, one with standout public Office Add-in work), the team may consider remote work depending on location, including Canada. Technical fit comes first, and location is not a strict blocker.
- Equity:
- None
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
Hybrid in San Francisco, CA.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
What you'll do
- Own and lead the technical direction of Harvey in Word, Harvey's flagship Office Add-in, along with our other Microsoft Office integrations on the Embedded Experiences team
- Build the AI-native editing experience, including agentic document rewrites, precise and reviewable redlines and track changes, and playbook automation that changes how lawyers draft and review
- Work closely with product, design, backend, and the sister Document Editing Engine team to shape APIs and UX for AI features like streaming results and tool-calling workflows
- Design scalable, maintainable solutions that handle the quirks of the Office Add-in environment on Windows, Mac, and Web, including requirement sets, manifests, and versioning
- Lead features from architecture through production launch, with crisp interactions and resilient error handling, shipping on a weekly cadence
- Contribute to Harvey in Outlook and help shape the next generation of agentic AI interfaces across the Microsoft suite, while mentoring engineers and raising the bar on quality and developer experience
What you need
- We need a strong core software engineer, typically 5+ years in, who has personally built and shipped production Office Add-ins with OfficeJS at scale. This is not an implementation or forward-deployed role. You should be comfortable owning hard technical problems in a fast-moving, high-intensity late-stage startup, and you should have a track record of shipping polished, high-performance products that real users depend on. Bonus points if you've worked on document editing engines (Open XML/OOXML, redlining, track changes), in legal tech (for example Ironclad, GC AI, Spellbook), or in a mix of big tech and hyper-growth startups.
Common questions
How do I apply for the Staff Software Engineer, OfficeJS (US) role at Harvey? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Harvey role pay? +
The listing gives $231k – $340k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. Hubs are San Francisco, New York City, and Toronto, and Chicago is also an option. Relocation help is available for the right candidate. For an exceptional OfficeJS engineer (for example, one with standout public Office Add-in work), the team may consider remote work depending on location, including Canada. Technical fit comes first, and location is not a strict blocker.
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →