Senior Systems Engineer

We need to output HTML fragment with sections: About the role? The posting includes Position Overview, Responsibilities, Qualifications, What You Can Expect (maybe Benefits?), Pay Range. Also maybe "Benefits" from description. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and produce sections with headings as appropriate. We have: - Position Overview: a paragraph describing role. Could be "About the role" or "Position Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map "Position Overview" to "About the role". Use

  About the role

  then

  with the overview text. - Responsibilities: list of bullet points (each sentence ends with period). Use

  Responsibilities

  then
  • each bullet. - Qualifications: includes Required and Desired. Could be split into Requirements (maybe Required) and Desired Knowledge/Skills. The instruction says we can have Requirements, Qualifications, Skills sections. We need to decide. The posting has "Qualifications Required:" and "Desired Knowledge of ...". So we could have

    Qualifications

    with required and desired as lists? Or separate:

    Requirements

    for required qualifications,

    Skills

    for desired knowledge. But we must not create thin sections. Perhaps combine required and desired under Qualifications with subheadings? But we cannot use headings other than h3? The instruction only says use h3 for section headings (list). It doesn't forbid other headings, but we should follow the pattern. Could have

    Qualifications

    then within that we can have

    for required and desired paragraphs, and maybe

    for lists. However the required qualifications are a list of items (each sentence). Desired knowledge also list. We could produce:

    Qualifications

    Required:

    ...

    Desired:

    ...
    That seems okay. - What You Can Expect: includes culture description, benefits, etc. This could map to Benefits section. The posting mentions benefits: healthcare, wellness, financial, retirement, family support, continuing education, time off benefits. Also mentions flexible time off benefit, learning resources. So we can create a Benefits section with those details. Also maybe "What You Can Expect" could be considered "Benefits". We'll create

    Benefits

    and include the description. - Pay Range: The posting includes "The Proposed Salary Range For This Position Is $94,400 - $198,200". Also earlier paragraph about pay range factors. So we should create a Pay section with that range. Use

    Pay

    then

    with the range and maybe note about factors. - Schedule: Not mentioned besides Full time. Could we create Schedule section? The posting says Time Type: Full time. That's schedule info. Should we include Schedule section? The instruction says only create Schedule section if posting actually states them. It does state Time Type: Full time. So we could include Schedule section with that info. However we might also incorporate that into a short paragraph under About the role? But better to follow instruction: include Schedule section if posting states it. It does state Full time. So we can add

    Schedule

    Full time

    . However we need to avoid filler placeholder text. "Full time" is substantive. - Also we have Job Category: Engineering, Minimum Clearance Required to Start: TS/SCI with Polygraph, Employee Type: Regular, Percentage of Travel Required: Up to 10%, Type of Travel: Local. These are metadata. The instruction says 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 top maybe under About the role? Or we could create a

    with that metadata. But we should preserve ALL substantive information. So we need to include that info somewhere. Could add a

    after the overview heading that includes Job Category, Clearance, Employee Type, Travel. Or we could incorporate into About the role paragraph. Better: After the overview paragraph, add a

    containing: Job Category: Engineering; Minimum Clearance Required to Start: TS/SCI with Polygraph; Employee Type: Regular; Percentage of Travel Required: Up to 10%; Type of Travel: Local. But we need to avoid duplication. The overview already mentions supporting DISA etc. So adding metadata is fine. Now we need to remove boilerplate: EEO statement, etc. At end there is "CACI is an Equal Opportunity Employer...". That's boilerplate, remove. Also remove "What You Can Expect" heading? We'll convert to Benefits. Now produce HTML. Structure:

    About the role

    [overview text]
    Job Category: Engineering; Minimum Clearance Required to Start: TS/SCI with Polygraph; Employee Type: Regular; Percentage of Travel Required: Up to 10%; Type of Travel: Local.

    But we need to keep overview text as is. Let's copy overview: "The Senior Systems Engineer Level 3 will support the Zero Trust Identity, Credential, and Access Management (ZT ICAM) program and related deployments for DISA and other Department of War clients. This role requires applying sound systems engineering practices to requirements, architecture, integration, verification, and technical documentation. Additionally, the engineer will support the ZT ICAM Federated Authorization Service by defining operational needs, interfaces, distributed authorization requirements, and customer integration strategies. Collaboration with government, industry, product, and customer teams is essential to produce clear standards, guides, and engineering artifacts that are implementable, testable, and suitable for diverse environments." We'll put that in a

    . Then after that maybe a

    for metadata. Alternatively we could combine into one

    with both. Now Responsibilities: list each bullet. Let's extract responsibilities sentences: - Develop, analyze, allocate, and maintain functional, interface, security, performance, and operational requirements with end-to-end traceability. - Apply systems engineering processes to architecture, interface management, trade studies, risk management, configuration control, integration, and verification activities. - Define use cases, requirements, interfaces, and interactions among PAP, PDP, PIP, PEP, identity providers, attribute sources, relying party services, and federation hubs. - Address person entity, non-person entity, resource, application, and service-to-service authorization across enterprise, multi-domain, tactical, and disconnected environments. - Develop architecture descriptions, interface documentation, requirements traceability matrices, verification procedures, release documentation, and customer integration guides. - Work with DISA and other Department of War customer teams to assess environments, identify integration gaps, support deployment planning, and resolve technical issues. - Draft and review technical standards, implementation guidance, conformance criteria, and compliance matrices using clear, measurable, and vendor-neutral requirements. - Lead technical reviews, adjudicate comments, brief stakeholders, and maintain approved engineering and documentation baselines. Each as

    • . Now Qualifications Required list: - TS/SCI clearance with polygraph. - Bachelor’s degree in Systems Engineering, Computer Science, Information Systems, Engineering, or a related discipline, or equivalent experience as permitted by contract. - Senior systems engineering experience supporting software-intensive systems through requirements, design, integration, test, deployment, and sustainment. - Experience with requirements elicitation, decomposition, allocation, baselining, traceability, interface management, risk management, and verification and validation. - Demonstrated ability to write clear technical requirements, architecture and interface documentation, installation/integration guides, and verification procedures. - Experience working with customer integration or deployment teams in regulated, mission, or enterprise environments. - Ability to assess designs and implementations, identify gaps and risks, and recommend technically sound courses of action. - Strong technical writing, facilitation, briefing, and cross-organizational collaboration skills. Desired Knowledge list: - Knowledge of Zero Trust, ICAM, Attribute-Based Access Control, and NIST SP 800-162. - Understanding of federated or distributed authorization, including PAP, PDP, PIP, PEP, policy and attribute exchange, trust, synchronization, and decision portability. - Experience supporting open architecture, modularity, interoperability, standards development, or conformance assessment across multiple organizations. - Familiarity with REST APIs, JSON, PKI, mutual TLS, OAuth 2.0, OpenID Connect, SAML, containers, and Kubernetes. - Experience with Department of War customers, DDIL operations, DevSecOps, software supply chain security, or Section 508 documentation. - Ability to understand and communicate complex software systems. - Experience using Jira, Confluence, Microsoft Word, Visio, SharePoint, or Git-based repositories. We'll put these under Qualifications heading with subheadings maybe

      Required:

      then
      etc. Or we could have two separate sections: Requirements and Skills. But we have Qualifications heading allowed. We'll do:

      Qualifications

      Required:

      ...

      Desired:

      ...
      Now Benefits section: extract from "What You Can Expect" and benefits paragraph. What You Can Expect paragraph: "A culture of integrity. At CACI, we place character and innovation at the center of everything we do. As a valued team member, you’ll be part of a high-performing group dedicated to our customer’s missions and driven by a higher purpose – to ensure the safety of our nation. An environment of trust. CACI values the unique contributions that every employee brings to our company and our customers - every day. You’ll have the autonomy to take the time you need through a unique flexible time off benefit and have access to robust learning resources to make your ambitions a reality. A focus on continuous growth. Together, we will advance our nation's most critical missions, build on our lengthy track record of business success, and find opportunities to break new ground — in your career and in our legacy." Then benefits paragraph: "Our employees value the flexibility at CACI that allows them to balance quality work and their personal lives. We offer competitive compensation, benefits and learning and development opportunities. Our broad and competitive mix of benefits options is designed to support and protect employees and their families. At CACI, you will receive comprehensive benefits such as; healthcare, wellness, financial, retirement, family support, continuing education, and time off benefits." We can combine into Benefits section. Thus

      Benefits

      ...

      containing all that. Now Pay section: The posting includes: "Pay Range There are a host of factors that can influence final salary including, but not limited to, geographic location, Federal Government contract labor categories