Senior Architect, Systems Verification & Validation, meoSphere

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID/requisition numbers as headings; fold minor metadata into short p or drop. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to parse the posting. Key parts: - Requisition Number: 20394 (metadata) - Contract Type: Permanent - Location(s): Betzdorf, LU; McLean, US, 22102-5971 - Title: Senior Architect, Systems Verification & Validation, meoSphere (but we don't repeat as heading) - The job responsibilities outlined ... (some generic statement) maybe not needed? It's boilerplate? It says "The job responsibilities outlined in this document are not exhaustive and may evolve over time and be reviewed according to business needs." That's generic; we can drop as boilerplate. - Programme Description: description of meoSphere. That's substantive; could be under "About the role" maybe? Actually "About the role" is typical heading for role description summary. We have "Role Description Summary" after Programme Description. So we can put Programme Description under "About the role" or maybe separate "About the program". But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have: - Role Description Summary: description of responsibilities (lead SI&T V&V). That's responsibilities. - Shared Responsibilities: PRIMARY RESPONSIBILITIES / KEY RESULT AREAS: list bullet-like sentences. - Focus Area Responsibilities: more detailed responsibilities. - Key Year 1 Deliverables: list of deliverables. - Qualifications: Background And Experience (education, experience, etc.) - Mindset & Values: list of values. - Other Key Requirements / Comments: security clearance, willingness to work 60% onsite, travel as required. - USA salary range: $121,000 - $190,000. Also note about compensation. - Benefits: not explicitly listed besides maybe "Additional compensation and benefits may apply depending on the location and terms of employment." That's vague; we should not create Benefits section unless posting actually states them. It says "Additional compensation and benefits may apply depending on the location and terms of employment." That's not specific benefit details. So we should not create Benefits section. - Pay: we have salary range. So we can include Pay section with that. - Schedule: not mentioned besides "Willing to work 60% onsite from office". That's schedule info (onsite percentage). Could be considered schedule. The posting says "Willing to work 60% onsite from office". That's a schedule detail. So we can include Schedule section with that. - Skills: not explicitly listed as separate; but qualifications include skills like technical writing, facilitation, stakeholder engagement, etc. Could be under Skills section. However we have Qualifications section already; we could put skills under Qualifications or separate Skills. The instruction: Prefer a few substantive sections over many thin ones. So we might combine skills into Qualifications or Responsibilities. But we have Qualifications already; we could include skills within Qualifications. However we have a separate "Skills" heading allowed; we could create Skills section if there is specific skill list. The posting includes: "Excellent technical writing, facilitation, stakeholder engagement, and executive communication skills." Also "Experience establishing verification frameworks, compliance tracking, and requirements traceability processes." Those are more experience. Could be under Qualifications. I'd rather keep Qualifications and maybe not create separate Skills to avoid thin section. But we need to decide. We have Mindset & Values: could be part of Qualifications or separate. Could be under Qualifications as well. We need to preserve all substantive information. So we need to include the values list somewhere. We could have sections: About the role (Programme Description), Responsibilities (Role Description Summary + Shared Responsibilities + Focus Area Responsibilities + Key Year 1 Deliverables), Qualifications (Background And Experience + Mindset & Values + Other Key Requirements), Pay, Schedule. We must not create sections with filler. Ensure each heading has real content. Let's extract content. Programme Description: "meoSphere is SES’s next-generation Medium Earth Orbit (MEO) satellite constellation, designed to deliver secure connectivity services to government agencies, enterprises, and commercial customers. It will also provide high-speed broadband internet to eliminate global connectivity dead zones. To accelerate development timelines, reduce costs, and ensure quality, SES is internalizing a critical segment of the satellite supply chain: the final integration of partner satellite platforms with SES’s software-defined payloads, all within a cutting-edge manufacturing and test facility." That's substantive. Role Description Summary: "The System Integration & Test (SI&T) Verification & Validation Lead is a hands-on technical leadership role responsible for developing and delivering verification and validation capabilities across a complex system-of-systems environment spanning spacecraft, ground systems, user terminals, communications networks, software platforms, operational processes, and supporting infrastructure. Working within the SI&T function, you will develop verification and validation strategies, plans, technical analyses, and evidence packages to verify requirements, validate end-to-end mission and service performance, and demonstrate operational readiness. Leading through technical expertise and influence, you will coordinate engineering, operations, suppliers, and program stakeholders to ensure activities are executed with appropriate rigor, coverage, and traceability. You will define verification methods, success criteria, evidence requirements, and closure approaches, leading reviews, validation assessments, and evidence-sufficiency evaluations across multiple subsystems and mission scenarios. The role provides delegated SI&T closure determinations and recommendations for requirement closure and mission readiness, while final approval and closure authority remain with the designated technical authorities." That's responsibilities. Shared Responsibilities: list: - Lead system integration, testing, verification, and validation work across hardware, software, networks, operations, laboratories, suppliers, and distributed teams. - Turn incomplete or conflicting inputs into clear, practical technical plans with visible assumptions, dependencies, risks, and evidence needs. - Apply discipline across requirements, interfaces, configuration control, readiness, anomalies, regression, traceability, and evidence. - Produce clear, decision-ready technical recommendations and communicate effectively with engineering, program, supplier, and executive stakeholders. - Define and lead System Integration & Test work while respecting retained authorities in product, facility, safety, flight, requirements, procurement, and acceptance decisions. Focus Area Responsibilities: more detailed: - Lead the development and execution of the program's verification and validation strategy, translating approved requirements and mission objectives into verification activities, validation scenarios, evidence requirements, and closure criteria. - Develop verification approaches, validation plans, technical analyses, and closure strategies across multiple subsystems, requirements sets, and verification methods. - Define verification methods, validation criteria, coverage requirements, data needs, pass/fail measures, and evidence standards required to support closure recommendations. - Lead verification reviews, validation assessments, and evidence-sufficiency evaluations to ensure requirements and mission outcomes are assessed with appropriate technical rigor. - Validate end-to-end mission and service performance under representative operating conditions, ensuring intended operational outcomes are achieved. - Assess verification and validation evidence, identify gaps, and recommend whether additional analysis, testing, operational data, or supporting evidence is required. - Lead delegated SI&T closure determinations and provide closure recommendations while ensuring final approval authority remains with the designated technical authorities. - Maintain end-to-end traceability from requirements and mission objectives through verification and validation activities to final evidence packages, decisions, and closure recommendations. Key Year 1 Deliverables: list: - Verification and validation strategies, standards, and governance processes. - A traceability framework linking requirements, verification methods, validation activities, evidence, and closure status. - Documented verification and validation approaches covering testing, analysis, operational demonstrations, flight results, supplier evidence, and related methods. - Defined success criteria, coverage expectations, evidence standards, and assessment processes. - Evidence-sufficiency review and delegated SI&T determination processes supporting closure recommendations and mission readiness assessments. Qualifications Background And Experience: - Bachelor's degree in Engineering, Aerospace, Telecommunications, Computer Science, Systems Engineering, or a related technical discipline. - Minimum 10 years of experience in systems integration, verification and validation, requirements management, testing, or related engineering functions involving complex hardware and software systems. - Proven technical leadership, including driving verification and compliance activities across multidisciplinary teams and suppliers. - Strong understanding of requirements management, traceability, interface control, configuration management, technical risk management, and evidence-based decision-making. - Experience establishing verification frameworks, compliance tracking, and requirements traceability processes. - Excellent technical writing, facilitation, stakeholder engagement, and executive communication skills. - Experience in space systems, satellite communications, ground systems, mission operations, telecommunications, or other mission-critical engineering programs. - Familiarity with systems engineering practices, requirements and test management tools, hardware-in-the-loop environments, simulators, digital engineering approaches, and model-based systems engineering (MBSE). - Experience with end-to-end system verification, supplier verification management, flight verification planning, or product acceptance activities is highly desirable. Mindset & Values: - Ownership: Takes accountability for outcomes, drives issues to resolution, and balances speed, risk, and quality to deliver results. - Systems Thinking: Understands how hardware, software, networks, operations, suppliers, and processes interact; always considers the full impact of decisions. - Evidence Driven: Uses objective data, testing, and measurable results to guide decisions, assess risk, and build confidence in system readiness. - Technical Leadership Through Influence: Builds alignment across teams and stakeholders through expertise, credibility, and sound judgment rather than formal authority. - Collaborative & Low Ego: Values diverse perspectives, welcomes constructive challenge, and works across disciplines to achieve the best outcome for the system and the business. Other Key Requirements / Comments: - The candidate must be eligible for a “SECRET” security clearance, in accordance with the national regulations as well as EU/ESA/NATO equivalents - Willing to work 60% onsite from office - Travel as required for project realization purposes Pay: - The USA salary range for this full-time position is $121,000 - $190,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 of factors, including job-related skills, experience, qualifications, and relevant education or training. - Additional compensation and benefits may apply depending on the location and terms of employment. We should not include EEO boilerplate. Now produce HTML. We need headings:

for each section. We'll have sections: - About the role (Programme Description) - Responsibilities (combine Role Description Summary, Shared Responsibilities, Focus Area Responsibilities, Key Year 1 Deliverables) - Qualifications (Background And Experience, Mindset & Values, Other Key Requirements) - Pay - Schedule (60% onsite, travel as required) We should not create Skills section separately. We need to use

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

  . Thus for each section we need to decide if content is list or prose. About the role: prose (programme description). Use

  . Responsibilities: we have multiple lists; we can combine into a single

  with items being the responsibilities. However some items are paragraphs (like Role Description Summary) which is prose. Could treat that as a

  then a

  for the bullet lists. But instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So we can have a

    for the Role Description Summary, then

    for the shared responsibilities, focus area responsibilities, and key year 1 deliverables. But we could also merge all bullet points into one list; but that would lose grouping. It's okay to have multiple lists. Qualifications: we have