Web Developer jobs in Toronto, ON

About the role

We are building an end-to-end workflow platform for a healthcare consulting company operating serving various clinical and private sector organizations (e.g., insurers, government agencies etc). Target organizations are those where accuracy, auditability, and turnaround time directly affect outcomes.

We are looking for a senior engineer who is equally comfortable designing a relational data model and shipping the interface that sits on top of it. This is a build role, not a maintenance role: significant parts of the domain are still being designed, and you will have real influence over how they are modelled.

What you will work on

• Ship features end to end: async Python services (FastAPI, SQLModel, asyncpg) behind a React 18 + TypeScript front end, with clean, maintainable code and no hidden business logic in the UI layer.
• Own the data model: design PostgreSQL schemas for scheduling, case management, fee schedules, and billing; write and sequence Alembic migrations; keep the model coherent as the domain expands.
• Turn business rules into engineering specifications: translate clinical and external contractual rules into workflow state machines, eligibility logic, and SLA rules and document the tradeoffs you accepted.
• Run services in production on GCP: Cloud Run, Cloud SQL, Cloud Build, Artifact Registry, Secret Manager, Cloud Tasks, Cloud Scheduler and Cloud Storage.
• Integrate deeply with third-party platforms: identity and auth (Firebase Auth / Identity Platform, custom claims, MFA), mapping and routing APIs, transactional email, and document generation pipelines. We expect real depth here, not surface-level wiring.
• Build for a regulated environment: least-privilege IAM, audit logging, PHI handling, country data residency, and SOC 2–aligned change management are constraints on every design, not an afterthought.
• Raise engineering standards: code review, technical mentorship, and helping establish automated testing and release practices on a codebase that is still young enough to get them right.
• Debug and resolve production issues quickly and reduce the class of problem rather than the instance.
• Communicate clearly with non-technical stakeholders (operations staff, clinicians, and business leadership) and with external partners.

What we are looking for

• 3-5+ years building production web applications, including work as a senior or lead engineer.
• Process clarity from conflicting requirements: You can take a complex set of conflicting scenarios from internal and external stakeholders, find the rules underneath them, and derive a single clear business process that can be built, tested, and defended. You surface the conflicts explicitly rather than quietly picking a side.
• Python at depth: FastAPI strongly preferred; equivalent async experience (Starlette, Django, Flask) is fine. SQLAlchemy or SQLModel, and migration discipline with Alembic or similar.
• Strong relational data modelling: normalization, keys and constraints, indexing, and knowing when to denormalize. PostgreSQL experience specifically.
• Modern TypeScript front-end work: React 18, Vite, React Router, and comfort with genuinely complex UI state. Calendars, rich text editing, and dynamic form generation all feature here.
• Ground-up ownership: You have architected and delivered an application from an empty repository to production, and you have lived with the consequences.
• Cloud-native deployment: GCP preferred; AWS or Azure experience translates.
• Judgment about scope: You scope aggressively, ship a defensible v1, and document what you deliberately left out.
• Strong written communication and the ability to work across functions without a translator.

Preferred Qualifications

• Undergraduate or graduate degree in computer science or a directly related field.
• UI/UX sensibility, or experience building and maintaining a design system.
• Experience in a regulated or PHI-handling environment (PHIPA, HIPAA, or SOC 2).
• Experience with workflow engines, state machines or workforce scheduling systems.
• Experience in document generation, OCR, or applied LLM pipelines.

How we work

• Planning before implementation. Investigation and a written plan come first; code follows a confirmed approach.
• Phased delivery with explicit scope gates, documented v1 gaps and an actively maintained backlog.
• A bias against unnecessary complexity. We choose the simplest architecture that satisfies the query patterns and constraints in front of us, and we revisit it when the constraints change.
• Small team, high autonomy, direct access to the people who own the business problem.

Work Location: Hybrid remote in North York, ON M2N 5P6