Senior Backend Developer

The short version

You build and run the backend services that move money to more than 100 countries. Node.js and TypeScript or Python — either is fine, we care about the depth, not the language. Postgres or MySQL, REST and GraphQL. You'll work onsite in a small agile team alongside QA, DevOps and the founders, which means you're in the room when requirements get decided rather than receiving them as tickets.

The thing that makes this different from most backend work: correctness has consequences you can name. A failed transfer isn't a degraded user experience, it's someone's rent landing late in another country. That shapes how we test and how we deploy.

You should also know that not all of this is greenfield. Part of the job is redesigning legacy systems that are still sitting in the live path — untangling code that predates the current architecture while it keeps running. If that's the part of engineering you find satisfying, this role has a lot of it. If it's the part you'd rather avoid, this isn't the right fit.

What you'll own

The services behind money movement.

Designing and building new ones, and rewriting the legacy pieces still carrying production traffic. You'll research the business need, weigh the options, and recommend the design — not just implement someone else's.

The full lifecycle of what you ship.

Analysis, design, build, test, release, and support afterward. You own your code in production.

Test coverage and documentation, as part of the work.

Not a phase at the end, and not something QA inherits from you.

What success looks like six months in

• Owning at least one core service end to end, with the team routing questions about it to you
• One legacy system migrated off, with no incidents attributable to the cutover
• Your services covered by tests that run in CI, and you trust them enough to deploy on a Friday

You must have these three things — it's what we screen on

Three-plus years building production backend services in Node.js and TypeScript, or in Python.

Either is fine — we're hiring for judgement about systems, not for a syntax. You'll walk us through one you owned: what it did, what you chose, and what you'd change now.

Relational databases at depth — PostgreSQL or MySQL, either is fine.

Not just writing queries. Bring an example of a schema or query you had to fix under real load, and what the symptom was before you found it.

APIs other teams depend on — REST or GraphQL.

You've shipped one, versioned it, and dealt with the consequences of a breaking change.

Nice to have, not required

An ORM you've used seriously — Sequelize, SQLAlchemy, Django ORM or similar; open-source contributions; experience mentoring or leading other engineers; fintech, payments, or any regulated-money environment.

You don't need

Front-end or mobile development, infrastructure and deployment pipelines, or design. We have DevOps, QA and design covered.

What it's actually like here

Remitbee is a Canadian fintech moving money to over 100 countries, alongside currency exchange, bill payments and digital wallets. Hierarchy isn't a barrier to being heard here — if you have a point and the data behind it, you take it to senior leadership directly, regardless of tenure. And we take the whole team on a trip every quarter.

Curious what that looks like day to day? Watch our team here: https://www.youtube.com/watch?v=yZzLcWqUWYY

Compensation and benefits

$60,000–$90,000, health insurance, Career Development Policy, Self Development Policy, and a quarterly team trip.