Senior Mechanisms Engineer - Satellite Mechanisms

We need to output HTML fragment with sections: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Compensation And Benefits (since salary and benefits given). Also maybe "About Cowboy Space Corp Mission" is not a section heading per rules: we only use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "About The Role", "Responsibilities", "Basic Qualifications", "Preferred Qualifications", "Compensation And Benefits". Also there is "ITAR Requirements" but that's likely boilerplate? It's a requirement but maybe we can include under Requirements? The rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We should not include Job ID etc. We should preserve all substantive info. Remove boilerplate like EEO, disclaimer, etc. Also remove navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ITAR requirement is substantive (citizenship requirement). It could be placed under Requirements or Qualifications. Since we have Basic Qualifications and Preferred Qualifications sections, we could incorporate ITAR requirement into Basic Qualifications as a bullet. But we must not invent sections; we can keep Basic Qualifications and add that as a bullet. The ITAR requirement is basically same as citizenship requirement already listed in Basic Qualifications: "Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum." That's already there. So ITAR is redundant; we can drop it as duplicate. We also have "Compensation And Benefits" includes salary range and list of benefits. We'll make a section

Compensation And Benefits

with

for salary range sentence and

• for benefits list. We need to ensure we don't create sections with placeholder text. All sections have content. We must not include markdown fences. Just raw HTML. Let's extract content: About The Role paragraph: "As a Mechanisms Engineer, you will own a critical spacecraft mechanism subsystem from concept through flight. Depending on your background and team priorities, your assignment will be hold-down and release mechanisms (HDRMs), solar array deployment and drive systems, deployable structures (antennas, booms, radiators), or thermal/radiator articulation mechanisms. This is a hands-on role at the center of spacecraft hardware development. You will work closely with structures, thermal, power, avionics, and mission operations to design integrated systems, build hardware, and validate through test. You'll be expected to move quickly, iterate often, and take full ownership of mechanisms that directly impact mission success." Responsibilities list: each bullet starts with "Own your mechanism subsystem..." etc. We'll put each as
• . Basic Qualifications list: bullet points. Preferred Qualifications list: bullet points. Compensation And Benefits: salary range sentence: "The salary range for this position is $150,000 – $180,000 annually. The actual base salary offered will depend on factors such as job-related skills, experience, qualifications, and internal equity." Then benefits list: "Equity in Cowboy Space Corp. Employees and their eligible dependents may enroll in medical, dental, and vision insurance 401(k) retirement savings plan Paid time off 10 paid holidays per calendar year Paid parental leave Relocation assistance if applicable Daily lunch in the office and a fully stocked kitchen with beverages and snacks" We need to split benefits into list items. The text is a bit run-on; we can separate by periods or commas. Let's parse: - Equity in Cowboy Space Corp. - Employees and their eligible dependents may enroll in medical, dental, and vision insurance - 401(k) retirement savings plan - Paid time off - 10 paid holidays per calendar year - Paid parental leave - Relocation assistance if applicable - Daily lunch in the office and a fully stocked kitchen with beverages and snacks We'll make each as
• . Now produce HTML:

  About the role

  ...

  Responsibilities

  • Own your mechanism subsystem from concept through design, analysis, test, and flight.
  • Drive structural and kinematic design for minimum mass while meeting strength, stiffness, fatigue, and operational-life requirements across launch, on-orbit deployment, and mission-life environments.
  • Balance performance, manufacturability, cost, and schedule in every design decision.
  • Perform analysis — hand calculations, FEA, tolerance stack-ups, deployment dynamics — and validate predictions with test and on-orbit data.
  • Define and execute qualification and acceptance test campaigns, including vibration, thermal vacuum, deployment, and life testing; author procedures, acceptance criteria, and anomaly dispositions.
  • Develop and maintain engineering drawings, models, and release documentation.
  • Work directly on the factory floor with manufacturing and integration & test teams to iterate quickly and resolve build issues in real time.
  • Troubleshoot hardware anomalies, perform root cause analysis, and implement design improvements.
  • Support spacecraft integration & test, launch site operations, and on-orbit commissioning/anomaly response.

  Basic Qualifications

  • Bachelor's degree in Mechanical Engineering, Aerospace Engineering, or related field.
  • 5+ years of experience designing mechanisms or mechanical systems for spacecraft, launch vehicles, or high-performance hardware.
  • Experience taking hardware from concept through build, integration, and test.
  • Strong fundamentals in structural mechanics, kinematics, materials, and manufacturing processes.
  • Proficiency with CAD (NX, SolidWorks, CATIA, or Creo) and creating engineering drawings to ASME Y14.5 GD&T standards.
  • Proficiency with FEA tools (ANSYS, Nastran, or Abaqus) for mechanism load-path and dynamic problems.
  • Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum.

  Preferred Qualifications

  • 10+ years of experience designing mechanisms or mechanical systems for spacecraft or high-performance flight hardware.
  • Direct experience with hold-down and release mechanisms (HDRMs), solar array deployment systems, or other spacecraft deployables.
  • Experience with pyrotechnic, non-explosive actuator (NEA), or other low-shock release devices.
  • Hands-on prototyping and machining experience.
  • Familiarity with spacecraft thermal environments and their effect on mechanism performance.
  • Experience at a fast-moving, hardware-focused startup or early-stage spacecraft program.

  Compensation And Benefits

  The salary range for this position is $150,000 – $180,000 annually. The actual base salary offered will depend on factors such as job-related skills, experience, qualifications, and internal equity.

  • Equity in Cowboy Space Corp.
  • Employees and their eligible dependents may enroll in medical, dental, and vision insurance
  • 401(k) retirement savings plan
  • Paid time off
  • 10 paid holidays per calendar year
  • Paid parental leave
  • Relocation assistance if applicable
  • Daily lunch in the office and a fully stocked kitchen with beverages and snacks
  We should not include any other sections like About Cowboy Space Corp Mission because that's not a standard heading; but could be considered "About the role"? Actually "About Cowboy Space Corp Mission" is introductory background; but rules say we should only include sections when posting has real, specific content for it. The heading "About the role" is already used for role description. The introductory background about company could be omitted? It's not under a standard heading; but we could include it as a

  before the role? The instructions: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says to use those for those sections. It also says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't say we cannot include other headings like "About Cowboy Space Corp Mission". However, the list of examples suggests those are the expected sections. The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The posting does have content about mission; but it's not under a standard heading. Should we create a section for it? The examples didn't include "About the company" but we could treat it as a section maybe "About Cowboy Space Corp". However, the instruction says to prefer a few substantive sections over many thin ones. The mission description is substantive but could be considered part of the role? Might be okay to include as a

  before the role without a heading. The instruction says to use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow the pattern. Usually these tasks expect only those standard headings. I'd output only the sections we identified: About the role, Responsibilities, Basic Qualifications, Preferred Qualifications, Compensation And Benefits. That seems sufficient. Check that we didn't miss any substantive info like "Current energy and data systems rely on complex logistics..." that's company background; we omitted it. Might be considered substantive but not under a standard heading. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that background, we are losing substantive info. But maybe it's considered boilerplate? It's describing the company mission; not boilerplate but could be considered relevant. However, the instruction also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company mission is not boilerplate; it's substantive. Should we include it? Perhaps we can include it as a

  before the role without a heading, or under a heading like "About Cowboy Space Corp". But the examples didn't list that; but we could still use

  for "About Cowboy Space Corp". The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we could add a heading for company overview. However, they also say "Prefer a few substantive sections over many thin ones." Adding a company overview section would increase sections. But we could incorporate that info into the About the role section? It's not about the role; it's about the company. Could we add a brief paragraph before the role heading? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities...)" but doesn't say we must have headings for every paragraph. So we could have an introductory

  without heading, then the headings. That would preserve the info without adding a section. That seems acceptable: we can put a

  with the company mission description before the About the role heading. That would not be a section heading, just a paragraph. The instruction says "Use

  for section headings (e.g. About the role