Mechanical Test Engineer I
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- About Rocket Lab (company description) – could be "About the role"? Actually "About the role" is a typical heading but we have company overview. Could use "About the role" for description of role? The posting includes "MECHANICAL TEST ENGINEER I Based out of Rocket Lab’s global headquarters in Long Beach, CA, the Mechanical Test Engineer I is responsible for supporting the design, build, and execution of internal test capabilities." That's role description. Then "What You’ll Get To Do" list of duties. Then "QUALIFICATIONS YOU’LL BRING AS A MECHANICAL TEST ENGINEER I:" list of qualifications. Then "These Qualifications Would Be Nice To Have" list of nice-to-have. Then some physical demands and equity grant info. Then benefits description. Then pay range. Then "What To Expect" (culture). Then important information about ITAR, EEO, accommodation request, etc. Those are legal boilerplate; we should remove EEO/equal-opportunity etc. Also remove accommodation request? It's not exactly EEO but it's about reasonable accommodation; might be considered legal boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the ITAR and EEO sections, also the accommodation request (maybe considered legal). Also remove the "Important Information FOR CANDIDATES SEEKING TO WORK IN US OFFICES ONLY:" and the NZ section. Those are legal. So we drop those.
We need to keep substantive info: company overview, role description, responsibilities list, qualifications list, nice-to-have list, benefits, pay range. Also maybe "What To Expect" (culture) could be a section? Could be "About the role" or "What To Expect". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have responsibilities (What You’ll Get To Do). We have qualifications (required). We have nice-to-have (could be Skills?). We have benefits. We have pay (salary range and equity). We have schedule? Not mentioned. So we may not include Schedule.
We also have "About Rocket Lab" and "SPACE SYSTEMS" which is company overview; could be placed under "About the role"? Actually About the role is more about the role, but we could also include a brief company overview under About the role or maybe a separate section like "About Rocket Lab". However the instruction only lists certain headings; but we can use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples; we could also use other headings if needed, but better to stick to those. We could put company overview under "About the role". Or we could have a preceding
before any headings? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid having a paragraph before headings. So we could start with a
containing the company overview (About Rocket Lab and SPACE SYSTEMS). Then
About the role
with role description paragraph. Then Responsibilities
with of duties. Then Qualifications
with of required qualifications. Then Skills
with of nice-to-have. Then Benefits
with of benefits. Then Pay
with containing salary range and equity info. Possibly also include "What To Expect" as a section? Could be under "About the role" or separate but not in list. Might be okay to add a
What To Expect
but not in the examples; but instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could incorporate that into About the role or maybe a separate
after Qualifications. However "What To Expect" is substantive culture description; we could include as a section named "What To Expect". The instruction says "include a section ONLY when the posting has real, specific content for it". It does have content. So we could add a heading "What To Expect". It's not in the examples but it's okay as a heading. However they gave examples; they didn't say you must only use those. Safer to stick to examples. Could we put "What To Expect" under "About the role"? Might dilute. But we could add a
About the role
that includes both role description and what to expect. That's acceptable.
Thus sections: About the role (company overview + role description + what to expect), Responsibilities, Qualifications, Skills, Benefits, Pay.
We need to ensure we don't include filler like "Level and base salary will be determined on a case-by-case basis..." That's part of Pay section; we can include that as prose.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content.
Company overview:
"About Rocket Lab Rocket Lab is the end-to-end space company building rockets, spacecraft, and critical subsystems that keep the world connected, protected, expand humanity’s reach to the Moon, Mars, and beyond. We move fast, build real hardware for meaningful missions, and make the impossible routine. Come shape the future with us. SPACE SYSTEMS At Rocket Lab, we’re not just launching rockets — we're building the future of space. Our Space Systems team builds everything from complete spacecraft, precision payloads to the components and subsystems that allow them to thrive in space, like solar panels, flight software, star trackers, optical systems, separation systems, radios, and more. Our Space Systems team has enabled more than 1,700 missions, ranging from interplanetary exploration, in-space manufacturing to national security and defense initiatives. The team has built spacecraft, payloads, and components for missions to the Moon and Mars, working with partners including NASA, the Space Development Agency, and the U.S. Space Force. Whether it’s a single high-performance spacecraft, constellation, or the vertically integrated components that help them get to space — our world class Space Systems team is empowering some of the boldest and most ambitious space missions."
We can combine into a paragraph.
Role description:
"MECHANICAL TEST ENGINEER I Based out of Rocket Lab’s global headquarters in Long Beach, CA, the Mechanical Test Engineer I is responsible for supporting the design, build, and execution of internal test capabilities. This may include assisting with test setups for qualification and acceptance tests for satellite components and systems. Hardware tests may include avionics boxes, complex mechanisms, and fully integrated spacecraft in stressing environments."
Then "What You’ll Get To Do" list:
- Assist in the preparation and execution of qualification and acceptance test campaigns.
- Support the development and maintenance of test infrastructure and equipment.
- Perform hands-on assembly and disassembly of test setups, including instrumentation and data acquisition systems.
- Collaborate with senior engineers to ensure test setups meet design and safety requirements.
- Document test procedures, results, and lessons learned.
- Troubleshoot and resolve issues during testing under the guidance of senior engineers.
- Ensure compliance with safety and quality standards during test operations.
Qualifications (required):
- Bachelor’s degree in mechanical engineering, aerospace engineering, or a related field.
- 0+ years of experience in mechanical testing, aerospace, or a related field (internship experience is acceptable).
- Familiarity with CAD software (e.g., NX, SolidWorks, or similar).
- Basic understanding of mechanical systems and testing principles.
- Strong problem-solving skills and attention to detail.
Nice-to-have:
- Experience with data acquisition systems and instrumentation.
- Familiarity with environmental testing (thermal, vibration, shock).
- Experience with Python or MATLAB for data analysis.
- Hands-on experience with mechanical assembly or prototyping.
Physical demands: "This position may require prolonged periods of sitting, standing, walking, computer work, and occasional exposure to moderate levels of noise, dust, and fumes in production areas." This is substantive; could be included under Qualifications or a separate section like "Work Environment". Not in headings list but could be added as a paragraph under Qualifications or maybe under About the role. We'll include as a paragraph under Qualifications maybe after the list.
Equity grant: "Anticipated annual equity grant value is designed around function, level, experience, and other factors; realized value depends on vesting and stock-price performance.Join one of the world's fastest-growing space companies and own a piece of it. In addition to competitive base pay, you'll receive company stock as part of your total compensation package, giving you a direct stake in our success. As we expand to new launch sites, groundbreaking missions, and global markets, your ownership has the opportunity to grow alongside the company."
Benefits: "Our comprehensive benefits package includes our industry-leading Employee Stock Purchase Program (with a 15% discount on company stock), top-tier medical plans (HMO, PPO, and a zero cost HDHP option with a significant HSA company contribution), dental and vision coverage, paid vacation and sick time, 11 paid holidays, flexible spending and dependent care accounts, paid parental leave, disability and life insurance, and a 401(k) retirement plan with company match.Additional perks include subsidized EV charging, onsite fitness centers (where available), discounted gym memberships, complimentary snacks and beverages, 50% employee discount on our popular merch store, and a variety of other employee discounts."
Pay: "Level and base salary will be determined on a case-by-case basis and may vary based on the following considerations: job-related knowledge and skills, education, and experience. Total Compensation (base and equity): $90,150 USD - $116,025 USD Base Salary: $83,200 USD - $106,080 USD"
What To Expect: "We’re on a mission to unlock the potential of space to improve life on Earth, but that’s not an easy task. It takes hard work, determination, relentless innovation, teamwork, grit, and an unwavering commitment to achieving what others often deem impossible. Our people out-think, out-work, and out-pace. We pride ourselves on having each
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - About Rocket Lab (company description) – could be "About the role"? Actually "About the role" is a typical heading but we have company overview. Could use "About the role" for description of role? The posting includes "MECHANICAL TEST ENGINEER I Based out of Rocket Lab’s global headquarters in Long Beach, CA, the Mechanical Test Engineer I is responsible for supporting the design, build, and execution of internal test capabilities." That's role description. Then "What You’ll Get To Do" list of duties. Then "QUALIFICATIONS YOU’LL BRING AS A MECHANICAL TEST ENGINEER I:" list of qualifications. Then "These Qualifications Would Be Nice To Have" list of nice-to-have. Then some physical demands and equity grant info. Then benefits description. Then pay range. Then "What To Expect" (culture). Then important information about ITAR, EEO, accommodation request, etc. Those are legal boilerplate; we should remove EEO/equal-opportunity etc. Also remove accommodation request? It's not exactly EEO but it's about reasonable accommodation; might be considered legal boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the ITAR and EEO sections, also the accommodation request (maybe considered legal). Also remove the "Important Information FOR CANDIDATES SEEKING TO WORK IN US OFFICES ONLY:" and the NZ section. Those are legal. So we drop those. We need to keep substantive info: company overview, role description, responsibilities list, qualifications list, nice-to-have list, benefits, pay range. Also maybe "What To Expect" (culture) could be a section? Could be "About the role" or "What To Expect". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have responsibilities (What You’ll Get To Do). We have qualifications (required). We have nice-to-have (could be Skills?). We have benefits. We have pay (salary range and equity). We have schedule? Not mentioned. So we may not include Schedule. We also have "About Rocket Lab" and "SPACE SYSTEMS" which is company overview; could be placed under "About the role"? Actually About the role is more about the role, but we could also include a brief company overview under About the role or maybe a separate section like "About Rocket Lab". However the instruction only lists certain headings; but we can use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples; we could also use other headings if needed, but better to stick to those. We could put company overview under "About the role". Or we could have a preceding
before any headings? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid having a paragraph before headings. So we could start with a
containing the company overview (About Rocket Lab and SPACE SYSTEMS). Then
About the role
with role description paragraph. ThenResponsibilities
with- of duties. Then
Qualifications
with- of required qualifications. Then
Skills
with- of nice-to-have. Then
Benefits
with- of benefits. Then
Pay
withcontaining salary range and equity info. Possibly also include "What To Expect" as a section? Could be under "About the role" or separate but not in list. Might be okay to add a
What To Expect
but not in the examples; but instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could incorporate that into About the role or maybe a separate
after Qualifications. However "What To Expect" is substantive culture description; we could include as a section named "What To Expect". The instruction says "include a section ONLY when the posting has real, specific content for it". It does have content. So we could add a heading "What To Expect". It's not in the examples but it's okay as a heading. However they gave examples; they didn't say you must only use those. Safer to stick to examples. Could we put "What To Expect" under "About the role"? Might dilute. But we could add a