Technical Lead - Architecture Focus, Full Stack

Responsibilities Define and evolve application architecture across a mixed .NET estate, from legacy .NET Framework 4 through to modern .NET) Set the modernisation roadmap, ensuring new work follows clean, sustainable patterns while legacy components are uplifted incrementally. Lead full-stack technical direction across backend, frontend and integration boundaries. Shape SPA/API integration patterns, ensuring frontend squads have well-designed, stable and versioned contracts to build against. Facilitate workshops with engineering squads, product owners, and customer stakeholders, and provide technical guidance through sprint reviews and release gates. Be the technical voice in customer-facing conversations — able to explain design decisions clearly and confidently to non-technical stakeholders. Requirements Deep, hands‑on experience with modern .NET and legacy .NET Framework in a commercial environment Strong full‑stack experience (Angular emphasis), with the ability to work effectively across backend, frontend and integration concerns. Good knowledge of a mainstream SPA framework (preferably Angular). You do not need to be a frontend specialist but must be able to work effectively with Angular squads, review component architecture, understand data‑binding patterns, and shape robust SPA/API integration patterns. Proven technical leadership across engineering teams, including mentoring, decision‑making and setting delivery standards. Azure‑based experience, including App Services, Azure Functions, API Management, Azure SQL, Service Bus, and related PaaS tooling. Solid grounding in web application security and secure API design. Strong client‑facing communication skills and ability to communicate with executives and other non‑technical stakeholders. Core Competencies Demonstrates expertise in modern and legacy .NET application architecture, with a strong emphasis on full‑stack development using Angular. Capable of leading technical direction, mentoring teams, and effectively communicating complex design decisions to non‑technical stakeholders. #J-18808-Ljbffr