Patrol Officer - Lateral Entry

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. We need to parse the posting. Content: Contact Information (address, website, phone, email) - maybe we can include as a short

under maybe "Contact Information"? But headings list does not include Contact Information; we can either fold into a short

before sections or drop? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Contact info is minor metadata; we can put in a short

before sections. Position Information: Application Deadline Until Filled, Salary Starting: $107,432, plus description about certified officer pay per CBA, represented by union. Benefits list. Position Details: description of department, population, staffing, shifts, special assignments/training. To Apply: link and instructions - we should remove application instructions (the instruction says remove application instructions). So we should drop the "To Apply" link and the "COMPLETED APPLICATIONS And REQUIRED DOCUMENTATION Should Be Returned To ..." etc. Also "Applications are valid for one year from the date of submission." That's application instruction; remove. Required Qualifications And Experience: list of qualifications. Selection Process: description of phases. Please Direct Any Questions To ... contact info again; we can fold into short

maybe. An Equal Opportunity Employer: boilerplate; remove. Ad viewed 310 times: boilerplate; remove. Thus we need sections: - About the role: maybe from Position Details description? Could be "About the role" includes description of department, population, staffing, shifts, special assignments/training. - Responsibilities: maybe not explicitly listed; but we could infer from special assignments? However we should not invent. If no explicit responsibilities, we should not create a Responsibilities section. The instruction: include a section ONLY when the posting has real, specific content for it. So we need to see if there is a responsibilities section. The posting includes "The Hodgkins Police Department offers special assignment and training including, but not limited to, ..." That's more about opportunities, not responsibilities. There's no explicit list of duties. So we may skip Responsibilities. - Requirements: maybe same as Qualifications? The posting has "Required Qualifications And Experience". That could be Qualifications section. Could also be Requirements. We need to decide which heading to use. The list includes: Must be a certified police officer..., age, citizenship, driver's license, no felony convictions, etc. That's qualifications. So we can put under

Qualifications

with

