Principal Systems Design Engineer

The role 

We are seeking a hands-on Principal Infrastructure Architect & Engineer to lead the technical integrations in the core infrastructure space.  

Our infrastructure environment spans networking, cloud, identity, and collaboration - and we're in the middle of integrating it all. We need someone who has done this before, knows where the landmines are, and can lead a program that involves a lot of teams who don't always agree. 

Day to day, that means owning the integration roadmap, running down dependencies, and doing real technical work in your strongest domains. You won't be the only engineer on any of this but you'll be the person everyone looks to when things get complicated. 

What you'll actually do 

Own the integration roadmap 

Not just write it - own it. That means knowing the dependencies, knowing which teams are behind, and being the person who drives things across the finish line. You'll work across networking, cloud, IAM, and collaboration simultaneously, so comfort with ambiguity and competing priorities is a given. 

Technical leadership across four domains 

We're not looking for someone who's equally deep in all four. We are looking for someone who is genuinely expert in two or three, and credible enough in the others to know when something's wrong and who to engage. 

Domain: The actual scope 

Networking 

Physical, wireless, SD-WAN, VPN, cloud networking. Consistent routing and segmentation across environments. You've done this at scale. 

Cloud & SRE 

Multi-cloud (AWS, Azure, GCP). IaC, CI/CD, observability, SLO/SLA design. You think in automation, not tickets. 

Identity & Access 

Okta, Entra ID, SSO, MFA, directory sync, RBAC, PAM. You understand why identity is where integrations break. 

Collaboration & Messaging 

O365, Gsuite, Slack, platform migrations. The technical side is straightforward - the hard part is the change management, and you know that. 

Security and compliance 

SOX, GDPR, NIST, HIPAA, FedRAMP, CMMC. You won't be running the compliance program, but you need to design for it and know when you're drifting out of bounds. That pattern recognition matters more than certification depth. 

Operational resilience 

HA and DR need to be in the design from day one, not retrofitted. You'll own the validation framework and run the DR testing program - not as a quarterly checkbox, but as a meaningful signal that the integration actually holds.

Department: Digital Technology
Function: Engineering
Experience Level: Not Applicable