Senior+ Software Engineer, Legal Tech

Anthropic · Remote-Friendly (Travel-Required) | San Francisco, CA | Seattle, WA | New York City, NY · Software Engineering - Infrastructure · listed September 29, 2026

The shape of it

Seniority
Senior
Where
Hybrid
Stated pay
$320,000 – $485,000 USD
Requirements listed
7
Length
1,439 words

In the posting’s own words

As a Senior+ Software Engineer on our Legal Tech team, you'll build dedicated, highly secure, and reliable cloud environments and data processing and storage capabilities at speed and scale. You will own your scope end to end: from raw requirements all the way through to large-scale production systems that satisfy legal invariants and unlock new possibilities. The systems you build won't just be dependable and scalable; they'll be interpretable and auditable, demonstrating to skeptical audiences exactly how they worked and why results can be trusted.

What it asks for · 7

  • Experience designing, building, and operating highly trusted infrastructure and data systems in production, including owning architectural decisions
  • Experience working across large, complex, multi-team environments, including in stacks and code you don't own
  • Ability to take ownership of a cloud account and secure it end to end (networking, storage, identity, encryption, least-privilege provisioning, etc.) on AWS and/or GCP
  • Ability to translate legal and privacy requirements into sound technical designs and implementations that teams are excited to adopt
  • A habit of verifying rather than assuming: designing checks for invariants and plainly naming what isn't proved
  • Self-directed in a high-change environment, and comfortable resequencing quickly when new needs emerge
  • Clear communication with nontechnical stakeholders, and an understanding of their needs

Also a plus

  • Software engineering experience with an infrastructure, data, privacy, and/or security focus
  • Proficiency with large-scale data tooling, such as distributed processing, lakehouse table formats, and/or query engines
  • Understanding of data processing pipelines, LLM training, and/or provenance and lineage
  • Experience with secure enclaves, confidential computing, clean rooms, or other purpose-built environments for sensitive data
  • Background in eDiscovery, litigation support, or records retention at scale, including chain of custody and verifiable integrity

What the job covers

  • Build and operate dedicated cloud infrastructure, storage, and data pipelines for specialized workloads that can't run on general-purpose systems
  • Design architectures with excellent security, privacy, reliability, scalability, and auditability baked in
  • Partner with a wide range of internal customer teams to translate requirements into sound approaches and realistic ETAs
  • Deliver against fixed deadlines
  • Support complex and novel legal requests on controlled infrastructure, with verifiable chain of custody
  • Pair with engineering teams across the company to extend existing infrastructure to support new workflows and/or legal requests
  • Work with nontechnical stakeholders to clarify their needs through responsive, easy-to-follow dialogue

Tools and skills named

Security & compliance
  • Security5×
Cloud & infra
  • AWS2×
  • GCP2×
Data
  • Data pipelines2×
  • Data warehouse2×
Models & research
  • LLM2×

Words the posting leans on

  • data13×
  • legal13×
  • infrastructure12×
  • and/or11×
  • experience8×
  • privacy7×
  • systems7×
  • end6×
  • support6×
  • build5×
  • cloud5×
  • complex5×
  • designing5×
  • requirements5×
  • secure5×
  • security5×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Anthropic

every open role at Anthropic →

How this page was made

An automated read of a public job posting, fetched September 29, 2026 and last changed by Anthropic on September 29, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.