Production Supervisor - Body

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: Shift, About 1X, About The Team, Your Charter, Key Outcomes, Key Competencies, Minimum Requirements, Preferred Skills, What Does a Successful Does a Successful 1X Team Member Look Like, Compensation Range, Benefits. Also shift info (Day Shift, 7:00 AM - 3:30 PM) maybe part of schedule? The instruction: include a section ONLY when posting has real, specific content. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings. The posting doesn't have explicit "About the role" but we have "Your Charter" which describes role. Could treat as "About the role". "Key Outcomes" could be responsibilities. "Key Competencies" could be skills/qualifications. "Minimum Requirements" and "Preferred Skills" could be qualifications/requirements. "What Does a Successful 1X Team Member Look Like" maybe culture fit, could be omitted or put under something else? Might be considered as "Skills" but it's more about traits. Could include as a section maybe "Team Fit" but not in allowed headings. Probably better to omit if not matching allowed headings. However we need to preserve all substantive information; we cannot drop content. So we need to embed that info somewhere within allowed sections. Could put under "Skills" or "Qualifications". The allowed headings list is examples, not strict? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those exact headings where appropriate. We can also add other headings if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should only use those headings. We need to map content to those. Sections we have: - About the role: could include Shift, About 1X, About The Team, Your Charter (description). Also maybe "What Does a Successful 1X Team Member Look Like" could be part of About the role. - Responsibilities: Key Outcomes (daily/weekly targets, build team, drive defect rates, own safety, lead process improvement). Also maybe "Your Charter" includes responsibilities. - Requirements: Minimum Requirements. - Qualifications: Preferred Skills? Or maybe Qualifications includes both minimum and preferred? Could split: Requirements = Minimum Requirements, Qualifications = Preferred Skills. - Skills: Key Competencies. - Benefits: Benefits list. - Pay: Compensation Range. - Schedule: Shift info (Day Shift, 7:00 AM - 3:30 PM). Also maybe mention available to work on-site in Hayward or San Carlos, on a day or swing shift. That's schedule/location. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: Equal Opportunity Employer text, duplicated lines, etc. Also remove "Compensation Range: $100K - $130K" duplicate. We need to preserve all substantive information: shift, about 1X, about team, your charter, key outcomes, key competencies, minimum requirements, preferred skills, what does a successful team member look like, compensation range, benefits. We need to embed "What Does a Successful 1X Team Member Look Like" somewhere. Could be under Skills or Qualifications. Probably under Skills as it's about traits. We must not create sections with filler like "commensurate with experience". We have real content. We must output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Shift: Day Shift, 7:00 AM - 3:30 PM. About 1X: We’re building humanoid robots that work in home - doing the chores, handling the tasks, and giving people their time back. Simple, but it’s not. To do this right, we have to solve robotics, AI, manufacturing - at the same time, at scale, in a form factor that has to be safe enough to live with your family. If you’re inspired by this, you’ll thrive here. We’ve been at this since 2014 and we’re at the point where the hard problems are behind us and the hard work is in front of us. NEO is our flagship - a home robot designed to move, learn, and operate in the real world alongside real people. We’re not demoing it - we’re shipping it. We’re excited to meet you, if this excites you. If you’ve spent your career working on problems that matter and want to see them actually reach the world - this is that moment. We’re scaling, we’re hiring with intention, and we need people who want to build something that will genuinely change how humans spend their time - safely creating abundance for all. About The Team: The Manufacturing team is where NEO becomes real. Every robot that ships to a home passes through our floor, and the standard we set here — in safety, quality, and pace — is the standard our customers feel when NEO walks into their living room. We are the bridge between an engineering breakthrough and a product that earns trust in the real world. Your Charter: To create an abundant supply of physical labor through safe, intelligent humanoids, we have to build them at a quality and cadence the world hasn’t seen in a humanoid program. As Production Supervisor, you own the daily rhythm of the assembly floor — the people, the workflow, the safety, and the output. You are the person who makes sure that when a NEO leaves our facility, it leaves built right, on time, and made by a team that’s proud of how it got there. This role sits squarely on 1X’s critical path: without a production floor that runs with discipline and care, we don’t ship.

Responsibilities

