Application Support Developer

We're looking for an Application Support Developer to join the TMT Technology team at TripArc. You'll split your time roughly equally between client-facing support and software development — and both halves demand strong coding ability. Understanding our application code isn't a nice-to-have; it's the prerequisite to solving most support problems.

Tickets arrive in Helpspot, often partially described. You'll trace through our TMT platform's .NET code and stored procedures, figure out what the correct data state should be based on application logic, and apply a fix in code, in the database, or both. You'll also monitor lower and production environments, catching issues before clients report them. Weekend on-call is part of the rotation when production needs a fast response.

• →Triage and resolve Helpspot tickets across our TMT Tour Operator platform — tracing through application code and stored procedures, identifying root causes, and applying targeted fixes in code or data with a rollback strategy considered before anything touches production.
• →Monitor lower and production environments proactively, catching and resolving anomalies before they become client escalations.
• →Build and maintain third-party integrations and data pipelines — including Azure Data Factory workflows that move data between internal databases, travel suppliers, and reporting layers.
• →Decompose legacy .NET Framework and Web Forms code into focused .NET Core microservices, deployed via Azure Pipelines onto Kubernetes.
• →Write and tune T-SQL: complex queries, stored procedures, and safe emergency data fixes — transaction isolation and rollback strategy first.
• →Build event-driven integrations using NServiceBus and Azure Service Bus to keep services loosely coupled.
• →Lead post-incident reviews that produce runbooks, code fixes, or monitoring improvements — not just incident records. Mentor junior and intermediate developers on debugging approaches and safe database practices.
• →Collaborate with Product, QA, and Business Analysts to scope and deliver build work within two-week sprints, while staying responsive to support obligations.

Must have

• 3 to 5 years with C# and the .NET ecosystem — hands-on in both .NET Framework (including Web Forms) and modern .NET (8/9). You can navigate an unfamiliar codebase to trace a bug, not just write greenfield code.
• SQL Server — comfortable querying and patching data, and knowing when each fits.
• Experience as a systems analyst or application support role, or similar.

Nice to have

• HubSpot integration experience — CRM, Custom Objects, Workflows, Webhooks, or two-way data syncs with .NET services. Broader CRM or SaaS API integration experience is equally welcome.
• Azure Data Factory, Azure Monitor, and Application Insights.
• MongoDB and T-SQL, Microservices patterns, NServiceBus, and/or Azure Service Bus for event-driven architectures, Docker, and Kubernetes
• Angular exposure — support issues occasionally pull you into the front end, but this is primarily a backend role.

• You are comfortable reading code you did not write. Whether it's a stored procedure from 2014 or a service you've never seen, you can orient yourself and figure out what's happening. That's a core requirement here.
• You're patient with messy problems — you can sit with ambiguity, gather evidence methodically, and form a hypothesis before reaching for a fix.
• You take ownership of incidents end-to-end: investigation, fix, verification, and the follow-up that prevents the same issue from recurring.
• You balance "fix it now" urgency with "fix it properly" engineering instincts — and you know which mode the moment calls for.
• You mentor without being asked, and you write documentation you'd actually want to read.

Our platform runs on Azure Cloud, and we're actively modernizing. Here's what you'll work with:

• Backend: Modern .NET (8/9) microservices alongside legacy .NET Framework and Web Forms applications. Internal libraries built on top of the framework. Entity Framework for data access.
• Integrations: Third-party travel supplier APIs and CRM platforms including HubSpot (Custom Objects, Workflows, Webhooks).
• Data Platform: Azure Data Factory, SQL Server (complex schemas, heavy stored procedure use), MongoDB for document storage, Redis for caching.
• Messaging: NServiceBus and Azure Service Bus for event-driven communication.
• Infrastructure: Docker on Kubernetes, deployed via Azure Pipelines. Git for source control.
• Frontend: Angular with Angular Material (where support pulls you in), plus legacy .NET Web Forms.
• Support & Monitoring: Helpspot for client ticketing, Azure Monitor and Application Insights for observability across environments.
• Tools: JIRA and Confluence for tracking and documentation. GitHub Copilot for AI-assisted development. VS 2022, VS Code, or Rider — your choice.

You'll build a deep, cross-cutting understanding of how our TMT platform actually works — the business logic in legacy code, how data flows between services, and exactly where things break under pressure. That knowledge is genuinely valuable: it gives you real influence over how the platform evolves, because you've spent time at the seams. The support work keeps you close to how the platform is actually used; the build work lets you fix it properly. At a senior level, your impact extends beyond what you personally resolve — the runbooks you write and the developers you mentor shape how the whole team handles hard problems.

Who will thrive

• People who like puzzles — especially ones that span multiple systems, code layers, and databases.
• Developers who'd rather investigate than escalate, and who find that detective work energizing.
• Those who are as comfortable in a legacy codebase as in a greenfield service, and don't complain about the difference.
• Team players who share what they learn, especially after a tough incident.
• People are comfortable with a dynamic environment where the next priority might come from a production alert.

Our team is made up of people who are smart, low ego, and accountable for their results. If you want to own real production systems, do meaningful integration work, and help shape how a platform modernizes, we'd like to hear from you.