Computer Systems Architect - Mid to Experienced Level (MD, TX)

We need to output HTML fragment with sections: Responsibilities, maybe Areas of Specialization? 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 (the page already shows it) and 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. We need to extract substantive content: Responsibilities (multiple bullet points). Also Areas of Specialization (EMS, EIA, ACS) each with description. Also Job Summary (maybe as About the role? but we can treat as a prose paragraph). Qualifications (minimum qualifications, degree, experience, etc). Pay, Benefits, Work Schedule (these are present: Pay, Benefits, Work Schedule). Also DCIPS Trial Period (maybe part of Benefits? but it's separate; but we can include under a section maybe "Additional Information"? However only allowed headings are those listed; we can maybe put trial period under Benefits? But it's not exactly benefits. Could include under a generic

  after Benefits? The instruction: include a section ONLY when posting has real, specific content for it. We have Pay, Benefits, Work Schedule sections present. So we should create those headings. We also have Qualifications heading present. Also Responsibilities heading present. Also maybe "Job Summary" could be under "About the role"? But we can just include a

  after Responsibilities before Qualifications? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content exists. We have Responsibilities, Qualifications, Pay, Benefits, Work Schedule. Also maybe "Skills"? Not explicit. Could omit. We need to preserve all substantive information. So we need to include the bullet lists under Responsibilities (the list of duties). Also include the Areas of Specialization details (maybe as sub-sections under Responsibilities? Or could be separate sections? The instruction says we should not create sections unless posting has real specific content. The Areas of Specialization are described under Responsibilities section (they appear after "Multiple opportunities are available in the following Areas of Specialization (AOS):" then each AOS with description). So we could keep them as part of Responsibilities (maybe as nested lists). But we need to preserve all detail. Could format as

  • for each AOS with sub-lists. Also Job Summary: we can include as a

    before Responsibilities or after? Probably after Responsibilities? The original posting: Responsibilities section then "Multiple opportunities are available..." then "Job Summary". We'll keep Job Summary as a

    maybe under a heading "About the role"? But we don't have that heading explicitly; but we could add an

    About the role

    and put Job Summary there. However instruction says use those headings as examples; we can use About the role if we have content. The Job Summary is substantive. So we could create About the role section. But we must not repeat the job title as a heading. That's fine. We need to strip boilerplate: "Note: Please upload a copy of your transcripts..." that's application instruction; we should remove. Also "How To Apply" etc. Remove. Also remove duplicated lines. Now craft HTML. Structure:

    About the role

    Job Summary text...

    Responsibilities

    • Modernize IT architecture through analysis of research and introducing changes based on evolving project requirements by designing, developing, and optimizing the structure and performance of computer systems and computing platforms
    • Integrate industry trends, by evaluating and selecting emerging technologies to improve system performance, scalability, reliability, and efficiency through technologies and standards and new vendor features
    • Evaluate emerging technologies, standards and new vendor features, while supporting research and development efforts for new technologies, networking solutions, virtualization, cloud computing and artificial intelligence capabilities
    • Collaborate with experts in technical and application teams to identify, evaluate and recommend technical solutions to support project requirements
    • Produce compliance results for established project requirements and IT architecture while ensuring systems architecture meet security, reliability, availability and regulatory compliance requirements
    • Define and analyze data requirements, mapping legacy data stores and formats to logical and physical data models, review technical designs providing guidance on architectural best practices
    • Propose standard ways for information transport between IT systems and stored within corporate knowledge databases
    • Perform architectural alignment of the enterprise logical data model and physical data models, while supporting capacity planning and long-term infrastructure strategy to accommodate organizational growth
    • Create technical documentation, architecture diagrams, and design specifications for stakeholders and development teams
    • Provide technical leadership and mentoring to engineering teams
    Then maybe a subheading for Areas of Specialization? Could be part of Responsibilities as a list. But we already have list; we could add another
    for AOS. However we need to preserve the AOS details. Could add another
    after the responsibilities list, with heading maybe

    Areas of Specialization

    but that's not in allowed headings list. But we could embed within Responsibilities as nested list items. However the instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings but better to stick to those. We could incorporate AOS details as part of Responsibilities using

    • with sublists. Simplify: after the responsibilities list, add another
      with each AOS as
      • containing

        ? But we cannot use headings inside li? Could use . But maybe better to create a separate section "Areas of Specialization" using

        though not in list but maybe acceptable. The instruction says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can use other headings as needed. But to be safe, we could embed AOS details within Responsibilities as a nested list. Let's do:

        Responsibilities

        • Modernize IT architecture through analysis of research and introducing changes based on evolving project requirements by designing, developing, and optimizing the structure and performance of computer systems and computing platforms
        ...
        • Provide technical leadership and mentoring to engineering teams
        • Areas of Specialization:
          • Environment Maintenance and Sustainment (EMS): ... description ...
          • Enterprise IT Architecture (EIA): ... description ...
          • Advanced Computing Systems (ACS): ... description ...

        That preserves details. Now Qualifications section: we need to include the qualifications text: minimum qualifications, degree requirements, relevant experience, FULL PERFORMANCE entry, SENIOR entry, etc. We'll put as

        maybe each bullet. But we need to preserve all substantive information: The qualifications paragraph includes many sentences. We'll break into bullet points for clarity but must not lose info. Could keep as

        but they said use

        • for any list of duties/requirements/benefits. Qualifications is a list of requirements, so we should use
          • . We'll split into logical items. Items: - Degree must be in Computer Science (CS). Related fields (e.g., Engineering, Mathematics, Information Technology, Information Systems) may be considered relevant if the programs contain, at minimum, a concentration of courses in the following foundational CS areas: algorithms; computer architecture (not network architecture); programming methodologies and languages; data structures; logic and computation; and advanced mathematics (for example, calculus, discrete mathematics). - Relevant experience must be in the design/development of computer or information systems and include engineering hardware and/or software over their lifecycle (i.e., requirements analysis, design, implementation, testing, integration, deployment/installation, and maintenance), programming, computer systems research, reverse engineering, and/or computer/network security. - Completion of military training in a relevant area such as JCAC (Joint Cyber Analysis course) will be considered towards the relevant experience requirement (i.e., 24-week JCAC course will count as 6 months of experience). - FULL PERFORMANCE Entry is with a Bachelor's degree plus 3 years of relevant experience or a Master's degree plus 1 year of relevant experience or a Doctoral degree and no experience. An Associate's degree plus 5 years of relevant experience may be considered for individuals with in-depth experience that is clearly related to the position. - SENIOR Entry is with a Bachelor's degree plus 6 years of relevant experience or a Master's degree plus 4 years of relevant experience or a Doctoral degree and 2 years of relevant experience. An Associate's degree plus 8 years of relevant experience may be considered for individuals with in-depth experience that is clearly related to the position. We'll put each as
          • . Now Pay, Benefits, Work Schedule sections. Pay: The posting says: "Pay: Salary offers are based on candidates' education level and years of experience relevant to the position and also take into account information provided by the hiring manager/organization regarding the work level for the position. Salary Range: $105,262 - $192,764 (Full Performance, Senior) Salary range varies by location, work level, and relevant experience to the position. Training will be provided based on the selectee's needs and experience." We need to include all that. Use
            • for list? It's prose but could be a

              . The instruction: Use

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

                for prose. Pay is not a list; it's prose. So we can use

                . Benefits: "NSA offers a comprehensive benefits package." That's it. That's prose; we can use

                . Work Schedule: "This is a full-time position, Monday - Friday, with basic 8hr/day work requirement between 6:00 a.m. and 6:00 p.m. (flexible)." Also DCIPS Trial Period details: maybe we could include under Work Schedule or Benefits? It's not exactly benefits. Could be its own section but not in allowed headings. Could include under Work Schedule as additional prose. We'll add after Work Schedule paragraph. Thus:

                Pay

                Salary offers are based on candidates' education level and years of experience relevant to the position and also take into account information provided by the hiring manager/organization regarding the work level for the position. Salary Range: $105,262 - $192,764 (Full Performance, Senior). Salary range varies by location, work level, and relevant experience to