Ph3Senior Azure .NET Architect – Role Specification /h3 h3Role Summary /h3 pWe are modernizing a mission‑critical communications layer responsible for routing messages and files between core systems and external parties. As a bSenior Azure .NET Architect /b, you will shape the technical design of a full rewrite of an existing application currently built using a mix of technologies including b.NET, IBM ACE, Service Fabric /b, and others. /p pThe target solution will be bcloud‑native, containerized, built in .NET, and hosted on Azure /b. You will design for bhigh resilience, performance, and scalability /b. /p h3Context /h3 pThe STP tribe operates messaging and group applications that ensure data, files, and messages are processed seamlessly end‑to‑end. This role directly contributes to that mission and supports the company’s strategic shift toward cloud adoption and scalable architectures. /p h3What You’ll Do /h3 ul lipDesign and deliver modern integration services to replace/upgrade the communications layer (message/file ingestion, transformation, routing, delivery; synchronous and asynchronous models). /p /li lipArchitect for resilience and scale using patterns such as bcircuit breaker, retries with backoff, timeouts, idempotency, outbox/inbox, DLQs, bulkheads, compensating transactions/sagas /b. /p /li lipDesign event‑driven systems using bAzure Service Bus/Event Hubs /b and/or bKafka‑style pub/sub /b, including contract definition, schema management, and backward‑compatible versioning. /p /li lipDesign high‑quality .NET services (b.NET 7/8, C#, ASP.NET Core, worker services, gRPC/REST /b) with TDD as a default practice and strong focus on code quality, security, and performance. /p /li lipArchitect workloads on bKubernetes (OpenShift/AKS) /b using Helm and Git‑based pipelines (Azure DevOps). Enforce enterprise container standards including image hardening and Kubernetes network policies. /p /li lipDefine observability: structured logging, tracing, metrics (App Insights/Splunk/OpenTelemetry), SLOs, error budgets, and actionable runbooks. /p /li lipCollaborate in an agile product setup (Scrum), contributing to backlog refinement, DoR/DoD, iterative delivery, and cross‑tribe ceremonies. /p /li lipLead and mentor: pair with, unblock, and coach junior developers; champion engineering best practices across the squad and Communities of Practice. /p /li /ul h3Minimum Qualifications /h3 ul lipb15+ years /b of professional software engineering experience, including b5+ years /b building mission‑critical or high‑throughput distributed systems (preferably in financial services or regulated environments). /p /li lipHands‑on Azure experience: bAKS, Functions, Service Bus/Event Hubs, Storage, Key Vault, Application Insights, Azure DevOps /b. /p /li lipExpert .NET engineer (C#, .NET, async/await, DI, testing frameworks). /p /li lipExperience with bDapr/KEDA, gRPC, API gateways /b. /p /li lipStrong containerization and orchestration experience: bDocker, Kubernetes (OpenShift/AKS), Helm /b, secure supply chain, image lifecycle. /p /li lipSolid understanding of event‑driven architecture: pub/sub, event streaming, consumer groups, schema evolution, exactly‑once/at‑least‑once trade‑offs. /p /li lipStrong TDD and automation mindset; CI/CD pipelines; trunk‑based development. /p /li lipProven resilience engineering knowledge (timeouts, retries, circuit breaker, backpressure, outbox/inbox, DLQ, bulkhead, saga). /p /li lipAbility to work autonomously, make sound architectural decisions, and mentor junior developers. /p /li lipProfessional English (written and spoken). /p /li /ul h3Nice to Have /h3 ul lipObservability stack experience: bOpenTelemetry, Splunk /b, distributed tracing; performance/load testing at message/file transfer scale. /p /li lipKnowledge of secure file exchange and enterprise integration patterns (SFTP/FTPS, AS2/AS4, MQ). /p /li lipFamiliarity with financial messaging standards and non‑functional controls (availability, integrity, confidentiality). /p /li /ul /p #J-18808-Ljbffr