Lead Site Reliability Engineer - Canada, Remote (CA)

🏢 Cimpress/Vista · all Cimpress/Vista jobs
📍 Canada
💰 CAD 104,000 - 143,000 / annual
📅 Posted 2026-08-22 · via Himalayas
🏷 Site-Reliability-Engineering,Incident-Response,Platform-Engineering,Observability-Engineering,Cloud-Infrastructure-Engineering,Site-Reliability-Engineering-Lead,Remote-Site-Reliability-Engineer,Senior-Site-Reliability-Engineer,Staff-Site-Reliability-Engineer-(SRE),DevOps-Site-Reliability-Engineer,Site-Reliability-Engineer
Apply on original site ↗

Our Team

The Incident Response Team sits at the intersection of every customer-impacting failure across Vista. We coordinate response to critical incidents, drive learning out of every event, and partner with engineering teams across the organisation to make Vista more reliable. Today the team is strong on incident handling, and we are deliberately raising the engineering bar to match.
What You Will Do

-
Identify patterns of failure across the organisation. Analyse incidents and post-incident reviews to find the recurring technical root causes behind customer impact, rather than treating each incident as a one-off.

-
Prioritise the biggest improvement levers. Focus reliability effort where it most reduces Mean Time to Detect and Mean Time to Resolve, and where it proactively prevents the next incident from happening at all.

-
Turn those patterns into the right engineering intervention and influence the teams who can build it. This includes safe deployment defaults, secret and credential rotation, resilience patterns such as circuit breakers and fallbacks, observability and alerting standards, contract testing, and infrastructure pre-flight validation. You drive the what and the why; the owning teams build it.

-
Help teams hands-on, in their code , through Merge Requests, pairing, code review, and active technical support, favouring the simplest intervention that prevents recurrence over the most elaborate one.

-
Disseminate and evangelise improvements across the organisation . Identify best practices, document them, and transfer the learning to other teams so that local fixes become shared practice and improvements compound rather than stay siloed.

-
Lead the technical conversation in post-incident reviews and operational forums. Ask the questions that surface missing monitoring, untested failure modes, incomplete rollback strategies, and unaddressed dependency risks, and steer toward the simplest solution that holds.

-
Help the Incident Response Team grow its engineering practice by pairing on real work, sharing what good engineering looks like in our context, and running internal learning sessions that bring the team from incident-response specialists toward incident-response engineers.

-
Partner across teams without direct authority. Work with Platform Engineering, Deployment Platform, Developer Productivity, and senior engineers across Vista; contribute as a reviewer on proposals that touch reliability, deployment safety, observability, or operational readiness; and take part in the team's on-call rotation, contributing incident leadership when shared coverage requires it.

Your Qualifications

At VistaPrint, we are striving to hire individuals that add new ideas and perspectives to our teams and enhance our culture. No matter your background or work experience, we strongly encourage you to apply—even if you feel that you don’t meet the exact requirements or have the same qualifications. You might be a great candidate for this or other opportunities.

-
5 or more years of hands-on Site Reliability, Platform, or Infrastructure Engineering experience in a large-scale, distributed production environment, with proficiency in at least one programming language (e.g., Python, Go, TypeScript, Java) and a track record of code shipped to production

-
Demonstrated experience driving adoption of a reliability or platform pattern (e.g., progressive delivery, observability standard, resilience library, secret rotation) across teams that did not report to you, with measurable outcomes.

-
Strong systems thinking and a demonstrable bias toward simple solutions - able to read an incident or a design and identify the underlying class of problem (retries, cascading failures, queueing behaviour, partial failures, head-of-line blocking) and the smallest, cheapest intervention that addresses it. Comfortable choosing a post-deploy curl check over a full sandbox environment when the simpler intervention would pre

← All remote jobs