Supply Chain Manager — Sonny V2

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. First part: "About Tutor We believe ..." That's company description. Could be "About the role"? Actually "About Tutor" is company overview. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" maybe includes description of role. But we have "The Role" section describing responsibilities. Also "What You'll Own" details responsibilities. Also "What We're Looking For" is requirements/qualifications. Also "Nice to Have" maybe skills. Also "How We Work — Our Values In This Role" maybe culture but not required. Benefits: "Tutor offers competitive benefits including fully employer-covered health insurance, a managed 401(k), and regular in-office meals. We also offer unlimited PTO and holidays. We host social events and maintain a collaborative, low-ego work culture where people are trusted to take ownership and solve real problems." That's benefits. Pay and Schedule: Not mentioned. So we should not include Pay or Schedule sections. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly combine Requirements and Qualifications? The instruction says use those headings if content exists. We have "What We're Looking For" which includes requirements: 5+ years experience, hands-on experience sourcing from Chinese vendors, proven negotiator, analytical tool-building skills, fluency with MES/ERP/PLM, mechanical/electrical literacy, willingness to be on shop floor, bachelor's degree. That's qualifications. Also "Nice to Have" could be skills. Could treat "Nice to Have" as Skills. We also have "Mindset and ownership over credentials." maybe part of responsibilities? Actually that's a heading inside "What You'll Own"? It says "Mindset and ownership over credentials." then bullet? Not exactly bullet but a sentence. We'll incorporate into responsibilities. We need to use

