jobapplier

Sr. Software Developer - Full-Stack

Range

Skills

Required

  • microservice
  • MFE
  • AI
  • Microservices
  • Angular
  • .NET
  • refunds
  • PostgreSQL
  • deposits
  • reconciliation
  • JIRA
  • C# / .NET Core
  • retries
  • payment lifecycle
  • TypeScript

Preferred

  • invoicing
  • billing
  • DDD
  • AI coding tools
  • GitHub
  • Copilot
  • Claude
  • Cursor
  • Domain Driven Design

TripArc's travel booking platforms are used every day by thousands of travel professionals to plan, price, book, and manage trips for their clients. We're re-envisioning them as a single AI-powered platform.

We're hiring a Sr. Software Developer for Trip Management, which covers everything after a client says yes. You'll help build our new payments, booking, invoicing, and accounting systems, along with the advisor-facing trip dashboard and trip detail experiences on top of them. Because these systems are new, we don't have to copy how travel payments have always worked.

About Range

Range Group we believe in the power of the professional travel advisor.

We represent over $4.5 billion in annual travel sales.

All our investments stem from a common thesis, that travel advisors add real value to a trip.

Travel advisors when equipped with technology and 24/7 support are irreplaceable.

Equally important is our philanthropy.

Range Foundation channels 10% of group profits to social impact.

From exploration grants, improved access to education, new discoveries on sea and land, cultural infrastructure, and helping our global neighbors in times of need — we are investing to build a better future.

Responsibilities

  • The work spans greenfield and existing platform in equal measure: new VESA microservices and Angular MFEs, plus extending and integrating with the mature ADX booking platform while trips and travel professionals move off the legacy system.
  • You'll know payments well enough to tell where the numbers have to be exact, and you'll help decide where AI belongs in the product.
  • You own your work end to end: design through deployment, in close collaboration with Product, QA, UX, and your pod.

How We Build

  • We expect every developer on this team to use AI coding tools (GitHub Copilot, Claude, Cursor, whatever fits your flow) as a standard part of how you develop. Not as an experiment, and not as a replacement for engineering judgment. We move faster because of these tools, and we ship with confidence because of the quality gates, code review culture, and testing discipline that sit alongside them. In a money flow, that discipline matters even more. If you've figured out how to get real leverage from AI-assisted development without cutting corners on quality, you'll fit right in here.
  • Payments: How money moves once a client says yes: deposits, final payments, refunds, credits, and multiple currencies, built on the Trip Payment microservice.
  • Booking & Invoicing: Booking gateway workflows that decide when a service is ready to book, plus the generation of client invoices, commission statements and supporting documents.
  • Ledger & Accounting: Ledger services and the integrations that support reconciliation, statements, refunds and audit needs for Finance, Accounting and 24/7 support. Amounts and ledger entries must stay exact and auditable.
  • Trip Dashboard & Trip Details: Read models that listen to events from shopping, booking, payment, and other upstream services and power the advisor-facing dashboard and trip views. Actions are routed to the right service or MFE through routing keys.
  • Legacy Migration: Extending and integrating with the mature ADX .NET platform, the daily workhorse for the advisor network, and helping move in-progress trips and travel professionals off the legacy system while it stays live.
  • Domain Driven Design (DDD)

Requirements

  • We need people who can hold both contexts without losing altitude.
  • You move across the stack without losing altitude: Angular MFE one moment, .NET microservice the next, event-sourced aggregate after that.
  • Our microservices follow a Vertical Event Sourcing Architecture (VESA): DDD bounded contexts, CQRS split by responsibility, and Postgres-backed event streams via Marten and Wolverine. You're comfortable thinking in events and streams, not just CRUD.
  • You design for correctness in financial flows: idempotency, retries, ordering, eventual consistency, and audit trails.
  • You understand the payment lifecycle (authorization, capture, deposits, refunds, chargebacks, reconciliation), or you learn quickly and ask the right questions.
  • You reduce handoff friction across a pod that spans MFEs, microservices, and integrations with other teams.
  • AI tooling is a first-class part of how you work. You have a workflow, not a dabbling habit.
  • You write documentation worth reading and JIRA tickets worth inheriting.
  • You own your sprint commitments and push back when timelines don't make sense.
  • You make the people around you better through reviews, pairing, and knowledge sharing.
  • Angular + TypeScript
  • C# / .NET Core
  • PostgreSQL
  • RESTful APIs
  • Microservices
  • Distributed tracing
  • AI-assisted development

Preferred

  • Experience building payments, billing, invoicing, or other financial-transaction systems
  • Payment provider integrations
  • Travel industry experience
  • Experience replacing a legacy system while it stays live

Pay

We provide a competitive compensation package with a strong pay-for-performance rewards approach. Employees have the oppo

This is a hybrid position, currently requiring a minimum of two days per week onsite at our office located at 2 Queen St. E in Toronto, ON.

Docker

Azure Service Bus

Command Query Responsibility Segregation (CQRS)

Event Sourcing

Vertical Slice Architecture

App Insights

Auth0

Our Tech

Azure Cloud · .NET Core microservices · Angular MFEs · React · Next.js · MongoDB Atlas · PostgreSQL · SQL Server · NServiceBus · Redis · GraphQL · Azure Service Bus · RabbitMQ · Docker / Kubernetes · Azure Pipelines · Cloudinary · Contentful · Figma · JIRA · Confluence

Why This Role

Everything after "yes" is where a booking becomes revenue, and this pod is building the core of it. The decisions made now, such as how money moves, how bookings are confirmed, and how trips are tracked and reconciled, will define the platform for years. You won't be inheriting someone else's design. You'll be making it.