Jobs · OTHR · Oregon

Police Officer - Out-of-State Lateral

City of Salem · Salem, OR · 1 mo ago
OTHR$39.11/hrFull-time
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 if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. We need to parse the posting for content. Key sections: - Job Summary: description about role, eligibility, etc. Could be "About the role" or "Job Summary". We'll use

About the role

with paragraph(s) summarizing. - Salary details: they have Salary Step table with hourly and monthly rates, plus incentives percentages. That is Pay info. So we should include a Pay section with that table? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. For tables, not specified; but we can still use

    or maybe

      for list? The salary step is a table; we could represent as

      with the data? But we need to preserve all substantive info. Could format as

      with the table as plain text? Probably acceptable to keep as

      containing the table content. However they said use

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

        for prose. Not forbidding tables; but we can keep as

        with the table content. - Benefits: they list many benefits: medical, dental, vision, paid vacation, sick time, competitive pay, employer-paid PERS contribution 6%, voluntary pre-tax contributions to 457b, health care and dependent care flexible spending accounts, voluntary long-term care, employee wellness program, employee assistance program, employee health clinic, free secure parking, department gym. Also they mention up to 80 hours vacation, 40 hours sick leave from date of hire. Also "The City offers an excellent compensation and benefits package." So we should include Benefits section with list. - Responsibilities: "What You Will Do" section: patrolling assigned areas, enforce laws, answer and investigate citizen complaints, reports, examine crime/accident scenes, preserve evidence, meeting with public, community meetings, presenting public with info to keep household/property/safe. So we can put Responsibilities. - Requirements/Qualifications: "What are the minimum qualifications?" includes list: High school graduate or GED, must possess Basic Police Certification by Oregon DPSST or out-of-state equivalent, currently or within past 12 months employed as Police Officer with minimum three years full-time employment (jail and most federal law enforcement experience not counted), currently employed and certified applicants do not need to take NTN Frontline National Test or ORPAT, possess and maintain valid Oregon class C driver's license or other state equivalent and driving record meeting City standards, must be able to work periodic overtime and variety of 24-hour rotating shifts including holidays and weekends, be at least 21 years old at date of hire, be US Citizen or ability to become within 18 months, participate in competitive testing including physical fitness, reading comprehension, writing skills, written, physical/vision, hearing and psychological examinations, pass strict background investigation, pass pre-employment drug test (including marijuana), pass pre-employment background check. Also "Submit resume with application." That's application instruction; we should drop application instructions per rule. Also "Additional Information: Submit resume with application." drop. - Also there is "About Us" section describing department, facility, city stats, etc. That could be "About the role" or maybe "About the department". Could be part of About the role. - Also "Make An Impact" section describing special teams, units, technology, fleet, equipment issued. That could be part of About the role or Responsibilities? It's more about the department and what you get. Could be part of About the role. - Also "Where can I find out more about the position?" etc. That's application instructions / links; drop. - Also "How can I apply?" etc. drop. - Also EEO etc drop. - Also Contact Information maybe keep? It's not boilerplate? It's contact info for the job. Might be considered metadata but not job ID. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. Contact info could be considered minor metadata; we could fold into a short

        at end. But we need to preserve all substantive information; contact info is substantive for applicants. Could include as a

        after sections. - Also "Selection Process" etc. That's part of process; could be considered part of Requirements? Might be considered procedural; but we could include as a short paragraph under maybe "Selection Process" but not a required heading. Since we only output headings for sections with real specific content; we could include a section "Selection Process" if we want, but not required. The instruction: Prefer a few substantive sections over many thin ones. So we might combine selection process into Requirements or About the role. We need to avoid duplication: there are repeated lines like "The City offers an excellent compensation and benefits package." appears twice; we should keep only once. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus final HTML: sections: About the role (maybe combine Job Summary, Make An Impact, About Us), Responsibilities, Requirements (or Qualifications), Benefits, Pay. Possibly also Schedule? The posting mentions "must be able to work periodic overtime and a variety of 24-hour rotating shifts including holidays and weekends." That's schedule info. So we could include Schedule section with that detail. But we could also fold into Requirements. Since schedule is specific, we could make a Schedule section. But instruction: Prefer a few substantive sections over many thin ones. So maybe combine schedule into Requirements. We'll decide sections: About the role, Responsibilities, Requirements, Benefits, Pay. Now craft content. About the role: combine Job Summary, Make An Impact, About Us. Job Summary: "The City of Salem's Police Department is hiring for a Police Officer - Out-of-State Lateral. If you are currently or have been a Police Officer Outside of the State of Oregon in the past 12 months; and were employed for more than 3 years, we encourage you to apply." Make An Impact: description of special teams, units, technology, fleet, equipment issued. About Us: description of department size, facility, city stats, etc. We need to preserve all substantive info; we can paraphrase but must not invent or summarize away detail. We can keep as prose but must keep details. We'll write a paragraph that includes all those details. Responsibilities: from "What You Will Do": patrolling assigned areas to enforce laws and ordinances; answer and investigate citizen complaints, reports; examine crime/accident scenes and/or preserve evidence as needed; meeting with the public, community meetings and/or presenting the public with information to keep their household, property, or themselves safe. Requirements: list all minimum qualifications plus maybe selection process? We'll include: High school graduate or GED; must already possess a minimum of a Basic Police Certification by the Oregon Department of Public Safety Standards and Training (DPSST) or out-of-state equivalent; currently, or has been within the past 12 months, employed as a Police Officer with a minimum of three years of full-time employment as a police officer (jail and most federal law enforcement experience will not be counted toward the three-year minimum); currently employed and certified applicants do not need to take the NTN Frontline National Test or the ORPAT; possess and maintain a valid Oregon class C driver's license or other state equivalent and have a driving record that meets the City of Salem's standards; must be able to work periodic overtime and a variety of 24-hour rotating shifts including holidays and weekends; be at least 21 years old at date of hire; be a U.S. Citizen or have the ability to become one within 18 months of hire; participate in competitive testing including physical fitness testing, reading comprehension, writing skills, written, physical/vision, hearing and psychological examinations, and be able to pass strict Police Department background investigation; must pass the pre-employment drug test (including marijuana); must pass the pre-employment background check. Also "Submit resume with application." is application instruction; we drop. Also maybe include "Entry Level (0-2 Years' Experience)" etc? That seems like a pay scale table for entry vs lateral? Actually there is a table showing steps based on years experience. That is part of Pay. We'll include in Pay. Benefits: list: Medical, dental, and vision coverage for you and your family; Paid vacation and sick time in accordance with City policies (including up to 80 hours vacation and 40 hours sick leave from date of hire); Competitive pay; Employer-paid PERS contribution of 6%; Opportunity for voluntary pre-tax contributions to a 457b account; Health care and dependent care flexible spending accounts; Voluntary long-term care; Employee wellness program; Employee assistance program; Employee health clinic; Free, secure parking; Department gym available for employee use. Also mention "The City offers an excellent compensation and benefits package." (we can include once). Pay: include Salary Step table with hourly and monthly rates, plus incentives: Certifications, Training, & College Incentives 2% - 10%; Extra Duty/Specialized Assignment Incentive 2.5% - 5%; Bi-Lingual Incentive 5%; Full List of Incentives Collective Bargaining Agreement. Also mention "Starting salary step will be based on years of qualified experience using and utilizing the equity pay act." Also maybe mention Longevity Rate? Actually table includes Longevity Rate? The table shows Step 1-6 with Hourly Rate and Monthly Rate. Also there is a Longevity Rate column? Actually the table headings: Salary Step Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Longevity Rate Hourly Rate $... Monthly Rate $... It seems Longevity Rate is a column but values not shown? Actually they listed Longevity Rate as a column header but no values under? Might be missing. We'll just include the hourly and monthly rates as given. We must not create sections with filler like "commensurate with experience". We have actual numbers. Now produce HTML. We'll wrap each section in

        heading then content. For lists: Use
        • for duties/requirements/benefits. For Pay: we could present as

          containing the table as plain text. Or we could use

            for each step? But it's a table; we can use

            with line breaks. We'll produce:

            About the role

            ...

            Responsibilities

            • ...
            • ...

            Requirements

            • ...
            • ...

            Benefits

            • ...
            • ...

            Pay

            ... table ...

            Optionally include contact info as

            at end. Now craft the About the role paragraph. We need to include: Job Summary, Make An Impact (special teams, units, technology, fleet, equipment), About Us (department size, facility, city stats, location, population, etc). Let's write: "The City of Salem's Police Department is hiring for a Police Officer - Out-of-State Lateral. Candidates must be currently or have been a police officer outside Oregon within the past 12 months and have more than three years of experience. The department offers a full complement of special teams and units including SWAT, Bomb Squad, Mobile Response Team, Crisis

Similar jobs