Senior Payload Engineer, Spacecraft Programmes

We need to output HTML fragment with sections only if real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections based on content. Let's parse the posting: - Requisition Number: 20341 (metadata) - Contract Type: Permanent - Location(s): Sterling, VA, US - Title: Senior Payload Engineer, Spacecraft Programmes Then description: "The job responsibilities outlined in this document are not exhaustive..." etc. We need to include sections: About the role (role description summary), Responsibilities (primary responsibilities), Requirements (maybe qualifications & experience, other key requirements), Skills (competencies), Benefits (maybe not explicit), Pay (salary range), Schedule (maybe not explicit). We must only include sections if posting has real specific content. Let's identify content: - About the role: Role Description Summary paragraph(s). We have "Role Description Summary As Senior Payload Engineer, Space Programmes, you will be responsible for providing resident payload (repeater and antenna subsystems) engineering support to all phases of the satellite procurement programs which includes daily oversight of Design, Assembly, Integration, and Launch Campaign. You will be part of the SES Resident Field Office Team located at spacecraft manufacturer premises. You will support the Field Office in addressing product assurance and quality oversight of all aspects of the project. You will review and trend the test data for the payload equipment at unit and subsystems level tests and provide technical support to the Field Office Program Manager on investigations, resolutions and corrective actions." That's substantive. - Responsibilities: "Primary Responsibilities / Key Results Areas" list many bullet-like sentences. We can extract them as list items. - Requirements: There's "Qualifications & Experience" and "Other Key Requirements / Comments". Could be combined into Requirements section. But we have separate sections for Qualifications and Skills. The instruction says use headings like Qualifications, Skills. So we can put qualifications under

Qualifications

and skills under

Skills

. Requirements maybe not needed if we split. But we need to decide: The allowed headings list includes Requirements as possible. We can use it if we have content. However we also have Qualifications and Skills separate. The posting includes "Qualifications & Experience" and "Competencies". So we can map Qualifications to Qualifications heading, Competencies to Skills heading. The "Other Key Requirements / Comments" could go under Requirements or maybe under Qualifications. We'll treat as Requirements. - Benefits: Not explicit. There's mention "Additional compensation and benefits may apply depending on the location and terms of employment." That's vague, not specific. So we should not create Benefits section because no specific benefits listed. - Pay: Salary range given: "$121,000 - $180,000". Also mention salary ranges determined by role etc. That's specific enough to include Pay section. - Schedule: Not explicit. There's "Willing to work at least 80% onsite from office" and travel 30% domestic/international. That's about work arrangement, not schedule (hours). No explicit schedule like full-time, part-time, shift. Could infer full-time but not explicit. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not stated, so omit. Thus sections: About the role, Responsibilities, Qualifications, Skills, Requirements (maybe Other Key Requirements), Pay. We need to ensure we don't repeat job title as heading. Use

