Senior Systems Integrator
ENSCO, Inc. · Colorado Springs, CO · 1 mo ago
Information Technology$139k–$190k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: navigation, EEO, etc. Also remove application instructions. The posting includes many paragraphs. We need to extract content.
We need sections: About the role (maybe from first paragraph describing ENSCO and role). Responsibilities (list of primary responsibilities). Requirements (maybe required qualifications). Qualifications (maybe desired qualifications). Skills (maybe technical knowledge etc). Benefits (the benefits paragraph). Pay (salary range). Schedule (maybe not present; there is no schedule info, so we should not include Schedule section). Also maybe include "Qualifications" vs "Requirements"? The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- About the role: description of ENSCO and role: first paragraph(s) about ENSCO and position description. Could be "About the role".
- Responsibilities: list of primary responsibilities (bulleted). We'll put
- for each.
- Requirements: required qualifications (Bachelor's degree etc, active DOD Top Secret clearance, US citizenship). Could be "Requirements".
- Qualifications: desired qualifications (direct experience with SCN, etc). Could be "Qualifications".
- Skills: maybe technical knowledge etc? Could combine with qualifications? But we have separate headings; we can put skills like "Ability to maintain and communicate technical documentation..." etc. However many of those are in required qualifications. Might be better to put skills under "Skills" heading: ability to lead multidisciplinary teams, build trusted relationships, influence decisions, maintain accountability, ability to maintain and communicate technical documentation, ability to work on-site, etc.
- Benefits: paragraph about benefits.
- Pay: salary range.
- Schedule: not present, so omit.
We must not include placeholder like "commensurate with experience". Not present.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize into sections.
We must remove boilerplate: EEO statement, Export Control and Licensing, Privacy, REAL ID Requirement? Actually REAL ID Requirement is substantive? It mentions requirement for accessing US federal facilities. Might be considered relevant but maybe it's a requirement. Could be included under Requirements or maybe as a note. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. REAL ID Requirement is not exactly EEO; it's a requirement for accessing federal facilities. Might be considered substantive. However it's more like a note. The instruction says remove legal boilerplate; REAL ID is a legal requirement. Might be considered boilerplate? Not sure. Safer to keep it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". REAL ID Requirement is legal. So we should remove it. Also "Export Control and Licensing", "Privacy", "EEO Statement" are legal boilerplate; remove.
Also "Background Check Type: 7 Year Pre-Employment Drug Screen Required: None Position Contingent Upon Contract Award: Yes" - these are metadata; maybe we can drop as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop those lines. We need to preserve all substantive information: job description, responsibilities, qualifications, desired qualifications, skills, benefits, pay. We must not repeat job title as heading. We must output only HTML fragment. Let's craft. First, maybe a short
for About the role: combine ENSCO description and role summary. About the role: "ENSCO has been providing leading-edge engineering, science and advanced technology solutions to governments and private industries worldwide for over 50 years. The company creates and applies advanced technologies for mission success, offering systems engineering, integration, and advanced technology services to transform the future safety, security, and resiliency of critical missions on the ground, in the air, in space, and in the information systems that connect these domains. ENSCO Inc. is seeking a Senior System Integration to work directly with Government mission leaders and independently governed program teams delivering elements of a critical space mission capability. The role establishes shared mission outcomes, converges competing architecture visions, builds trusted technical relationships, influences without formal authority, synchronizes portfolio timing, recommends acceleration and deliberate pacing, creates integration agreements, designs rapid integration learning, preserves modularity and options, drives decision-ready trade space, maintains the integrated decision rhythm, and connects integration to fielding." We need to ensure we don't lose any detail. Might be too summarized but we must preserve all substantive information; summarizing may lose detail. However we can keep the bullet list of responsibilities exactly as given. For About the role we can keep a prose summary but must not omit substantive info. The original description includes many details about the role's purpose. We can keep a paragraph that captures the essence but not omit any key points. It's tricky. Maybe better: About the role: just a short paragraph describing the company and the role's purpose, not repeating the responsibilities list. That's acceptable. Responsibilities: list each bullet from "Primary Responsibilities". We'll copy each sentence as
- .
Requirements: list required qualifications: Bachelor's Degree or equivalent with 10+ years of progressive experience in satellite communications, space operations, radio frequency transmission systems, mission systems, information technology, or a closely related technical environment. Demonstrated experience integrating, modernizing, sustaining, or troubleshooting complex space, satellite control, communications, cyber, or ground mission capabilities across Government and contractor organizations. Technical knowledge of satellite mission operations across ground, link, and space segments, with the ability to analyze complex issues and translate findings into practical integration or sustainment actions. Experience directing project milestones, assigning work, monitoring completion, and coordinating technical activities across operational units, program offices, headquarters organizations, contractors, and external agencies. Experience coordinating planned and unplanned equipment outages, maintenance schedules, technical dependencies, configuration changes, and continuity information needed for mission and leadership decisions. Demonstrated success planning or leading system testing, mission system upgrades, ground-system installations, capability activation, technical acceptance, or transition to operations. Experience analyzing and resolving hardware, software, network, radio frequency, cyber, or interface problems that affect mission availability, performance, or integration readiness. Experience applying cybersecurity requirements through assessments, vulnerability testing, finding remediation, security documentation, or defensive capability implementation in a mission environment. Proven ability to lead multidisciplinary teams, build trusted relationships, influence decisions without relying on formal authority, and maintain accountability through project completion. Ability to maintain and communicate technical documentation, drawings, schedules, outage reports, memorandums, action items, milestone status, and factual briefings for senior leaders and technical stakeholders. Ability to work on-site in Colorado Springs, Colorado, and support periodic coordination or travel as required. AN ACTIVE DOD TOP SECRET CLEARANCE IS REQUIRED FOR THIS POSITION FOR WHICH, YOU MUST BE A U.S. CITIZEN.
We could also include U.S. Citizenship Required: Yes, Security Clearance Required: Top Secret. But those are covered.
Qualifications (desired): list each desired qualification bullet.
Skills: maybe we can combine some abilities that are not covered elsewhere? But many are in requirements. Could still have a Skills section for abilities like "Ability to lead multidisciplinary teams, build trusted relationships, influence decisions without relying on formal authority, and maintain accountability through project completion." etc. However those are already in requirements. To avoid duplication, maybe we skip Skills section or include only those not already captured. The instruction: prefer a few substantive sections over many thin ones. So we could omit Skills if its content overlaps heavily with Requirements/Qualifications. But we need to ensure we don't lose any substantive info. If we omit Skills, we must ensure that the abilities are still present somewhere else (they are in Requirements). So we can omit Skills.
Benefits: paragraph about benefits: "At ENSCO, a positive working environment and a competitive salary are only part of the reason for choosing a career here. We offer a comprehensive benefits package that creates a stimulating and supportive environment where you can thrive - visit ensco.com/careers/benefits to learn more."
Pay: salary range: "$139,172.80 - $190,000 USD".
Schedule: not present, omit.
We also need to include maybe a short
for metadata like "Employment Type: Regular Full-time". Could be minor metadata; we could drop or include in a short paragraph. The instruction: fold minor metadata into a short
or drop it. So we could include a short
with "Employment Type: Regular Full-time". But it's minor; we could drop. I'd drop to keep clean. Now produce HTML. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
...
Pay
...
Make sure no extra whitespace? It's fine. Now craft the content precisely. Let's extract responsibilities list exactly as in text: Primary Responsibilities Establish the shared mission outcome. Translate operational need into an integrated capability outcome, mission threads, measurable effects, time-to-field targets, decision points, and minimum evidence required for commitment. Converge competing architecture visions. Create a fact-based forum where participating programs can reconcile different end states, boundaries, interfaces, data flows, standards, and technical assumptions into decision-ready alternatives and a coherent mission architecture. Build trusted technical relationships. Earn credibility with program leaders, operators, acquisition teams, technical authorities, cybersecurity teams, test organizations, logistics teams, and industry partners; understand what each team must protect before asking it to change course. Influence without formal authority. Use mission impact, transparent evidence, and reciprocal commitments to align autonomous programs around shared decisions while preserving each organization's accountability for its own execution. Synchronize portfolio timing. Map program milestones, critical paths, integration dependencies, funding decisions, contract actions, test resources, facilities, training, cybersecurity, production, and transition activities against a common mission delivery window. Recommend acceleration and deliberate pacing. Identify where a program should accelerate, resequenced, narrow an increment, protect schedule margin, or deliberately slow activity so interfaces, evidence, resources, and operational users are ready at the same point in time. Create integration agreements. Define interface ownership, data exchanges, configuration boundaries, integration entry and exit criteria, decision rights, evidence owners, escalation paths, and commitment dates that teams can execute. Design rapid integration learning. Plan focused demonstrations, interface tests, mission-thread events, digital integration activities, and knowledge points that expose incompatibility and weak assumptions before expensive commitment. Preserve modularity and options. Advance open interfaces, modular increments, replaceable components, data-rights objectives, and competitive integration paths that reduce lock-in and allow individual programs to evolve without breaking the mission. Drive decision-ready trade space. Frame choices across mission effect, performance, interoperability, cost, schedule, cybersecurity, integration complexity, sustainment, time-to-field, and production scalability so leaders can act quickly. Maintain the integrated decision rhythm. Lead technical interchange meetings, architecture convergence sessions, dependency reviews, executive decision forums, and action follow-through; surface unresolved commitments before they become mission-level delays. Connect integration to fielding. Align operational acceptance, training, infrastructure, support equipment, continuity, sustainment, reconstitution, and transition activities so the combined capability is usable when delivered. We need each as - . Ensure we keep the sentences exactly. Now Required qualifications list: Required Bachelor's