Backend Developer

Verifran; Canada; Hybrid; CAD 100,000 - 150,000; Full time

Job summary

Verifran is seeking a back-end-focused software engineer to own the services behind the score, the assessment pipeline, and the consent rules that govern data visibility. You will shape the data model, implement domain logic, and ensure robust API contracts.

You will work in a fully remote environment, with four hours overlap with Eastern Time, and collaborate directly with end users to ship real privacy-preserving capabilities for franchise scoring.

Qualifications

• Strong Python, and opinions about where domain logic belongs.
• You have designed a data model that outlived its first three requirement changes.
• Comfortable with SQL as a place rules live, not just a place rows go.
• You test the rule, not the function — and you can tell the difference.
• You would rather delete a feature than carry one nobody uses.

Responsibilities

• Build and own services in the assessment, scoring, consent and matching domains.
• Design the rules that gate disclosure — who sees what, when, and on whose consent.
• Keep the API contract honest: typed schemas, regenerated clients, no silent drift.
• Write the tests that make a privacy rule impossible to break by accident.
• Work directly with the people using it, rather than through a tissue of tickets.

Skills

Python programming

API design

Domain modeling

SQL

Testing

Tools

FastAPI

Alembic

Pytest

Railway

SQL

Job description

Own the services behind the score: the assessment pipeline, the scoring engine, and the consent and disclosure rules that decide who is allowed to see whom.

TeamEngineering TypeFull-time LocationRemote — anywhere with 4 hours overlap with Eastern Time

Verifran turns a fifteen-minute conversation into a Franchise Readiness Score across nine weighted dimensions, then matches that franchisee against a brand’s own Franchise DNA. The backend is where all of that actually happens.

What you will do

• Build and own services in the assessment, scoring, consent and matching domains
• Design the rules that gate disclosure — who sees what, when, and on whose consent
• Keep the API contract honest: typed schemas, regenerated clients, no silent drift
• Write the tests that make a privacy rule impossible to break by accident
• Work directly with the people using it, rather than through a tissue of tickets

What we are looking for

• Strong Python, and opinions about where domain logic belongs
• You have designed a data model that outlived its first three requirement changes
• Comfortable with SQL as a place rules live, not just a place rows go
• You test the rule, not the function — and you can tell the difference
• You would rather delete a feature than carry one nobody uses

Nice to have

• Payments, KYC, credit or any other regulated data surface
• Experience with consent regimes — PIPEDA, CASL, GDPR
• You have worked somewhere small enough that you owned something end to end

The stack

• Python 3.12
• FastAPI
• Alembic
• Pytest
• Railway

Remote

This role is fully remote. We care about overlap, not postcode — four hours with Eastern Time is enough.

How we hire

A conversation, a piece of real work paid at our rate, and a call with the team you would join. No whiteboard puzzles, no unpaid take-homes.