• for any list of duties/requirements/benefits. So we should turn lists into
  • . For prose, use

    . We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, equal opportunity, etc. At end there is "Tutor is an equal opportunity employer..." that's boilerplate; remove. Also remove duplicated lines, cookie/navigation/legal etc. Not present. We need to output only HTML fragment. Let's structure:

    About the role

    ... maybe combine company description and role overview? The "About Tutor" is company description; but heading is About the role. Could include both company mission and role description. We'll include the paragraph about Tutor's mission and then the role description: "We're scaling to 1,000+ robots by 2028, and Sonny ramps in Q2 2027. You'll own its purchased-part supply chain end to end..." etc. Better: Use two paragraphs: one about Tutor, one about the role. Then Responsibilities: from "What You'll Own" bullet points. We'll list each as

  • . Also include the mindset sentence maybe as a

    before list? Could incorporate as part of responsibilities prose. We need to preserve all substantive info: The bullet points under "What You'll Own" are many sentences. We'll turn each into

  • . Ensure we keep details. Let's extract: - The Sonny V2 vendor base. Source, qualify, and manage suppliers for every purchased part on the Sonny V2 BOM. - Lead second-sourcing on single-point-of-failure parts. - Build real partnerships with critical suppliers, not just transactional relationships - The buy. Own purchase orders, buffer strategy, and material coverage against the build plan. Decide when to bulk-order for lead-time insurance, when to air freight, and when to hold. Attach controlled drawings and revs to every PO on a critical part — no exceptions - Clear to Build. Build and maintain the predictive tools the company relies on: clear-to-build reports (now / 30 / 60 / 90 days), shortage callouts, lead-time trackers, and material risk dashboards pulled from ION and the build forecast. Supply Chain should get actionable buy signals from these tools, and so should Engineering and Sales - Cost and negotiation. Drive unit cost, payment terms, MOQs, and lead times down through structured negotiation. Own landed cost and COGS visibility for the product - Design change absorption. BOM and design changes on Sonny will keep coming on a cadence greater than zero. Work directly with Production Engineering and R&D through the ECO process so the supply chain absorbs changes at monthly build cutovers rather than stalling the line - Outsourcing strategy. Evaluate and stand up outsourced sub-assembly and contract-manufacturing options as Sonny volume grows, including offshore options - Supplier performance. Track on-time delivery, quality (NCMRs back to the vendor), and responsiveness. Escalate early and hard when a supplier slips - The system of record. Keep ION accurate: part numbers, unit costs, purchased assemblies, on-order quantities, and inventory so the shop floor and the finance team see the same truth Also earlier: "Mindset and ownership over credentials." maybe a heading but no detail; we can incorporate as a short sentence: "Mindset and ownership over credentials." but that's vague; maybe we can treat as a responsibility: "Demonstrate mindset and ownership over credentials." Not sure. Safer to omit if it's just a heading without detail. The instruction: never emit a heading followed by filler/placeholder text. So we should not create a heading for that. We'll just ignore that line. Now Requirements/Qualifications: from "What We're Looking For". List: - 5+ years in supply chain, purchasing, or strategic sourcing for a hardware product, ideally through a new-product-introduction ramp (prototype → pilot → production) - Hands-on experience sourcing from and managing Chinese vendors: factory qualification, PI/T/T payment structures, EXW and freight tradeoffs (sea vs. air), customs, and the reality of time-zone and communication gaps - A proven negotiator with examples of cost, lead-time, MOQ, or terms wins you personally drove - Strong analytical and tool-building skills: you've built clear-to-build, MRP-style, or shortage-forecasting tools in Excel, SQL, Python, or a BI tool — not just consumed them - Fluency with an MES/ERP/PLM system (ION, NetSuite, Arena, Odoo, SAP, or similar) and comfort working from a controlled BOM with revision control - Mechanical and electrical literacy: you can read a drawing, understand a harness spec, and talk to an engineer about why a tolerance matters to a supplier - Willingness to be on the shop floor, in the warehouse, and occasionally on a plane to a supplier - Bachelor's degree in supply chain, engineering, business, or equivalent experience We could put these under Requirements or Qualifications. Since both headings allowed, we could put Requirements for experience and Qualifications for education/skills. But we can also combine. To follow instruction: prefer a few substantive sections over many thin ones. So maybe we combine into one section "Requirements" containing all. Or we could have "Qualifications" for education and "Skills" for technical skills. Let's decide: We'll have:

    Requirements

    with the experience items (years, Chinese vendor experience, negotiator, willingness to travel, bachelor's degree). Then

    Skills

    for analytical tool-building, MES/ERP fluency, mechanical/electrical literacy. And maybe

    Qualifications

    for education? But we already have bachelor's degree in Requirements. Could move education to Qualifications. Let's think. Better: Use Requirements for experience, Qualifications for education, Skills for technical abilities. That yields three sections. Let's extract: Experience (Requirements): - 5+ years in supply chain, purchasing, or strategic sourcing for a hardware product, ideally through a new-product-introduction ramp (prototype → pilot → production) - Hands-on experience sourcing from and managing Chinese vendors: factory qualification, PI/T/T payment structures, EXW and freight tradeoffs (sea vs. air), customs, and the reality of time-zone and communication gaps - A proven negotiator with examples of cost, lead-time, MOQ, or terms wins you personally drove - Willingness to be on the shop floor, in the warehouse, and occasionally on a plane to a supplier Education (Qualifications): - Bachelor's degree in supply chain, engineering, business, or equivalent experience Skills: - Strong analytical and tool-building skills: you've built clear-to-build, MRP-style, or shortage-forecasting tools in Excel, SQL, Python, or a BI tool — not just consumed them - Fluency with an MES/ERP/PLM system (ION, NetSuite, Arena, Odoo, SAP, or similar) and comfort working from a controlled BOM with revision control - Mechanical and electrical literacy: you can read a drawing, understand a harness spec, and talk to an engineer about why a tolerance matters to a supplier Nice to Have could be additional skills but not required; we could include under Skills as optional? The instruction says preserve all substantive information; we could add a subsection "Nice to Have" but not a heading unless we have real content. We could add a

    under Skills for nice-to-have items. But better to add a separate section "Nice to Have" maybe as Skills? However headings list includes Skills only. We could incorporate nice-to-have as part of Skills with a note. But to preserve all, we can add a

    after Skills list: "Nice to have: Mandarin or Cantonese fluency, experience with robotics/automation/EV/drones, prior experience setting up or managing a China-based sourcing presence, APICS/CPSM/CSCP certification or Lean Six Sigma training, experience with First Resonance ION specifically, contract manufacturing/EMS outsourcing experience." Now Benefits: we have paragraph. Now we need to ensure we don't include Pay or Schedule. Now produce HTML. Let's craft.

    About the role

    Tutor believes general-purpose, generally-intelligent robots will be built in our lifetimes. Robots will work in our factories, move our goods, walk on our streets and eventually be in our homes. To build that future, research and deployment must work in lockstep: real-world operation must make the technology better, and better technology must make deployment easier. As an AI robotics company that deploys its inventions directly into the facilities that need them, on state-of-the-art hardware, every part we buy and every robot we ship has a direct impact on the global, physical economy. Founded by MIT alumni and backed by leading AI and robotics investors, we don't just build robots — we deploy, maintain, and continuously improve them in production environments.

    We're scaling to 1,000+ robots by 2028, and Sonny ramps in Q2 2027. You'll own its purchased-part supply chain end to end: the vendor base, the buys, the buffers, the cost, and the data that tells the company what we can build and when. Our critical parts come from China with 100+ day lead times, and the design is still changing monthly. We are only as good as our suppliers — you're the person who makes that work. We want someone as comfortable in a spreadsheet as on a call with a factory in Shenzhen. Someone who builds the tools that predict shortages instead of chasing them, and who negotiates like every dollar and