Lead DevOps Engineer

We ship enterprise software for the legal industry. Our customers trust us with confidential litigation material, so how we run our infrastructure is part of the product; at the same time, we need safe lanes to prototype, test, and launch features fast (monthly toward weekly). This role owns the environments and databases our engineers build on and ship through.

This is a player-coach seat, and above all a team-enabler seat: you will lead the environment and platform work directly, set the standard for a small existing team of two engineers with room to grow, and measure your platform by what the engineers and product teams around you ship on it without needing you in the room. Expect roughly 60% of your time hands-on building and operating, and 40% leading, reviewing, and designing.

The three things this role needs in one person:

1. You have owned environments end to end, as code.

You have built and run the full set of environments (e.g. production, staging, QA, development, prototyping and compliance environments) for a product team, and kept them reproducible through infrastructure as code rather than tribal knowledge. Provisioning a new environment is an automated, audit-ready act, not a project.

Evidence looks like: "Rebuilt provisioning on Terraform so a full new non-prod environment stands up in under an hour," or a multi-account cloud setup you designed with automated guardrails. In an interview, you can walk through exactly how prod and staging drift apart at your last job and what you did about it.

2. You have built observability and alerting that other teams actually use.

You have designed and run the monitoring, dashboards, and alerting for production systems, and you built them for the people who own the services, not just for the platform team. Your alerts mean something: each one is actionable, routed to a named owner, and tied to what the business feels when it fires. You have taken a noisy estate and made it quiet enough that a page means act now.

Evidence looks like: "Built the dashboards and runbooks that let application teams diagnose their own incidents instead of paging infrastructure first," or "cut alert volume to a set where every alert has an owner and an action after an alert-fatigue audit." In an interview, you can walk through an alert you deleted and why, and a dashboard a non-infrastructure team uses weekly.

3. You have designed infrastructure solutions that solve technical and business problems.

You build infrastructure that answers to both engineering and the business, not just plumbing. That includes automating compliance reporting so evidence collection is not a manual scramble, and safe ways to stand up and run prototypes. It also includes the security controls a regulated setting demands: least-privilege and break-glass access, and safe read paths (read replicas or sanitized exports) when analysts and business teams need data without needing production.

Evidence looks like: "Automated SOC 2 evidence collection so audit prep dropped from weeks to days," or "stood up a compliant prototyping lane that let product teams ship experiments without a security exception each time." You can walk through a break-glass access process you designed and why you drew the line where you did.

Essential Functions:

• Design, provision, and govern all product environments, including database tiers, with infrastructure as code
• Own and evolve our existing CI/CD pipelines, and design new ones from scratch for green-field projects, across every environment from commit to production; delegate pipeline work as the team grows
• Steward database operations with the team: backup/recovery, availability, capacity, patching (deep DBA specialization is not required; the standard is that the platform's data layer is operated deliberately, not that this person is a DBA)
• Design compliance-reporting automation and access controls (least-privilege, break-glass, safe analyst read paths) at the infrastructure layer, including audit support
• Build observability (today: CloudWatch) that lets service-owning teams troubleshoot their own systems, not just alert this team
• Coordinate releases and environment readiness across internal and external (vendor) development teams
• Set the documentation standard: runbooks and infrastructure docs that are readable by both humans and agents; automate documentation to stay current
• Lead and mentor the engineers doing this work; be the senior escalation point for production incidents. Be comfortable with junior engineers attending standups and coordinating with you asynchronously.
• Partner with application engineers to gather