AISR Satellite Operations Technician, Tier 2

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are" and "Summary". We need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content for it. So we need to map content. We have: - Who We Are: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "Who We Are" which is company overview. Could we treat as "About the role"? Might be better to use "About the role" heading and put the company description there? However the instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. We need to decide which sections have content. Content: - Summary: description of role responsibilities. That maps to Responsibilities. - Primary & Essential Accountabilities: list of duties. Also Responsibilities. - Required Qualifications: list of qualifications (education, experience, clearance, etc.) That maps to Requirements or Qualifications. The headings list includes Requirements and Qualifications separate. We need to decide which to use. Probably "Requirements" for mandatory qualifications, "Qualifications" for desirable? But we have both Required and Desirable Qualifications. Could split: Required Qualifications -> Requirements; Desirable Qualifications -> Qualifications (or Skills). However Skills heading could be for skills like IP Routing, Linux/Unix, etc. The Desirable Qualifications list includes IP Routing, Linux/Unix, Microsoft Office suite, Trouble ticket tracking, One or more DoD 8570 IAT-II certifications, Technical certification (CCNA, CCDA, CCNP or CCDP). Those could be Skills. Thus: - About the role: maybe we can put company overview under "About the role". Or we could omit About the role if not specific? The instruction: "include a section ONLY when the posting has real, specific content for it". We have company overview content, so we can include About the role. - Responsibilities: combine Summary and Primary & Essential Accountabilities. - Requirements: Required Qualifications (Bachelor's degree, experience, clearance, experience managing KuSS Arclight etc.) - Qualifications: maybe we could put Desirable Qualifications under Qualifications. - Skills: maybe we could put specific technical skills under Skills (IP Routing, Linux/Unix, Microsoft Office, Trouble ticket tracking, certifications). But those are also desirable qualifications. Could combine. - Benefits: posting mentions benefits programs: paid vacation, sick and personal leave; medical, dental, vision, life, and disability insurance; a 401(k)-retirement plan; and others. Also mentions possible annual bonus. So we have Benefits content. - Pay: posting says "The final base salary offered will be determined based on factors such as the position’s location, the candidate’s relevant skills, experience, and qualifications. Where applicable, this position may also be eligible for an annual bonus." That's not specific numbers, but it's still mention of pay. However instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "final base salary offered will be determined based on factors..." is somewhat vague but not exactly placeholder like "commensurate with experience". It's still not a specific number. Might be considered filler? The instruction says never emit a heading followed by filler/placeholder text. The example includes "commensurate with experience". The given text is similar: "final base salary offered will be determined based on factors...". That is essentially saying salary is not specified; it's variable. Likely we should omit Pay section because it's not specific. - Schedule: posting mentions shift work, weekends, holidays. That's schedule info. So we can include Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO etc. We need to preserve all substantive information. Let's extract content. About the role (company overview): "We deliver secure, resilient connectivity and integrated space solutions for customers operating in the world’s most demanding environments. As part of SES S.A., a global leader in satellite-enabled communications, we combine capabilities across all orbits with extensive global ground infrastructure, managed networks, hosted payload solutions, and mission integration services to support communications, sensing, data transport, and operational resilience worldwide. Our vertically integrated space and ground capabilities bring together satellite capacity, terrestrial infrastructure, advanced network technologies, and deployed user terminals to support mission-critical government operations around the world. We are a trusted partner to the U.S. Federal Government and national security community, allied governments, NATO, NASA, and other civilian agencies, delivering reliable, high-performance solutions when mission success is critical. At SES Space & Defense, our people are our competitive advantage. You’ll work alongside a mission-driven team committed to integrity, innovation, accountability, and delivering real-world impact for customers whose missions matter most." That's prose; put in

  . Responsibilities: combine Summary and Primary & Essential Accountabilities. Summary paragraph: "The AISR Tier 2 Satellite Operations Technician will provide tier 2 and tier 3 satellite and network operations support. Tier 2 and tier 3 level support is considered advanced support which includes the day-to-day operation, Quality Control (QC), and oversight of a Ku/Ka Spread Spectrum (KuSS) networks and associated equipment, Master Station Log (MSL) entries, and Remedy trouble ticket entries. The Technician is part of a team that ensures the effective monitoring, control, and configuration of a global satellite communications network including forward deployed satellite earth terminals and embedded network communications equipment. The Technician will provide daily operational support for ViaSat Arclight hubs and remote systems supporting global TDMA/IP networks. As an integral part of the team, the Technician’s tasking may include shift work, including weekends and holidays. Analyzes moderately complex communication systems, including planning, designing, evaluating, selecting operating systems and protocol suites, and configuring communication media with concentrators, bridges, and other devices. May include local and wide area networks, data, and voice communications. Networks may be one or a combination of terrestrial, wireless, or satellite." Then Primary & Essential Accountabilities list (many bullet-like sentences). We need to turn them into

  • . Let's extract each sentence that starts with a verb. List: - Continuously monitor network and space segment performance to provide customer tier 2 and tier 3 support as required - Resolve customer issues related to broadband IP communication via satellite transmission; support complex systems installations and startup at customer sites - Monitor ViaSat Arclight equipment configurations and network performance, in real-time, and report conditions and anomalies to the designated team lead - Prepare reports on network utilization, performance and activity as required - Open and track trouble tickets as required to resolve network or terminal issues. - Provide Quality Control (QC) and oversight of configuration files, Master Station Log (MSL) entries and Remedy trouble ticket entries - Isolate and correct network faults provided software toolsets - Troubleshoot network anomalies, satellite outages, and any deployable KuSS terminal satellite related issues - Proactively monitor the AISR-T networks for impending issues by using an analysis of measured vs. planned performance, detection and analysis of performance trends, and the KuSS terminals performance characteristics - Manage service restoration activities and track/update trouble ticketing system (Remedy). - Provide status reports to customers and management personnel - Provide testing and implementation support of new software releases for deployed network equipment - Analyze, troubleshoot and resolve product related issues resulting from installation, software and hardware upgrades, configuration changes, equipment integration or testing - Maintain timely and accurate helpdesk records using the ticket management system - Assist with the detailed project planning efforts on larger projects, and may act as a project manager on smaller efforts - May review proposals, including gathering facts, analyzing data and preparing project overview to compare alternatives - Provide technical input to the development of information technology project planning. - Update job knowledge by participating in educational opportunities; reading professional publications; maintaining personal networks; participating in professional organizations. - Show initiative in constantly reassessing business requirements and make suggestions that proactively address changing business needs - Protect organization's value by preserving the confidentiality of information We need to ensure each is a list item. Now Requirements (Required Qualifications): "Bachelor’s degree in Computer Science or related field with five years progressively complex network systems engineering experience or equivalent combination of education/training and experience)Competent technical expertise and application domain knowledgeActive U.S. Government Department of Defense (DoD) Top Secret level security clearance with SCI eligibility determinationExperience managing and supporting KuSS Arclight ground hub and air component solutions, TCP/IP and general networking concepts and SATCOM/RF concepts" We need to parse into list items. Let's break: - Bachelor’s degree in Computer Science or related field with five years progressively complex network systems engineering experience or equivalent combination of education/training and experience - Competent technical expertise and application domain knowledge - Active U.S. Government Department of Defense (DoD) Top Secret level security clearance with SCI eligibility determination - Experience managing and supporting KuSS Arclight ground hub and air component solutions, TCP/IP and general networking concepts and SATCOM/RF concepts Now Qualifications (Desirable Qualifications): "IP RoutingLinux/UnixMicrosoft Office suiteTrouble ticket trackingOne or more DoD 8570 IAT-II certifications (Security+, etc.)Technical certification (CCNA, CCDA, CCNP or CCDP)" We need to separate items. The text seems concatenated without spaces. We'll parse: - IP Routing - Linux/Unix - Microsoft Office suite - Trouble ticket tracking - One or more DoD 8570 IAT-II certifications (Security+, etc.) - Technical certification (CCNA, CCDA, CCNP or CCDP) Now Skills: maybe we could treat these as Skills as well, but we already used Qualifications for desirable. Could also have Skills separate for things like IP Routing, Linux/Unix, Microsoft Office, Trouble ticket tracking. But we already have them in Qualifications. To avoid duplication, we could put Skills heading with same list? But that would duplicate content. Better to assign Desirable Qualifications to Qualifications heading, and maybe Skills heading could be left out if no distinct skills beyond those. However we have some skills like IP Routing etc. They are already in Qualifications. Could we treat Qualifications as mandatory and Skills as desirable? But we already used Requirements for mandatory. So we could put Desirable Qualifications under Skills heading. Let's decide: Use Requirements for mandatory qualifications. Use Skills for desirable technical skills/certifications. Use Qualifications maybe for something else? But we have no other qualifications. Could combine Desirable Qualifications into Skills. Then we might not need Qualifications heading. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. That's six sections. We need to ensure we don't create a heading with filler. Benefits we have specific content. Schedule we have shift work etc. Now Benefits: "Employees are eligible to participate in SES Space & Defense’s benefits programs, which include paid vacation, sick and personal leave; medical, dental, vision, life, and disability insurance; a 401(k)-retirement plan; and others." Also mention possible annual bonus earlier but that's under Pay; we omitted Pay. Could include bonus in Benefits? The text about annual bonus was in Pay paragraph: "Where applicable, this position may also be eligible for an annual bonus." That's still about compensation, not benefits. Since we omitted Pay, we could mention bonus under Benefits as additional? But it's not a benefit program;