Staff Site Reliability Engineer

Who We Are

KEV builds mission-critical financial software for K12 schools across North America. Our platform provides real-time visibility and control over how funds are collected and managed, replacing fragmented workflows with secure, modern systems that schools rely on every day.

Who We Are

KEV builds mission-critical financial software for K12 schools across North America. Our platform provides real-time visibility and control over how funds are collected and managed, replacing fragmented workflows with secure, modern systems that schools rely on every day. Trusted by more than 27,000 K12 schools managing over $8B annually, KEV delivers mission-critical software for payments, accounting, and reporting, where reliability and security matter. Headquartered in Toronto with teams across North America, we are scaling quickly and investing deeply in cloud-native, data-driven technology. KEV is a place for people who care about building durable software at scale and doing work that has real impact in public education. We focus on solving hard problems, raising the bar on engineering craft, and building products that earn long-term trust from the communities we serve. This role is for an active vacancy.

About the Role

We are hiring a Staff Site Reliability Engineer to raise the bar on how reliably KEV's platforms run in production, from the SLOs and error budgets that define what "reliable" means for each service to the incident practice that keeps issues from repeating. This role requires deep hands-on SRE experience and the judgment to assess where reliability is at risk, shape a strategy for closing the gap, and break that strategy into work a team can execute. You will partner closely with KEV's DevOps Engineering team and product engineering teams to embed reliability into how services are built and operated, and coach and mentor other engineers on reliability practices. This is a role for someone who can surface trade-offs clearly and communicate them well.

How You Will Contribute

• Reliability Strategy & SLOs Assess the current state of reliability across KEV's platforms, define and evolve the SLOs, SLIs, and error budgets that make "reliable" a measurable target rather than a feeling, and build a strategy for closing the gaps you find. Break that strategy into concrete workstreams and lead a team through execution.
• Incident Management & Postmortem Practice Own how KEV responds to production incidents, driving blameless postmortems that get to root cause rather than surface symptoms. Use recurring incidents and operational issues to identify durable fixes and longer-term reliability investments, not just one-off patches.
• Observability & Monitoring Platform Design and evolve the monitoring, alerting, logging, and tracing platform that gives engineering teams real visibility into system health. Use data to reduce noisy or ineffective alerts and make sure the signals teams rely on are ones they can trust.
• Automation & Toil Reduction Identify repetitive, manual operational work and replace it with automation and tooling that's maintainable, testable, and treated as production code. Build the tools yourself where that's the right answer, rather than only advocating for automation from the sidelines.
• Capacity & Performance Engineering Lead capacity planning and performance analysis so that KEV's platforms scale ahead of demand rather than in reaction to it. Use load testing and performance data to anticipate where systems will break before they do.
• AI-Assisted Reliability Operations Evaluate and apply AI tooling where it can meaningfully improve reliability and operational workflows — such as anomaly detection or incident triage — applying the same trade‑off thinking to new tooling that you'd apply to any other operational decision.
• Coaching & Reliability Mentorship Coach and mentor other engineers on reliability practices — on‑call hygiene, incident response, SLO‑driven prioritization — raising the operational maturity of the broader engineering organization over time.
• Cross‑Functional Partnership Partner closely with KEV's DevOps Engineering team and product engineering teams to embed reliability into how services are designed, built, and operated. Communicate trade‑offs clearly so stakeholders understand what's changing, why, and what was weighed to get there.

Who You Are

• 10+ years of hands‑on experience in Site Reliability Engineering, Platform Engineering, or a similar infrastructure/operations role, with a track record of leading reliability strategy and incident practice at scale.
• Familiarity working with Microsoft Azure and .
  NET, including legacy .
  NET Framework applications and IIS, so reliability practices hold up across KEV's full stack and not just its newest services.