Role Summary

The overall technical owner for the POD. end-to-end architecture across the Platform and Core Intelligence layers, define and follow integration with POD and central platform, make the cross-cutting decisions on orchestration, security, data and AI patterns that let the rest of the team move fast and independently.

Key Responsibilities

• Own the target architecture for the Orchestrator, Workflow Builder, Conduit and MCP / A2A components, and the Signal Engine, Action Engine, Librarian Agent and Ontology Graph.
• Define event-driven and workflow-orchestration patterns (Temporal, Azure Event Hub) and the service/API contracts between POD services and the central platform.
• Set the security architecture — identity (Auth0), secrets management (Azure Key Vault), service-to-service auth — in line with central platform standards.
• Establish the agentic-AI reference patterns (LangGraph, Azure AI Foundry, MCP / A2A, Graph Database retrieval) so the AI and backend engineers build consistently.
• Guard non-functional requirements: scalability, resilience, observability, cost, and independence from other PODs.
• Run design reviews, maintain architecture decision records, and act as the technical liaison to the central platform and the POD.

Must-have Skills & Technologies

• Distributed, microservices and event-driven architecture on Microsoft Azure (AKS, Event Hub, Key Vault).
• Workflow / orchestration engines — Temporal or equivalent (e.g. Cadence, Camunda) — and saga / long-running process patterns.
• API design (REST, async, webhooks) and integration patterns including MCP/A2P or comparable agent-to-agent / tool-calling protocols.
• Data architecture spanning lakehouse (Atlas Data Lake, Databricks), relational (Postgres, SQL), caching (Redis) and graph/ontology stores.
• AI/ML platform architecture — LLM orchestration, RAG, agentic frameworks (LangGraph), Azure AI Foundry. Security-by-design: identity, secrets, zero-trust service communication.

Prior Experience

• 10+ years in software engineering with 4+ years in an architect role on cloud-native platforms.
• Demonstrable ownership of a production distributed system on Azure at meaningful scale.
• Experience architecting AI or data-intensive platforms is strongly preferred.

Nice to Have

• Logistics / supply-chain domain exposure.
• Team Topologies / platform-engineering operating models; experience defining paved road contracts between central and stream-aligned teams.