TechOps Engineer

About the role

The role treats internal IT infrastructure as a product within Technical Operations, balancing user support with projects to solve problems in US healthcare. The team owns automation that enables stakeholders to tackle the hardest infrastructure challenges.

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

The team builds automated workflows to manage onboarding and offboarding, removing repetitive manual work so the organization can scale operations.

Critical initiatives migrate Apple MDM platforms, perfect Zero-Touch Enrollment pipelines, and build Just-in-Time access automation to directly improve reliability and user experience.

Implementation of zero-trust controls secures business applications, enforced through SSO, SAML, and MFA to protect systems and data.

Curiosity drives investigation of root causes, fixing core infrastructural issues rather than applying repetitive patches to symptoms.

Requirements

The posting states a bachelor's degree requirement. Hands-on Technical Operations or IT experience of 4+ years is required, typically gained in fast-paced tech startups or high-volume Managed Service Provider environments. A degree is held as required.

Deep troubleshooting skills across macOS are demonstrated, with hands-on experience managing Apple MDM tools such as Jamf and Kandji and packaging workflows using AutoPkg.

Manual tasks performed twice are scripted or automated by you, showing a bias toward action that removes repetitive work. Internal employees are treated as customers, and complex security or technical changes are translated clearly for non-technical audiences.

Compliance, data protection, and secure offboarding processes prioritize patient data safety, upholding security and privacy standards across all operational activities.

Practical notes

The role expects in-person work at offices in Denver, New York, or San Francisco, with a weekly schedule of four days onsite and one day remote. 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

Technical operations blends infrastructure engineering and IT support to keep systems reliable. Common tools include configuration management and automation platforms. Strong security practices protect sensitive data in regulated industries. Clear communication bridges technical and non-technical teams. Automation reduces repetitive work and improves consistency.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

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.