Member of Technical Staff, Release Ops/Production Engineering Lead

 

THE ROLE

We are seeking a highly technical Lead Release Engineer with a strong engineering foundation to lead the end-to-end release lifecycle of our storage products. You will serve as the bridge between Development, QA, and Product Management — ensuring that complex storage stacks are delivered with high quality and predictable cadences.

Unlike traditional project-based release management, this role demands deep hands-on expertise across CI/CD orchestration, codeline management, system-level triaging, fleet operations, and the engineering rigor required for data-critical products. You will own the health of our release pipelines, lead triage war rooms, drive automation initiatives, and participate in on-call rotations to keep CI and test-orchestration infrastructure running reliably. You will also build developer-facing tooling, manage HW test fleet operations, and maintain high-quality integration workflows across our codelines.

WHAT YOU'LL DO

• Release Orchestration: Own the end-to-end release process for storage software and firmware, from development to GA (General Availability).
• CI/CD Leadership: Design and build optimized pipelines and tools to scale code management and merge operations. Work closely with systems such as Jenkins, test frameworks, Premerge, Orchestrator, and related developer productivity tooling to keep the codeline healthy and actionable.
• Technical Triaging: Act as the primary technical point of contact during the "war room" phases of a release. You must be able to understand bug reports, analyze logs, and work with engineers to prioritize fixes based on product impact.
• Quality Governance: Lead or contribute to cross-functional projects with engineering teams and TPMs to improve CI and release quality, developer experience, and overall reliability. Partner with product and infrastructure teams to find issues earlier in the pipeline, improve signal quality, and reduce manual toil in triage and merge operations.
• SDLC Optimization: Continuously improve the SDLC by identifying bottlenecks in the build-test-deploy loop and implementing automated gates.
• Stakeholder Management: Communicate release status, risks, and trade-offs to executive leadership, ensuring transparency across the organization.
• Fleet Management: Improve the health, automation, and operational efficiency of HW test fleets that support CI and merge workflows.
• Operation support: Participate in on-call duty rotations for CI and test-orchestration infrastructure; lead incident triage and mitigation, bring order to chaos, and ensure thorough follow-through on root-cause fixes.
• Automation: Build easy-to-use tools that help developers diagnose failures in test and infrastructure systems. Own and improve automation, workflows, and quality gates around git collaboration and code integration across FA and FB codelines.

WHAT YOU BRING

Required Technical Skills

• Engineering Background: 8+ years in software engineering or DevOps, with at least 3-5 years specifically in a Release Management or Lead Capacity.
• CI/CD Mastery: Expert knowledge of orchestration tools (Jenkins, GitLab CI, or GitHub Actions) and infrastructure-as-code (Terraform, Ansible).
• Systems Thinking: Deep understanding of the full SDLC, including branching strategies (Gitflow/Trunk-based development) and versioning.
• Scripting/Automation: Proficiency in Python, Bash, or Go for automating release tasks and data analysis.
• Branching/Codeline management: Strong git and codeline intuition, with an appreciation for merge quality, guardrails, and release-safe integration workflows.

Technical Triaging & Problem Solving
In this role, triaging is not just about moving tickets; it is about deep-system forensics. You will lead the "Bug Council" and must possess:

• Root Cause Analysis (RCA): Ability to analyze system logs, kernel dumps, and performance traces to distinguish between software regressions, hardware failures, and environmental bottlenecks.
• Prioritization Matrix: Skilled at balancing "Criticality vs. Risk"—determining when a bug is a "release blocker" (e.g., data corruption, silent data loss) versus a "deferrable issue" (e.g., edge-case UI glitch).
• Cross-Functional Mediation: Acting as the "technical judge" between QA (who finds the bugs) and Dev (who fixes them), ensuring that the most impactful issues are addressed first under tight deadlines.
• Incident Management: Experience leading "War Rooms" for high-severity issues found late in the release cycle, providing clear technical status updates to stakeholders.

Soft Skills & Leadership
Risk Mitigation: The ability to stay calm under pressure and make data-driven "Go/No-Go" decisions.

#LI-ONSITE 

#LI-KT7