Software Developer (Systems Software)

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Overview: "Acuity, Inc. seeks dynamic, self-motivated individuals with experience as a Software Developer (Systems Software). This position will fill a LEAD position on the team. High visibility. Support a team building an integrated enterprise IT support model to drive efficiencies in the talent space and better address strategic requirements associated with learning, training compliances, foreign language development and retention, job advertisements, selection, and performance." That's overview; could be About the role. Then "Why Acuity?" repeated twice: first bullet list: Strong work-life balance and a people-first culture, Competitive compensation + Health/Dental/Vision coverage, 401(k) with company match, Up to $3,000 annually for training and certifications and up to $3,000 for degree seeking programs, Recognized as a Best Places to Work..., Named a Top Workplace... Second "Why Acuity?" paragraph: "Are you ready to use your expertise in the areas of IT Modernization, Data Enablement, and Hyperautomation to make a real difference? Join Acuity, Inc., a technology consulting firm that supports federal agencies. We combine industry partnerships and long-term federal experience with innovative technical leadership to support our customers’ critical missions." That could be part of About the role or maybe separate. Qualifications: "Required Skills:" list many bullet points. Then "Preferred Skills" list. Then "Clearance Requirements TS/SCI w/Poly Min USD $160,000.00/Yr. Max USD $210,000.00/Yr." Then "Salary Range" paragraph. We need sections: About the role (overview), Responsibilities? Not explicit responsibilities listed; maybe the overview includes responsibilities: "Support a team building an integrated enterprise IT support model..." Could treat as responsibilities. But we need to decide. We have Qualifications (Required Skills) and Preferred Skills. Could combine into Requirements and Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content. We have overview -> About the role. Responsibilities: maybe not explicit; but we could infer from overview: "Support a team building an integrated enterprise IT support model to drive efficiencies..." That's more like responsibilities. Could put under Responsibilities. Requirements: maybe the clearance and maybe required skills? Actually Required Skills are qualifications. Could put under Qualifications. Skills: maybe Preferred Skills. Benefits: the Why Acuity? bullet list: work-life balance, compensation, health/dental/vision, 401(k), training/certification, degree seeking, awards. Pay: salary range (min/max) plus maybe mention of compensation. Schedule: not mentioned; we should not create Schedule section if not present. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We must not create empty sections. Now format: Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. Let's extract details precisely. About the role prose: "Acuity, Inc. seeks dynamic, self-motivated individuals with experience as a Software Developer (Systems Software). This position will fill a LEAD position on the team. High visibility. Support a team building an integrated enterprise IT support model to drive efficiencies in the talent space and better address strategic requirements associated with learning, training compliances, foreign language development and retention, job advertisements, selection, and performance." We could split into two paragraphs? But we can keep as one

  . Responsibilities: maybe we can list duties: "Support a team building an integrated enterprise IT support model to drive efficiencies in the talent space and better address strategic requirements associated with learning, training compliances, foreign language development and retention, job advertisements, selection, and performance." Also maybe "Provide technical expertise and communications to the Client." Actually that is in Required Skills. But responsibilities could be derived from Required Skills? However we should not invent. Better to keep Responsibilities as the same as overview? Might be duplication. But we need to avoid duplication? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's in the source. The overview already contains that sentence. If we also put it under Responsibilities, we are duplicating but still preserving. Might be okay but could be considered redundant. However we could treat overview as About the role, and Responsibilities could be empty -> we should not create heading if no specific content. So maybe we omit Responsibilities section because no explicit responsibilities beyond overview. But we need to see if there are any explicit responsibilities listed elsewhere. The Required Skills list includes many duties like "Demonstrated experience as a lead on a team providing technical expertise and communications to the Client." That's more like qualifications. There's no separate responsibilities section. Thus we will not include Responsibilities heading. Qualifications: Could include Required Skills list. Also maybe include Clearance Requirements? Could be separate but we can include under Qualifications. Skills: Preferred Skills list. Benefits: list from Why Acuity? first block. Pay: Salary range and maybe mention of compensation. We must not include boilerplate like "Why Acuity?" repeated; we need to extract the substantive content. Let's capture each piece. About the role: as above. Qualifications (Required Skills): list each bullet: - Demonstrated experience as a lead on a team providing technical expertise and communications to the Client. - Demonstrated experience implementing industry best practices and associated technical solutions consistent with accessibility standards and agile methodology. - Demonstrated experience proposing recommendations that provide business value while supporting goals and objectives, with an emphasis on improving User Experience/User Interface (UX/UI), reducing O&M, increasing quality and speed of delivery, transforming, and modernizing web-based application, system, and service components. - Demonstrated experience in developing, maintaining, analyzing, and documenting web-based application, system, and service components and associated interfaces, including those with databases and web services/APIs to assist in decision-making regarding future development. - Demonstrated experience in Java development. - Demonstrated experience with cloud technologies. - Demonstrated experience in developing and maintaining AWS environments and service components and associated interfaces, including those with databases and web services/APIs to assist in decision-making regarding future development. - Demonstrated experience working with COTS products including ServiceNow. - Demonstrated experience in the full accreditation lifecycle. - Demonstrated experience managing Tier 1, Tier 2, and Tier 3 support, using service management systems. - Demonstrated experience developing IT support documents that include SOPs, digital IT workflows, IT knowledge base, pre and post deployment checklists, IT architectural diagrams, system security plans, and administrative processes. - Demonstrated experience developing and maintaining enterprise software, to include license renewals (where applicable), patching, and version update administration. We need to preserve each as

