Manager, Software Engineering
- Market p25–p75
- CAD 105k–CAD 179k
- Opened · 30d
- +1
- Closed · 30d
- −2
- Opened · 7d
- +19110% of open
- All software engineering
- 75,120open
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.
About the Role
We are hiring an Engineering Manager to lead product-focused engineering teams at KEV, owning delivery, technical direction, and team health across an area of our product organization. You’ll work closely with Product and other cross-functional partners to turn business priorities into clear plans and reliable execution, while ensuring the teams are building durable, scalable software.
You will lead a portfolio of several squads through their technical leads, who own day-to-day execution and technical decisions within each squad. You’ll work with Product to align on priorities, then hold the squads accountable for turning the roadmap into predictable, on-time, quality delivery. You’ll also own the people side: developing your technical leads and senior engineers into stronger leaders, planning capacity, and building the leadership depth the organization needs as it grows.
This is a senior engineering leadership role for someone who leads through other leaders but stays close to the technical work: reviewing significant changes, shaping architecture, and making pragmatic calls on modernization and scalability. We’re growing quickly and still shaping how engineering works here, so this role is about improving how teams deliver, not keeping things as they are.
How You’ll Contribute
- Engineering Leadership: Manage and develop the engineers and technical leads across your squads. Run regular 1:1s, set clear expectations, coach consistently, and address performance concerns directly. Keep a close read on team health too, including morale, burnout, engagement, and retention risk, and step in when something’s off.
- Organizational Capability: Own capacity planning and the engineering roadmap for your area. Spot capability and succession risks early, and build the leadership depth the group needs to keep growing. That means working closely with Product to keep engineering capacity and delivery planning realistic against the roadmap.
- Delivery Ownership: You’re accountable for delivery outcomes across your teams. Translate priorities into clear plans with predictable results, and build the operating rhythms that keep teams honest about progress. When a dependency or blocker threatens a commitment, you’re the one surfacing it early and clearing the path.
- Product Partnership: Act as the primary engineering counterpart to Product for your area. Shape priorities, scope, sequencing, and trade-offs together, and make sure engineering has a seat at the table early in discovery, not just at handoff.
- Agile Practices: Lead teams operating in Agile environments, strengthening planning, estimation, and delivery discipline while keeping the focus on outcomes over process. Add no more process than the teams need, and track commitments against delivery and cycle time in ways the teams actually use, not just report.
- Quality and Reliability: Make sure quality, reliability, and security are built into the development lifecycle, not bolted on afterward. Set clear testing and engineering standards that teams actually understand and follow, with a shift-left mindset baked in.
- Technical Leadership: Set technical direction for teams building on React, .NET, and API-driven microservice architectures on Azure. Work with your technical leads to manage cross-team technical risk and make the pragmatic calls on architecture, modernization, and scalability your area needs, while letting technical leads own day-to-day technical decisions within their own squads. Bring in new tools and practices where they earn their place, including AI-assisted development.