Programmer III
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content.
We need to parse the posting.
Key info:
- Date: Sep 2, 2026 (maybe not needed)
- Location: AUSTIN, TX, US, 78751
- Agency: Texas Health and Human Services Commission (HHSC)
- Benefits: comprehensive benefits package includes 100% paid employee health insurance for full-time eligible employees, a defined benefit pension plan, generous time off benefits, numerous opportunities for career advancement and more. Also mention "Explore more details on the Benefits of Working at HHS webpage." So we have benefits content.
- Functional Title: Programmer III (same as job title)
- Job Title: Programmer III
- Agency: Health & Human Services Comm
- Department: Medi-Social Serv Apl Dev
- Posting Number: 20887 (metadata, drop)
- Closing Date: 09/16/2026 (metadata)
- Posting Audience: Internal and External (metadata)
- Occupational Category: Computer and Mathematical (maybe part of qualifications)
- Salary Range: $5,425.33 - $8,886.16 (Pay)
- Pay Frequency: Monthly
- Salary Group: TEXAS-B-24
- Shift: Day
- Additional Shift Telework: Travel (maybe schedule)
- Regular/Temporary: Regular
- Full Time/Part Time: Full time
- FLSA Exempt/Non-Exempt: Exempt
- Facility Location: Job Location City: AUSTIN
- Job Location Address: 701 W 51ST ST
- Other Locations: MOS Codes: ... (metadata)
- Brief Job Description: paragraph about role.
- Essential Job Functions (EJFs) with percentages: list of duties.
- Knowledge, Skills And Abilities (KSAs): list of knowledge, skills, abilities.
- Registrations, Licensure Requirements Or Certifications: N/A (skip)
- Initial Screening Criteria: Graduation from accredited four-year college... Experience may be substituted... Five (5) or more years’ experience in programming with Java/J2EE and Web Services.
- Additional Information: None
- Review our Tips for Success... (boilerplate)
- Active Duty... (boilerplate)
- ADA Accommodations (boilerplate)
- Pre-Employment Checks... (boilerplate)
- Telework Disclaimer (maybe schedule/telework)
- Nearest Major Market: Austin (location)
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Review our Tips for Success", "Active Duty...", "ADA Accommodations", "Pre-Employment Checks", "Telework Disclaimer" maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Telework disclaimer maybe not exactly those categories but could be considered boilerplate? However telework info could be relevant to Schedule or Benefits? It says "This position may be eligible for telework. Please note, all HHS positions are subject to state and agency telework policies..." That's somewhat generic but still specific about telework eligibility. Might keep as part of Schedule or maybe a note. But we should keep substantive info: telework eligibility.
We need to include sections only when posting has real specific content.
Potential sections:
- About the role: could use the Brief Job Description paragraph.
- Responsibilities: Essential Job Functions (EJFs) list.
- Requirements: maybe Initial Screening Criteria (education/experience) plus maybe Occupational Category? Could be Requirements.
- Qualifications: maybe Knowledge, Skills And Abilities (KSAs) split into Skills and Knowledge? But we have separate Skills section allowed. Could put KSAs under Skills (or Knowledge). The instruction: Use headings like Skills, Benefits, Pay, Schedule. So we can have Skills section for KSAs (knowledge, skills, abilities). Could also have Qualifications for education/experience.
- Benefits: we have benefits paragraph.
- Pay: Salary Range and Pay Frequency.
- Schedule: Shift, Full time, Telework eligibility maybe.
We must not create sections with filler like "commensurate with experience". We have actual data.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings.
We must preserve ALL substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
Graduation from an accredited four-year college or university with major coursework in computer science, computer information systems, management information systems, or a related field. Experience may be substituted for education on a year for year basis. Five (5) or more years’ experience in programming with Java/J2EE and Web Services.
Skills
- Knowledge of the principles, practices, and techniques of computer programming and systems analysis; of computer operations procedures and systems; and of computer programming languages. ... etc.
. Pay: Salary Range: $5,425.33 - $8,886.16 Pay Frequency: Monthly Salary Group: TEXAS-B-24 maybe include. We'll put in
. Schedule: Shift: Day Additional Shift Telework: Travel Regular/Temporary: Regular Full Time/Part Time: Full time FLSA Exempt/Non-Exempt: Exempt Facility Location: Job Location City: AUSTIN Job Location Address: 701 W 51ST ST Other Locations: MOS Codes: ... (maybe drop as metadata). Telework Disclaimer: "This position may be eligible for telework. Please note, all HHS positions are subject to state and agency telework policies in addition to the discretion of the direct supervisor and business needs." Also Nearest Major Market: Austin. We could combine schedule info: Shift: Day; Full-time; Telework eligible; Pay Frequency monthly already in Pay. We'll include Shift, Full time, Telework eligibility. We must not create Schedule section if content is just generic? We have specific shift/day, full-time, telework eligibility. That's substantive. We'll output Schedule section with
containing: Shift: Day. Full-time position. This position may be eligible for telework (subject to state and agency telework policies and supervisor discretion). Also mention Regular/Temporary: Regular; FLSA Exempt. We'll keep it concise but preserve all substantive info. Now About the role: Use Brief Job Description paragraph: "Performs complex (senior-level) analysis and development with a responsible amount of direction working with current and emerging business processes, system solutions, while providing technical programming assistance, while supporting more senior level staff with customer interactions for application activities/support and often overseeing the work of other functional