ServiceNow · San Diego, CA · posted yesterday
Applications are handled on ServiceNow’s own site. Fortune Vacancies does not collect applications and is not the employer.
Source: US DOL Office of Foreign Labor Certification, LCA disclosure data, FY2026 Q2. Government data is published roughly one quarter in arrears.
This advert was matched to Staff Software Engineer, a job title ServiceNow has itself sponsored.
About Veza Veza is the identity security platform for human, non-human, and AI agent access. Customers use it to see who and what has access to what, govern it, and remediate risk across cloud, SaaS, and on-prem systems. Agent security is the inflection point. Static access reviews can't keep up with autonomous agents acting at machine speed. Security is shifting to continuous, real-time control: just-in-time access for agents, automated remediation of policy violations, and real-time governance of agent actions as they happen—replacing standing privileges and periodic reviews. Veza is in transition, growing quickly as part of ServiceNow's Security & Risk organization. The Chief Architect will shape how the platform scales to meet this new category. What you'll do - Own the end-to-end architecture of the Veza platform , including the access graph, ingestion pipeline, authorization and policy engine, and the services built on them. Lead the evolution toward a graph-native data model (Neo4j or equivalent) that scales to billions of relationships and complex permission hierarchies. Set the standards every team builds to. - Lead the next-generation data architecture. Evolve the core graph and storage model for order-of-magnitude growth in customers, entities, and relationships, with a clear migration path from today's system and no customer disruption. - Define the architecture for non-human identity and AI agent security. Make Veza the system of record for what agents can access, and design for governance, guardrails, and auditability. - Set the AI architecture for Veza's own agents and features : agentic patterns, evaluation, observability, cost and capacity planning, and a multi-vendor LLM strategy that avoids lock-in. - Modernize the integrations framework. Veza has 300+ integrations, and they drive a disproportionate share of support load. Establish a scalable, testable, self-service framework that raises reliability and cuts onboarding time. - Architect how Veza fits into ServiceNow. Veza is not built on the ServiceNow platform. Define the integration model, shared identity and data contracts, and UI surfacing patterns that deliver a unified customer experience without forcing a rewrite. - Drive deployment flexibility : multi-region SaaS, data residency, regulated-industry requirements (e.g., EU financial regulation such as DORA), and federal-grade deployment, including the compliance and operational constraints each brings. - Govern architecture across teams. Run architecture reviews, manage tech debt and the security backlog, and make clear, documented build-vs-buy and sequencing decisions. - Raise the bar on engineering practice , including heavy use of AI coding agents, automated testing coverage, defect escape reduction, and operational excellence with SRE. - Represent Veza's architecture to executives, customers, partners, and ServiceNow architecture and security leadership. - Mentor architects and senior engineers and build the next layer of technical leadership.
What you bring Core - 15+ years in software engineering, with 5+ years as a staff/principal/chief architect, or equivalent, over a large multi-team platform. - Deep experience designing multi-tenant, cloud-native SaaS at enterprise scale: distributed systems, large-scale data and graph systems, APIs, and microservices. - Hands-on Kubernetes and cloud experience (AWS required; multi-cloud a plus) and modern DevOps, IaC, and SRE practices. - Strong background in graph databases and data structures. Hands-on experience with Neo4j, or similar graph platforms; understanding of immutable or event-sourced storage models and their operational trade-offs. - A track record of leading large architectural migrations in a live production system. - Experience influencing without direct authority across multiple teams and geographies (US, EU, India). - Executive-level communication, with the ability to write and defend an architecture decision to engineers, cu