Software Development Manager

The Gift and Loyalty platform at Moneris is a merchant-facing product used by businesses across Canada to run gift card and loyalty programs. The team responsible for it is six developers based primarily in Burnaby, B.C., managed from Toronto. The platform is in active modernization: architecture decisions are being made now, and the person in this role owns those decisions.

Success here looks like a team that ships against committed roadmap milestones, improves platform reliability and test coverage over time, and operates with enough clarity that engineers know what good looks like and why. Failure looks like a manager who stays in meetings while the team drifts, or one who makes architecture calls without bringing the team along. This role requires both: the ability to hold a technical opinion and the ability to develop the people around you.

The work sits at the intersection of delivery management and hands-on technical leadership. You will be in the code at the review and architecture level, not writing features day to day, but close enough to catch problems early and coach effectively. The platform handles payment-adjacent data for enterprise merchants, so security posture, availability, and compliance considerations are part of every significant design conversation.

- Languages: C# (primary), SQL
- Frameworks: .NET ecosystem
- Enterprise patterns: CQRS, event-driven architecture, microservices
- Data layer: Relational databases at enterprise scale (SQL)
- Cloud: Microsoft Azure
- CI/CD: exposure to GitHub Actions
- Testing: unit, API, and UI test automation practices
- Exposure to: React Native, Node.js, Java (architectural review level)

- Produce and own the technical roadmap for the Gift and Loyalty platform covering at least two roadmap cycles within the first six months
- Complete a documented architecture review of the current platform state, with a gap analysis and a prioritized modernization plan
- Establish or formalize code review standards and CI/CD hygiene practices across the team
- Deliver at least one committed roadmap initiative from scoping through production release
- Implement or improve shift-left testing practices, with measurable increase in automated test coverage
- Build a regular cadence of one-on-ones and development conversations with all six direct reports, with documented growth goals for each
- Produce a recurring reporting artifact (status, risks, KPIs) used in leadership updates

A typical week involves a mix of synchronous touchpoints with the Burnaby team and focused work blocks in Toronto. Monday often starts with a team standup and a backlog review to confirm priorities for the week. Later in the day there may be a working session with Product or Infrastructure to align on an upcoming feature or a pending security review.

Mid-week work blocks are where most of the technical depth happens: reviewing pull requests, giving written feedback with enough context that developers understand the reasoning, and occasionally sitting in a design session where the team is working through an architectural question. These sessions are collaborative, but you are expected to arrive with a point of view.

Thursday or Friday typically includes a one-on-one with one or two direct reports, a check-in on delivery progress against the roadmap, and preparation for any leadership update due that week. The reporting artifact for leadership is a standing deliverable, not an ad hoc task, so it gets drafted during the week rather than assembled at the last minute.

Because the team is distributed across time zones, written communication carries more weight than in a co-located setup. Decisions made in meetings get documented. Architecture choices get written down with the reasoning attached.