We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting.
Content:
- Intro about ASRC Federal: description of company, mission, etc. Could be "About the role"? Actually "About the role" could be a summary of the position. The posting includes description of the program, environment, etc. That could be "About the role". We'll include that.
- Responsibilities: list of primary responsibilities bullet points.
- Requirements: maybe Minimum Qualifications? Could be "Requirements" or "Qualifications". The posting has "Minimum Qualifications". We'll treat as "Requirements" or "Qualifications". We need to decide which headings to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. But we should avoid thin sections. The posting includes Minimum Qualifications (education, experience). Could be "Requirements". Also there is "We invest in the lives..." benefits. That's Benefits.
- Skills: maybe not explicitly listed separate; but we could infer from qualifications: Java/Spring, Kubernetes, etc. Could be a Skills section. However we should only include if posting has real specific content. The posting does list specific technical skills: Java/Spring, Kubernetes, Azure IL6, PostgreSQL EDB, REST APIs, DevSecOps, SIPR, etc. Could be a Skills section.
- Pay: posting mentions salary depends on factors, posted pay ranges are guideline only, not guarantee. No specific numbers. So we should NOT include Pay section because no specific pay info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: posting mentions benefits offered may include health care, dental, vision, life insurance; 401(k); education assistance; paid time off including PTO, holidays, and any other paid leave required by law. That's specific enough to include Benefits.
- Schedule: posting says full-time position located onsite at Fort Meade, Maryland. Less than 10% travel. That's schedule info (full-time, onsite, travel). So we can include Schedule section.
- About the role: we can include a paragraph summarizing the role.
- Responsibilities: list.
- Requirements/Qualifications: we have Minimum Qualifications. Could be one section "Requirements". Or we could split into Requirements (education/experience) and Qualifications (technical). But to avoid thin sections, maybe combine into "Requirements". However the instruction allows both if content. But we need to avoid filler. Let's decide: Use "Requirements" for education/experience/minimum qualifications. Use "Skills" for technical skills. That seems reasonable.
Now we need to strip boilerplate: EEO statement, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. There's no explicit application instructions. We'll exclude EEO statement.
We need to preserve all substantive information. So we need to include details about ASRC Federal being Alaska Native owned, government contractor, etc. That's part of "About the role"? Might be better as a brief intro before headings. The instruction: do NOT repeat the job title as a heading (the page already shows it). So we can start with a
about the company and role.
Then headings.
Let's draft:
ASRC Federal is a leading government contractor furthering missions in space, public health and defense. As an Alaska Native owned corporation, our work helps secure an enduring future for our shareholders. Join our team and discover why we are a top veteran employer and Certified Great Place to Work™. ASRC Federal is seeking a Chief Engineer/Lead Architect supporting the Defense Information Systems Agency Joint Planning and Execution Services and Joint Capabilities Requirements Manager Sustainment Services program. JPES/JCRM supports mission-critical Global Force Management planning, execution coordination, operational data management, and interoperability for globally distributed Department of Defense users and command organizations. The program encompasses Agile software sustainment and enhancement, secure cloud and platform operations, system integration, testing and release management, cybersecurity compliance, and operational mission support. The technical environment includes classified SIPR and Azure IL6 enclaves, Kubernetes, Red Hat Enterprise Linux, Java/Spring, React, PostgreSQL EDB, transitional Oracle integration, REST APIs, ELK observability, and DevSecOps pipelines integrated with DISA’s C2FS/C2SF environment. The work requires close collaboration with DISA program, engineering, product, security, and operational-user stakeholders. This is a full-time position located onsite at Fort Meade, Maryland. The position requires U.S. citizenship, an active Secret security clearance, and less than 10% travel. Employment is contingent upon contract award and Government approval of key personnel.
Then
About the role
maybe we already covered that. Actually we could treat the above as "About the role". But we already have a paragraph describing the role and company. Could be considered About the role. However we might duplicate. Better to move that paragraph under About the role heading. The instruction: do NOT repeat the job title as a heading. It's okay to have About the role heading with a paragraph.
Thus:
About the role
ASRC Federal is a leading government contractor furthering missions in space, public health and defense. As an Alaska Native owned corporation, our work helps secure an enduring future for our shareholders. Join our team and discover why we are a top veteran employer and Certified Great Place to Work™. ASRC Federal is seeking a Chief Engineer/Lead Architect supporting the Defense Information Systems Agency Joint Planning and Execution Services and Joint Capabilities Requirements Manager Sustainment Services program. JPES/JCRM supports mission-critical Global Force Management planning, execution coordination, operational data management, and interoperability for globally distributed Department of Defense users and command organizations. The program encompasses Agile software sustainment and enhancement, secure cloud and platform operations, system integration, testing and release management, cybersecurity compliance, and operational mission support. The technical environment includes classified SIPR and Azure IL6 enclaves, Kubernetes, Red Hat Enterprise Linux, Java/Spring, React, PostgreSQL EDB, transitional Oracle integration, REST APIs, ELK observability, and DevSecOps pipelines integrated with DISA’s C2FS/C2SF environment. The work requires close collaboration with DISA program, engineering, product, security, and operational-user stakeholders. This is a full-time position located onsite at Fort Meade, Maryland. The position requires U.S. citizenship, an active Secret security clearance, and less than 10% travel. Employment is contingent upon contract award and Government approval of key personnel.
Then Responsibilities:
Responsibilities
- Serve as the primary contractor technical interface to DISA engineering leadership.
- Establish and govern the JPES/JCRM technical architecture and modernization roadmap.
- Lead architecture for Java/Spring enterprise applications deployed on RHEL and Kubernetes.
- Oversee Azure IL6 and multi-enclave deployment architecture.
- Govern PostgreSQL EDB architecture, database synchronization, and transitional Oracle/JOPES data replication.
- Architect secure REST APIs, web services, and external DoD system interfaces.
- Guide containerization, infrastructure-as-code, automated deployment, and DevSecOps integration.
- Oversee ELK-based logging, monitoring, performance, and observability.
- Evaluate technical changes, alternatives, dependencies, and risks.
- Lead technical reviews, design sessions, sprint demonstrations, troubleshooting, and security assessments.
- Ensure modular, maintainable, open architectures consistent with Government Purpose Rights requirements.
- Coordinate technical decisions across development, integration, platform, test, database, and cybersecurity teams.
Then Requirements (minimum qualifications):
Requirements
- Bachelor’s degree in engineering, computer science, information technology, or a related discipline; four additional years of experience may be accepted in lieu of a degree.
- At least 10 years of enterprise software architecture or chief‑engineer experience.
- At least eight years of Java/Spring development or technical leadership experience.
- Deep experience with enterprise web applications, Kubernetes, secure government cloud environments, and DevSecOps.
- Experience architecting PostgreSQL databases, replication, and multi‑system data exchange.
- Strong experience with REST APIs, web services, and external system integration.
- Experience operating in SIPR or comparable classified environments.
- Demonstrated ability to communicate complex technical decisions to Government stakeholders and senior leadership.
- Active Secret clearance required at time of hire.
Then Skills: we could list specific technologies mentioned: Java/Spring, Kubernetes, Red Hat Enterprise Linux, Azure IL6, PostgreSQL EDB, Oracle integration, REST APIs, React, ELK, DevSecOps, SIPR, etc. But many are already in Requirements. Might be redundant. However we could still have Skills section focusing on technical proficiencies: Java/Spring, Kubernetes, Azure, PostgreSQL, REST APIs, DevSecOps, containerization, infrastructure-as-code, observability (ELK), etc. But to avoid thin sections, maybe we skip Skills and incorporate into Requirements. However the instruction says prefer a few substantive sections over many thin ones. So we can omit Skills if it's thin. But we have already covered many skills in Requirements. So we can skip Skills.
Benefits:
Benefits
- Health care, dental, vision, life insurance
- 401(k)
- Education assistance
- Paid time off including PTO, holidays, and any other paid leave required by law
Schedule:
Schedule
- Full‑time position
- Onsite at Fort Meade, Maryland
- Less than 10% travel
We should not include Pay section.
Check for any duplicated lines: we have not included EEO statement.
Check for any boilerplate: we removed EEO statement.
Check for any placeholders: we have no "commensurate with experience" etc.
Check for preserving all substantive information: we included company description, role description, responsibilities, requirements, benefits, schedule. Did we miss any details like "U.S. citizenship"? We included in About the role paragraph. Also "Employment is contingent upon contract award and Government approval of key personnel." included. Also "less than 10% travel" included in schedule. Also "full-time position located onsite at Fort Meade, Maryland" included. Also "Active Secret clearance required at time of hire" included in Requirements. Also "U.S. citizenship" included. Also "The position requires U.S. citizenship, an active Secret security clearance, and less than 10% travel." we captured.
Also "The work requires close collaboration with DISA program, engineering, product, security, and operational-user stakeholders." included in About the role.
Also "The Chief Engineer / Lead Architect will serve as the senior technical authority for the DISA JPES/JCRM modernization and sustainment effort." This is somewhat covered in Responsibilities (first bullet). Might be okay.
Also "This position will govern application, integration, data, cloud, infrastructure, DevSecOps, and security architecture while maintaining the technical integrity of the overall solution." covered.
Also "The Chief Engineer will lead technical strategy for cloud-hosted, containerized enterprise applications operating in classified, multi-enclave environments." covered.
Also "The position will oversee Java/Spring application architecture, Azure and Kubernetes deployment patterns, database synchronization, external DoD interfaces, observability, DevSecOps integration, and modernization of legacy capabilities while maintaining operational continuity." covered.
Thus all substantive info present.
Now output HTML fragment