Job Description & Details
This is a heavy-hitting Enterprise Architect role where you'll spend your days wrangling legacy systems, modernizing applications, and steering cloud migrations on Azure. If you enjoy playing the bridge between high-level business leadership and deeply technical engineering teams without getting bogged down in endless bureaucracy, this one actually gives you some room to drive real change.
What You'll Actually Be Doing
You'll be knee-deep in designing target-state architectures and building out solution roadmaps that make sense for both the business and the developers writing the code. Day-to-day involves running architecture reviews, evaluating new tech, and figuring out how to stitch together cloud, on-prem, SaaS, and legacy systems without breaking production. Expect to spend a solid chunk of your time leading cross-functional teams—dev, QA, and DevOps—while also translating complex technical decisions into plain English for stakeholders and leadership.
The Core Tech Stack
You need to know Microsoft Azure inside and out, specifically Azure Kubernetes Service (AKS) and cloud-native patterns, because that's where everything lives. On the engineering side, you'll be dealing with .NET Core, Angular, microservices, and distributed systems, so you should understand how these components interact at scale. API management, event-driven architectures, PostgreSQL, and Azure DevOps round out the heavy hitters, alongside Microsoft Entra ID for identity management and Application Insights for keeping tabs on system health.
Interview Expectations
They are definitely going to probe your ability to balance technical purity with pragmatic delivery by asking how you handle migrating a heavily coupled legacy monolith into a microservices architecture on AKS without taking the whole system offline. When they hit you with that, the hiring manager isn't just looking for a textbook cloud pattern; they want to hear about your battle scars, how you handled team pushback, and how you mitigated risks around data consistency. You'll also likely get grilled on API-led integration strategies where they want to see if you can design scalable, event-driven pipelines that won't choke under peak enterprise loads.
Application Advice
Your resume needs to scream enterprise modernization and Azure governance right at the top, or the ATS will filter you out before a human ever looks at it. Make sure keywords like "Enterprise Architecture", "Azure Kubernetes Service", "microservices", and "Infrastructure as Code" are explicitly highlighted with quantifiable outcomes attached to them—don't just list technologies, explain the scale of the cloud environments you've designed and the distributed systems you've successfully delivered.