Lead Mechanical Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. The posting includes job description (lead mechanical engineer) with duties & responsibilities, required qualifications, clearance requirements, work environment, pay scales & benefits. We need to map to headings. We should not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove application instructions (none). Remove cookie/navigation/legal etc. We need to preserve all substantive info. We need sections: maybe "About the role" could be a brief summary from first paragraph? The posting includes description of company and role. Could put that under "About the role". Then "Responsibilities" from Duties & Responsibilities. Then "Requirements" maybe combine Required Qualifications and Clearance Requirements? Or separate "Qualifications" and "Skills"? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple. We need to decide which sections have content. We have content for: - About the role: company description and role overview. - Responsibilities: Duties & Responsibilities. - Requirements: maybe Required Qualifications (citizenship, degree, experience, etc.) plus Clearance Requirements. - Qualifications: maybe advanced degree preferred? But that's part of required qualifications. Could split: Required Qualifications vs Preferred Qualifications? The posting mentions "advanced degree preferred" and "Experience with defense systems... is preferred". So we could have "Qualifications" for required, and "Skills" for preferred/expert-level understanding etc. But we need to avoid duplication. Better: Use "Requirements" for mandatory (citizenship, degree, 15+ years, etc.) and "Skills" for expert-level understanding, tools, etc. Also "Qualifications" maybe for education? But we have limited headings. We could do:

About the role

...company description and role overview...

Responsibilities

• ...list each duty...

Requirements

• U.S. Citizenship with ability to obtain and maintain a DoD Security Clearance.
• Bachelor’s degree in Mechanical Engineering or related technical discipline; advanced degree preferred.
• 15+ years of experience in mechanical subsystem research, innovation, design, development, integration, test, production transition, or technical oversight.
• Demonstrated ability to serve as a technical authority or subject matter expert for complex mechanical, electromechanical, sensor, payload, or integrated defense system development efforts.
• Experience overseeing subcontractor, supplier, or external design partner execution, including review of technical data packages, drawings, analyses, manufacturing documentation, test plans, and delivered hardware.
• Demonstrated experience contributing to multidisciplinary engineering projects, working with cross-functional teams, and adapting to changing project requirements.
• Experience with defense systems, radar sensors, unmanned systems, maritime systems, weapons-related systems, or advanced payload integrations is preferred.

But note "is preferred" maybe should go to Skills or Qualifications. However we can keep it in Requirements but it's not a strict requirement. Might be okay. We could separate "Qualifications" for education and experience, and "Skills" for technical expertise. Let's think: The posting includes "Required Qualifications" block with bullet points (citizenship, degree, 15+ years, ability to serve as technical authority, experience overseeing subcontractor, experience contributing to multidisciplinary projects, experience with defense systems preferred, expert-level understanding of mechanical engineering concepts..., fluency with CAD/tools..., strong understanding of configuration management..., excellent analytical..., excellent written/verbal..., willingness to develop skills). That's a long list. We could treat that as "Qualifications" (required) and maybe "Skills" for the expert-level understanding and tools etc. But the list includes both. Given instruction to prefer few substantive sections over many thin ones, we could combine all into "Requirements" and maybe have "Skills" for the tools and expert-level understanding. But we need to avoid filler. We also have "Clearance Requirements" separate but could be merged into Requirements. We have "Work Environment": on-site/hybrid, travel. Could be a section "Work Environment" but not in allowed headings list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Work Environment not listed, but we could incorporate into About the role or Responsibilities? Probably better to include as a short paragraph under About the role? But the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. It doesn't say we cannot use other headings, but to follow the example. Safer to stick to those. Thus we need to map content to those headings. We have Pay and Benefits: we have pay range and benefits list. So we can have

Pay

The Pay Range For This Role Is 141,426 - 172,000 USD per year

. And

Benefits

