Animal Control Officer

We need to output HTML fragment with sections: Pay, Schedule, Benefits, About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have: - Pay Range: $25.00/hr. So Pay section with that. - Workdays & Hours: Rotating work schedule, including overnights and holidays; Some evening/weekend work required. So Schedule section. - Benefits: list: 11 Paid Holidays, Medical, Dental, Vision, Paid Time Off, Pension Plan, Professional Development Opportunities. So Benefits section. - About the role: The City of Fort Worth description and Animal Control Officer Position description. Could be About the role. - Responsibilities: The Animal Control Officer Job Responsibilities Include ... list. - Requirements: Minimum Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: maybe not separate; but we could include Skills if there is specific content like Microsoft Word, Excel, data entry, bilingual, two-way radio. Could be Skills section. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, etc. Also remove "Apply Now!" etc. Remove conditions of employment? That's boilerplate EEO etc; we should drop that. Also drop "Candidates who do not meet..." etc. Keep substantive info. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all details from the posting that are substantive. Let's extract: Pay: $25.00/hr. Schedule: Rotating work schedule, including overnights and holidays; Some evening/weekend work required. Benefits: 11 Paid Holidays, Medical, Dental, Vision, Paid Time Off, Pension Plan, Professional Development Opportunities. About the role: The City of Fort Worth is one of the fastest growing large cities in the U.S. Our employees serve the needs of over 1,000,000 residents, promoting our values of exceptional customer experience, mutual respect, embracing our diversity, continuous improvement, ethical behavior, and accountability. An Animal Control Officer Position is available with The City of Fort Worth Code Compliance Department – Animal Care and Control Division. If you enjoy working with animals and have a desire to learn how to achieve your true potential, our team is seeking positive, customer-oriented individuals to train in an exciting career as Animal Control Officer. Responsibilities: list bullet points: - Responding to complaints and patrolling in assigned geographic areas for stray, sick, injured, aggressive, unwanted or abandoned animals in addition to impoundment of stray and wild animals - Perform public education and enforcement of State, County and City laws concerning care, treatment and control of owned animals - Conduct preliminary investigations on reports of Bites, Cruelty and Dangerous or Aggressive animals - Assist Code Compliance, Police Department, Fire Department and Med Star on animal calls - Issue notices and citations for violations of city ordinances and testify in court on animal cases Minimum Qualifications (Requirements): - High School Diploma or - One (1) year of increasingly responsible experience in animal care control and/or animal welfare - Valid Texas Driver License - Possession of, or ability to obtain, an Animal Control Officer Basic Certification through the Texas Department of State Health Services - Candidate selected for hire must pass Pre-Employment Drug Screen, Physical and Criminal Background check Preferred Qualifications (Qualifications): - Possession of or ability to obtain Euthanasia Certificate - Microsoft Word, Excel and data entry experience - Extensive public contact work experience - Bilingual skills (English/Spanish) - The two-way radio experience is a plus Skills: Could combine Microsoft Word, Excel, data entry, bilingual, two-way radio as skills. But we already have them in Preferred Qualifications. Might still create Skills section with those specifics. However we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put them in both Qualifications and Skills, that's duplication but still preserving. Might be okay but could be considered redundant. Better to put them under Skills if we want a separate section, but then we would need to move them from Qualifications? The posting lumps them under Preferred Qualifications. We could treat Preferred Qualifications as Qualifications section, and Skills maybe not needed. But we can still include Skills if we want, but we need to ensure we don't lose any info. If we put them only under Skills and not under Qualifications, we would be omitting the "Preferred Qualifications" label but still preserving the content. That's okay as long as we keep the content. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Preferred Qualifications and Skills into one section called Qualifications (or Skills). But we have both Requirements (minimum) and Qualifications (preferred). That's fine. Thus sections: - About the role (p) - Responsibilities (ul) - Requirements (ul) for minimum qualifications - Qualifications (ul) for preferred qualifications - Benefits (ul) - Pay (p) - Schedule (p) We should not include empty sections. Now format: Use

for section headings. Use

