At Chexy, we're building modern financial tools for Canadians - starting with their largest expenses. We turn rent, tuition, insurance, and other big bills into opportunities to build credit, earn rewards, and gain financial flexibility,
We're the first platform in Canada that lets users pay nearly any bill using their credit card, while unlocking meaningful benefits like cashback, points, and credit-building tools. With ~$2B in annual payment volume and hundreds of thousands of transactions a month, we're building financial infrastructure that needs to be fast, reliable, and bulletproof.
About the Role
We're looking for a Backend Engineer to build payment systems in Chexy's core backend service. You'll work on the systems that move money - payment inflows, outflows, ledgering, settlement, and direct integrations with card networks and banking systems.
Every line of code you write will process real money for real people, which means your work needs to be precise, well-tested, and built to be trusted. You don't need to have built a ledger before - you need to want to, and to care about getting it right.
What You'll Be Doing
- Build and maintain payment processing across inflows, outflows, and multi-rail settlement
- Work inside our double-entry ledger - posting entries, reconciling against processors and banks, and keeping the books provably correct
- Build and extend integrations with payment networks and Canadian banking rails
- Write clean, well-tested, production-grade TypeScript (we use NestJS, Prisma, and PostgreSQL)
- Build event-driven and durable workflows (Google Cloud Pub/Sub, Temporal) so payments retry, recover, and never double-send
- Build APIs consumed by our web and mobile apps through our backend-for-frontend layer
- Instrument what you ship - Datadog traces, structured logs, and alerts are part of done
- Review code, write tests, and help keep our engineering standards real
Who We're Looking For
- 2+ years of backend engineering experience with TypeScript/Node in production
- Solid grasp of relational databases-schema design, transactions, and what happens when two writes race
- You understand idempotency and can explain why it matters when money is involved
- Familiarity with event-driven systems or message queues (Pub/Sub, Kafka, SQS, or similar)
- You already build with AI coding tools every day and can tell when they're wrong
- You write clear PRs and clear messages, and you ask when you're stuck instead of spinning
- You'd rather make a call with most of the information than wait for all of it, and when a requirement changes mid-build you get curious about why
- You want to own something - a rail, a domain, a problem - not just close tickets
Bonus Points
- Experience with payment processing, banking integrations, or fintech
- Google Cloud Platform (Cloud Run, Cloud SQL, Pub/Sub) or Terraform
- Interest in Rust or high-performance ledgers (TigerBeetle)
How We Build
We're early. The roadmap moves as we learn from users, partners, and regulators - sometimes week to week - and you'll regularly pick things up outside your title. The people who do best here find that energizing. They'd rather make a call with most of the information than wait for all of it, they get curious instead of frustrated when a requirement changes halfway through, and they've usually been early somewhere before and wanted to do it again.
The way software gets built is changing faster than anyone's best practices can keep up, and we're not pretending otherwise. Most of what we ship is written with AI tools - but that's the least interesting part. The interesting part is working out what that means for how we review, test, and take responsibility for code: what you hand to a model and what you never do, what "I read the diff" means when the diff is two thousand lines, how a small team keeps quality up while moving faster than it should be able to. We're writing that playbook as we go, and we want people who want to write it with us, not people waiting to be handed it. We care a lot about attitude - someone who brings energy into a room rather than absorbing it. When something breaks, they're already on it before anyone asks.
Why Join Chexy?
💥 Build payments infrastructure that matters: Your code moves ~$2B a year for tens of thousands of Canadians
🤖 Work the way engineering works now: AI-native tooling, category-defining technology, and end-to-end ownership
💬 Join a tight-knit team: Work directly with the founders and CTO, who trust you to make real decisions
📈 Early equity: Access equity in a high-growth fintech
📍 Toronto office: We work in-office 5 days a week
How We Hire
We keep our hiring process clear and human. You'll go through a mix of conversational interviews and technical deep-dives designed to show how you think, how you've solved real problems, and how you work with others.
We use AI tools to help us organize and review applications; every decision about who we interview and who we hire is made by a person. This posting is for an existing vacancy. If you interview with us, we'll let you know within days of your last interview whether a decision has been made.
Chexy is an equal opportunity employer. If you require any accommodations or support during the hiring process, let us know and we'll do our best to help.
Know someone who would be a perfect fit? Let them know!