for each. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end: "SES and its Affiliated Companies are committed to providing fair and equal employment opportunities...". That's boilerplate; remove. Also "For more information on SES, click here." Remove. Also "Nearest Major Market: Washington DC" maybe location metadata; we can keep location? It's not a heading but could be part of location metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph with Requisition Number, Contract Type, Location(s). Possibly also Nearest Major Market. But we should not duplicate location. We'll include a short paragraph at top maybe. We must not repeat the job title as a heading. So we won't have

  Senior Payload Engineer... etc. We need to output only HTML fragment. Let's craft:

  Requisition Number: 20341 | Contract Type: Permanent | Location: Sterling, VA, US | Nearest Major Market: Washington DC

  But we should avoid using ? Not prohibited. It's okay. Could just plain text. Better:

  Requisition Number: 20341 • Contract Type: Permanent • Location: Sterling, VA, US • Nearest Major Market: Washington DC

  Now sections:

  About the role

  As Senior Payload Engineer, Space Programmes, you will be responsible for providing resident payload (repeater and antenna subsystems) engineering support to all phases of the satellite procurement programs which includes daily oversight of Design, Assembly, Integration, and Launch Campaign. You will be part of the SES Resident Field Office Team located at spacecraft manufacturer premises. You will support the Field Office in addressing product assurance and quality oversight of all aspects of the project. You will review and trend the test data for the payload equipment at unit and subsystems level tests and provide technical support to the Field Office Program Manager on investigations, resolutions and corrective actions.

  Responsibilities

  • Ensure that the specification of each payload equipment unit is consistent with meeting the end-to-end system performance and functional requirements
  • Ensure that all payload units, subsystem and system test procedures comply with the contractual requirements
  • Participate in design, test readiness, material and failure review meetings at manufacturer sub- and prime- contractor facilities as needed
  • Monitor flow of payload components through build, test and integration into next higher assembly
  • Critically examine the anomaly investigation results in root cause analysis and verify corrective actions are implemented
  • Provide daily oversight of Design, Assembly, Integration, Test, and Launch phases
  • Provide daily oversight of activities at Manufacturer and Subcontractor facilities as needed
  • Ensure that the specification of each payload equipment unit meets the end-to-end system performance and functional requirements
  • Perform in process inspections with manufacturers
  • Perform the equipment and Spacecraft repeater and antenna test data review for compliance with contractual requirements
  • Contribute digital payload expertise to innovation projects pursued by technology in interaction with the satellite manufacturer
  • Contribute digital payload expertise to RFI/RFP discussions with the satellite manufacturer
  • Support the SES Product Assurance Lead in MPCB, PCB, and RCB meetings, as well as in the review and approval of EEE parts, materials, mechanical parts, and processes
  • Monitoring integration and test activities with quality assurance audits, mandatory and key inspection points, test witnessing and configuration inspections
  • Critically examine the anomaly investigation results to root cause analysis and verify corrective actions are implemented
  • Review design, manufacturing and test documentation
  • Provide summary reports of issues and recommended actions
  • Ensure that the program action items are adequately addressed and closed
  • Provide 24/7 on call support during payload system testing
  • Support Payload In Orbit Testing (PIOT) post launch activities
  • Flexible to work across various projects as required
  • Act as Payload expert for other people in SES Group and to satellite users pertaining to satellite performance. Support end-to-end design solutions. Requires a thorough understanding of end-to-end communications link budgets and infrastructure
  • Develop training material and provide technical training to satellite engineering team

  Note there may be duplicate items: "Ensure that the specification..." appears twice. We should keep both? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate. Let's identify duplicates: - "Ensure that the specification of each payload equipment unit is consistent with meeting the end-to-end system performance and functional requirements" - Later: "Ensure that the specification of each payload equipment unit meets the end-to-end system performance and functional requirements" These are similar but not identical; one says "consistent with meeting", the other "meets". Might be considered duplicate in meaning but not exact text. The instruction says duplicated lines, likely exact duplicates. We'll keep both as they are slightly different. - "Critically examine the anomaly investigation results in root cause analysis and verify corrective actions are implemented" - Later: "Critically examine the anomaly investigation results to root cause analysis and verify corrective actions are implemented" Again slight variation; keep both. - "Provide daily oversight of Design, Assembly, Integration, Test, and Launch phases" appears once. - "Provide daily oversight of activities at Manufacturer and Subcontractor facilities as needed" appears once. Ok. Now Qualifications section:

  Qualifications

  • Master’s degree or PhD in Telecommunications, Electrical Engineering or related discipline
  • 7+ years of applicable experience in Space Engineering
  • Experience with payload mission specification and operations
  • Experience with analogue and digital payload equipment
  • Experience with repeater and/or antenna subsystems
  • Experience with link budgets and repeater RF performance measurement
  • Strong ability in persuasive and diplomatic communication to inspire collaboration and drive collective goal achievement
  • Strong ability to work independently and with limited supervision in complex environments, including multi-stakeholder projects

  Now Skills (Competencies):

  Skills

  • High level knowledge in satellite payload subsystems and ability to challenge industry expert in their field
  • Self-Starter with a high level of personal accountability
  • Prioritization
  • Team Player
  • Demonstrated influencing and negotiation skills
  • A willingness to be self-critical, continuously improves skills, learn from mistakes, acts within her or his circle of competence and knows their boundaries

  Now Requirements (Other Key Requirements / Comments): We have "Willing to work at least 80% onsite from office" and "Willingness to travel (supplier visits) - 30% domestic and international travel". Also maybe "Other Key Requirements / Comments". We'll put as list.

  Requirements

  • Willing to work at least 80% onsite from office
  • Willingness to travel (supplier visits) - 30% domestic and international travel

  Now Pay:

  Pay

  The USA salary range for this full-time position is $121,000 - $180,000. Salary ranges are determined by role, level, and geographic location. Individual compensation within the range is determined based on work location and a variety