ServiceNow: Principal Software Engineer - Veza — San Diego, CALIFORNIA, United States

About ServiceNow

ServiceNow develops an enterprise software platform bringing together data, workflows and AI for business operations. Its employer introduction traces the business to automating a repetitive workplace task and describes a continuing focus on freeing people from routine work. The platform is intended to connect technology with how organisations carry out their processes. This makes workflow automation and the use of information in everyday business activity central themes, rather than a product aimed at only one industry.

The position and its setting

ServiceNow lists Principal Software Engineer - Veza in San Diego, CALIFORNIA, United States, under reference JB0076129. The details below separate the work described by the employer from essential conditions, preferred experience and practical preparation advice.

• Department: Engineering, Infrastructure and Operations
• Employment type: Full-time
• Employer listing date: 22 October 2026
• Brands: ServiceNow

Responsibilities and work described

• Identity
• Own the identity model for workloads and agents: SPIFFE/SPIRE trust domains, workload attestation, and how identities are issued, scoped, rotated, and revoked
• Architecture: ephemeral authentication and authorization end to end: short-lived credential issuance, token exchange and delegation (for example RFC 8693-style flows), and revocation that takes effect in practice
• Define runtime authorization for agents: what an agent can access, under whose delegated authority, with what guardrails, and with audit trails that hold up to review
• Leadership: the identity architecture for the Agent Security roadmap, including Runtime Authorization, the Access Policy Engine, and AgentID with short-lived credentials, and its integration with the NHI program
• Set the identity standards for non-human identities across Veza’s integrations, covering how connectors authenticate, get scoped, and rotate secrets
• Core architecture
• Define identity contracts that the graph, data model, and integrations architects build against, and review designs in those areas for identity correctness
• Shape how identity fits into the Veza-ServiceNow integration model, including shared identity and data contracts and UI surfacing patterns
• Partner with the integrations, graph, and deployment owners on decisions that touch identity, without taking over their domains
• Leadership
• Represent Veza’s identity architecture to customers, partners, ServiceNow Security leadership, and standards bodies
• Mentor engineers

Essential requirements and candidate background

• 12+ years in security or identity engineering, with a substantial share spent designing identity systems in production at scale
• Background in identity and access: IGA, IAM, PAM, authorization models, access reviews, lifecycle management, or adjacent security domains
• Deep hands-on expertise in workload identity, specifically SPIFFE/SPIRE or an equivalent, and in ephemeral credential design
• You can explain trust bootstrapping and rotation failure modes without notes
• Grounding in OAuth 2.x, OIDC, token exchange, and authorization models (RBAC, ABAC, ReBAC, and policy engines such as OPA or Cedar)
• Understanding: non-human identity (service accounts, secrets, API keys, workload identity) and emerging agent identity and authorization models
• Experience building security products that meet their own security and compliance bar (SOC 2, FedRAMP or equivalent, data residency)
• Experience delivering production AI or agentic systems, including evaluation, guardrails, and human-in-the-loop controls
• Active use of AI-native development tools (Claude Code, Cursor, Codex, or equivalent)
• Python or Go, with the ability to go deep in code and design reviews
• Executive-level communication, with the ability to defend an identity decision to engineers, customers, and security leadership
• Breadth to hold your own on graph data models, integration architecture, and multi-region deployment, even if you don’t own them
• Experience through an acquisition or platform integration, aligning an acquired architecture with a parent platform
• Experience: integration-heavy platforms and the authentication and secrets challenges they bring
• Familiarity: graph databases or immutable or event-sourced storage models
• Authored or shaped identity standards or RFCs
• Built or operated a production credential broker or identity provider
• BS/MS in Computer Science or a related field, or equivalent experience
• Success in the first 12 months
• A published identity architecture for workload and agent access, with committed milestones

Preferred experience and additional strengths

• Preferred

Location, schedule and contract conditions

For this overseas or regional listing, confirm work authorisation and any location restrictions with the employer. The location does not establish visa sponsorship or permission to work remotely from India.

• Work arrangement: On-site
• Advertised location: San Diego, CALIFORNIA, United States

Employer details to confirm

• The employer’s seniority category and its stated experience requirements do not agree. Follow the role-specific requirements above rather than assuming this is a fresher opening.

Pay and application dates

A verified salary figure is not established in this article. An online estimate for another Principal Software Engineer - Veza vacancy is not an offer for reference JB0076129; use the employer’s own pay disclosure and recruitment communication.

A closing date is not confirmed in this article. Check the current employer page before submitting: an undated posting can change or be withdrawn.

How to apply to ServiceNow

Applications follow the official employer page linked below.

Open the official ServiceNow posting below and match the title and reference JB0076129.

Compare your qualifications and experience with the essential conditions for the San Diego, CALIFORNIA, United States position, then read the preferred criteria separately.

Prepare an accurate CV and the supporting items requested in that employer’s application. Provide only information and documents you are authorised to share.

Use the employer’s application option, complete the required fields and review the submission. Retain the acknowledgement when one is provided. Job Alerts World does not receive the application.

Practical preparation: Python

Python work is easier to assess through a concrete example than a list of libraries. Explain the problem, the input data, the parts you implemented and how you checked the output. Include a repository or a short technical note when you can share it.

Relevant skills

• Python
• APIs
• AI/ML
• ServiceNow
• audit
• AI
• compliance
• sales
• communication