Senior DevOps Engineer at ShyftLabs
Toronto
—
Jul 21, 2026
Toronto
Jul 23, 2026
What this job asks for AI summary
A hands-on senior infrastructure role responsible for designing, building, and operating cloud environments, CI/CD pipelines, and platform tooling across multiple production projects. The work centers on writing Terraform modules, automation scripts, and deployment tooling; maintaining reliability in live systems; and setting technical direction for DevOps practices. The role also involves mentoring engineers and collaborating closely with application developers. Suits an experienced practitioner with deep AWS and Kubernetes expertise who is comfortable owning end-to-end delivery.
Senior level · 5+ years · Toronto, ON · Full-time
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (4)
This role is based in Toronto, Canada (hybrid, 3 days/week in office) — the salary range of $120,000–$140,000 is explicitly stated in CAD, and US compensation benchmarks will not apply.
The SOC classification is a judgement call: the role is titled 'Senior DevOps Engineer' but the JD strongly emphasises writing Terraform modules, automation code, deployment scripts, and CI/CD pipelines — i.e., building software — which points to 15-1252 Software Developers. 15-1244 (Network/Systems Admins) is listed as the runner-up for the infrastructure operations dimension of the role.
All skills listed under 'What You'll Bring' are treated as hard gates given the firm, explicit language used ('Deep, practical expertise', 'Extensive hands-on', 'Fluent on the command line', 'Working knowledge of'). The 'Working knowledge of Elasticsearch' phrasing is slightly softer but still sits within the required qualifications block.
Kafka appears in the required qualifications block alongside other AWS services, though it is not an AWS-native service — it is listed as a hard gate based on its placement in the requirements section.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.