Senior Systems Engineer, On-Orbit Test Coordinator

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 include only sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the posting. Company Overview: description of Iridium and Aireon. Could be "About the role"? Actually "Company Overview" could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role (maybe includes company overview and what we're looking for). Responsibilities: "What You’ll Do". Requirements/Qualifications/Skills: "What You’ll Need to Succeed" and "Things That Would be Great if You Brought to the Table". Benefits: "Employee benefits also include ...". Pay: "Base Pay Range: $115,000 - $155,000 USD". Schedule: "You will work 12-hour shifts with a team onsite in a 24/7, multi-satellite operations environment." Also "Be able to work shifts of four days on, four days off, with 12 hours a day expected per shift". Also "Under Iridium’s Hybrid Work Policy, employees are expected to work at least four days per week (approximately 80%) in an Iridium office". So schedule details. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. Need to ensure we preserve all substantive info. We need to output only HTML fragment, no /, no markdown fences. Let's craft sections:

About the role

Company overview: Iridium is an award-winning satellite communications company operating the world's only truly global voice and data network, delivering reliable connectivity anywhere on Earth. For more than 20 years, Iridium has powered mission-critical communications for governments, businesses, aviation, maritime, and the rapidly expanding Internet of Things. Now part of Iridium, Aireon is the world’s only space-based air traffic surveillance system, providing real-time visibility of aircraft over oceans, the poles, and remote regions. Together, Iridium and Aireon are helping build a safer, more connected, and more efficient future for global aviation. We foster a collaborative, inclusive culture where employees are empowered to innovate, grow professionally, and make a meaningful impact.

Maybe also include "What We’re Looking For:" but that could be part of About the role or Responsibilities. Probably better to put that in About the role. But we have separate sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Responsibilities: "What You’ll Do:" list of duties. We'll put as

• items. Requirements: maybe "What You’ll Need to Succeed:" includes degree, 8+ years experience, knowledge, etc. Could be Requirements. Qualifications: maybe "Things That Would be Great if You Brought to the Table:" could be Qualifications or Skills. But we have Skills section separate. Could treat "Things That Would be Great if You Brought to the Table:" as Skills (preferred qualifications). Or we could have Qualifications for mandatory, Skills for preferred. Let's map: - About the role: company overview + what we're looking for (experienced systems engineer with background in space systems architecture and design, at least 8 years experience, Senior Systems Engineer opening with Iridium on SDA Project). Also mention interface etc. - Responsibilities: the bullet list under "What You’ll Do:" (starting "Lead the on-orbit checkout..."). - Requirements: "What You’ll Need to Succeed:" bullet list (degree, 8+ years, strong knowledge, etc.) - Skills: "Things That Would be Great if You Brought to the Table:" bullet list (Top-Secret clearance, IC/DoD acquisition background, orbital mechanics, programming languages, Atlassian, SAFe). Also maybe "Be able to travel up to 10% of the time", "Be a US Citizen", "Be able to work shifts...". Those could be Schedule or Requirements? Travel and citizenship maybe Requirements. But we have Schedule section for shift details. Travel and citizenship could be under Requirements or maybe a separate section but we only have allowed headings. Could put them under Requirements as well. - Benefits: paragraph about benefits. - Pay: Base Pay Range. - Schedule: shift details, hybrid work policy. We must not include duplicated lines. Ensure we capture all substantive info. Let's extract details. Company Overview paragraph: as above. What We’re Looking For: "If you are an experienced systems engineer with a background in space systems architecture and design, and have at least 8 years of experience, you will be excited about the Senior Systems Engineer opening with Iridium on our SDA (Space Development Agency) Project. As a Senior Systems Engineer, you’ll be responsible for interfacing between the Iridium Operations team supporting the SDA and the Iridium System Engineering team in developing artifacts associated with the operations of the mesh network and ground segment. You will provide critical operations and integration support to improve our efficiency and effectiveness by implementing processes, procedures, checklists, and software tools for ground and satellite operations. Working in this role, you’ll interface with the U.S. government in dealing with Iridium generated and delivered System Engineering documents that govern operations at the SDA operation centers. You’ll also be responsible for the design, development and maintenance of functional on-orbit test procedures, working with multiple satellite vendors to ensure synergy of on-orbit tests, assist the SDA in the development of operational test procedures, and act as a liaison between the space contractors, ground contractors and government team during operations. You will work 12-hour shifts with a team onsite in a 24/7, multi-satellite operations environment. You will thrive in this role if you enjoy tackling complex challenges and working in a fast-paced, dynamic environment. This position requires an active/current Secret Security Clearance (A U.S. Security Clearance that has been active in the past 24 months is considered active)." Note: Some of this overlaps with Responsibilities etc. But we need to preserve all substantive info, not duplicate. We'll need to decide where to place each piece to avoid duplication. Better approach: Keep About the role as company overview + what we're looking for (high-level). Responsibilities as the detailed "What You’ll Do:" list. Requirements as "What You’ll Need to Succeed:" list. Skills as "Things That Would be Great if You Brought to the Table:" list. Benefits as benefits paragraph. Pay as base pay range. Schedule as shift details and hybrid work policy. But we must ensure we don't duplicate info that appears in multiple places. For example, the "You will work 12-hour shifts..." appears in What We’re Looking For and also later in schedule. We'll include schedule details only once, maybe under Schedule. The "active/current Secret Security Clearance" appears in What We’re Looking For and also later under Things That Would be Great (Top-Secret). We'll include clearance requirements under Requirements (maybe as mandatory Secret) and preferred Top-Secret under Skills. We need to capture all details: From What We’re Looking For: - experienced systems engineer with background in space systems architecture and design - at least 8 years of experience - Senior Systems Engineer opening with Iridium on SDA Project - responsible for interfacing between Iridium Operations team supporting SDA and Iridium System Engineering team developing artifacts associated with operations of mesh network and ground segment - provide critical operations and integration support to improve efficiency and effectiveness by implementing processes, procedures, checklists, and software tools for ground and satellite operations - interface with U.S. government dealing with Iridium generated and delivered System Engineering documents that govern operations at SDA operation centers - responsible for design, development and maintenance of functional on-orbit test procedures, working with multiple satellite vendors to ensure synergy of on-orbit tests, assist SDA in development of operational test procedures, act as liaison between space contractors, ground contractors and government team during operations - will work 12-hour shifts with a team onsite in a 24/7, multi-satellite operations environment - thrive if enjoy tackling complex challenges and fast-paced dynamic environment - position requires active/current Secret Security Clearance (active in past 24 months considered active) Now Responsibilities (What You’ll Do): List: - Lead the on-orbit checkout and commissioning of a satellite and its ground segment, serving as the primary technical point of contact for all related activities - Develop, author, and execute detailed test plans and procedures for a variety of on-orbit activities, including payload activation, spacecraft subsystem checkouts, and system performance validation - Coordinate and lead integrated test teams, including operators, analysts, and subsystem engineers, to ensure seamless execution of on-orbit checkout procedures and anomaly resolution - Analyze telemetry data in real-time during checkout events to assess system health and performance, identify anomalies, and provide critical insights to the mission team - Conduct root cause analysis for any on-orbit anomalies or performance deviations, working with design engineers and subject matter experts to develop and implement effective solutions - Prepare and present technical briefings to senior leadership and stakeholders, providing updates on mission status, checkout progress, and any identified risks or issues - Develop and maintain comprehensive documentation related to the on-orbit checkout process, including test reports, anomaly logs, and final system performance reports - Generate and develop test procedures, in conjunction with existing plans for on-orbit test procedures - Be responsible for the disposition and maintenance of test procedures - Generate and develop System Engineering documentation as it relates to SDA Operations - Work with satellite vendors to ensure synergy of on-orbit tests - Be responsible for assigned documentation within SharePoint, Microsoft Teams, or other relevant Iridium databases or tools - Collaborate with SDA and Iridium program leadership to assess risks and provide recommendations for improvement to on-orbit operations - Provide technical writing assistance in the development of Basis of Efforts (BOE) - Interface between the Iridium Operations team supporting the SDA and the Iridium System Engineering team in developing artifacts associated with the operations of the mesh network and ground segment - Provide integration support to improve our efficiency and effectiveness by implementing processes, procedures, checklists, and software tools for ground and satellite operations Note some duplicates with earlier list (e.g., interfacing, integration support). We'll keep them but ensure not duplicate exact sentences? Might be okay but we should avoid duplication. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication if it's in original. But better to avoid duplicate sections. We could merge but risk losing some nuance. However we can keep both as they are separate bullet points; duplication may be okay but we should try to avoid repeating same sentence. Let's see: The "Interface between the Iridium Operations team supporting the SDA and the Iridium System Engineering team in developing artifacts associated with the operations of the mesh network and ground segment" appears both in What We’re Looking For and Responsibilities. Also "Provide integration support to improve our efficiency and effectiveness by implementing processes, procedures, checklists, and software tools for ground and satellite operations" appears both. We could keep only one occurrence, but we risk losing info? The info is same; keeping one is fine as it's still preserved. We'll deduplicate. Now Requirements (What You’ll Need to Succeed): List: - Bachelor’s degree in aerospace engineering, electrical engineering, or related field, OR equivalent on-orbit test experience in lieu of a degree - 8+ years of relevant experience in satellite operations, satellite on-orbit testing, ground system engineering, software integration and test, and/or software development - Strong knowledge of system engineering methodologies and AGILE processes - Strong familiarity with tools and software applications that support system engineering best practices