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 Frontend Engineer to lead the architecture and technical direction of KEV's frontend platform, from the design systems and micro frontend patterns that let teams build consistently to the day-to-day judgment calls that keep delivery moving. This role requires deep hands-on experience with React and its surrounding ecosystem, and the ability to assess where our frontend architecture needs to evolve, shape a technical strategy for that evolution, and break it into work a team can execute.

You will partner closely with tech leads to align frontend architecture decisions with the platform's broader technical direction, and coach and mentor other frontend engineers to raise the team's collective capability. This is a role for someone who can surface trade-offs clearly and make decisions that hold up over the long term without stalling the delivery happening right now.

How You Will Contribute

Frontend Architecture & Technical Strategy

Assess the current state of KEV's frontend architecture, identify where it's creating friction or limiting scale, and shape a technical strategy for evolving it. Break that strategy into concrete workstreams and lead a team through execution, surfacing trade-offs and making decisions that hold up over the long term without stalling delivery in the short term.

Design Systems

Design, build, and evolve the design system(s) that frontend teams build on, so components, patterns, and interactions stay consistent as the platform grows. Balance the needs of individual product teams against the long-term coherence of the system as a whole.

Micro Frontend Architecture

Assess where micro frontend architecture would benefit KEV's products and services, and design and implement the patterns that let teams ship independently while keeping the platform's frontend cohesive for the people using it. Make and document the architectural calls — module boundaries, shared dependencies, integration patterns — that keep this approach maintainable as more teams adopt it.

React Ecosystem & Technical Craft

Bring deep, hands-on expertise in React and its surrounding ecosystem to both your own contributions and the standards you set for others — state management, build tooling, testing, and performance. Stay current with how the ecosystem is evolving and make deliberate calls about what KEV should adopt.

AI-Assisted Engineering

Use and evaluate AI coding tools as part of how frontend work gets done at KEV, applying the same judgment to new tooling that you'd apply to any other technical decision — where it genuinely improves quality or velocity, and where it doesn't.

Coaching & Technical Mentorship

Coach and mentor other frontend engineers, helping them build depth in frontend architecture, design systems, and modern React practice. Raise the technical bar of the team through hands-on pairing, review, and knowledge-sharing.

Cross-Functional Technical Partnership

Partner closely with tech leads to keep frontend architecture decisions aligned with the platform's broader technical direction. Communicate clearly about trade-offs so that stakeholders understand what's changing, why, and what was weighed to get there.