Software Engineer 2

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We need to parse the job posting. Key info: - Title: SOFTWARE ENGINEER SENIOR (but we must not repeat as heading). So we will not output a heading for title. - Clearance: Must Currently Possess Top Secret SCI + Polygraph; Must Be Able To Obtain Top Secret SCI + Polygraph. This is a requirement. - US Citizenship Required Yes. - Experience: 5+ years of related experience. - Education: Bachelor of Arts/Bachelor of Science. - Position Required Skills list (bullets). Also Position Desired Skills list. - Benefits: "Comprehensive benefits and wellness packages, 401K with company match, and competitive pay and paid time off". Also later "Total Rewards At GDIT Our benefits package for all US-based employees includes a variety of medical plan options, some with Health Savings Accounts, dental plan options, a vision plan, and a 401(k) plan offering the ability to contribute both pre and post-tax dollars up to the IRS annual limits and receive a company match. To encourage work/life balance, GDIT offers employees full flex work weeks where possible and a variety of paid time off plans, including vacation, sick and personal time, holidays, paid parental, military, bereavement and jury duty leave. To ensure our employees are able to protect their income, other offerings such as short and long-term disability benefits, life, accidental death and dismemberment, personal accident, critical illness and business travel and accident insurance are provided or available." Thus we have benefits content. - Pay: "The likely salary range for this position is $152,150 - $205,850." So we have Pay section. - Schedule: "Scheduled Weekly Hours 40". Also "Telecommuting Options Onsite Work Location: USA MD Annapolis Junction". Travel Required None. So schedule: 40 hours per week, onsite, no travel. - About the role: The job description paragraph: "SOFTWARE ENGINEER SENIOR Transform technology into opportunity as a Software Engineer Senior at GDIT. Shape what’s next for mission-critical government projects while shaping what’s next for your engineering career. MEANINGFUL WORK AND PERSONAL IMPACT The Software Engineer shall be responsible for implementing access controls and permission solutions for securing access to critical HPC system resources through robust security mechanisms, ensuring compliance with the Agency’s security policies and industry standards." Thus we can have About the role section with that prose. - Responsibilities: The description includes responsibilities: implementing access controls and permission solutions for securing access to critical HPC system resources through robust security mechanisms, ensuring compliance with the Agency’s security policies and industry standards. Possibly also other responsibilities? Not much else. We'll include that. - Requirements: Education, experience, clearance, citizenship, maybe also required skills list? Usually required skills go under Skills or Requirements. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put what. We have "Education: Bachelor of Arts/Bachelor of Science", "Experience: 5+ years of related experience", "Security clearance required: TS/SCI w/ Polygraph", "US Citizenship Required Yes". Those are requirements. Qualifications maybe similar to Requirements? Could be used for certifications etc. There's "Certifications None". So we could skip Qualifications if no content. Skills: we have required skills list and desired skills list. We'll put them under Skills. Benefits: we have content. Pay: salary range. Schedule: weekly hours, onsite, travel none. We must not include headings with filler like "commensurate with experience". We have actual content. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, legal, navigation, etc. Also remove "About Our Work", "Join our Talent Community", etc. Also remove "GDIT IS YOUR PLACE" maybe considered boilerplate? It's about growth, support, rewards, community. That could be considered benefits? But we already have benefits section. The "GDIT IS YOUR PLACE" includes Growth, Support, Rewards, Community. That's somewhat fluff but still describes benefits and culture. However we already have benefits; we could incorporate some of that into Benefits section? The instruction: Prefer a few substantive sections over many thin ones. So we could combine those into Benefits? But they are not exactly benefits; they are about culture. Might be considered fluff. Safer to omit unless it's specific substantive content. The "Growth: AI-powered career tool..." etc is somewhat generic. Might be considered boilerplate. I'd omit. Also "OWN YOUR OPPORTUNITY" etc is fluff. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all substantive info from the posting: clearance, citizenship, experience, education, responsibilities, required skills, desired skills, benefits details, pay range, schedule (hours, location, travel). Also maybe note "Telecommuting Options Onsite Work Location: USA MD Annapolis Junction". That's location info; maybe we can include under Schedule or a separate section? There's no heading for Location. Could put under Schedule as part of schedule details (onsite location). Or we could add a separate section? Not allowed headings beyond the list. So we can include location in Schedule section. Also "Travel Required None". Include in Schedule. Now we need to output HTML fragment with

headings and appropriate

or

