About this role
About the Role The Systems Engineer, Architecture owns the long-term design of Shield's internal technology environment. Where day-to-day operations keep systems running, this role decides what those systems should look like in two to five years and defines the standards, roadmap, and reference designs to get there. You will own the architecture of our core platforms, including Microsoft 365, Entra ID, Intune, Azure, and our SaaS ecosystem, and ensure that every new tool, integration, and acquired environment fits a coherent, secure, and scalable design. Architecture Ownership: Define and maintain the target-state architecture for Shield's internal systems, including identity, endpoint, collaboration, and cloud platforms. Maintain the technology roadmap and sequence changes to get from current state to target state. Standards and Governance: Author and enforce technical standards for configuration, security baselines, naming, tenancy, and integration patterns. Serve as the design authority for new tooling and platform changes. Identity and Access Design: Own the identity architecture across Entra ID and connected SaaS, including SSO, SCIM provisioning, conditional access, and privileged access models. Design for scale as new entities and users are added. Integration Architecture: Design how internal business systems connect, including HRIS-driven provisioning, PSA and ticketing platforms, and automation flows. Set the patterns that engineers implement. M&A Integration Design: Assess acquired companies' technology stacks, define migration and consolidation plans for tenants, identity, and endpoints, and establish repeatable integration playbooks. Platform Lifecycle Planning: Evaluate emerging platforms and plan the retirement and replacement of legacy systems. Lead proofs of concept and produce decision records with clear rationale and tradeoffs. Security Architecture: Partner with IT security to embed Zero Trust principles, device compliance, encryption, MFA, and EDR coverage into platform design rather than bolting them on afterward. Documentation: Maintain architecture diagrams, design standards, and decision records so the environment is understandable and supportable by the broader IS&T team.