Level

Cerebras

AI Inference Core - Technical Lead Manager, Release Qual & Integration

Cerebras is hiring an AI Inference Core - Technical Lead Manager, Release Qual & Integration in Sunnyvale, United States. Level rates it ; you can apply on Cerebras.

Level's read on this job

  • Builds AI ●●●● is how Level rates this role: the job is building AI systems.
  • Some of the work can be done remotely, according to the posting.
  • The posting mentions OpenAI and AI research among its tools and skills.
  • Level classes it as a lead role.
  • Cerebras has 120 other open roles on Level.

AI in this role

openai
ai-research

Cerebras Systems builds the world's largest AI chip, 56 times larger than GPUs. This architecture allows Cerebras to deliver industry-leading training and inference speeds; over 10 times faster than GPU-based hyperscale cloud inference services.

This order of magnitude increase in speed is transforming the user experience of AI applications, unlocking real-time iteration and increasing intelligence via additional agentic computation.

Cerebras works with the leading model labs, global enterprises, and cutting-edge AI-native startups. OpenAI recently announced a multi-year partnership with Cerebras, to deploy 750 megawatts of scale, transforming key workloads with ultra high-speed inference.

About the Role

We are looking for a hands-on Technical Lead Manager (Release Qual & Integration) to establish and lead Release Integration Testing within Release & Feature Qualification for AI Inference Core.

The Production Engine for Inference Core — turning integrated features into reliable production releases.

You will define the quality strategy across the pre-release and release cycle, from feature and model integration through branch stability, release qualification, deployment, and post-release learning. You will work across AI frameworks, runtime, compiler, kernels, distributed systems, infrastructure, and hardware to make release risk visible and actionable.

This is a technical-leadership role, not a coordination-only position. You will design test architecture, lead difficult debugging and release decisions, mentor engineers, and write software and automation alongside the team.

Release Integration Testing (RIT) is the bridge between feature qualification and release qualification. Feature teams retain ownership of feature design, feature-level qualification, and feature regression. Release Integration Testing owns inference-core integration strategy, inference-path readiness approval, integrated cross-stack validation, and first-pass rollout triage.

What Makes This Role Distinct

  • Dedicated Release Integration Testing ownership: Engage before feature qualification completes while keeping the boundary clear: feature teams own feature behavior and qualification; Release Integration Testing owns integration strategy, readiness approval, integrated validation, and first-pass rollout triage.

  • Inference-path readiness gate: Require evidence across unit, simulation, benchmark, feature, and integration testing, with explicit coverage gaps before release entry.

  • Cross-stack test strategy: Define risk-based E2E and regression coverage for features spanning components, organizations, software layers, infrastructure, and hardware.

  • Branch and rollout leadership: Establish measurable health standards for master and release branches, and coordinate inference-impacting rollout across multiple product and release projects.

  • Hands-on technical authority: Lead through code, test architecture, difficult debugging, quality metrics, and evidence-based release decisions.

  • Team multiplier: Raise the technical bar, mentor engineers, and align feature, infrastructure, integration, qualification, and release teams.

What You Will Do

  • Define the Release Integration Testing strategy, engagement criteria, ownership boundaries, entry and exit criteria, coverage expectations, and escalation thresholds for AI Inference Core.

  • Engage early on high-risk inference changes; identify dependencies and interaction risks across runtime, host, device programming, memory, scheduling, model execution, infrastructure, and hardware.

  • Own the inference-path readiness gate by reviewing unit, simulation, benchmark, feature-test, and integration evidence, documenting gaps, and approving integration readiness before release entry.

  • Lead integrated inference E2E validation across features and the cloud-to-wafer stack; promote durable feature tests and add risk-based scenarios to release regression.

  • Improve master and release-branch stability through actionable health metrics, failure classification, release-quality reporting, dashboards, qualification workflows, and release pipelines.

  • Lead first-pass regression and rollout triage, coordinate owners through resolution, drive RCA, place missing coverage at the correct layer, and plan rollout across multiple product and release projects.

  • Partner with and mentor SDETs, feature teams, Integration, Core Infra, release owners, and deployment teams; between active engagements, advance automation efficiency, diagnostics, probes, and roadmap test planning.

Minimum Skills & Qualifications

  • Strong software-engineering fundamentals and programming ability in Python Go, or a similar language.

  • Demonstrated technical leadership in software quality, test infrastructure, systems validation, release engineering, or complex software integration.

  • Experience designing automation and test architecture for distributed, systems-level, infrastructure, or AI software.

  • Proven ability to break down ambiguous cross-stack failures, form hypotheses, gather evidence, and drive issues to resolution.

  • Strong understanding of risk-based testing, release readiness, regression strategy, failure analysis, and quality metrics.

  • Ability to influence and align multiple engineering teams without relying solely on organizational authority.

  • Clear communication and sound judgment during high-pressure release situations, including the ability to explain technical risk to engineering and leadership audiences.