• . We must not output markdown code fences. Let's craft:

  About the role

  SOFTWARE ENGINEER SENIOR Transform technology into opportunity as a Software Engineer Senior at GDIT. Shape what’s next for mission-critical government projects while shaping what’s next for your engineering career. MEANINGFUL WORK AND PERSONAL IMPACT The Software Engineer shall be responsible for implementing access controls and permission solutions for securing access to critical HPC system resources through robust security mechanisms, ensuring compliance with the Agency’s security policies and industry standards.

  But note we repeated the title "SOFTWARE ENGINEER SENIOR". The instruction: Do NOT repeat the job title as a heading (the page already shows it). It didn't say we cannot include it in prose. It's okay to keep it in the description. However we might want to avoid duplication but it's fine. Alternatively we could start after that: "Transform technology into opportunity..." but we need to preserve all substantive information. The title is part of the posting; but we already have it displayed elsewhere. It's okay to keep it in the paragraph. Now Responsibilities: Could be same as above? Actually the responsibilities are the implementing access controls etc. We could put that under Responsibilities. But we already have that in About the role. To avoid duplication, we could split: About the role includes the introductory transform technology sentence; Responsibilities includes the specific duty. Let's parse: About the role: "Transform technology into opportunity as a Software Engineer Senior at GDIT. Shape what’s next for mission-critical government projects while shaping what’s next for your engineering career." Responsibilities: "The Software Engineer shall be responsible for implementing access controls and permission solutions for securing access to critical HPC system resources through robust security mechanisms, ensuring compliance with the Agency’s security policies and industry standards." Thus we separate. Now Requirements: Education, Experience, Clearance, Citizenship. We can make a
  • list. Education: Bachelor of Arts/Bachelor of Science Experience: 5+ years of related experience Security clearance required: TS/SCI w/ Polygraph US Citizenship Required: Yes We could also include "Must Currently Possess Top Secret SCI + Polygraph Clearance Level Must Be Able To Obtain Top Secret SCI + Polygraph". That's essentially same as TS/SCI w/ Polygraph. We'll capture as "Must currently possess Top Secret SCI + Polygraph clearance; must be able to obtain Top Secret SCI + Polygraph clearance." Now Qualifications: There's "Certifications None". That's not substantive; we can skip Qualifications section. Skills: Required skills list and Desired skills list. We'll make two subheadings? Not allowed; only the main headings. We can put both under Skills heading, maybe separate

    for Required Skills and Desired Skills, each with

    . Thus:

    Skills

    Required Skills:

    • Experience using the Linux CLI and Linux tools
    • Proficiency in scripting (Bash/Python) to automate tasks and processes
    • Recent software development experience using Python
    • Recent software development experience using Rust
    • Experience with automation frameworks including Ansible for orchestrating deployment
    • Experience developing authentication protocols, authorization logic, access control lists, and permissions for HPC systems in a Linux environment
    • Basic Linux systems administration including User and Group Management
    • Experience with CI/CD principles, methodologies, and tools including GitLab CI
    • Familiar with Agile, Scrum, or Scaled Agile Framework (SAFe) methodologies
    • Experience with Git Source Control System

    Desired Skills:

    • Experience with containerization technologies such as Docker, PodMan, containerd
    • Experience with the Atlassian Tool Suite (JIRA, Confluence)
    Now Benefits: We have detailed benefits. We'll create a

    summarizing. But we need to preserve all substantive information: medical plan options with HSA, dental, vision, 401(k) pre/post tax, company match, flex work weeks, paid time off plans (vacation, sick, personal, holidays, paid parental, military, bereavement, jury duty), short/long-term disability, life, AD&D, personal accident, critical illness, business travel accident insurance. Also earlier: "Comprehensive benefits and wellness packages, 401K with company match, and competitive pay and paid time off". We'll include the detailed list. Thus:

    Benefits

    GDIT offers a comprehensive benefits package for all US-based employees, including:

    • Medical plan options, some with Health Savings Accounts
    • Dental plan options
    • Vision plan
    • 401(k) plan allowing pre‑ and post‑tax contributions up to IRS annual limits with company match
    • Flexible work weeks where possible
    • Paid time off plans: vacation, sick, personal time, holidays, paid parental, military, bereavement, and jury duty leave
    • Short‑ and long‑term disability benefits
    • Life, accidental death and dismemberment (AD&D), personal accident, critical illness, and business travel/accident insurance
    • Wellness programs and additional offerings reviewed regularly for competitiveness
    Now Pay: salary range.

    Pay

    The likely salary range for this position is $152,150 - $205,850. Salary will be set based on experience, geographic location, and possibly contractual requirements and may fall outside this range.

    Now Schedule: weekly hours, onsite location, travel.

    Schedule

    Scheduled weekly hours: 40. Work location: Onsite at USA, MD, Annapolis Junction. Travel required: None.

    We might also include "Telecommuting Options Onsite Work Location". Already captured. Now we need to ensure we didn't include any boilerplate like EEO, legal, etc. We omitted. Check for any other substantive info: "About Our Work" etc we omitted. "Join