• items. - Skills: not explicitly listed; maybe special assignments/training could be considered skills? But they are more like opportunities. Could be considered Skills? The posting mentions "special assignment and training including, but not limited to: ..." That's more like available assignments/training, not required skills. Might be better to put under "About the role" as part of description. - Benefits: we have a list: Health Benefit Plans, Life Insurance, Pension Plan, Tuition Reimbursement, 457 Plans, Paid Holidays, Personal Days, Sick Time, Vacation Days, Compensatory Time, Uniforms and Equipment Provided by the Department, Pension approx 80% funded as of July 2024, Cutting edge gym offered on-site. So we can create Benefits section with
  . - Pay: we have Salary Starting: $107,432 and note about certified officer pay per CBA. So we can create Pay section with

  stating starting salary and note. - Schedule: we have "At full staffing, the department has 22 sworn police officers that work 12 hours shifts." So schedule is 12-hour shifts. Could be included under Schedule section. - About the role: we can include description of department, population, business community, staffing, special assignments/training. We also have contact info; we can put a short

  at top. We must not include application instructions, EEO, etc. We must preserve all substantive information. Let's extract. Contact info: Address: Hodgkins Police Department 6015 Lenzi Avenue Hodgkins, IL 60525; Website: www.hodgkinspd.org; Phone: 708-352-4623; Email: slynn@hodgkinspd.org. We can put as a paragraph:

  Hodgkins Police Department, 6015 Lenzi Avenue, Hodgkins, IL 60525 • www.hodgkinspd.org • Phone: 708-352-4623 • Email: slynn@hodgkinspd.org

  Now About the role: combine Position Details paragraph(s). Let's extract: "The Board of Police Commissioners of the Village of Hodgkins is accepting applications for the position of Police Officer Lateral Entry. The Village of Hodgkins Police Department serves a residential population of just over 1,400 residents and a large retail oriented business community in the southwest suburbs of Chicago. At full staffing, the department has 22 sworn police officers that work 12 hours shifts. The Village of Hodgkins strongly supports the police department, heavily investing in training and equipping officers while they work out of a state of the art facility. The Hodgkins Police Department offers special assignment and training including, but not limited to, the following: Major Case Assistance Team (MCAT) South Suburban Major Crimes Task Force (SSMCTF) 5th District SWAT Team Evidence Technician Traffic Crash Reconstruction Expert Suburban Major Accident Reconstruction Team (SMART) Bike Patrol Truck Enforcement Officer" We can put that as prose in

  maybe with line breaks? Could also list special assignments as

  but it's part of description. The instruction: Use
  • for any list of duties/requirements/benefits. This is a list of special assignments/training; could be considered a list. Might be better to put as
    under About the role? But we already have a heading for About the role; we can include a
    inside. However the instruction says use
    • for any list of duties/requirements/benefits. This list is not duties/requirements/benefits but special assignments/training. Still could be a list; but we can keep as prose to avoid over-sectioning. Probably fine as prose. Now Qualifications: list: - Must be a certified police officer with the State of Illinois through the Illinois Law Enforcement Training and Standards Board and have an active certification status in another law enforcement agency preceding the application OR - Applicants who have previously been certified as a law enforcement officer in another state must meet the conditions of reciprocity as regulated by the Illinois Law Enforcement Training and Standards Board. - Must be at least 21 years of age but must not have reached the age of 36 at time of application. - Must be a U.S. Citizen. - Must have a valid Driver's License. - Must have no felony convictions and be of good moral character, of temperate habits, of sound health, and must be physically able to perform the essential job functions of the position of police officer. We need to preserve the OR condition. Could split into two bullet points: first bullet includes the OR condition; second bullet for out-of-state reciprocity. But the original says "Applicants must meet the following: Must be a certified police officer ... OR Applicants who have previously been certified ...". So we can combine as one bullet: "Must be a certified police officer with the State of Illinois through the Illinois Law Enforcement Training and Standards Board and have an active certification status in another law enforcement agency preceding the application, OR if previously certified in another state, meet the conditions of reciprocity as regulated by the Illinois Law Enforcement Training and Standards Board." That preserves. Then other bullets. Now Benefits: list as given. - Health Benefit Plans - Life Insurance - Pension Plan - Tuition Reimbursement - 457 Plans - Paid Holidays - Personal Days - Sick Time - Vacation Days - Compensatory Time - Uniforms and Equipment Provided by the Department - Pension approximately 80% funded as of July, 2024 - Cutting edge gym offered on-site Now Pay: Starting salary $107,432; note: "A newly hired individual that is trained and certified as a law enforcement officer shall be paid as a certified officer per the collective bargaining agreement. This position is represented by the Illinois Fraternal Order of Police Labor Council, Lodge No. 151." We can put that in

      . Now Schedule: "At full staffing, the department has 22 sworn police officers that work 12 hours shifts." So schedule: 12-hour shifts. We can put

      Schedule: Officers work 12-hour shifts.

      Now we need to ensure we don't repeat info. The schedule info also appears in About the role paragraph; we might duplicate. To avoid duplication, we could mention schedule only in Schedule section and not repeat in About the role. But we need to preserve all substantive info; we can mention schedule in Schedule section and still mention in About the role? That would be duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but could be considered redundant. Better to avoid duplication by moving schedule detail to Schedule section and remove from About the role. However the About the role paragraph currently includes that sentence. We could edit it to remove the schedule sentence, but we must preserve the info; we can keep it in Schedule section and still mention in About the role but maybe rephrase to not duplicate? The instruction doesn't forbid duplication, but says "do NOT invent or summarize away detail." Duplication is not inventing or summarizing away; it's preserving. It's okay but might be considered thin. However they said "Prefer a few substantive sections over many thin ones." Duplication could make sections thin? Not sure. I'd keep schedule only in Schedule section and adjust About the role to not include that sentence. But we must ensure we didn't lose any substantive info; we moved it to Schedule section, so it's preserved. Thus About the role paragraph will be: "The Board of Police Commissioners of the Village of Hodgkins is accepting applications for the position of Police Officer Lateral Entry. The Village of Hodgkins Police Department serves a residential population of just over 1,400 residents and a large retail oriented business community in the southwest suburbs of Chicago. The Village of Hodgkins strongly supports the police department, heavily investing in training and equipping officers while they work out of a state of the art facility. The Hodgkins Police Department offers special assignment and training including, but not limited to, the following: Major Case Assistance Team (MCAT) South Suburban Major Crimes Task Force (SSMCTF) 5th District SWAT Team Evidence Technician Traffic Crash Reconstruction Expert Suburban Major Accident Reconstruction Team (SMART) Bike Patrol Truck Enforcement Officer" We could format the list of special assignments as
      for clarity. Since it's a list, we could use
      • . The instruction says use
        • for any list of duties/requirements/benefits. This is not duties/requirements/benefits but special assignments/training. Still could be a list; but we can keep as prose. Now we need to output only HTML fragment, no /, no markdown. Let's construct:

          Hodgkins Police Department, 6015 Lenzi Avenue, Hodgkins, IL 60525 •