Staff Mechanical Engineer

We need to output HTML fragment with sections: About the role (position summary), Responsibilities, Requirements (Qualifications), maybe Skills? The posting includes "Required Qualifications" and "Preferred Qualifications". We can combine into Requirements (maybe separate Required and Preferred). But we need to follow rule: include a section only when posting has real specific content. We have content for About the role (position summary). Responsibilities: there is a list after "In this role you will:" and then "Your responsibilities:" with bullet-like sentences. We'll extract those as list items. Requirements: we have "Required Qualifications" and "Preferred Qualifications". Could combine into a single Requirements section with sub-lists? But rule: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have separate sections: Requirements (maybe Required Qualifications) and Preferred Qualifications? But they said prefer a few substantive sections over many thin ones. Could combine both into Requirements with subheadings? But we cannot add extra headings besides those listed. Could use

for Requirements and then within that list separate required and preferred? Might be okay to have two sections: Requirements (Required Qualifications) and Preferred Qualifications (maybe as Skills?). However "Preferred Qualifications" is not exactly Skills but could be placed under Requirements or maybe under Skills. The list of allowed headings includes Skills. Could put Preferred Qualifications under Skills. But better to follow the posting: have Required Qualifications and Preferred Qualifications as separate sections? The instruction: "Prefer a few substantive sections over many thin ones." Having both Required and Preferred might be thin but they are substantive. Could combine into one Requirements section with two sub-lists: Required and Preferred. But we cannot add custom headings like "Required" and "Preferred" as

? Not prohibited but they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they suggest using those. Safer to stick to those headings. So we could have:

About the role

...summary...

Responsibilities

• ... each responsibility...

Requirements

• ... required qualifications...

Skills

• ... preferred qualifications...

We also have Benefits: "MicroVision offers a flexible work schedule that could include a hybrid schedule of onsite and remote work, subject to team and business needs. Individual work schedules will be at the discretion of management and dependent on role and business needs. You must live and reside within commuting distance from MicroVision’s headquarters in Orlando, FL. We are not able to provide visa sponsorship for this position. You must be able to work in the U.S. without sponsorship." That's more about work schedule and location, not benefits. Then there is a Benefits line: "MicroVision is proud to offer a comprehensive benefit program, if you would like to learn more, please visit: Careers - About | MicroVision". That's vague, no specifics. According to rule: never create Benefits section unless posting actually states them. It does state they offer a comprehensive benefit program but no details. That's vague but still states they offer a benefit program. However they say "if you would like to learn more, please visit". That's not specific detail. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states they offer a comprehensive benefit program, but no specifics. Is that considered filler? It's a statement but no detail. Might be considered vague but still states they have benefits. However they also mention flexible work schedule (Schedule). That is specific: flexible work schedule that could include hybrid schedule of onsite and remote work, subject to team and business needs. Individual work schedules at discretion of management. That's specific enough for Schedule section. Also location requirement (must live within commuting distance from Orlando, FL) and no visa sponsorship. That could be part of Schedule or maybe a separate note but we can include in Schedule section as details. Thus we can have Schedule section with those details. Benefits: they say comprehensive benefit program but no detail; could be considered filler. Better to omit Benefits section. Pay: not mentioned. Thus sections: About the role, Responsibilities, Requirements (maybe combine required and preferred?), Skills (maybe preferred qualifications), Schedule. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none. We need to extract responsibilities list: after "In this role you will:" there are bullet-like sentences (starting with Design and own..., Translate..., Balance..., Enable..., Drive...). Then after "Your responsibilities:" there is a long list of items each starting with a verb. Many are repeated (Lead design and development of precision mechanical components and assemblies for electro‑optical sensor systems appears twice). We need to preserve all substantive information but we can deduplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines are duplicated content; we could keep both but it's redundant. Might be considered boilerplate? Not exactly. Safer to keep each unique responsibility; but we can deduplicate to avoid repetition while preserving all unique info. The duplicated line appears twice exactly; we can keep one instance. That's not summarizing away detail, just removing duplicate identical line. Acceptable. We'll produce

