Satellite Operator/Technician Trainee (Active Secret Clearance Required)
- for each.
- Then "Qualifications" heading and list (Active Secret Security Clearance, High school diploma or equivalent, Ability to successfully complete the Satellite Controller Training and Certification Program, Ability to obtain an Intermediate level 8140 certification within 6 months of hire, Ability to work rotating shifts supporting a 24/7/365 mission, Ability to read and follow Technical Orders and maintenance procedures, Strong troubleshooting, communication, and analytical skills, Basic knowledge of electronics, RF communications, satellite communications, or computer systems.)
- Then "Preferred Qualifications" heading and list (Experience supporting the Satellite Control Network (SCN), Experience operating or maintaining RBC, ARTS, Hybrid, or MTR systems, Security + or Cloud + Certification, Military or DoD contractor experience supporting satellite operations, Experience with telemetry, tracking, commanding, and payload (TTC&P) operations, Technical degree or certification in Electronics, Telecommunications, or Computer Systems.)
- Then "Job ID 2026-25601 Work Type On-Site" - we should fold minor metadata into a short
or drop it. Probably include a short paragraph with Job ID and Work Type. - Then "Company Description" with details about Five Rivers Analytics. That could be "About the company" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". Could we put company description under About the role? Probably not. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should only use those headings? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those exact headings when appropriate. So we need to map content to those headings. Company description maybe could go under About the role? But that seems odd. However we could omit company description if not fitting any heading. But we must preserve ALL substantive information; cannot drop company description unless it's boilerplate. It's substantive about the company. Could we treat it as "About the role"? Not really. Could we create a section "About the role" that includes both role description and company description? The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding extra info under About the role. So we could put company description under About the role as a paragraph. But we also have "Benefits" and "Schedule". The posting mentions "comprehensive benefits and competitive pay" in company description. It mentions benefits generally but not specific. It says "You will also have access to our comprehensive benefits and competitive pay in addition to growth opportunities and excellent retirement options." That's vague but mentions benefits. However we should only include Benefits section if posting actually states them. It does mention comprehensive benefits but not specifics. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (comprehensive benefits). So we could include Benefits section with that statement. However we should avoid filler like "commensurate with experience". "comprehensive benefits" is somewhat vague but still stated. I'd include Benefits section with that sentence. Schedule: The posting mentions "Ability to work rotating shifts supporting a 24/7/365 mission." That indicates schedule: rotating shifts, 24/7/365. So we can include Schedule section with that. Pay: we have specific pay rates. Skills: Could we extract skills from qualifications? There's a "Skills" heading optional. We could put skills like troubleshooting, communication, analytical, basic knowledge of electronics, RF, satellite comms, computer systems. But we already have qualifications. Might be better to put skills under Qualifications. But we have a separate Skills heading allowed. We could create Skills section listing those skills. However we must not invent or summarize away detail. We can extract from qualifications: Strong troubleshooting, communication, and analytical skills. Basic knowledge of electronics, RF communications, satellite communications, or computer systems. Those are skills. So we can put them under Skills. Requirements: Could be same as Qualifications? The posting has Qualifications and Preferred Qualifications. We could treat Qualifications as Requirements. But we have both Qualifications and Requirements headings allowed. We could put mandatory qualifications under Requirements, and preferred under Qualifications? Or we could combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Requirements (combining qualifications), Pay, Benefits, Schedule. Avoid too many sections. But we need to preserve all substantive info. If we combine, we must still include preferred qualifications somewhere. Could put them under Requirements as well, maybe label as "Preferred Qualifications" inside a
or
- . But we cannot create headings not allowed. We could include a
- for lists. Use
for prose. We must not repeat job title as heading. Not include Job ID/requisition numbers as headings; we can include them in a short
maybe under About the role or separate paragraph. But we said we fold minor metadata into a short
or drop it. We could include a
at end: "Job ID: 2026-25601 | Work Type: On-Site". That's minor metadata. Now let's craft. About the role paragraph: Combine intro and company description. Intro: "Five Rivers Analytics, an Akima company, is seeking a Satellite Controller to support the Satellite Control Network Operations, Remote Site and Mission Partner Support (STORMS) contract at New Boston Space Force Station, New Hampshire. To join our team of outstanding professionals, apply today!" Then role description: "The Satellite Controller performs real-time satellite operations and organizational-level maintenance on the Remote Block Change (RBC) and Automated Remote Tracking Station (ARTS) satellite communications terminals supporting the United States Space Force Satellite Control Network (SCN). This position supports telemetry, tracking, commanding, and payload (TTC&P) operations while maintaining continuous mission readiness for Department of Defense satellite operations. This position includes a structured training and certification program. Employees begin as Satellite Controller Trainees and progress through Operator and Controller certification milestones before becoming fully qualified independent controllers." Then company description: "Five Rivers Analytics (FRA), an Akima company, is not just another federal IT contractor. As an Alaska Native Corporation (ANC), our mission and purpose extend beyond our exciting federal projects as we support our shareholder communities in Alaska. At FRA, the work you do every day makes a difference in the lives of our 15,000 Iñupiat shareholders, a group of Alaska natives from one of the most remote and harshest environments in the United States. For our shareholders, FRA provides support and employment opportunities and contributes to the survival of a culture that has thrived above the Arctic Circle for more than 10,000 years. For our government customers, FRA delivers streamlined operations in support of an increasingly fast-paced, complex, and dynamic digital environment. As a FRA employee, you will be surrounded by a challenging, yet supportive work environment that is committed to innovation and diversity, two of our most important values. You will also have access to our comprehensive benefits and competitive pay in addition to growth opportunities and excellent retirement options." We could combine. Now Responsibilities list: each bullet from the responsibilities section. List them: - Perform real-time satellite operations using the Remote Block Change (RBC) and Automated Remote Tracking Station (ARTS) systems. - Execute telemetry, tracking, commanding, and payload (TTC&P) operations in accordance with Space Force technical orders and established procedures. - Monitor satellite contacts, mission equipment status, communication systems, and operational displays during scheduled and contingency operations. - Configure, operate, monitor, and restore SCN mission systems supporting satellite operations. - Perform organizational-level maintenance on RBC, ARTS, HPA, communications equipment, antenna systems, RF equipment, timing systems, and associated support equipment. - Perform preventive maintenance inspections (PMIs), troubleshooting, fault isolation, corrective maintenance, and equipment restoration. - Respond to equipment failures, mission anomalies, and emergency satellite support requirements. - Document maintenance actions, operational events, and equipment discrepancies using approved maintenance documentation systems. - Coordinate operations and maintenance activities with Government personnel and other SCN sites. - Comply with Technical Orders, Space Force guidance, cybersecurity, COMSEC, safety requirements, and local operating procedures. - Support contingency operations, shift turnover activities, and mission surge requirements. - Perform other duties as assigned. Now Requirements: mandatory qualifications list: - Active Secret Security Clearance. - High school diploma or equivalent. - Ability to successfully complete the Satellite Controller Training and Certification Program. - Ability to obtain an Intermediate level 8140 certification within 6 months of hire. - Ability to work rotating shifts supporting a 24/7/365 mission. - Ability to read and follow Technical Orders and maintenance procedures. - Strong troubleshooting, communication, and analytical skills. - Basic knowledge of electronics, RF communications, satellite communications, or computer systems. Preferred qualifications list: - Experience supporting the Satellite Control Network (SCN). - Experience operating or maintaining RBC, ARTS, Hybrid, or MTR systems. - Security + or Cloud + Certification. - Military or DoD contractor experience supporting satellite operations. - Experience with telemetry, tracking, commanding, and payload (TTC&P) operations. - Technical degree or certification in Electronics, Telecommunications, or Computer Systems. We could put both under Requirements with headings inside? But we cannot add extra headings. Could we separate into two
- with a
indicating "Preferred qualifications:"? That's okay. Now Pay: Fully Certified Operator $47.94/hour, Fully Certified Controller $50.30/hour. We
inside Requirements that mentions both required and preferred. That's okay. Let's decide sections: - About the role: includes introductory paragraph about role and company description. - Responsibilities: list of duties. - Requirements: includes mandatory qualifications and preferred qualifications (maybe separate sub-lists). We'll include both. - Pay: specific hourly rates. - Benefits: statement about comprehensive benefits, competitive pay, growth opportunities, retirement options. - Schedule: rotating shifts, 24/7/365. We should not include Skills separately if we covered in Requirements. Now we need to output HTML fragment only, no /. Use
for each section heading. Use
- for lists. Use