Mechanisms Engineer III — Opto-Mechanical Systems

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Application Close Date Applications will be accepted on an ongoing basis until the requisition is closed." That's boilerplate? It's not EEO but maybe considered application instructions? It's about application close date; we should remove it as it's not substantive content about role. Also remove repeated paragraphs like "At Blue Origin, we envision millions..." repeated twice; we should keep only one instance? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate repeated content. The repeated paragraph appears twice; we should keep one. We need to extract sections: - About the role: The paragraph after "About The Role". It includes description of Emerging Systems, TeraWave, etc. Also includes "Special Mentions Relocation assistance is available for qualified candidates. Travel expectations: Up to 20% travel may be required for integration activities, launch campaigns, and customer/vendor meetings." This could be part of About the role or maybe separate? Probably part of About the role. We'll include it there. - Responsibilities: list after "Responsibilities". It includes bullet points (starting with "Own the design..." etc). Also includes "Examples Of Additional Areas Where You May Contribute Include ..." which is also responsibilities? Might be considered responsibilities. We'll include them as list items under Responsibilities. - Requirements: The posting has "Minimum Qualifications" and "Preferred Qualifications". According to headings list, we have Requirements, Qualifications, Skills. We need to map content appropriately. Typically Minimum Qualifications go under Requirements or Qualifications. Preferred Qualifications maybe under Qualifications. Skills maybe under Skills. But we need to decide based on content. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (maybe specific skills like CAD, FEA, GD&T etc). However the Minimum Qualifications already list many skills. Could split: Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications, Skills = maybe extract specific technical skills from both? But we risk duplication. Better to follow typical pattern: Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications, Skills = maybe not needed if covered. But we need to include a section only when posting has real specific content. We have content for Minimum Qualifications and Preferred Qualifications, so we can have Requirements and Qualifications sections. Skills maybe not needed separately unless we extract distinct skill list not already covered. However the Minimum Qualifications includes proficiency in 3D CAD, FEA tools, mechanism kinematics, etc. That's skills. But we could still have a Skills section summarizing those. But we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to ensure we don't lose any detail from Minimum Qualifications. Could we just put Minimum Qualifications under Requirements and Preferred under Qualifications, and not have a separate Skills section? That would preserve all info. The instruction says we can have sections like Skills, but we don't have to if not needed. It says "Prefer a few substantive sections over many thin ones." So we can have Requirements and Qualifications only. - Benefits: The posting has a Benefits section with details. So include Benefits. - Pay: The posting has "Base Pay Range For CA applicants is $121,023.00 - $169,432.20 CO applicants is $110,938.00 - $155,312.85 WA applicants is $121,023.00 - $169,432.20 Other Site Ranges May Differ". That's specific pay info. So include Pay. - Schedule: Not mentioned. No schedule info. So we should not include Schedule heading. - Also there is "Culture Statement" and "Why Blue Origin" etc. Those could be considered part of About the role or maybe separate but not in allowed headings. We could incorporate into About the role or maybe omit as boilerplate? The "Why Blue Origin" is motivational but still substantive. However allowed headings list does not include a generic "Why Blue Origin". We could fold into About the role or maybe into a separate section not allowed; better to incorporate into About the role as it's still about role/culture. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should stick to those headings. It doesn't forbid other headings, but says use those for section headings. Likely they expect only those headings. So we should not add other headings like "Why Blue Origin" or "Culture Statement". We can incorporate that content into About the role or maybe into Responsibilities? Probably About the role is appropriate to include company vision etc. We'll include the "Why Blue Origin" paragraph(s) inside About the role. We must remove duplicated lines: The repeated "At Blue Origin, we envision millions..." appears twice; we keep one. Also remove "Application Close Date..." line. Remove EEO boilerplate etc. Now construct HTML. Structure:

About the role

... (combined paragraph(s) about role, including vision, TeraWave description, Special Mentions)

Responsibilities