• Hit daily and weekly NEO build targets without compromising on safety or quality, and own the metrics that prove it (throughput, yield, first-pass quality, on-time completion).
• Build and lead a production team that is trained, accountable, and engaged — measured by retention, cross-training coverage, and team-level performance against plan.
• Drive defect rates and rework down quarter over quarter through root-cause problem solving, process control, and tight feedback loops with Quality and Engineering.
• Own floor safety as a non-negotiable — zero preventable incidents, full compliance with safety protocols, and a culture where the team raises issues early.
• Surface and lead at least one meaningful process improvement per quarter — something that measurably improves cycle time, ergonomics, quality, or cost.

Requirements

• 3+ years directly supervising production or manufacturing teams in a hands-on, on-floor capacity.
• Demonstrated track record of hitting production targets while maintaining quality and safety standards.
• Working fluency in production planning, quality systems, and safety practices (e.g., standard work, defect tracking, lockout/tagout, PPE compliance).
• Comfortable in a fast-paced, evolving environment where the process you ran last quarter may not be the process you run next quarter.
• Available to work on-site in Hayward or San Carlos, on a day or swing shift.

Qualifications

• Experience in low-volume, high-complexity manufacturing — robotics, aerospace, medical devices, EVs, or advanced electromechanical assembly.
• Hands-on experience with lean, Six Sigma, Kaizen, or other structured continuous-improvement methodologies.
• Experience launching a new product line or ramping a new process from pilot to production.
• Familiarity with MES, ERP, or production tracking systems.
• Experience training and developing technicians, including building cross-training and skills matrices.

Skills

• A builder who leads from the floor. You’re visible, you know your team, and you’d rather solve a problem at the station than from a desk.
• High ownership and high standards. You don’t wait to be asked, you don’t hand off problems, and you hold the line on quality even when the pressure is on.
• Clear, direct communicator. You give feedback in real time, escalate cleanly, and translate between technicians, engineers, and leadership without losing the signal.
• Structured problem solver. You can move fast under pressure and still get to root cause — not just clear the jam in front of you.
• Calm in ambiguity. New products, evolving processes, and changing priorities don’t rattle you - they’re the job.
• What Does a Successful 1X Team Member Look Like: Team members at 1X who thrive here are builders. They move fast, own their work completely, and treat time like it’s the one thing you can’t get back - because it is. They say what they mean, finish what they start, and hold themselves to a standard before anyone has to ask. We push each other to be better, and we do it with honesty and respect.

Benefits

• Comprehensive medical, dental, and vision coverage
• Generous paid time off, company holidays, and parental leave
• 401(k) plan with company match (100% on the first 3% of contributions, 50% on the next 2%)
• Flexible Spending Accounts (FSA) and Health Savings Accounts (HSA) options
• Commuter benefits (transit and parking)
• Short-term and long-term disability, and life insurance
• Employee Assistance Program (EAP) for mental health, financial, and personal support
• Onsite snacks and catered lunches

Pay

Compensation Range $100,000 – $130,000 + Equity

Schedule

Day Shift, 7:00 AM - 3:30 PM. Available to work on-site in Hayward or San Carlos, on a day or swing shift.

We need to ensure we didn't duplicate shift info. Already in About the role we included shift. Then Schedule also includes shift. Might be duplication but it's okay to have both? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep shift info somewhere. Having it in both About the role and Schedule duplicates but still preserves. Could we avoid duplication by putting shift only in Schedule and not in About the role? But About the role currently includes shift sentence; we could remove it from there to avoid duplication but still preserve info in Schedule. However About the role currently includes shift as part of the paragraph; we could keep it but it's okay to have duplicate? The instruction didn't forbid duplication, but said remove duplicated lines (like boilerplate). Duplicating shift is not boilerplate but still duplication of same content. Might be considered unnecessary but not prohibited. Safer to avoid duplication: keep shift only in Schedule, and remove from About the role. Let's adjust About the role paragraph to not include shift line. We'll rewrite About the role paragraph without shift. Also ensure we keep "Available to work on-site in Hayward or San Carlos, on a day or swing shift." That's in Requirements and also Schedule. Could duplicate but okay. We'll keep in Requirements (makes sense) and Schedule maybe just shift times. But schedule could include location