• . Skills (Preferred Skills): list: - Demonstrated experience working with Client and partner IT organizations. - Demonstrated experience working with learning applications. - Demonstrated experience working with language, compliance, and performance management applications. - Demonstrated experience with networking and platform hosting technologies. Benefits: from first Why Acuity? block: - Strong work-life balance and a people-first culture - Competitive compensation + Health/Dental/Vision coverage - 401(k) with company match - Up to $3,000 annually for training and certifications and up to $3,000 for degree seeking programs - Recognized as a Best Places to Work (Washington Business Journal, 8+ years) - Named a Top Workplace by The Washington Post (2022–2025) We should keep as list. Pay: Salary Range paragraph plus clearance min/max? The clearance includes salary min/max. Also there is a Salary Range paragraph describing that final compensation determined based on factors. We need to preserve all substantive info. So we can include both: The clearance requirements line includes "TS/SCI w/Poly Min USD $160,000.00/Yr. Max USD $210,000.00/Yr." And the Salary Range paragraph: "The salary range for this position represents Acuity's good faith estimate of the compensation for this job title at the time of posting. Final compensation will be determined based on factors including, but not limited to, the candidate's qualifications, experience, education, certifications, skills, geographic location, contract requirements, applicable labor categories, and, where applicable, contract award and funding." We could combine into a

  for Pay section. We must not include headings for Pay if content is present. We'll include. Now we need to output only HTML fragment, no /, no markdown. Thus:

  About the role

  Acuity, Inc. seeks dynamic, self-motivated individuals with experience as a Software Developer (Systems Software). This position will fill a LEAD position on the team. High visibility. Support a team building an integrated enterprise IT support model to drive efficiencies in the talent space and better address strategic requirements associated with learning, training compliances, foreign language development and retention, job advertisements, selection, and performance.

  Qualifications

  • Demonstrated experience as a lead on a team providing technical expertise and communications to the Client.
  ...

  Skills

  • Demonstrated experience working with Client and partner IT organizations.
  ...

  Benefits

  • Strong work-life balance and a people-first culture
  ...

  Pay

  TS/SCI w/Poly Min USD $160,000.00/Yr. Max USD $210,000.00/Yr. The salary range for this position represents Acuity's good faith estimate of the compensation for this job title at the time of posting. Final compensation will be determined based on factors including, but not limited to, the candidate's qualifications, experience, education, certifications, skills, geographic location, contract requirements, applicable labor categories, and, where applicable, contract award and funding.

  We should ensure no duplicate content. The overview sentence about support a team... appears also in About the role; we included it there. That's fine. Check for any other substantive content: The second "Why Acuity?" paragraph: "Are you ready to use your expertise in the areas of IT Modernization, Data Enablement, and Hyperautomation to make a real difference? Join Acuity, Inc., a technology consulting firm that supports federal agencies. We combine industry partnerships and long-term federal experience with innovative technical leadership to support our customers’ critical missions." This is substantive; we haven't included it anywhere. Could be part of About the role or maybe a separate section like "About the company". But we have only allowed headings list; we could add another section like "About Acuity" but not in list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could add other headings if needed, but better to stick to those. However we need to preserve all substantive information; we must include that paragraph somewhere. Could incorporate into About the role as additional paragraph. That would preserve it. So we can add another