We need to output HTML fragment with sections: About the role? The posting includes description. We need to decide sections: maybe "About the role", "Responsibilities", "Qualifications", "Benefits", "Pay". Also maybe "Schedule"? The posting includes "Salary Range $195,000 - $230,000 USD". So Pay section. Benefits: they mention benefits package but no specifics; they say "visit ensco.com/careers/benefits to learn more." That's not specific content, just a link. According to rule: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Benefits: they say "We offer a comprehensive benefits package..." but no specifics. That's vague; maybe we should not include Benefits because no specific details. However they mention "positive working environment and a competitive salary are only part of the reason..." but still vague. Probably we should omit Benefits.
Schedule: not mentioned.
Thus sections: About the role (maybe we can use "About the role" as heading for the initial description). Responsibilities: list of primary responsibilities. Qualifications: required and desired? Could combine required and desired under Qualifications. Could separate Required Qualifications and Desired Qualifications but rule: prefer few substantive sections over many thin ones. So maybe one Qualifications section containing both required and desired bullet lists.
Pay: include salary range.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, privacy, export control, REAL ID, etc.
We need to preserve all substantive information.
Let's extract:
About the role: first paragraph after "Position Description": "ENSCO Inc. is a diverse engineering and technology company that provides engineering, science, and advanced technology solutions supporting mission success, safety, and security for government and commercial customers worldwide. We are seeking a Senior Staff Solution Architect to work directly with Government acquisition and mission customers responsible for a critical Satellite Control (Telemetry, Tracking, and Commanding - TT&C) capability. This position serves as the technical lead for an assigned solution area, connecting mission need, acquisition activity, architecture, integration, fielding, operational acceptance, and sustainment into a practical path to capability delivery. Working within the overall technical direction for the effort, this individual will own the technical coherence and customer outcomes of the assigned area. The role is an individual-contributor position with no personnel-management or supervisory responsibility. Success depends on technical credibility, strong customer relationships, clear decision evidence, disciplined follow-through, and the ability to unite Government, operational, program, technical, contracting, logistics, cybersecurity, test, and industry participants around a shared mission outcome."
That's the about.
Responsibilities: list bullet points under "Primary Responsibilities". We'll extract each bullet.
Let's list them:
- Own an assigned solution area.
- Maintain the end-to-end technical view for a defined mission, capability, integration, fielding, or sustainment area and keep its decisions aligned with the full-effort technical direction.
- Put the customer mission first. Build trusted relationships with Government mission and acquisition customers, understand the outcome they need, clarify constraints, and turn ambiguous or competing inputs into a focused technical action plan.
- Connect architecture to delivery. Align mission threads, operational workflows, interfaces, data flows, dependencies, infrastructure, cybersecurity, logistics, training, operational acceptance, and sustainment considerations for the assigned area.
- Create decision-ready options. Frame alternatives and consequences across mission effect, performance, cost, schedule, integration complexity, readiness, risk, time-to-field, and long-term support so Government decision owners can act with confidence.
- Drive focused pre-prototype learning. Define the smallest useful body of analysis, demonstration, test, supplier evidence, or site validation needed to confirm feasibility, expose weak assumptions, and retire risk before commitment.
- Coordinate cross-functional execution. Bring program offices, operators, technical specialists, contracting, finance, cybersecurity, test, logistics, suppliers, and mission partners together to resolve issues, confirm ownership, and protect delivery milestones.
- Prepare the area for fielding. Plan for installation, deployment, operational acceptance, training, support equipment, supply availability, maintenance, configuration control, continuity, and life-cycle support from the beginning.
- Resolve mission-impacting problems. Lead fact-based investigations of multidomain issues, isolate constraints and dependencies, coordinate corrective actions with subject-matter experts, and communicate the impact to schedule, readiness, and mission delivery.
- Develop customer-facing products. Produce concise technical action plans, option papers, site and readiness assessments, capability roadmaps, risk and opportunity views, decision schedules, briefings, and status products that move work forward.
- Preserve delivery options. Evaluate commercial and Government solutions, supplier capacity, competitive approaches, modular increments, open interfaces, and transition choices that improve resilience, affordability, and time-to-field.
- Support targeted growth activity. Participate selectively in customer discovery, technical solution shaping, capability demonstrations, technical proposal content, and basis-of-estimate development for closely related opportunities; the role does not own capture strategy, pipeline management, or sales targets.
- Maintain disciplined follow-through. Track technical commitments, decision evidence, risks, dependencies, and customer actions through the next integration, fielding, or transition milestone and elevate blockers early.
- Lead through execution. Surface blockers early, assign evidence and action owners, challenge unsupported assumptions, mentor technical contributors, and maintain accountability through the next Government decision and transition milestone.
Qualifications Required: list bullet points.
Let's extract required qualifications:
- Bachelor's degree or equivalent in engineering, logistics, supply chain management, acquisition, business, operations, management, organizational leadership, or a closely related discipline, with a minimum of 10 years of relevant professional experience.
- At least 10 years of progressive experience supporting defense, space, national security, or another complex mission environment through capability acquisition, logistics, operational planning, fielding, sustainment, readiness, or technical program execution.
- Demonstrated success working directly with Government acquisition, program, operational, and mission customers to clarify needs, build trust, present options, and carry decisions into executable actions.
- Experience translating complex mission needs into structured action plans by identifying constraints, dependencies, integration considerations, operational acceptance needs, and life-cycle support requirements.
- Experience fielding, deploying, activating, or transitioning mission-critical systems or equipment, including coordination of sites, users, suppliers, support resources, training, and sustainment activities.
- Proven ability to coordinate cross-functional investigations, work with subject-matter experts, isolate multidomain problems, and implement corrective actions that protect capability delivery or operational readiness.
- Working knowledge of defense acquisition and contracting processes, logistics planning, supplier evaluation, risk management, and the relationship between technical choices and long-term mission support.
- Experience producing and briefing decision-quality products such as technical action plans, readiness assessments, site surveys, risk-mitigation recommendations, procurement or contract reviews, schedules, and executive-level status updates.
- Ability to influence outcomes across organizations without formal authority, maintain productive customer relationships in high-pressure settings, and follow commitments through completion.
- Strong written, verbal, analytical, and interpersonal skills, including the ability to explain complex operational and technical issues to senior Government customers and multidisciplinary teams.
- Ability to work on-site in Albuquerque, New Mexico, travel to Colorado Springs, Colorado, and support periodic travel to Government, operational, supplier, or mission sites as required.
- AN ACTIVE TOP SECRET DOD SECURITY CLEARANCE IS REQUIRED FOR THIS POSITION FOR WHICH, YOU MUST BE A U.S. CITIZEN
Also "U.S. Citizenship Required: Yes" and "Security Clearance Required: Top Secret". Already covered.
Qualifications Desired: list bullet points.
- Master's degree in human resource management, organizational leadership, acquisition management, logistics, supply chain management, business, engineering management, or a related discipline.
- Direct experience supporting U.S. Space Force, another military space organization, a rapid capabilities office, or a national security organization responsible for accelerated capability delivery.
- Experience with Satellite Control, TT&C, space operations, space-ground integration, command and control, terrestrial mission systems, or other space mission infrastructure.
- Experience coordinating the global or multi-site fielding of high-value ground or terrestrial systems and integrating operational acceptance with sustainable life-cycle support.
- Familiarity with the Joint Capabilities Integration and Development System (JCIDS), the Federal Acquisition Regulation (FAR), rapid acquisition pathways, capability maturation, or prototype-oriented acquisition activities.
- Experience with strategic sourcing, competitive bidding, best-value determinations, commercial product evaluation, supplier capability assessments, or acquisition packages for specialized prototype or mission projects.
- Experience managing or evaluating significant contract, supply, equipment, or resource portfolios while maintaining strong accountability, compliance, and mission readiness.
- Experience conducting joint, multinational, or remote site surveys; validating operational or logistics plans; and resolving constraints in austere or high-consequence environments.
- Six Sigma Green Belt or comparable process-improvement, acquisition, logistics, project-management, or quality credential.
- Current Top Secret/SCI eligibility; Special Access Program eligibility or experience; or active Department of Energy Q clearance
Also "Required Certifications: None" maybe not needed.
Pay: Salary Range $195,000 - $230,000 USD.
We should not include "REAL ID Requirement", "Export Control and Licensing", "Privacy", "EEO Statement", etc.
Now produce HTML.
Structure:
About the role
... (the paragraph)
Responsibilities
Qualifications
Maybe split into Required and Desired subheadings? But rule: prefer few substantive sections over many thin ones. Could have two subsections using
? Not allowed? Only headings allowed are for section headings. Could we use for Required Qualifications and another for Desired Qualifications? That would be two sections. Might be okay but they said prefer few substantive sections over many thin ones. Having two qualification sections may be thin but still substantive. Could combine into one Qualifications section with two lists, maybe with a intro distinguishing required vs desired. That's one section.
Thus:
Qualifications
Required:
Desired:
But we must not invent headings; using is okay.
Pay:
Pay
Salary Range $195,000 - $230,000 USD
We should not include schedule or benefits.
Now ensure we preserve all substantive information. Check we didn't miss any details like "Position Contingent Upon Contract Award: Yes", "Employment Type: Regular Full-time", "Background Check Type: 7 Year Pre-Employment", "Drug Screen Required: None". Those are metadata; maybe we can drop as minor metadata per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." So we could include a short paragraph at end maybe under About the role? But they said fold minor metadata into a short
or drop it. Could include a short paragraph after About the role containing those details. However they also said "Preserve ALL substantive information". Are those substantive? They are employment details; maybe considered substantive. But they also said "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 those details.
Let's capture: Employment Type: Regular Full-time; Background Check Type: 7 Year Pre-Employment; Drug Screen Required: None; Position Contingent Upon Contract Award: Yes; U.S. Citizenship Required: Yes (already covered); Security Clearance Required: Top Secret (covered). Also "Required Certifications: None". Could include.
We'll add a
after Qualifications maybe: "Employment Type: Regular Full-time; Background Check: 7 Year Pre-Employment; Drug