TDCJ - Maintenance Supervisor I, II, III - Laundry

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Need to parse the job posting. Let's extract content: Job Description: "Performs highly complex supervisory maintenance and construction work..." etc. We have "Job Duties:" then description. Then "You'd be a GOOD fit if:" bullet list (though not bullet but lines). Then "You'd be a GREAT fit if:" bullet list. Then "Additional Information:" includes Travel 100%, Position may spend 16+ nights away per month, Work Site Visits, No Study Material, No Pre-Service Training Academy Required Yes Hazardous Duty/Longevity Position Hazardous, This position has access to critical infrastructure..., This is a career ladder position. Title Months of Experience Monthly Salary table. Then "Apply once annually for multiple related positions through this posting. Indicate your desired roles and locations using the Statement of Availability in the application. Qualified applications are valid for one year (from the date of submission) and require yearly renewal if over a year old. We will contact qualified candidates for interviews as positions become available. Applicants not meeting the requirements will be notified by email." Then "*Outside applicants will be required to submit to pre-employment drug testing as a condition of employment." Then Contact Information: two contacts. Then "Important Note to the Candidate: Military Preference..." etc. Then "Applications submitted through Work in Texas..." etc. Then "Eligibility..." etc. Then "EEO Statement:" etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statement, application instructions like "Apply once annually..." maybe considered application instructions? The instruction says remove application instructions. So we should remove that paragraph about applying once annually, etc. Also remove contact info? Contact info maybe not boilerplate but could be considered metadata; but not explicitly said to remove. It says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Contact info maybe minor metadata; we could fold into a short

or drop. Probably better to include as a

with contact details. Military Preference note maybe not boilerplate; it's specific info. Keep. Eligibility: maybe keep? It's generic but maybe considered boilerplate? It's about eligibility to work in US; could be considered standard but maybe keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Eligibility is legal but not EEO. Might be considered boilerplate but not explicitly listed. Safer to keep? Might be considered generic; but we need preserve ALL substantive information. Eligibility is substantive? It's a requirement. Could keep as a

. EEO Statement definitely remove. Now we need sections: About the role (maybe a summary), Responsibilities (job duties), Requirements/Qualifications/Skills (we have GOOD fit and GREAT fit). Could combine into Requirements and Skills. Benefits: we have travel, hazardous duty, career ladder, salary table. Pay: we have salary table. Schedule: maybe travel 100% and nights away per month indicates schedule? Could be schedule. But we should not create sections unless posting has real specific content. We have salary table (specific). So we can have Pay section with table. Benefits: we have travel, hazardous duty, career ladder, maybe also "No Pre-Service Training Academy Required Yes"? That's confusing. Actually "No Pre-Service Training Academy Required Yes" maybe means Pre-Service Training Academy Required? Not clear. Might be a benefit? Probably not. We have "Travel 100%" and "Position may spend 16+ nights away per month". That's more about travel requirement, could be under Schedule or Benefits. We'll make a Schedule section for travel/nights. We have "Hazardous Duty/Longevity Position Hazardous" maybe a benefit? Could be under Benefits. We have "This is a career ladder position." with salary table. Thus we can have sections: About the role (maybe a brief summary from first paragraph), Responsibilities (job duties), Requirements (good fit), Qualifications (great fit?) Actually great fit could be Qualifications. Skills maybe from good fit? But we can combine. We need to avoid thin sections. Let's decide: - About the role: short paragraph summarizing role: Performs highly complex supervisory maintenance and construction work, overseeing maintenance and construction inmate staff involved in installation, care, and repair of state facilities and equipment, etc. - Responsibilities: maybe same as About? Actually job duties already listed. Could put Responsibilities as the list of duties (plumbing, HVAC, etc). We'll extract the duties list. - Requirements: Good fit bullet list. - Qualifications: Great fit bullet list. - Skills: maybe combine? But we already have good fit includes multi-task, organized, communicate ideas. That's skills. Could put Skills section. - Pay: salary table. - Benefits: Travel 100%, 16+ nights away per month, Hazardous Duty/Longevity, Career ladder, maybe also "No Pre-Service Training Academy Required Yes"? Not clear. We'll omit unclear. - Schedule: maybe not needed if travel covered in Benefits. Could omit Schedule. We must not create Pay/Schedule/Benefits unless posting actually states them. We have Pay (salary table). Benefits: we have travel, hazardous duty, career ladder. So we can include Benefits. Schedule: we have travel 100% and nights away; that's more about travel requirement, could be considered Schedule but we already have Benefits covering travel. Might be redundant. Safer to omit Schedule. Now we need to format lists with

