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.

The Role 

TripArc is building an AI-powered vacations booking platform that will put 10,000+ pre-packaged, instantly bookable itineraries in the hands of North American travel advisors.

The work spans both greenfield and existing platform in equal measure. You'll be building new Angular MFEs, AI agent pipelines, and integrating with MongoDB-backed catalog infrastructure for the Vacations Platform, while extending and integrating with the mature ADX booking platform and the new Product Builder that sits alongside it. We need people who can hold both contexts without losing altitude. 

Whichever track you're in, you own your work end-to-end: design through deployment, in close collaboration with Product, QA, 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. 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.

What You'll Work On 

• Itinerary Catalog & AI Pipelines: Building the Chorus AI agent system — 8 agents across Generation and QA pipelines — that auto-generates, validates, and enriches itinerary content at scale. Backed by MongoDB that feed everything downstream. 
• Advisor-Facing MFEs: Search & Browse and Itinerary Detail experiences advisors use to find, evaluate, and customize pre-built trips. Includes the NL Search API connecting MongoDB to ADX or direct to Product Builder using MCPs — an open architectural decision spanning LLM query layers, Atlas vector search, and existing API patterns. 
• Trip & Bundle Workflows: Bundle Manager MFE and Make Bundle Payable microservice within TSP — turning an itinerary into a structured, transactable trip with embedded pricing and commission logic.
• Existing ADX Platform: You'll work within and extend the existing ADX platform: a mature .NET system that's the daily workhorse for the advisor network. Extending it, integrating with it, and improving it as you build the new layer on top. 

What We're Looking For
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, and you reduce handoff friction across a pod that spans MFEs, microservices, and AI pipelines.
• 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 

Must haves: 

• Angular + TypeScript, C# / .NET Core, DDD, CQRS, MongoDB, Postgres, RESTful APIs 
• MongoDB Atlas — schema design, aggregation pipelines, Atlas Search 
• RESTful API design, Azure Service Bus / NServiceBus 
• Docker-based local development, structured logging, distributed tracing, health checks, production debugging, Azure monitoring/App Insights, Auth0
• Event Sourcing with immutable event streams — comfortable designing systems where state is derived from an append-only event log, not stored directly
• CQRS — clear separation of write-side (command) and read-side (query) models, including schema-level separation
• Azure Service Bus messaging patterns at two levels: queues for intra-microservice cross-process messaging, topics for cross-microservice messaging

Nice to have:

• Vertical Slice Architecture — organizing code by use case rather than by technical layer
• Docker-based local development, structured logging, distributed tracing, health checks, production debugging, Azure monitoring/App Insights, Auth0
• Experience with an event-sourcing framework (Marten, EventStoreDB, Axon, or similar) or a message-bus framework (Wolverine, MassTransit, NServiceBus) is a strong plus

Our Tech

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

Why This Role 

The ADX Vacations Platform targets significant revenue in the form of gross bookings, and this pod is building the core of it. The decisions made now — how the NL Search API works, how the AI agent pipeline scales, how itineraries move from catalog to quote — will define the platform for years. You won't be inheriting someone else's design. You'll be making it. 

Compensation

We provide a competitive compensation package with a strong pay-for-performance rewards approach. Employees have the opportunity to participate in incentive programs and compensation tied to business and individual performance. The expected base compensation range for this position is: $115,000 to $125,000 CAD.

The actual compensation may vary depending on local market conditions, geography, and relevant job-related factors such as knowledge, skills, qualifications, experience, and education/training. #LI-Hybrid

We are committed to providing employment accommodation in accordance with the Ontario Human Rights Code and the Accessibility for Ontarians with Disabilities Act. If you require accommodation due to a disability at any stage of our hiring process, please advise us when completing your application.