GIS and CMMS Supervisor - Parks, Recreation, and Open Space

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraph about City of Aurora, core values, Why Work for Aurora? Then primary duties & responsibilities, then minimum qualifications & working conditions. Also includes salary range: "The hiring range for this role is $106,340 - $132,295 annually." Also "Salary to be commensurate with experience." We need to include Pay section only if posting actually states them. It does state hiring range. So we can include Pay section with that range. Also schedule? Not mentioned. Benefits? There's mention of benefits: "Well-Funded General Employees Retirement Plan", "Light rail station minutes away", "On-site fitness center and overall employee well-being programs", "Internal educational programs to assist with career advancement", "Access to innovation workspaces". Also "Competitive total compensation package". Those are benefits. So we can include Benefits section with those bullet points. We need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have: - About the role: could include introductory paragraph about City of Aurora, core values, Why Work for Aurora? Might be considered "About the role". Could also be separate "About the City". But we can use About the role. - Responsibilities: primary duties & responsibilities. - Requirements: Minimum qualifications & working conditions (education, experience, preferred qualifications, knowledge, skills, abilities, licenses, working conditions). Could split into Qualifications and Skills sections. But we can follow instruction: prefer few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one "Requirements" section? But they ask to use headings like Qualifications, Skills separately if content exists. We have both qualifications and skills listed. Could create Qualifications (education, experience, preferred qualifications, licenses) and Skills (interpersonal, analytical, etc.) and Abilities maybe part of Skills. However we need to avoid thin sections. But we have enough content for each. We also have Benefits and Pay. Schedule: not mentioned, so omit. We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions, deadline? The deadline is substantive? It's a date to submit applications. Might be considered metadata but could be kept? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Deadline is maybe minor metadata; could be included in a short p. But we can drop it? It says preserve ALL substantive information; do NOT invent or summarize away detail. Deadline is substantive? It's about application process; but they said remove application instructions. Deadline is part of application instructions. So we should drop it. Also remove "The deadline to submit applications is September 29, 2026. Please note, The City of Aurora will conduct ongoing screenings..." That's application instruction/boilerplate; drop. Also remove "The listed primary duties and responsibilities are not a comprehensive list..." maybe keep? It's a note about duties; could be considered boilerplate but it's about the job. Might keep as part of responsibilities? It's a disclaimer; could be considered boilerplate but it's about the job. I'd keep it as part of responsibilities maybe as a note. Also remove "The city of Aurora will implement furlough days..." that's a policy; maybe keep as part of Benefits? It's about furlough days (unpaid days off) - that's a negative benefit; maybe include in Benefits? Could be considered a policy; but it's substantive. Could include in Working Conditions? Might be part of Working Conditions. We'll include in Working Conditions under "Working Conditions" maybe as a note. But we have Working Conditions already in Minimum qualifications & working conditions section. Could incorporate furlough days there. We need to output only HTML fragment, no html/body tags. Let's craft sections:

About the role

It is an exciting time to work for the City of Aurora, we're growing and looking for dedicated and collaborative individuals to join our team of talented and valued employees. Excellent organizations have a set of principles, or core values, that are used to implement their mission and vision. Those values represent the touchstone for the organization, guiding the decisions of the individuals and the organization. At the City of Aurora, we demonstrate our excellence by modeling the CORE 4 Values of: Integrity, Respect, Professionalism, and Customer Service, and we welcome all who share these values to apply.

Why Work for Aurora? Make a difference in the lives of real people every day. Diverse community. Competitive total compensation package. Well-Funded General Employees Retirement Plan. Light rail station minutes away. On-site fitness center and overall employee well-being programs. Internal educational programs to assist with career advancement. Access to innovation workspaces.

But we might want to move benefits to separate Benefits section. So About the role could be just the introductory paragraph about city and core values. Then Benefits section separate. Let's decide: About the role: introductory paragraph about city growth, core values, welcome. Benefits: list of benefits: Competitive total compensation package, Well-Funded General Employees Retirement Plan, Light rail station minutes away, On-site fitness center and overall employee well-being programs, Internal educational programs to assist with career advancement, Access to innovation workspaces. Pay: hiring range $106,340 - $132,295 annually. Also note "Salary to be commensurate with experience." Could include both. Responsibilities: primary duties & responsibilities (the long list). We'll put as