• Own the design and development of precision gimbal assemblies and pointing mechanisms for space-based optical communications terminals, from concept through flight qualification
• Develop and be accountable for mechanism-level performance requirements, error budgets, and design margins across structural, thermal, and dynamic domains
• Drive design trades for gimbal configurations, balancing mass, volume, stiffness, pointing accuracy, and on-orbit lifetime, and defend your recommendations in design reviews
• Plan and execute mechanism qualification including component- and system-level testing in shock, vibration, and thermal vacuum environments, and own the resulting data and corrective actions
• Author and maintain mechanism design documentation, analysis reports, and test procedures supporting hardware build and test
• Coordinate directly with cross-functional partners on mechanism integration, harness routing, and interface definition — acting as the point of contact for your hardware
• Partner with senior and principal engineers on the toughest technical problems, escalating risks early and proposing solutions
• Support production transition through tolerance analysis, DFM/DFA improvements, and direct supplier engagement
• Examples of additional areas where you may contribute include motor and encoder selection for precision drive systems
• Bearing selection, preload analysis, and lubrication strategies for space mechanisms
• Mechanism-level FMEA and reliability analysis

Note: The "Examples Of Additional Areas Where You May Contribute Include" line is a heading; we turned into list items. Now Requirements (Minimum Qualifications):

Requirements

• Bachelor's degree in Mechanical Engineering, Aerospace Engineering, Automotive or related technical field
• 5+ years of experience in precision mechanisms design for space, aerospace, or high-reliability applications
• Demonstrated ability to independently own the design, analysis, and qualification of gimbal assemblies, multi-axis pointing mechanisms, or similar precision mechanical systems
• Proficiency in 3D CAD software (e.g., Creo, NX, SolidWorks) and finite element analysis tools (e.g., ANSYS, NASTRAN, Comsol)
• Working knowledge of mechanism kinematics, dynamics, and structural analysis
• Hands-on experience with space qualification testing including vibration, shock, and thermal vacuum
• Experience with bearing systems, drive trains, or precision actuators for space mechanisms
• Solid understanding of GD&T, tolerance stack-up analysis, and interface control documentation
• Familiarity with Design for Manufacturing (DFM) and Design for Assembly (DFA) principles
• Self-directed work style with a strong sense of ownership and the ability to thrive with minimal oversight on a small team

Now Qualifications (Preferred Qualifications):

Qualifications

• Master's degree in Mechanical Engineering, Aerospace Engineering, Automotive or related field
• Experience with optical communications terminals or lasercom pointing, acquisition, and tracking (PAT) systems
• Exposure to lubrication and tribology for space mechanisms (e.g., dry film, ionic liquid, oil-impregnated)
• Familiarity with STOP (Structural-Thermal-Optical-Performance) analysis workflows
• Experience supporting transition of precision mechanisms from development into production
• Exposure to statistical process control or production data analysis for mechanism performance verification

Now Benefits:

Benefits

• Medical, dental, vision, basic and supplemental life insurance
• Paid parental leave
• Short and long-term disability
• 401(k) with a company match of up to 5%
• Education Support Program
• Stock Options for all regular employees (working at least 20 hours/week)
• Paid Time Off: Up to four (4) weeks per year based on weekly scheduled hours, and up to 14 company-paid holidays
• Dependent on role type and job level, employees may be eligible for benefits and bonuses based on the company's intent to reward individual contributions and enable them to share in the company's results, or other factors at the company's sole discretion. Bonus amounts and eligibility are not guaranteed and subject to change and cancellation.

Now Pay:

Pay

Base Pay Range: CA applicants $121,023.00 - $169,432.20; CO applicants $110,938.00 - $155,312.85; WA applicants $121,023.00 - $169,432.20; Other site ranges may differ.

We should not include Schedule. Now ensure we didn't include any boilerplate like "Equal Employment Opportunity", "Export Control Regulations", "Background Check", etc. Remove them. Also remove "Culture Statement" and "Why Blue Origin" paragraphs? We incorporated some of Why Blue Origin into About the role? Let's see: The About the role paragraph we need to include the description of TeraWave etc. The "Why Blue Origin" paragraph includes motto etc. We could incorporate that into About the role as well. Let's combine. We need to preserve all substantive info. So we need to include the content from "Why Blue Origin" and "Culture Statement" maybe. But we can't add new headings; we can merge into About the role. Thus About the role paragraph should include: - At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight! - Blue Origin is pioneering the future of space-based communications with TeraWave, a revolutionary satellite communications network designed to deliver symmetrical data speeds of up to