Public Safety Dispatcher I

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Education and Experience, Skills and Knowledge, Physical Requirements maybe). Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Tools/Equipment Not Applicable". Also remove "Application Instructions". Also remove EEO statement etc. Also remove "About Syracuse University", "About The Syracuse Area", etc? Those are not part of job description but maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It didn't explicitly say to remove "About Syracuse University" etc. However those are not part of job description; they might be considered boilerplate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Syracuse University" and "About The Syracuse Area" are substantive info about employer, maybe we should keep? The instruction didn't say to remove them. However typical job posting cleaning might keep them as part of description? The user said: "Reformat a job posting into clean, well-structured semantic HTML." Likely they want to keep the description sections: About the role (maybe from first paragraph), Responsibilities, Requirements (Education and Experience, Skills and Knowledge, Physical Requirements). Benefits, Pay, Schedule only if present. There's no explicit pay/benefits/schedule. There's schedule info: "Must be willing to work nights, weekends, and holidays and be flexible with schedule. Must be willing to work unplanned overtime, special events, planned overtime, and overtime related to emergency call back." That's schedule info. So we could include a Schedule section. Benefits? Not mentioned. Pay? Not mentioned. So we include Schedule. We need to decide headings: About the role (maybe from first paragraph: "A Public Safety Dispatcher I is a position that is responsible for all law enforcement emergency and non-emergency safety and security communications for the University community.") Could be considered About the role. Responsibilities: list of duties. Requirements: could combine Education and Experience, Skills and Knowledge, Physical Requirements. Could separate into subheadings? But we only have h3 for section headings; we could have multiple sections: Education and Experience, Skills and Knowledge, Physical Requirements. Or combine into Requirements with lists. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Education and Experience + Skills and Knowledge + Physical Requirements into a single "Requirements" section with sub-lists? But we need to use

  • for any list. Could have nested lists? Probably okay. We need to preserve all substantive information. So we must include all details from Education and Experience, Skills and Knowledge, Physical Requirements, Responsibilities, and schedule info. We must not include duplicated lines. Check for duplicates: The responsibilities list includes many items; ensure we don't repeat. We must not include boilerplate: EEO statement, About Syracuse University, About The Syracuse Area, Commitment to Supporting and Hiring Veterans, Commitment to a Respectful and Welcoming Community. Those are likely considered boilerplate/EEO etc. The instruction says remove EEO/equal-opportunity boilerplate. The "About Syracuse University" and "About The Syracuse Area" are not EEO but maybe still considered boilerplate? Not explicitly. However they are not part of the job description core; they are generic about the university. Might be considered filler but not prohibited. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we remove those, we are summarizing away detail (the description of the university). That might be considered removing substantive info. However the user likely wants just the job description content, not the university overview. The instruction about removing boilerplate includes EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not mention removing "About the company" sections. So we should keep them? But they are not part of the job description; they'd be extra sections. The user might want them included as they are substantive about the employer. However typical job posting cleaning might keep them. I'd keep them as separate sections maybe "About Syracuse University" and "About the Syracuse Area". But the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not limited to those. So we could add headings for those as well. But we need to avoid creating sections with filler like "commensurate with experience". Not relevant. Thus final HTML could have sections:

    About the role

    A Public Safety Dispatcher I is a position that is responsible for all law enforcement emergency and non-emergency safety and security communications for the University community.

    Responsibilities

    • Communicate via radio and telephone with patrol units, with various University service and auxiliary departments and with the Onondaga County 911 Center.
    • Practices proper radio dispatching techniques using appropriate terminology in a calm and professional manner.
    • Monitor, acknowledge and dispatch various alarms and access control systems events, and is responsible for monitoring a vast campus wide closed circuit television (CCTV) video security system.
    • Provide professional and composed verbal communications with outside police agencies and the general public; maintaining sound customer service practices and meeting the needs of community members under sometimes stressful conditions is essential.
    • Operate an extensive array of law enforcement and emergency related communications equipment as well as the latest computer software related technologies, including alert systems, intrusion and duress alarms.
    • Manage all records pertaining to daily tour of duty.
    • Prioritize all radio and telephone communications.
    • Answer multiple telephone lines, receiving emergency and non-emergency calls for law enforcement, safety and security services, and dispatch patrol and other units to respond.
    • Make urgent and critically important decisions regarding emergency situations based on knowledge, skills and policies and procedures.
    • Monitor video security system CCTV as assigned and report and/or dispatch any anomalies.
    • Service all walk-in customers
    • Perform administrative duties such as data entry and retrieval, information filing, record-keeping, supply and equipment inventory and repair requests.
    • Runs NYSPIN/NCIC inquiries as requested.
    • Monitor key control.
    • Comply with all Federal, State and Local regulations relative to communications and protected data and information.
    • Report technical problems clearly and expeditiously to appropriate department/division.
    • May perform or safety, security or community service related duties as assigned.
    • Other duties as assigned.

    Requirements

    We could split into subheadings but maybe keep as one with lists. Education and Experience:
    • An Associate’s degree or equivalent combination of education and experience is preferred.
    • Must be able to obtain a New York State Division of Licensing security guard license.
    • Successfully pass a 480-hour field training program.
    • Must be proficient in data entry/keyboarding using various Microsoft Office and law enforcement applications.
    • Must successfully pass a background investigation, including but not limited to an initial drug screening, psychological exam, and fingerprinting.
    Skills and Knowledge:
    • Good knowledge of the geography, patrol territories, roads, streets, buildings owned/operated by the university and special hazards within the University Campus.
    • Must have strong communications skills and ability to communicate with a diverse community.
    • Must be able to operate and perform under varying degrees of stress and pressure and be able to prioritize emergencies.
    • Multi-task in a high-volume, community and student service centered environment.
    • Must have the ability to be creative and innovative in problem-solving.
    • Candidates may be required to sit for extended periods of time.
    • Must be willing to work nights, weekends, and holidays and be flexible with schedule.
    • Must be willing to work unplanned overtime, special events, planned overtime, and overtime related to emergency call back.
    Physical Requirements:
    • Candidates must have the ability to effectively engage in communications that are often various and multiple, e.g.: hearing alarms, speaking clearly and hearing feedback on multi-channel radio system, speaking clearly and understanding various dialects on the telephone, viewing live-streaming video with adept concentration skills, navigating various software technologies including those associated with law-enforcement applications and Internet-based websites, and excellent data entry skills.
    Schedule: Actually schedule info is already in Skills and Knowledge (willing to work nights etc). Could separate but it's already there. Might be redundant to create separate Schedule section. Since we already have schedule info in Skills and Knowledge, we could keep it there. The instruction says prefer few substantive sections over many thin ones. So maybe combine schedule into Skills and Knowledge. We also have About Syracuse University and About The Syracuse Area. Should we include? Let's decide to include them as sections: About Syracuse University and About the Syracuse Area. They are substantive info about employer. Not prohibited. Thus final HTML:

    About the role

    ...

    Responsibilities

    ...

    Requirements

    Education and Experience

    ... but we cannot use h4? The instruction only mentions h3 for section headings. It didn't forbid other headings, but to be safe we could use

    for each subsection, but that would be many sections. Could use

    with bold? But we need to preserve structure. Maybe we can keep as

    for each major section: Education and Experience, Skills and Knowledge, Physical Requirements. That would be many sections but each is substantive. The instruction says prefer a few substantive sections over many thin ones. Having three sub-sections under Requirements might be okay. But we could also combine into one Requirements section with

    and separate paragraphs for each category. However we need to preserve all detail; we can do paragraphs with bold headings inside

    . But the instruction says use

    • for any list of duties/requirements/benefits. So we can have multiple
      under a single

      Requirements, each preceded by a

      describing the category. That seems acceptable. Thus:

      Requirements

      Education and Experience:

      ...

      Skills and Knowledge:

      ...

      Physical Requirements:

      ...
      That uses

      for prose (including bold headings). Good. Now About Syracuse University and About The Syracuse Area: we can add sections:

      About Syracuse University

      ...

      About the Syracuse Area

      ...

      We must ensure we didn't include any boilerplate like EEO etc. We removed those. Check for duplicated lines: Ensure we didn't repeat any sentence. Now produce HTML fragment only. Let's craft the content precisely. About the role: "A Public Safety Dispatcher I is a position that is responsible for all law enforcement emergency and non-emergency safety and security communications for the University community." Responsibilities list: copy each bullet exactly as in text, ensure no duplication. Let's list them: - Communicate via radio and telephone with patrol units, with various University service and auxiliary departments and with the Onondaga County 911 Center. - Practices proper radio dispatching techniques using appropriate terminology in a calm and professional manner. - Monitor, acknowledge and dispatch various alarms and access control systems events, and is responsible for