Senior DevOps Engineer
Job description
About the role
This role ensures production and corporate systems remain reliable and available within a diverse, mission-driven team. The position delivers resilient infrastructure that supports global access to mental health care.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Reliable systems and processes are shaped, deployed, and maintained to meet organizational objectives.
Service outage escalation response is provided with software engineers whenever incidents arise.
On-call incident management rotation is followed to address production issues quickly.
Instance configuration and security are handled across multiple environments to manage access and risk.
Production systems and networks are observed to sustain performance and detect issues.
Automation is created and released to streamline operations and reduce manual effort.
Training resources are used to strengthen capabilities and support success in the role.
Requirements
A minimum of 5+ years of experience in DevOps or as an SRE in equivalent production engineering roles is required.
Strong experience with AWS, Docker, and Kubernetes for cloud operations is necessary.
CI/CD pipelines and methodologies are used to enable automated delivery.
IaC tooling such as Terraform is employed to manage infrastructure as code.
Linux systems knowledge is applied very deeply for troubleshooting and operations.
Verbal and written communication skills are strong for effective collaboration.
The ability to think quickly supports solving unique problems and proposing innovative solutions.
Practical notes
This role requires US-based candidates, with remote work allowed across time zones and travel to San Jose, CA up to three times yearly. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Remote work is common, with scheduled in-person collaboration a few times per year. The role uses cloud platforms, containers, orchestration tools, and monitoring systems. Engineers balance sustainable work practices with demanding production responsibilities. The position operates within a large, regulated mental health technology environment.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.