Preferred Skills

  • Experience with software/hardware co-design, hardware accelerators, compilers, kernels, runtimes, or low-level systems.

  • Experience with AI infrastructure, model deployment, LLMs, multimodal workloads, or large-scale compute clusters.

  • Experience building test frameworks, distributed test systems, release pipelines, dashboards, or internal developer tooling.

  • Experience with performance testing, profiling, observability, fault injection, reliability, or production failure analysis.

  • Experience managing geographically distributed teams across multiple regions and time zones is preferred

  • Experience in a startup or similarly fast-moving, resource-constrained engineering environment.

  • Track record of taking a quality or release capability from zero to one and scaling it across teams.

  • Familiarity with containers, cluster orchestration, cloud infrastructure, CI/CD, or high-performance computing.

What Success Looks Like

  • Release readiness is based on explicit criteria and high-signal evidence rather than intuition.

  • Fewer inference-path integration defects are first discovered in final release qualification or production.

  • Cross-component risks are found earlier, debug cycles are shorter, and coverage ownership is explicit.

  • Master and release-branch health is measurable, actionable, and steadily improving.

  • Test automation and release infrastructure shorten feedback loops without sacrificing signal quality.

  • Release metrics and reports drive clear decisions, ownership, and predictable feature rollout.

  • Engineers across the organization are more effective because Release Integration Testing provides strong technical direction, tooling, and mentorship.

Location

  • This role requires in-office presence, at least three days per week. Fully remote work is not available.

  • Office locations: Sunnyvale, CA or Toronto, ON.

Why Join Cerebras

People who are serious about software make their own hardware. At Cerebras, we have built a breakthrough architecture that is unlocking new opportunities for the AI industry. With dozens of model releases and rapid growth, we’ve reached an inflection point in our business. Members of our team tell us there are five main reasons they joined Cerebras:

  1. Build a breakthrough AI platform beyond the constraints of the GPU.

  2. Publish and open source their cutting-edge AI research.

  3. Work on one of the fastest AI supercomputers in the world.

  4. Enjoy job stability with startup vitality.

  5. Our simple, non-corporate work culture that respects individual beliefs.

Find out more about what it's like to work at Cerebras here!

Apply today and become part of the forefront of groundbreaking advancements in AI!

Cerebras Systems is committed to creating an equal and diverse environment and is proud to be an equal opportunity employer. We celebrate different backgrounds, perspectives, and skills. We believe inclusive teams build better products and companies. We try every day to build a work environment that empowers people to do their best work through continuous learning, growth and support of those around them.

This website or its third-party tools process personal data. For more details, click here to review our CCPA disclosure notice.

How we rate this

AI Inference Core - Technical Lead Manager, Release Qual & Integration at Cerebras rates 90 out of 100 for how much of the daily work is AI. That makes it Builds AI (AI Level 4 of 4). The level is about AI in the job, not seniority.

Classification

Builds AI. The job is building AI systems.

  1. ●●●● Builds AI80 to 100
  2. ●●●○ Works on AI60 to 79
  3. ●●○○ Uses AI40 to 59
  4. ●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.

Prepare for this job

Built from this posting and from similar jobs on Level.

Skills and AI tools this role asks for

AI ResearchOpenAI

Questions you could be asked

  1. Tell me about a research question you investigated. What did you find?
  2. Walk me through how you've used OpenAI in your day-to-day work.
  3. How would you decide a model or AI system is ready to ship?
  4. Tell me about a time a model underperformed in production. How did you find out, and what did you change?

Adapt your resume

  • List these exact terms on your resume: AI Research and OpenAI. An applicant tracking system matches the wording, not the idea.
  • Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
  • Lead with what you built, trained or shipped. This role is judged on the AI system itself, not the tools around it.

Want an expert to read your CV for this job?

Free. Send your CV and the role you want next. We reply by email within 2 to 4 business days.

Get new remote AI jobs (Builds AI ●●●●) by email

One email a week with the new remote AI jobs (Builds AI ●●●●), each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.

Free. One email a week. Unsubscribe in one click.

Similar roles

Other roles that build AI, at other companies.

What kind of AI work fits you?

Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.

Find my next step

More jobs at Cerebras

Related searches

Same AI level

Jobs by city