• for each responsibility. Now Required Qualifications list: items: - 10-15+ years of mechanical engineering experience in precision or complex hardware products - Strong foundation in mechanical design, drafting, and GD&T (SolidWorks) - Demonstrated experience owning mechanical designs from concept through release - Knowledge of designing precision components for injection molding, machining, die casting, and metal injection molding (MIM) processes, with an understanding of material selection and manufacturability tradeoffs - Hands‑on experience managing BOMs, configuration control, and formal change management processes (ECO/ECR) through PLM system (Arena) - Practical application of structured problem‑solving methodologies such as 8D or equivalent - Experience developing and maintaining DFMEAs - Familiarity with Design‑to‑Cost and Value Engineering approaches - Strong cross‑functional communication skills, with experience working across mechanical, manufacturing, electrical, optical, and systems engineering teams Preferred Qualifications list: - Experience serving as mechanical lead or subsystem owner on a hardware product - Background in precision electro‑mechanical or opto‑mechanical systems - Experience supporting products across concept, development, validation, and release phases - Exposure to supplier‑driven design optimization or cost reduction initiatives - Experience working in a regulated industry such as automotive, defense, aerospace, or safety‑critical products, including adherence to structured development and documentation processes We'll put these under Requirements (maybe separate required and preferred but we can combine). However we need to avoid thin sections. Could have two sub-sections: Required Qualifications and Preferred Qualifications as separate

  headings? But allowed headings include Qualifications. Could use

  Qualifications

  and then inside have two
  with headings? Not allowed to add extra headings? Might be okay to add inside. Safer: Use

  Requirements

  for required qualifications, and

  Skills

  for preferred qualifications. That follows allowed headings. Now Schedule section: details: - MicroVision offers a flexible work schedule that could include a hybrid schedule of onsite and remote work, subject to team and business needs. - Individual work schedules will be at the discretion of management and dependent on role and business needs. - You must live and reside within commuting distance from MicroVision’s headquarters in Orlando, FL. - We are not able to provide visa sponsorship for this position. - You must be able to work in the U.S. without sponsorship. We'll put these as
  • . Now About the role: we need to capture the position summary paragraph(s). The text: "POSITION SUMMPARY MicroVision a leader in advanced perception solutions for industrial, security and defense, and automotive applications, is seeking a Staff Mechanical Engineer - Precision Mechanical Design. As a key member of MicroVision's Mechanical Design Engineering team, you will collaborate with technical teams across the company to design and bring to production market-defining LiDAR products for automotive, defense, and industrial applications. In this role you will support the design and development of next‑generation electro‑optical sensor products. This role is responsible for owning mechanical designs from early concept and architecture definition through detailed design, system integration, and release, ensuring solutions meet performance, cost, manufacturability, and quality requirements. The engineer in this role will design and own precision mechanical components and assemblies within a highly integrated, multidisciplinary system. This position emphasizes hands‑on mechanical design, strong documentation rigor, tolerance control, and close collaboration with electrical, optical, systems, manufacturing, and program teams throughout the product development process. This position is expected to provide mechanical technical oversight, guiding architecture decisions, trade studies, and design rigor across the product. In this role you will: Design and own precision mechanical solutions for advanced electro‑optical sensor productsTranslate system‑level requirements into robust mechanical architecture and detailed designsBalance performance, cost, reliability, and manufacturability through disciplined engineering practicesEnable smooth system integration through strong interface definition and cross‑functional executionDrive mechanical design rigor across documentation, change management, and risk mitigation" Note there is a typo "POSITION SUMMPARY". We'll just treat as summary. We'll output a

    containing that summary (maybe combine into one paragraph). Ensure we preserve all info. Now produce HTML fragment:

    About the role

    MicroVision a leader in advanced perception solutions for industrial, security and defense, and automotive applications, is seeking a Staff Mechanical Engineer - Precision Mechanical Design. As a key member of MicroVision's Mechanical Design Engineering team, you will collaborate with technical teams across the company to design and bring to production market-defining LiDAR products for automotive, defense, and industrial applications. In this role you will support the design and development of next‑generation electro‑optical sensor products. This role is responsible for owning mechanical designs from early concept and architecture definition through detailed design, system integration, and release, ensuring solutions meet performance, cost, manufacturability, and quality requirements. The engineer in this role will design and own precision mechanical components and assemblies within a highly integrated, multidisciplinary system. This position emphasizes hands‑on mechanical design, strong documentation rigor, tolerance control, and close collaboration with electrical, optical, systems, manufacturing, and program teams throughout the product development process. This position is expected to provide mechanical technical oversight, guiding architecture decisions, trade studies, and design rigor across the product. In this role you will: Design and own precision mechanical solutions for advanced electro‑optical sensor products Translate system‑level requirements into robust mechanical architecture and detailed designs Balance performance, cost, reliability, and manufacturability through disciplined engineering practices Enable smooth system integration through strong interface definition and cross‑functional execution Drive mechanical design rigor across documentation, change management, and risk mitigation

    But note the colon list after "In this role you will:" we already included as sentences. Might be better to keep as list? But they are responsibilities; we already have Responsibilities section. However the summary also includes those same items. To avoid duplication, we could keep summary without that list, but the instruction says preserve ALL substantive information. The summary includes that list; if we omit it we lose info. However we also have Responsibilities section that includes similar items (the list after "Your responsibilities:"). The summary