Tracking 100,000+ career sites

Senior DevOps and Infrastructure Jobs

This list is updated hourly from 100K+ company job sources and surfaces senior DevOps and infrastructure roles across CI/CD, SRE, platform engineering, systems, networks, databases, and observability.

Openings may be labeled senior DevOps engineer, site reliability engineer, platform engineer, infrastructure engineer, systems or network engineer, database administrator, production engineer, or infrastructure lead. Responsibilities can include deployment automation, internal developer platforms, Kubernetes operations, network and database reliability, monitoring, capacity planning, incident response, and modernization of core systems. The balance between software development, platform enablement, and direct operations varies by team and should be clear in the source description. Some postings measure the role through developer adoption and delivery speed; others focus on availability, recovery, capacity, or safe change. Seniority is reflected in production ownership, architectural judgment, incident command, automation depth, and the ability to reduce recurring operational work. Staff and principal roles may set technical direction without direct reports; managers and operations leaders can add staffing, service-level, and escalation responsibilities.

Production responsibility is the most useful starting point. Determine whether the engineer owns services, a shared platform, networks, databases, or an operating process, and how much of the work is software development versus administration. Then verify the cloud and operating environment, coding and infrastructure-as-code tools, container stack, observability systems, security or clearance needs, on-call rotation, and role during high-severity incidents. Look for evidence of who sets service objectives, approves risky changes, and follows remediation work after an incident. A disclosed interview plan may call for coding, systems design, troubleshooting, or incident examples; tailor preparation to the ownership described. Compare pay with call frequency, remote-access limits, and platform maturity. Company, location, compensation, and sponsorship filters refine the list, while the original posting controls authorization and workplace requirements.

The list remains free to browse and filter. An optional free account keeps saved infrastructure roles and application progress together and offers Copilot for selected forms. Revisit any saved posting before applying.

4,245
roles in this list
1,341
added this week
Featuring roles at
Canva
Netflix
Notion
Visa
Capital One
& 100K+ more
Got questions?

Explore our FAQ section to learn more.

This list covers senior DevOps and infrastructure positions, including platform, cloud, site reliability, systems, networking, and production-engineering work. Every matched title must include senior.

DevOps often emphasizes delivery automation and collaboration, platform engineering builds internal systems for developers, and site reliability engineering focuses on production reliability and operational engineering. Boundaries differ across employers.

Highlight production scale, reliability improvements, deployment speed, incident reduction, infrastructure automation, cloud migrations, security improvements, and cost savings. Explain both your technical contribution and operational impact.

Expect troubleshooting, systems design, cloud and networking questions, incident retrospectives, automation discussions, and tradeoff analysis. Some roles also include coding, scripting, or infrastructure-as-code exercises.

Tool requirements vary, but common areas include Linux, cloud platforms, containers, orchestration, CI/CD, infrastructure as code, observability, networking, and scripting. Demonstrated operational judgment matters more than listing every tool.

Ask about rotation size, incident frequency, escalation practices, service ownership, runbooks, and recovery expectations. Clarify whether the role is expected to improve the systems causing repeated incidents.

Many are senior individual-contributor positions with broad technical ownership. Others include team leadership, so check for direct reports, hiring responsibilities, performance reviews, and organizational planning.

Compare system maturity, technical debt, deployment practices, cloud strategy, staffing, on-call load, security ownership, and authority to improve reliability. Ask what outcomes are expected during the first year.