About the company
It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started.
Responsibilities
- 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.
- 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.
Requirements
- 12+ years in infrastructure architecture. You've worked through at least one complex integration or M&A - the kind where the org charts don't match, the documentation is wrong, and you had to figure it out anyway.
- You've led cross-functional technical programs where you had influence but not direct authority over most of the people doing the work.
- You can hold a detailed technical conversation with an engineer and a strategic conversation with an executive - without switching personas.
- You know the difference between a roadmap that's politically correct and one that's actually executable. You push for the latter.
- You've made calls under incomplete information and owned the outcomes.