If you thrive in dynamic environments, love solving complex challenges, and want to make an impact with cutting-edge technology, we’d love to hear from you!
You spend your day turning messy, cross-functional problems into structured insights and scalable fixes—so the product works reliably at scale.
Morning: Data, Triage, and Alignment
You usually start by reviewing dashboards and overnight reports:
•
Fleet health metrics (uptime, failure rates, MTBF/MTTR)
•
Manufacturing yield and defect paretos from the previous build
•
Any critical field escalations or production line stops
If something is off—say a spike in failures in a subsystem—you’ll quickly prioritize it for deeper investigation.
From there, you jump into a cross-functional stand-up with hardware, software, manufacturing, and operations:
•
Align on top quality risks across EVT/DVT/PVT or production builds
•
Review open issues, owners, and timelines
•
Decide where escalation or additional resources are needed
You’re setting the tone: what matters today, and what cannot slip.
Mid-Morning: Deep Dive on Issues
This is where you spend focused time on root cause analysis.
•
A recurring field failure in the robotic fleet → you’re reviewing logs, diagnostic data, and failure modes with the firmware and systems teams
•
A yield drop at a contract manufacturer → digging into process changes, supplier variation, or test coverage gaps
•
A reliability test failure → working with engineering to understand whether it’s a design limitation or test artifact
You’re not just asking “what failed”—you’re pushing toward:
•
Root cause clarity (not symptoms)
•
Containment actions (what do we do now?)
•
Permanent fixes (design, process, or supplier changes)
Midday: Factory / Lab / Field Interface
Depending on the phase of the program, this block varies:
•
**During NPI builds (EVT/DVT/PVT):**You’re on the line (physically or virtually), reviewing:
•
Assembly issues (DFA gaps)
•
Test coverage and escapes
•
•
Reviewing IQC/IPQC/OQC trends
•
Syncing with supplier quality teams on incoming defects
•
Auditing process controls and corrective actions
•
•
Meeting with field ops on triage trends
•
Reviewing top downtime drivers
•
Prioritizing fixes that impact uptime and serviceability
Afternoon: Systems, Process, and Scaling
This is where you zoom out from individual issues to system-level improvements.
•
Building or refining quality dashboards and KPIs
•
Defining new quality gates for upcoming builds or releases
•
Improving diagnostic frameworks so failures are easier to detect and classify
•
Working on automated test strategies (production or validation)
This is also where AI and tooling come in:
•
Setting up automated anomaly detection on fleet or manufacturing data
•
Streamlining how issues are categorized and routed
•
Reducing manual triage work through smarter workflows
The goal: make the system smarter so the same problems don’t repeat.
Late Afternoon: Cross-Functional Reviews & Decisions
You’ll often close the day in decision-making forums:
•
Design reviews (pushing for DFM/DFA improvements)
•
Quality reviews with leadership (status, risks, mitigation plans)
•
Supplier calls for escalations or performance management
This is where you influence:
•
Whether a build proceeds or is gated
•
Whether a design is ready for the next phase
•
Where the team invests time and resources
End of Day: Synthesis & Prioritization
•
Reassess top risks across product, manufacturing, and fleet
•
Ensure owners and timelines are clear for critical issues
•
Prepare concise updates for leadership (what’s broken, what’s improving, what’s at risk)
What Makes the Role Unique:
•
You’re one of the few roles that sees the full picture—design → factory → field
•
You operate at both microscopic level (root cause) and system level (process + metrics)
•
You constantly balance speed vs. quality in a fast-moving hardware environment
•
No two days are the same—priorities shift based on real-world data