Dot NET Full Stack AI-Native Applications Developer

Role & responsibilities

• C# on modern .NET (8 or later) with ASP.NET Core Web APIs. The RFP says new components should be modern .NET unless a documented constraint says otherwise, so this is the primary skill.

• Working comfort in legacy .NET Framework 4.x. The VAX booking engine mixes .NET Core and .NET Framework. Itinerary Builder and Smart Recommendations sit on booking-engine pages, so developers will need to read that code and make integration changes, even if new work stays on modern .NET.

• Azure application services: App Service or Container Apps, Functions, Azure Cache for Redis, Key Vault, and Azure SQL or Cosmos DB. The solution runs inside ALGV/Trisept’s hub-and-spoke Azure setup, so experience with private networking and managed identity helps.

• Strong TypeScript plus React

• Hands-on LLM application work: calling Azure OpenAI or similar, structured outputs, tool/function calling, and retrieval (RAG) with something like Azure AI Search. Each pod builds an agent (FindDeals, BuildItinerary, Recommend), so this isn’t optional.

• Unit and API testing as part of their own work, and CI/CD pipeline experience. Nice to have:

• Optimizely CMS development. The Deal Finder page lives on the Optimizely content site, so at least one or two developers in the Deal Finder pod should have it.

• Microsoft Agent Framework or Semantic Kernel (consistent with the Technical Architect JD).

• Embedding a shared UI component into multiple host applications (web components, micro-frontends).

• Accessibility (WCAG) implementation experience.