Integration Technician I, Thrust Structure

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "At Relativity Space, we’re building rockets..." intro? That's not a section heading; it's prose. Should we keep it? It's part of the description, not under a heading. We can keep as

before sections? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements...). 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." Thus we need to extract sections: About The Team, About The Role, About You, Nice To Haves But Not Required, compensation info, benefits, schedule. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: About The Team (maybe not a standard heading but could be considered About the role? Actually "About The Team" is separate. Could map to "About the role"? Not exactly. But we can create a section "About the team" not in list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings if applicable; but we can also use other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we need to map content to those. We have "About The Team" - could be considered "About the role"? Not exactly but maybe we can treat as "About the role" (since it's about the team). But we also have "About The Role" separate. Could combine? Might be better to have two sections: "About the role" (covering About The Role) and maybe "About the team" not allowed. Could we omit About The Team? It contains substantive info about manufacturing team responsibilities, schedule, etc. That info is important: schedule (first-shift, Monday-Friday 5:00 a.m. to 3:30 p.m. PT, 50-hour workweek including 10 guaranteed overtime). That's schedule info. Also responsibilities of manufacturing team. Could fit under Responsibilities? Possibly. We need to preserve ALL substantive information. So we need to include schedule details somewhere. The schedule heading is allowed. So we can put schedule info under

  Schedule

  . Also we have Pay info: hiring range $25.58—$38.37 USD. That's pay. So

  Pay

  . Benefits: they mention competitive salary and equity, generous PTO and sick leave, parental leave, annual learning and development stipend, etc. So

  Benefits

  . Responsibilities: we have details about Integration technician role: ensuring components assembled, tested, installed; operate fast-paced; collaborate; primary area of focus assembly, install, testing of flight hardware through development and production of Thrust Structure for Terran R, including Secondary Structures, Fluids Systems, Avionics Systems, Engine Installations. Also manufacturing team responsibilities: factory floor layout, developing complex tooling, interfacing with vehicle engineering, translate engineering requirements into optimized production lines, cross functionally enhance vehicle program. Could combine. Requirements: "About You" list: 1+ years aerospace mechanical experience or related field; experience in fast-paced production environment handling flight hardware; wide range of technical skills including fastener/torque applications, secondary retention, testing, avionics familiarity, bonding operations; ability to communicate; ability to set up and operate hand/pneumatic tools, calibrated tools, measuring devices; able to climb ladders, work in tight spaces; navigate uneven terrain; crouch, bend, squat; kneel; reach arms overhead. Those are requirements/qualifications. Skills: maybe the technical skills list could be under Skills. But we already have them in About You. Could separate: Requirements (experience, education) and Skills (technical abilities). Qualifications maybe similar. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate: EEO statement, accommodation contact, unsolicited resumes note, etc. Remove those. Also remove duplicated lines: maybe "At Relativity Space, we are committed to transparency and fairness in our compensation practices." That's not boilerplate but maybe part of compensation. Keep? It's substantive about compensation practices. Could keep as part of Pay section. Also "Compensation is only one part of our total rewards package." Keep. Now produce HTML fragment. Structure: maybe start with a

  for introductory paragraph(s) before sections? The intro paragraph about building rockets etc. Could keep as

  . Then sections. We must not include markdown fences. Let's draft:

  At Relativity Space, we’re building rockets to serve today’s needs and tomorrow’s breakthroughs. Our Terran R vehicle will deliver customer payloads to orbit, meeting the growing demand for launch capacity. But that’s just the start. Achieving commercial success with Terran R will unlock new opportunities to advance science, exploration, and innovation, pioneering progress that reaches beyond the known. Joining Relativity means becoming part of something where autonomy, ownership, and impact exist at every level. Here, you're not just executing tasks; you're solving problems that haven’t been solved before, helping develop a rocket, a factory, and a business from the ground up. Whether you’re in propulsion, manufacturing, software, avionics, or a corporate function, you’ll collaborate across teams, shape decisions, and see your work come to life in record time. Relativity is a place where creativity and technical rigor go hand in hand, and your voice will help define the stories we’re writing together. Now is a unique moment in time where it’s early enough to leave your mark on the product, the process, and the culture, but far enough along that Terran R is tangible and picking up momentum. The most meaningful work of your career is waiting. Join us.

  Then sections:

  About the role

  The Integration technician role will play a critical role in ensuring that various components and systems of flight hardware are assembled, tested, and installed with the highest quality. The role requires a combination of technical skills, attention to detail, and knowledge of aerospace processes. Ability to operate in a fast-paced manufacturing environment to successfully build and install flight hardware. Collaborate with the production team, integration engineers and quality team to build, develop, and document job operations. Primary area of focus will be assembly, install, and testing of flight hardware through development and production of Thrust Structure for Terran R. Including Secondary Structures, Fluids Systems, Avionics Systems, and Engine Installations.

  Maybe also include About The Team content under About the role? Could add another paragraph about team responsibilities. But we have separate About The Team. Could we add another

  About the team

  ? Not in allowed list but maybe okay? The 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 says "use

  for section headings (e.g ...)". It implies those are examples; we could still use other headings but better to stick to those. However we need to preserve team info. Could incorporate into Responsibilities or About the role. Let's add a paragraph under About the role about the Manufacturing team: "The Manufacturing team owns all process development, fabrication strategy, and production equipment for Terran R, our next generation, reusable rocket. This team has a wide variety of responsibilities – from factory floor layout, to developing complex tooling for novel processes, and interfacing with our vehicle engineering team to heavily influence design of the rocket. We leverage our deep expertise to translate engineering requirements into highly optimized production lines, working cross functionally to consistently enhance the vehicle program." That seems fine. Now Responsibilities: maybe we can list duties as

  • . But we already have prose. Could create a Responsibilities section with list of duties: ensure assembly/test/install; operate fast-paced; collaborate; primary focus; etc. But we already have that in About the role. To avoid duplication, maybe we keep About the role as prose and Responsibilities as list of specific duties. However we risk missing some info if we split. But we can keep About the role as overview and Responsibilities as detailed list. Let's extract duties: - Ensure various components and systems of flight hardware are assembled, tested, and installed with highest quality. - Operate in a fast-paced manufacturing environment to build and install flight hardware. - Collaborate with production team, integration engineers, and quality team to build, develop, and document job operations. - Primary focus: assembly, install, and testing of flight hardware through development and production of Thrust Structure for Terran R, including Secondary Structures, Fluids Systems, Avionics Systems, and Engine Installations. - Manufacturing team responsibilities: factory floor layout, developing complex tooling for novel processes, interfacing with vehicle engineering to influence rocket design, translating engineering requirements into optimized production lines, working cross-functionally to enhance vehicle program. We can put those under Responsibilities as
    . Now Requirements: maybe experience and education: 1+ years aerospace mechanical experience or related field; experience in fast-paced production environment handling flight hardware; ability to communicate; ability to set up and operate tools; physical demands (climb ladders, tight spaces, uneven terrain, crouch/bend/squat, kneel, reach overhead). Could be under Requirements. Qualifications: maybe similar; but we can combine Requirements and Qualifications? Better to separate: Requirements = experience and education; Qualifications = technical skills and abilities? But we also have Skills section for technical skills. Let's define:

    Requirements

    • 1+ years of aerospace mechanical experience or related field.
    • Experience working in a fast-paced production environment handling flight hardware and performing critical operations.
    • Ability to effectively communicate (verbal and written) with engineering and production.
    • Ability to set up and operate a wide range of hand and pneumatic tools along with calibrated tools and measuring devices.
    • Must be able to climb ladders and be comfortable working in tight spaces.
    • Able to safely navigate and walk on uneven terrain or surfaces, as frequently required in the work environment.
    • Able to frequently crouch, bend, or squat to access low-level areas or equipment.
    • Able to kneel to perform work duties, as needed throughout a shift (Personal Protective Equipment provided).
    • Able to reach and extend arms overhead for the duration required to complete assembly tasks.

    Skills

    • Fastener/torque applications
    • Secondary retention
    • Testing
    • Avionics familiarity
    • Bonding operations
    Nice To Haves But Not Required: could be under Skills as optional? Or we could add a separate section "Nice-to-haves" but not in allowed list. Could incorporate into Skills as a note? Might be better to add a