ChromeOS Platform Engineer

Tenarai; New York (NY); On-site; USD 180,000 - 280,000; Full time

Job summary

Tenarai seeks an experienced kernel/firmware engineer to own platform defect resolution across kernel, drivers, and hardware integration for ChromeOS. You will sign off RCs, drive critical escalations, and lead lab validation with cross-team coordination in US hours.

Ideal candidates have 8+ years in kernel/firmware domains, upstream contributions, and direct ChromeOS experience. This onsite role in the United States expects collaboration with nearshore teams and client stakeholders.

Qualifications

• 8+ years of Linux kernel, device driver, or firmware engineering experience.
• Hands-on kernel debugging, crash-dump analysis, and board bring-up.
• Upstream contributions, patch review, or CVE/security backporting.
• Experience owning RC sign-off or go/no-go decisions for shipping hardware.
• Onsite in the US with core hours 09:00–18:00 EST.
• Experience evaluating AI-assisted classification tools for correctness.

Responsibilities

• Own root cause and fix authorship for P0/P1 and other escalated ChromeOS platform defects — kernel, drivers, firmware, and peripheral/hardware integration.
• Sign off release candidates against the agreed blocking criteria; target is 98% on-time RC sign-off.
• Own escalation for anything the Bug Triage & Diagnostics or Release & Sustaining engineers cannot close— the final technical decision-maker in the pod.
• Direct lab execution and hardware validation: physical device benches, flashing, peripheral compatibility, and multi-day stability runs.
• Independently verify any AI-assisted triage output that reaches platform-level severity — confirm the classifiers component assignment and verify evidence.
• Serve as the onsite technical point of contact for the client during core US hours — design reviews, escalation calls, and decisions that need deep architectural context.
• Mentor and direct the nearshore engineers on complex, cross-cutting cases.
• Participate in the daily triage stand-up, weekly release-readiness review, and quarterly efficiency verification.

Skills

Linux kernel

Device drivers

Firmware engineering

Kernel-level debugging

Crash-dump analysis

KASAN/KGDB tooling

Board bring-up

Upstream contributions

Patch review

CVE / security backporting

RC sign-off / go-no-go decisions

SLA escalation

Onsite collaboration

AI-assisted classification evaluation

Tools

KASAN KGDB tooling

ChromeOS source tooling

Job description

• 8+ years of professional experience in Linux kernel, device driver, or firmware engineering.
• Deep, hands-on experience with kernel-level debugging (crash-dump analysis, KASAN/KGDB-class tooling) and board bring-up.
• A track record of upstream or large-scale kernel contribution, patch review, or CVE / security backporting.
• Experience owning release-candidate sign-off or go/no-go decisions for a shipping hardware or platform product.
• Comfortable being the final technical escalation point under SLA pressure.
• Able to work onsite in the US, core hours 09:00–18:00 EST.
• Experience evaluating AI-assisted classification or drafting tools for correctness rather than accepting output at face value.

PREFERRED QUALIFICATIONS

• Direct ChromeOS / Chromium OS experience (source tree, board/overlay structure, public issue tracker conventions).
• Prior experience leading a distributed, follow-the-sun delivery team.

KEY RESPONSIBILITIES

• Own root cause and fix authorship for P0/P1 and other escalated ChromeOS platform defects — kernel, drivers, firmware, and peripheral/hardware integration.
• Sign off release candidates against the agreed blocking criteria; target is 98% on-time RC sign-off.
• Own escalation for anything the Bug Triage & Diagnostics or Release & Sustaining engineers cannot close alone— the final technical decision-maker in the pod.
• Direct lab execution and hardware validation: physical device benches, flashing, peripheral compatibility, and multi-day stability runs.
• Independently verify any AI-assisted triage output that reaches platform-level severity — confirm the classifiers component assignment where relevant, and never treat an automatically drafted root-cause hypothesis as final without checking it against the cited evidence.
• Serve as the onsite technical point of contact for the client during core US hours — design reviews, escalation calls, and decisions that need deep architectural context.
• Mentor and direct the nearshore engineers on complex, cross-cutting cases.
• Participate in the daily triage stand-up, weekly release-readiness review, and quarterly efficiency verification.