• . For prose use

  . We need to include headings

  for each section. We must not repeat job title as heading. Job title is Maintenance Supervisor I/II/III/IV? Not needed. We need to include minor metadata like Contact Information maybe as a

  after sections. We must output only HTML fragment. Let's craft. First, About the role paragraph: combine first sentences: "Performs highly complex supervisory maintenance and construction work. Work involves overseeing maintenance and construction inmate staff involved in the installation, care, and repair of state facilities and equipment. Equipment repairs include but are not limited to plumbing, boilers, heating, ventilation, and air conditioning (HVAC), locking mechanisms, electrical, water plant operations, wastewater plant operations, carpentry, Laundry and Food Service equipment repair, and general maintenance and construction. Works under minimal supervision with extensive latitude for the use of initiative and independent judgement." That's basically the job duties but we can put as About. Responsibilities: maybe we can list the same duties as bullet list? But we already used that in About. To avoid duplication, maybe Responsibilities can be a brief statement: "Oversee maintenance and construction inmate staff; ensure installation, care, and repair of state facilities and equipment; manage repairs across plumbing, HVAC, electrical, water/wastewater plants, carpentry, laundry and food service equipment; exercise independent judgment with minimal supervision." But we need to preserve ALL substantive information; we cannot summarize away detail. So we need to keep the detailed list. So we should put the detailed list under Responsibilities as

  • items. Thus About the role could be a short summary: "Performs highly complex supervisory maintenance and construction work under minimal supervision, overseeing inmate staff responsible for installation, care, and repair of state facilities and equipment." That's a summary but we might be losing detail. However the instruction says preserve ALL substantive information; we cannot invent or summarize away detail. Summarizing might be considered summarizing away detail? It says "do NOT invent or summarize away detail." So we must not summarize away detail; we must keep all detail. So we cannot create a summary that omits details. Therefore we need to keep the detailed duties somewhere. If we put them under Responsibilities as a list, that's fine. Then About the role could be a brief intro that doesn't omit details? But any intro will omit some details; but maybe it's okay as long as we also have the detailed list elsewhere. The instruction likely means don't create sections with placeholder text; summarizing is allowed as long as you also have the detail elsewhere. We'll keep a brief About the role that captures essence but not omit required details? It's ambiguous. Safer to not have About the role if we risk summarizing away detail. But we need sections; we can have Responsibilities with detailed list, Requirements, Qualifications, Skills, Pay, Benefits. That may be enough. We need to include a section ONLY when posting has real specific content for it. So we can have: - Responsibilities (

    Responsibilities

    ) with
    • each duty. - Requirements (

      Requirements

      ) for GOOD fit. - Qualifications (

      Qualifications

      ) for GREAT fit. - Skills (

      Skills

      ) maybe from GOOD fit? But GOOD fit includes multi-task, organized, communicate ideas. That's skills. Could put under Skills. - Pay (

      Pay

      ) with table. - Benefits (

      Benefits

      ) with travel, hazardous duty, career ladder. We need to ensure we don't create sections with filler like "commensurate with experience". We have concrete info. Now extract details: Responsibilities list items: - Performs highly complex supervisory maintenance and construction work. - Work involves overseeing maintenance and construction inmate staff involved in the installation, care, and repair of state facilities and equipment. - Equipment repairs include but are not limited to: - plumbing - boilers - heating, ventilation, and air conditioning (HVAC) - locking mechanisms - electrical - water plant operations - wastewater plant operations - carpentry - Laundry and Food Service equipment repair - general maintenance and construction - Works under minimal supervision with extensive latitude for the use of initiative and independent judgement. We could break into separate
    • items. Requirements (GOOD fit): - You have full-time wage-earning experience in a maintenance field. - You can multi-task. - You are organized. - You have the skills to communicate ideas and instructions clearly. Qualifications (GREAT fit): - You completed an applicable program from a trade or technical school. - You can read and interpret blueprints, drawings, plans, and specifications. - You have plumbing or pipefitting experience. - You have knowledge of basic components of boilers and water and wastewater treatment facilities. Skills: maybe we can combine the communication, multi-task, organized as skills. But we already have them in Requirements. Could omit Skills section to avoid thin. But we have those as requirements; maybe we can treat them as Skills. However we need to avoid duplication. Could merge Requirements and Skills? But we need headings only when real specific content. We could have Requirements (including experience) and Skills (multi-task, organized, communication). That's fine. Pay: table: Title | Months of Experience | Monthly Salary Maintenance Supervisor I | 0-12 | $3,871.51 Maintenance Supervisor II | 13-24 | $4,103.81 Maintenance Supervisor III | 25+ | $4,352.39 Maintenance Supervisor IV | 48+ and HVAC License | $4,903.13 We need to output as HTML table. Benefits: - Travel 100% - Position may spend 16+ nights away per month - Hazardous Duty/Longevity Position (Hazardous) - This is a career ladder position (with progression as shown in Pay table) - This position has access to critical infrastructure in accordance with the Governor's executive order GA-48. We