• Paid Time Off
... etc. Schedule: not mentioned; we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to decide what goes where. Let's extract: About the role: company description and role overview: first paragraph about Lyntris, then "Job Description Lead Mechanical Engineer Full Time Remote The Senior Mechanical Engineer will serve as a senior technical leader..." That's about role. Responsibilities: Duties & Responsibilities block (with subheadings Mechanical Engineering Leadership, Subcontractor, Supplier & Technical Oversight, System Design, Integration & Test, Program, Proposal & Customer Support). We'll turn each bullet into
• . Requirements: maybe the mandatory items: U.S. Citizenship, Bachelor's degree, 15+ years experience, ability to serve as technical authority, experience overseeing subcontractor, experience contributing to multidisciplinary projects, willingness to develop skills? Actually willingness is more skill. Qualifications: maybe education and experience? But we already used education in Requirements. Could swap: Requirements = citizenship, clearance, willingness to develop skills? Not ideal. Better: Use Requirements for the mandatory qualifications (citizenship, degree, years, ability to serve as technical authority, oversight experience, multidisciplinary experience). Use Qualifications for preferred qualifications (advanced degree preferred, defense systems experience preferred). Use Skills for expert-level understanding of mechanical concepts, fluency with CAD/tools, configuration management, analytical/problem-solving, communication skills. Let's do that. Thus:

  About the role

  Lyntris is a defense technology company that connects sensing to action across the connected battlespace. Lyntris brings together the talents of Accelint and Vitesse teams under one mission, with each contributing deep expertise within their domain. Combining differentiated hardware, software and mission expertise, Lyntris helps customers sense threats, make sense of complex conditions and act with greater speed, precision and confidence in contested environments. Lyntris supports U.S. and allied defense organizations across every branch — including Navy, Army, Air Force, Space Force and allied partners — spanning strategic, operational and tactical missions and every domain: Space, Air, Land, Sea and Cyber. With more than 200 active defense programs, Lyntris works at every level of the mission, from national command authority to the tactical edge. Solutions are designed by operators who understand the mission, engineered for the conditions that degrade or defeat standard systems, and built on an open, modular architecture that integrates into existing programs without requiring them to start over. Lyntris moves faster than the traditional defense cycle — with integrated design, build and test capabilities in-house — and delivers systems that sustain and endure long after initial fielding. Job Description Lead Mechanical Engineer Full Time Remote The Senior Mechanical Engineer will serve as a senior technical leader and mechanical engineering subject matter expert supporting the research, design, development, integration, and demonstration of advanced defense sensor and mission systems across Lyntris’ portfolio. This role will work closely with engineering leadership, internal multidisciplinary teams, external design partners, subcontractors, suppliers, and government stakeholders to develop practical, mission-focused hardware solutions. This individual will play a critical role in the technical oversight, implementation, and maturation of mechanical subsystems across structural, thermal, packaging, manufacturability, integration, environmental performance, and production-readiness domains. The ideal candidate is an experienced mechanical engineering leader who can act as a technical authority for major hardware development efforts, guide architecture and design trades, evaluate subcontractor designs and deliverables, mentor engineering personnel, support proposal and customer engagement activities, and help scale Lyntris’ internal design, development, test, and production-transition capabilities.

  That's a lot but preserves all. Now Responsibilities: we need to list duties from Duties & Responsibilities. We'll break into items. We have four main categories with sub-bullets. We'll flatten into list items. Let's extract each sentence that starts with a verb. From Mechanical Engineering Leadership: - Serve as a mechanical engineering subject matter expert responsible for guiding technical approaches, assessing design maturity, and ensuring mechanical solutions align with system-level performance, environmental, producibility, and mission requirements. - Develop, review, and mature mechanical architectures, subsystem designs, packaging concepts, interface definitions, and integration approaches aligned to system and mission requirements. - Recommend and articulate hardware and system design approaches using current and next-generation components, materials, manufacturing methods, and technologies. - Support structural, thermal, environmental, producibility, maintainability, survivability, and design-for-manufacturing trade studies across complex hardware and integrated system efforts. Subcontractor, Supplier & Technical Oversight: - Provide technical oversight of subcontractor and supplier mechanical engineering activities, including design concepts, analyses, CAD models, drawings, interface control documents, test plans, and delivered hardware. - Review subcontractor technical data packages, drawings, analyses, manufacturing plans, inspection data, and design artifacts to ensure quality, completeness, traceability, and compliance with program requirements. - Coordinate technical interchange meetings, design reviews, action-item closure, discrepancy resolution, and engineering change activities with external development partners and internal stakeholders. - Identify technical risks, integration issues, producibility concerns, and requirement gaps early, then drive mitigation plans and corrective actions across internal and external teams. - Maintain technical alignment between customer requirements, system architecture, subcontractor execution, supplier deliverables, and Lyntris integration and production-readiness objectives. System Design, Integration & Test: - Support integration, checkout, troubleshooting, and demonstration activities for radar sensors, unmanned systems, payloads, weapons-related systems, and associated mechanical subsystems. - Develop and review CAD models, engineering drawings, interface control documentation, assembly documentation, verification artifacts, and production-support materials. - Support root cause analysis, discrepancy resolution, engineering change activities, nonconformance evaluation, and corrective actions in dynamic development, integration, and operational environments. - Contribute to verification planning, test procedures, environmental qualification approaches, design reviews, field demonstrations, and transition of prototype systems into repeatable production configurations. - Coordinate with suppliers, fabrication teams, machine shops, manufacturing partners, and integration teams to improve producibility, assembly efficiency, configuration control, technical quality, and delivery readiness. Program, Proposal & Customer Support: - Assist with bid and proposal activities by providing engineering cost estimates, technical writing, technical evaluations, engineering approaches, subcontractor technical inputs, and detailed solution concepts. - Write technical papers, white papers, status reports,