• for any list. Use

  for prose. We need to output only HTML fragment. Let's craft:

  About the role

  The City of Fort Worth is one of the fastest growing large cities in the U.S. Our employees serve the needs of over 1,000,000 residents, promoting our values of exceptional customer experience, mutual respect, embracing our diversity, continuous improvement, ethical behavior, and accountability. An Animal Control Officer Position is available with The City of Fort Worth Code Compliance Department – Animal Care and Control Division. If you enjoy working with animals and have a desire to learn how to achieve your true potential, our team is seeking positive, customer-oriented individuals to train in an exciting career as Animal Control Officer.

  Responsibilities

  • Responding to complaints and patrolling in assigned geographic areas for stray, sick, injured, aggressive, unwanted or abandoned animals in addition to impoundment of stray and wild animals
  • Perform public education and enforcement of State, County and City laws concerning care, treatment and control of owned animals
  • Conduct preliminary investigations on reports of Bites, Cruelty and Dangerous or Aggressive animals
  • Assist Code Compliance, Police Department, Fire Department and Med Star on animal calls
  • Issue notices and citations for violations of city ordinances and testify in court on animal cases

  Requirements

  • High School Diploma or
  • One (1) year of increasingly responsible experience in animal care control and/or animal welfare
  • Valid Texas Driver License
  • Possession of, or ability to obtain, an Animal Control Officer Basic Certification through the Texas Department of State Health Services
  • Candidate selected for hire must pass Pre-Employment Drug Screen, Physical and Criminal Background check

  Qualifications

  • Possession of or ability to obtain Euthanasia Certificate
  • Microsoft Word, Excel and data entry experience
  • Extensive public contact work experience
  • Bilingual skills (English/Spanish)
  • The two-way radio experience is a plus

  Benefits

  • 11 Paid Holidays
  • Medical
  • Dental
  • Vision
  • Paid Time Off
  • Pension Plan
  • Professional Development Opportunities

  Pay

  $25.00/hr.

  Schedule

  Rotating work schedule, including overnights and holidays; Some evening/weekend work required.

  Check: Did we preserve all substantive info? We omitted the line "Job Posting Closing on: Saturday, September 19, 2026 📅". That's a date; maybe considered metadata but not required? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. The closing date is minor metadata; we could drop it or include in a short p. The instruction says we can fold minor metadata into a short

  or drop it. Since we already have Pay and Schedule sections, we could add a short p for the closing date under maybe About the role? But better to drop it as it's not essential. The instruction says preserve ALL substantive information; is the closing date substantive? It's about application deadline; maybe considered substantive but also could be considered metadata. The instruction says fold minor metadata into a short

  or drop it. So we can drop it. It's okay. We also omitted the emojis etc. That's fine. Check for any other substantive info: "The City of Fort Worth is proud to be an Equal Employment Opportunity employer." That's EEO boilerplate; we should remove. Also "Conditions of Employment" etc. Remove. We kept the physical demands? Actually we omitted "Working Conditions and Physical Demand" section. That is substantive info about physical demands. Should we include? The instruction: include a section ONLY when the posting has real, specific content for it. The posting includes a paragraph about Working Conditions and Physical Demand. That's specific content. We should include it, perhaps as a section like "Working Conditions" but we don't have a predefined heading for that; allowed headings are only the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create other headings. So we must fit that content into one of those sections. Where does it belong? Could be under Responsibilities? Not really. Could be under Requirements? Not exactly. Could be under About the role? Possibly as part of role description. The instruction says we can only use those headings; we cannot create a new heading like Working Conditions. So we need to embed that content somewhere else, perhaps in a

  under About the role or Responsibilities. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but maybe we can use others? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; not that we are limited to them, but likely we should stick to those. The instruction also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section for Working Conditions if we treat it as a heading like "Working Conditions". But the examples didn't list it; but they said e.g., not exhaustive. However later they say "Prefer a few substantive sections over many thin ones." It may be okay to add a Working Conditions section. But to be safe, we could incorporate that content into the Responsibilities or About the role as a paragraph. However that might dilute the specificity. But we must preserve all substantive info; we can add a

  under About the role after the existing description, describing working conditions. That would preserve it. Let's add a paragraph after the About the role description: "Depending on assignment, positions in this class typically require touching, talking, hearing, seeing, grasping, standing, stooping, kneeling, crouching, reaching, walking, repetitive motions, climbing, balancing, pushing, pulling, and lifting, depending on assignment. Incumbents may be exposed to moving mechanical parts, odors,