System Analyst (IT-G Integration)
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content to appropriate sections.
The first paragraph: "Analyzes and evaluates existing or proposed systems and devises solutions to enhance system integration." This sounds like an "About the role" or summary.
Job Grade, Job Tier, Career Area, Supervisor: metadata. Could fold into a short
maybe under a "Position details" or similar, but the rules say don't create headings for minor metadata. Could include in a
at top or in a "Position details" section if we have one. But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We shouldn't invent new headings. So maybe we can put metadata in a
under "About the role" or just a
before sections.
Job Qualifications: This includes experience/education requirements, degree preferences, certificate preferences. This fits "Requirements" or "Qualifications". The rules mention both "Requirements" and "Qualifications" as possible headings. We need to decide. Usually "Requirements" for required qualifications, "Qualifications" for preferred? But the posting has "Job Qualifications" (required) and "Preferred Qualifications". Also "Additional Qualifications/Requirements" (work location). And "Technical (Preferred/Required Skills/Systems)" which is a mix.
Major Duties: clearly "Responsibilities".
Technical skills list: could be "Skills" or part of "Requirements".
Preferred Qualifications: could be "Qualifications" or "Requirements".
We need to avoid thin sections. Let's think about grouping.
Possible sections:
1. About the role (summary paragraph)
2. Responsibilities (Major Duties)
3. Requirements (Job Qualifications, Additional Qualifications/Requirements, Technical required skills)
4. Qualifications (Preferred Qualifications, Preferred technical skills, Degree/Major/Certificate preferences)
5. Skills (Technical skills list) - but maybe combine with Requirements.
But the rules say: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those.
We must not create a section if no real content. The posting has no Benefits, Pay, Schedule explicitly. So omit those.
Now, let's structure:
- About the role: include the first paragraph and maybe the metadata (Job Grade, Tier, Career Area, Supervisor) as a short paragraph.
- Responsibilities: Major Duties as a list.
- Requirements: Job Qualifications (required experience/education), Additional Qualifications/Requirements (work location, remote policy), and the required technical skills from "Technical (Preferred/Required Skills/Systems)" that are required. However, the technical section says "Technical (Preferred/Required Skills/Systems)" and lists many items. It doesn't explicitly separate required vs preferred. But the heading says "Preferred/Required". The list seems to be a mix. The "Preferred Qualifications" section later lists additional preferred items. So maybe the technical list is required? The posting says "Technical (Preferred/Required Skills/Systems)" then a list. Could be both. But we need to preserve all substantive info. Perhaps we can split: Required technical skills and Preferred technical skills. But the posting doesn't clearly separate. However, there is a separate "Preferred Qualifications" section that includes some technical preferences (AWS, SonarQube, etc.). The technical list might be the core required skills. I'll treat the technical list as required skills (since they are under "Technical (Preferred/Required Skills/Systems)" and the preferred qualifications are separate). But the heading says "Preferred/Required". To be safe, I'll include the technical list under "Requirements" as a list of required technical skills, and the "Preferred Qualifications" under "Qualifications". Also the degree/major/certificate preferences are under "Job Qualifications" as "Preferred". So those go to "Qualifications".
Let's parse the content:
Job Qualifications:
- Five years of experience in business systems analysis or development which includes at least two years of experience with Hyperion Essbase development.
- Or Bachelor's degree and three years of experience in business systems analysis or development which includes at least two years of experience with Hyperion Essbase development.
- Required technical skills may vary as requested by the supervisor depending on specific requirements of the position being filled.
- Degree (one Of) BACHELORS DEGREE - Preferred
- Major/Minor (one Of) BUSINESS - Preferred, COMPUTER SCIENCE - Preferred, ENGINEERING MANAGEMENT - Preferred, FINANCE - Preferred, INFORMATION TECHNOLOGY - Preferred, STATISTICS - Preferred
- Certificate/License (one Of) PROJECT MGMT PROFESSIONAL CERT - Preferred
Additional Qualifications/Requirements:
- Work – Onsite (HQ – Dallas, Texas)
- Remote/Telework not authorized per Presidential Memorandum “Return to In Person Work”
- PCS Not Authorized/LSP Not Authorized
Technical (Preferred/Required Skills/Systems): (list of 14 bullet points)
Preferred Qualifications: (list of 7 bullet points)
Major Duties: (list of 7 bullet points)
Job Type: Management
Number of Positions Remaining: 1
Date: 29-Oct-2026 (maybe closing date)
Now, I'll create sections:
About the role
Analyzes and evaluates existing or proposed systems and devises solutions to enhance system integration.
Job Grade: 4 | Job Tier: 3 | Career Area: Information Technology | Supervisor: No
Responsibilities
- Develops programs, dashboards and/or reports using Hyperion Essbase, SQL, UNIX, Oracle, OBIEE or Mainframe applications.
- Prepare technical analysis and documents to include projects scope and timelines.
- Conducts root cause analyses and provides recommendations for solutions.
- Utilize various systems and software to compile and prepare program enhancements.
- Writes programs and user acceptance test plans as required supporting business systems.
- Coordinates installation with end users.
- Performs other duties as assigned.
Requirements
Five years of experience in business systems analysis or development which includes at least two years of experience with Hyperion Essbase development. Alternatively, a Bachelor's degree and three years of experience in business systems analysis or development with at least two years of Hyperion Essbase development experience. Required technical skills may vary as requested by the supervisor depending on specific requirements of the position being filled.
Work location: Onsite at HQ in Dallas, Texas. Remote/telework not authorized per Presidential Memorandum “Return to In Person Work”. PCS and LSP not authorized.
Technical skills
- Five or more years of experience in DevSecOps, DevOps, platform engineering, infrastructure engineering, application security, or a related discipline.
- Demonstrated experience designing, operating, securing, and improving enterprise software delivery platforms and supporting infrastructure.
- Hands-on experience administering enterprise CI/CD platforms, such as GitLab and Jenkins, including pipeline development, build agents, access controls, integrations, and upgrades.
- Experience integrating security testing into CI/CD pipelines, including static application security testing (SAST), secret detection, and container image scanning.
- Experience assessing security findings, prioritizing vulnerabilities based on risk, and coordinating remediation with development, infrastructure, and security teams.
- Strong Linux system administration and troubleshooting skills, including networking, TLS certificates, permissions, and service management.
- Hands-on experience with container technologies and Kubernetes administration, including deployment, troubleshooting, access controls, and platform security.
- Proficiency in Python, Bash, or another scripting language for automation, API integrations, and operational tooling.
- Experience with Infrastructure as Code (IaC) and configuration automation using tools such as Terraform, CloudFormation, or Ansible.
- Experience implementing least-privilege access, secrets management, and credential rotation across delivery platforms and automation workflows.
- Experience managing platform upgrades, security patching, monitoring, backups, recovery procedures, and production changes.
- Demonstrated ability to independently lead technical initiatives, evaluate architectural trade-offs, establish engineering standards, and mentor team members.
- Strong communication and documentation skills, with the ability to explain technical issues, risks, and recommendations to technical and nontechnical stakeholders.
Qualifications
Preferred education: Bachelor's degree in Business, Computer Science, Engineering Management, Finance, Information Technology, or Statistics.
Preferred certification: Project Management Professional (PMP).
Preferred qualifications
- Hands-on experience with AWS cloud services, particularly IAM, VPC, EC2, S3, EKS, CloudWatch, and Secrets Manager.
- Experience with enterprise security and software delivery tools such as SonarQube, Fortify, JFrog Artifactory, or UrbanCode Deploy.
- Experience administering or supporting Atlassian products, including Jira and Confluence.
- Experience with software supply-chain security, including software bills of materials (SBOMs), dependency governance, artifact integrity, and repository management.
- Experience working in regulated environments, implementing security controls, and supporting audits and compliance evidence collection.
- Experience designing highly available platforms and validating disaster recovery procedures.
- Relevant AWS, Kubernetes, Linux, or security certifications.
Position details
- but not in allowed headings. The allowed headings are only those listed. So maybe we should not create "Position details". Instead, fold the job type and number of positions into a at the end or under About the role. The rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can add a
at the bottom
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content to appropriate sections. The first paragraph: "Analyzes and evaluates existing or proposed systems and devises solutions to enhance system integration." This sounds like an "About the role" or summary. Job Grade, Job Tier, Career Area, Supervisor: metadata. Could fold into a short
maybe under a "Position details" or similar, but the rules say don't create headings for minor metadata. Could include in a
at top or in a "Position details" section if we have one. But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We shouldn't invent new headings. So maybe we can put metadata in a
under "About the role" or just a
before sections. Job Qualifications: This includes experience/education requirements, degree preferences, certificate preferences. This fits "Requirements" or "Qualifications". The rules mention both "Requirements" and "Qualifications" as possible headings. We need to decide. Usually "Requirements" for required qualifications, "Qualifications" for preferred? But the posting has "Job Qualifications" (required) and "Preferred Qualifications". Also "Additional Qualifications/Requirements" (work location). And "Technical (Preferred/Required Skills/Systems)" which is a mix. Major Duties: clearly "Responsibilities". Technical skills list: could be "Skills" or part of "Requirements". Preferred Qualifications: could be "Qualifications" or "Requirements". We need to avoid thin sections. Let's think about grouping. Possible sections: 1. About the role (summary paragraph) 2. Responsibilities (Major Duties) 3. Requirements (Job Qualifications, Additional Qualifications/Requirements, Technical required skills) 4. Qualifications (Preferred Qualifications, Preferred technical skills, Degree/Major/Certificate preferences) 5. Skills (Technical skills list) - but maybe combine with Requirements. But the rules say: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those.
We must not create a section if no real content. The posting has no Benefits, Pay, Schedule explicitly. So omit those.
Now, let's structure:
- About the role: include the first paragraph and maybe the metadata (Job Grade, Tier, Career Area, Supervisor) as a short paragraph.
- Responsibilities: Major Duties as a list.
- Requirements: Job Qualifications (required experience/education), Additional Qualifications/Requirements (work location, remote policy), and the required technical skills from "Technical (Preferred/Required Skills/Systems)" that are required. However, the technical section says "Technical (Preferred/Required Skills/Systems)" and lists many items. It doesn't explicitly separate required vs preferred. But the heading says "Preferred/Required". The list seems to be a mix. The "Preferred Qualifications" section later lists additional preferred items. So maybe the technical list is required? The posting says "Technical (Preferred/Required Skills/Systems)" then a list. Could be both. But we need to preserve all substantive info. Perhaps we can split: Required technical skills and Preferred technical skills. But the posting doesn't clearly separate. However, there is a separate "Preferred Qualifications" section that includes some technical preferences (AWS, SonarQube, etc.). The technical list might be the core required skills. I'll treat the technical list as required skills (since they are under "Technical (Preferred/Required Skills/Systems)" and the preferred qualifications are separate). But the heading says "Preferred/Required". To be safe, I'll include the technical list under "Requirements" as a list of required technical skills, and the "Preferred Qualifications" under "Qualifications". Also the degree/major/certificate preferences are under "Job Qualifications" as "Preferred". So those go to "Qualifications".
Let's parse the content:
Job Qualifications:
- Five years of experience in business systems analysis or development which includes at least two years of experience with Hyperion Essbase development.
- Or Bachelor's degree and three years of experience in business systems analysis or development which includes at least two years of experience with Hyperion Essbase development.
- Required technical skills may vary as requested by the supervisor depending on specific requirements of the position being filled.
- Degree (one Of) BACHELORS DEGREE - Preferred
- Major/Minor (one Of) BUSINESS - Preferred, COMPUTER SCIENCE - Preferred, ENGINEERING MANAGEMENT - Preferred, FINANCE - Preferred, INFORMATION TECHNOLOGY - Preferred, STATISTICS - Preferred
- Certificate/License (one Of) PROJECT MGMT PROFESSIONAL CERT - Preferred
Additional Qualifications/Requirements:
- Work – Onsite (HQ – Dallas, Texas)
- Remote/Telework not authorized per Presidential Memorandum “Return to In Person Work”
- PCS Not Authorized/LSP Not Authorized
Technical (Preferred/Required Skills/Systems): (list of 14 bullet points)
Preferred Qualifications: (list of 7 bullet points)
Major Duties: (list of 7 bullet points)
Job Type: Management
Number of Positions Remaining: 1
Date: 29-Oct-2026 (maybe closing date)
Now, I'll create sections:
About the role
Analyzes and evaluates existing or proposed systems and devises solutions to enhance system integration.
Job Grade: 4 | Job Tier: 3 | Career Area: Information Technology | Supervisor: No
Responsibilities
- Develops programs, dashboards and/or reports using Hyperion Essbase, SQL, UNIX, Oracle, OBIEE or Mainframe applications.
- Prepare technical analysis and documents to include projects scope and timelines.
- Conducts root cause analyses and provides recommendations for solutions.
- Utilize various systems and software to compile and prepare program enhancements.
- Writes programs and user acceptance test plans as required supporting business systems.
- Coordinates installation with end users.
- Performs other duties as assigned.
Requirements
Five years of experience in business systems analysis or development which includes at least two years of experience with Hyperion Essbase development. Alternatively, a Bachelor's degree and three years of experience in business systems analysis or development with at least two years of Hyperion Essbase development experience. Required technical skills may vary as requested by the supervisor depending on specific requirements of the position being filled.
Work location: Onsite at HQ in Dallas, Texas. Remote/telework not authorized per Presidential Memorandum “Return to In Person Work”. PCS and LSP not authorized.
Technical skills
- Five or more years of experience in DevSecOps, DevOps, platform engineering, infrastructure engineering, application security, or a related discipline.
- Demonstrated experience designing, operating, securing, and improving enterprise software delivery platforms and supporting infrastructure.
- Hands-on experience administering enterprise CI/CD platforms, such as GitLab and Jenkins, including pipeline development, build agents, access controls, integrations, and upgrades.
- Experience integrating security testing into CI/CD pipelines, including static application security testing (SAST), secret detection, and container image scanning.
- Experience assessing security findings, prioritizing vulnerabilities based on risk, and coordinating remediation with development, infrastructure, and security teams.
- Strong Linux system administration and troubleshooting skills, including networking, TLS certificates, permissions, and service management.
- Hands-on experience with container technologies and Kubernetes administration, including deployment, troubleshooting, access controls, and platform security.
- Proficiency in Python, Bash, or another scripting language for automation, API integrations, and operational tooling.
- Experience with Infrastructure as Code (IaC) and configuration automation using tools such as Terraform, CloudFormation, or Ansible.
- Experience implementing least-privilege access, secrets management, and credential rotation across delivery platforms and automation workflows.
- Experience managing platform upgrades, security patching, monitoring, backups, recovery procedures, and production changes.
- Demonstrated ability to independently lead technical initiatives, evaluate architectural trade-offs, establish engineering standards, and mentor team members.
- Strong communication and documentation skills, with the ability to explain technical issues, risks, and recommendations to technical and nontechnical stakeholders.
Qualifications
Preferred education: Bachelor's degree in Business, Computer Science, Engineering Management, Finance, Information Technology, or Statistics.
Preferred certification: Project Management Professional (PMP).
Preferred qualifications
- Hands-on experience with AWS cloud services, particularly IAM, VPC, EC2, S3, EKS, CloudWatch, and Secrets Manager.
- Experience with enterprise security and software delivery tools such as SonarQube, Fortify, JFrog Artifactory, or UrbanCode Deploy.
- Experience administering or supporting Atlassian products, including Jira and Confluence.
- Experience with software supply-chain security, including software bills of materials (SBOMs), dependency governance, artifact integrity, and repository management.
- Experience working in regulated environments, implementing security controls, and supporting audits and compliance evidence collection.
- Experience designing highly available platforms and validating disaster recovery procedures.
- Relevant AWS, Kubernetes, Linux, or security certifications.
Position details
- but not in allowed headings. The allowed headings are only those listed. So maybe we should not create "Position details". Instead, fold the job type and number of positions into aat the end or under About the role. The rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can add a
at the bottom