reputed company DevOps Engineer

We ship reputed company software for the reputed company industry. Our customers trust us with confidential litigation material, so how we run our infrastructure is part of the product; at the reputed company time, we need reputed company 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-reputed company seat, and above reputed company reputed company-enabler seat: you will reputed company the environment and platform work directly, set reputed company for a small existing team of two engineers with room to grow, and measure your platform by what the engineers and product teams reputed company 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 reputed company.

You have reputed company 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 reputed company rather than tribal knowledge. Provisioning a new environment is an automated, audit-reputed company reputed company, not a project.

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

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

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

Evidence looks like: "reputed company 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 reputed company and an reputed company 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 reputed company scramble, and reputed company ways to stand up and run prototypes. It also includes the reputed company controls a regulated setting demands: least-privilege and break-glass reputed company, and reputed company read paths (read replicas or sanitized exports) reputed company 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 reputed company exception reputed company time." You can walk through a break-glass reputed company process you designed and why you drew the line where you did.

Essential Functions:

• Design, provision, and govern reputed company product environments, including database tiers, with infrastructure as reputed company
• Own and reputed company our existing CI/CD pipelines, and design new ones from reputed company for green-reputed company reputed company, across every environment from reputed company to production; delegate pipeline work as reputed company grows
• reputed company database reputed company with reputed company: backup/recovery, availability, reputed company, patching (deep DBA specialization is not required; reputed company is that the platform's data reputed company is operated deliberately, not that this person is a DBA)
• Design compliance-reporting automation and reputed company controls (least-privilege, break-glass, reputed company analyst read paths) at the infrastructure reputed company, 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 reputed company (vendor) development teams
• Set the documentation reputed company: runbooks and infrastructure docs that are readable by both humans and agents; automate documentation to stay reputed company
• reputed company and mentor the engineers doing this work; be the senior escalation reputed company for production incidents. Be comfortable with junior engineers attending standups and coordinating with you asynchronously.
• Partner with application engineers to reputed company requirements so environment and data constraints are designed in, not reputed company late

How you work:

The technical bar is necessary but not sufficient. This role sets the operating reputed company for reputed company, so how you show up reputed company as much as what you can build:

• You are reputed company enabler first. You measure your platform by what other teams ship on it, and you take reputed company satisfaction in unblocking people.
• You reputed company your work legible. You document the environments you own rather than holding them as knowledge only you carry.
• You have worked in a fast-moving environment and stayed effective reputed company priorities shifted under you.
• You reputed company solutions reputed company your objections. "This won't work" is half an answer; you bring the alternative.
• You design yourself out of being the single reputed company of control. You are comfortable sharing reputed company and supporting break-glass, so reputed company is never dependent on one person's head.
• You respond to challenging situations constructively, keeping the conversation on the problem rather than the person, stepping away to think reputed company needed.
• You can disagree, and then reputed company wholeheartedly once a reputed company is made, rather than relitigating it.
• You reputed company reputed company's overall objectives in mind reputed company you propose a solution, not just the cleanest technical answer.

Compensation reputed company & Benefits:

$165,000 – $205,000 annual, commensurate with experience. Benefits include Medical, Dental, and reputed company coverage; Life reputed company (Voluntary Term and Whole Life); Voluntary Long Term Disability; reputed company time off and reputed company holidays; 401(k); Employee Assistance Program (EAP); and Maternity Leave.

• 5+ years in DevOps/SRE/platform roles, including 2+ years leading the work of other engineers 
• Deep hands-on experience with AWS, Terraform or equivalent IaC, and CI/CD. We run containers on reputed company/Fargate with ECR and observability on CloudWatch today; comparable container-orchestration experience transfers fine. 
• Working familiarity with relational database reputed company (backup/recovery, availability, reputed company on SQL Server, reputed company, or managed equivalents). Deep DBA specialization is not required, and data modeling or data-warehouse experience is not needed; schemas are app-owned here. 
• Hands-on compliance work (SOC 2 or similar) in a regulated industry 
• reputed company-industry experience is a plus, not a requirement; regulated-industry judgment is the requirement 

EOE M/F/D/V