Senior Release Infrastructure Architect

NVIDIA•Santa Clara, CA

About The Position

NVIDIA is seeking a Senior Release Infrastructure Architect to manage the architecture of its critical release management platform. Based in Santa Clara, California, the role will define the technical vision for modern infrastructure supporting multi-tenant, multi-environment systems across multiple hardware platforms. The architect will lead technical direction across engineering domains and collaborate with product, technical program management, release management, and other partners to align roadmaps, capacity, and operational ownership. The role encompasses full-stack platform architecture, including lifecycle and promotion workflows, ingestion and reconciliation pipelines, validation and release gating, authoring and production environment separation, APIs and security controls, frontend authoring and review experiences, and platform onboarding. It also includes setting deployment, rollout, migration, incident-response, and on-call practices; mentoring engineers; conducting architecture reviews; and continuously evaluating tools and patterns to improve the platform.

Requirements

BS, MS, PhD, or equivalent experience in Computer Science or a related field.
More than 12 years of hands-on software engineering experience.
At least 5 years in a senior technical leadership role.
Proven experience leading large-scale, multi-year, full-stack platform projects from inception to production.
Expertise in Python or a modern backend stack, with production-grade PostgreSQL experience and complex relational data modeling.
Strong frontend architecture skills with React, Angular, and TypeScript, and an interest in data-heavy user interfaces.
Demonstrated success designing and implementing state machines, workflow engines, or lifecycle systems.
Background in CI/CD orchestration, event-triggered integrations, and background-job systems.
Strong API development experience, including REST contracts, versioning, and automation-friendly interfaces.
Proficiency in Linux, containerization, and management of stateful production services.
Ability to lead through influence, drive architectural decisions across teams, and build consensus.
Excellent communication skills and the ability to translate complex business requirements into detailed technical solutions.

Nice To Haves

Experience architecting large-scale release engineering or configuration management platforms.
Background in event-driven architectures, microservices, or workflow orchestration engines.
Familiarity with regulated environments, audit trails, and customer-facing sanitized exports.
Knowledge of hardware and firmware release flows and board/SKU management.
Expertise integrating AI-assisted authoring, structured data extraction, or natural-language interfaces into engineering tools.

Responsibilities

Manage the architecture of a full-stack release management platform and advance it to support multi-tenant, multi-environment systems across multiple hardware platforms.
Design hierarchical domain models and state machines for complex lifecycles and multi-axis promotion flows.
Architect ingestion and reconciliation pipelines that maintain data fidelity and compliance across representations.
Define and integrate validation, promotion, and gating models with automated sanity stages and customer-release pipelines.
Establish separation between authoring and production environments to ensure data integrity and sanitization.
Set platform standards for API construction, authentication, role-based access control, audit logging, and observability.
Lead frontend architecture for authoring and review experiences, including complex tabular editing and bulk operations.
Drive platform onboarding workflows and define naming schemes, validation rules, and notification topologies for new hardware platforms.
Mentor engineers, conduct architecture reviews, and raise technical standards across engineering domains.
Partner with product, TPM, release managers, and other collaborators to align roadmaps, capacity, and operational ownership.
Define and manage deployment, rollout, and incident-response models, including database migration strategies and on-call runbooks.
Continuously evaluate and incorporate tools, frameworks, and patterns to improve platform capabilities.