• items. Requirements: maybe split into Qualifications and Skills. But we can combine into one Requirements section with subheadings? But instruction says use headings for sections; we can have multiple sections. Let's do:

  Qualifications

  Education: Bachelor's Degree in GIS, Geography, Asset Management, drafting or related field.

  Experience: Five (5) years of GIS operating experience; Two (2) years of Asset Management/CMMS experience.

  Preferred Qualifications: Two (2) years of supervisory experience; Two (2) years of project management experience; Three (3) years of municipal organization experience; GISP certification.

  Licenses And Certifications Required: Colorado driver's license with a good driving history.

  Skills

  • Strong interpersonal, analytical, project management, and leadership skills
  • Coordinate, prioritize, and assign tasks
  • Specify and enforce project deliverables and keep stakeholders apprised of the deliverable schedule
  • Perform geospatial modeling, analysis, and data manipulation
  • Analyze and compile technical information and reports

  Abilities

  • Establish and maintain effective working relationships with employees, users, consultants, individuals from other agencies, and citizens
  • Communicate effectively both verbally and in writing
  • Apply critical thinking and sound judgment to resolve problems and manage challenging situations
  But we might be creating many thin sections. However each has substantive content. Could combine Skills and Abilities into one "Skills & Abilities" section. But headings list includes Skills but not Abilities. Could put Abilities under Skills. Let's combine Skills and Abilities into one Skills section with both bullet lists. Thus:

  Skills

  • Strong interpersonal, analytical, project management, and leadership skills
  • Coordinate, prioritize, and assign tasks
  • Specify and enforce project deliverables and keep stakeholders apprised of the deliverable schedule
  • Perform geospatial modeling, analysis, and data manipulation
  • Analyze and compile technical information and reports
  • Establish and maintain effective working relationships with employees, users, consultants, individuals from other agencies, and citizens
  • Communicate effectively both verbally and in writing
  • Apply critical thinking and sound judgment to resolve problems and manage challenging situations
  Now Working Conditions: we have details about essential personnel, physical demands, work environment, equipment used, furlough days. Could be a section "Working Conditions". But headings list does not include Working Conditions; but we could use "Requirements" to include them? However we already have Qualifications and Skills. Could add a "Working Conditions" section using

  Working Conditions

  though not in the list but maybe allowed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could still use other headings but better to stick to those. Working Conditions could be part of Requirements or Qualifications? Might be better to include under "Requirements" as a paragraph. But we already have Qualifications and Skills separate; we could add a "Working Conditions" subsection inside Requirements? But we need to follow instruction: use those headings for sections; we can add other headings if needed but better to stick to given list. However we have a lot of content about working conditions; we could incorporate into "Requirements" section as a paragraph after qualifications and skills. But we already split Qualifications and Skills; maybe we combine them into one "Requirements" section that includes education, experience, preferred qualifications, licenses, skills, abilities, working conditions. That would be fewer sections. Let's think: The instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 4-5 sections: About the role, Responsibilities, Requirements (including qualifications, skills, abilities, working conditions), Benefits, Pay. Thus we will have:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  Education: Bachelor's Degree in GIS, Geography, Asset Management, drafting or related field.

  Experience: Five (5) years of GIS operating experience; Two (2) years of Asset Management/CMMS experience.

  Preferred Qualifications: Two (2) years of supervisory experience; Two (2) years of project management experience; Three (3) years of municipal organization experience; GISP certification.

  Licenses And Certifications Required: Colorado driver's license with a good driving history.

  Skills: Strong interpersonal, analytical, project management, and leadership skills; coordinate, prioritize, and assign tasks; specify and enforce project deliverables and keep stakeholders apprised of the deliverable schedule; perform geospatial modeling, analysis, and data manipulation; analyze and compile technical information and reports; establish and maintain effective working relationships with employees, users, consultants, individuals from other agencies, and citizens; communicate effectively both verbally and in writing; apply critical thinking and sound judgment to resolve problems and manage challenging situations.

  Working Conditions: Essential personnel may be required to work during emergencies; sedentary physical work with ability to lift up to 10 pounds; occasional lifting, carrying, walking, standing; sufficient vision for screens; dexterity to operate computer equipment; speech and hearing for communication; endurance to sit and work at computer long periods; work in clean, comfortable environment with occasional field visits to PROS facilities and linear assets; uses standard office equipment, personal computer, common office software, advanced software, on-premise and cloud databases; may require personal equipment (vehicle, cell phone, tools); city implements furlough days (unpaid) in 2026 on Jan 16, Apr 10, Jul 2, Dec 24.

  Benefits

  • Competitive total compensation package
  • Well-Funded General Employees Retirement Plan