Police Crime Analyst - Variable Hour
or drop it. Location is minor metadata; we can put in a p. Also we have introductory paragraph about City of Aurora, core values, Why Work for Aurora? That's substantive; we can include as a p or maybe under a heading like "About the role"? Actually "Why Work for Aurora?" could be a section heading "Benefits"? But we have separate Benefits section maybe. The "Why Work for Aurora?" includes bullet points: Make a difference..., Diverse community..., Competitive total compensation package..., Well-Funded General Employees Retirement Plan..., Light rail station minutes away..., On-site fitness center..., Internal educational programs..., Access to innovation workspaces. Those are benefits. So we can create a Benefits section with those items as ul li. Also we have "Primary Duties & Responsibilities" repeated twice (typo). We'll combine into Responsibilities section. We have "Hiring Range for this position is $34.45 - 43.06/Hourly. This is classified as VHBE (Variable Hour Benefit Eligible), where the selected candidate will work an average of 40 hours per week. The selected candidate will be eligible to elect Medical Benefits as well as accrue paid time off and receive 11 paid holidays." This includes Pay (hiring range), Schedule (40 hours per week), Benefits (medical, PTO, holidays). So we could have Pay section with the range, Schedule section with 40 hours/week, Benefits section with medical, PTO, holidays plus the Why Work for Aurora list. But instruction: Prefer a few substantive sections over many thin ones. So maybe combine Pay, Schedule, Benefits into one "Compensation and Benefits" section? But they said use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect separate headings if content exists. However they also say prefer a few substantive sections over many thin ones. So we need to balance. We have real content for Pay (range), Schedule (40 hrs/week), Benefits (medical, PTO, holidays, plus other perks). Could make three sections; each is substantive enough. Might be okay. We also have "Minimum Qualifications & Working Conditions" which includes Education, Experience, Technical skills, Preferred Experience, Licenses and Certifications, Knowledge, Abilities, Skills, Physical Demands, Work Environment, Equipment Used. That's a lot; we could split into Requirements (Education, Experience), Qualifications (maybe Preferred Experience, Licenses), Skills, etc. But we have headings list includes Requirements, Qualifications, Skills. So we can map. Let's parse: - Education: Bachelor's Degree in ... with course work... - Experience: Two (2) years of experience as a crime and or intelligence analyst at a municipal police department... - Technical skills and experience related to the use of data, relational databases, software and technical troubleshooting. - Preferred Experience: list of items. - Licenses and Certifications: NCIC/CCIC certification preferred - Knowledge: list - Abilities: list - Skills: list - Physical Demands: list - Work Environment: description - Equipment Used: list Thus we can create sections: - Requirements (Education + Experience) - Qualifications (Technical skills, Preferred Experience, Licenses/Certifications) - Skills (Skills list) - Physical Demands (maybe under Working Conditions? but we could include as its own section? Not in list of headings but we could still use h3 for Physical Demands if we want; but instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. Physical Demands could be part of Working Conditions; we could include under a "Working Conditions" heading but not in list. Might be okay to create a "Working Conditions" section. However instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can create a "Working Conditions" section with Physical Demands, Work Environment, Equipment Used. That seems reasonable. Thus sections: - About the role (intro paragraph about City of Aurora, core values, Why Work for Aurora? maybe combine with Benefits? But we have Benefits separate.) - Responsibilities (Primary Duties & Responsibilities) - Requirements (Education + Experience) - Qualifications (Technical skills, Preferred Experience, Licenses/Certifications) - Skills (Skills list) - Benefits (Why Work for Aurora list + medical, PTO, holidays) - Pay (Hiring Range) - Schedule (VHBE classification, 40 hrs/week) - Working Conditions (Physical Demands, Work Environment, Equipment Used, Drug-free workplace policy maybe) We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO lines, application instructions, deadline, ongoing screenings, veterans preference, etc. Also remove duplicated lines like "Primary Duties & Responsibilites" (typo) and second occurrence. Also remove "The city of Aurora will implement furlough days (unpaid days off) for most employees in 2026. The scheduled furlough dates are January 16, April 10, July 2, and December 24." That's substantive about schedule? Could be part of Working Conditions or Schedule. It's a policy; we could include under Working Conditions as note. It's not boilerplate; it's specific. Keep. Also remove "Despite the changes in Colorado law, the City of Aurora maintains a drug-free workplace..." Keep as part of Working Conditions. Now craft HTML. We'll start with a p for location: "
Location: 15001 E Alameda Pkwy, Aurora, Colorado 80012-1554
" maybe. Then About the role: combine intro paragraph: "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." Then maybe a separate p for "Why Work for Aurora?" but we will put those under Benefits. Responsibilities: we need to list duties from the Primary Duties & Responsibilities section (the long list). We'll extract bullet points. Let's list duties: - The Crime Analyst identifies crime patterns and trends, identifies, collects, and evaluates case information and intelligence in order to conduct research that assists police with the apprehension of offenders, clearance of cases, and suppression or prevention of further criminal activity. - Use a variety of computer applications, electronic spreadsheets, mapping software, word processing, and statistical applications to conduct analysis. - Use EXCEL macros or other similar editing techniques on crime data to analyze, format, simplify, and present findings. - Identify and collect data factors using a variety of police reports to track patterns, forecast trends, and report actionable findings that inform resource deployment - Query public safety databases (RMS, NCIC/CCIC, Accurint, Lumen, Linx, etc.) to collect, analyze, interpret, evaluate and disseminate crime, arrest, intelligence, operational, and procedural data using modern data and program analysis techniques. - Conduct analysis relating to modus operandi, spatial, temporal, and statistical factors. - Correlate new information with existing information to identify emerging, evolving or existing patterns, series and hotspot activity. - Attend team meetings to receive and provide relevant information. - Work to identify new solutions to connect data to strategic decision-making and resource deployment. - Prepare real time analysis, monthly summaries; publish and disseminate said materials as requested. - Clearly present information about analysis and findings to internal and external partners who do not have a background in analysis . - Compile, create, and present materials used for problem-solving meetings to inform police executives, consent decree monitors, and other entities as needed. - Prepare PowerPoint presentations, maps, graphs, charts, tables and other illustrative devices that organize and simplify information to support investigations, police administration, and quarterly annual reports. - Utilize ArcMAP/ArcPRO to prepare a variety of map products as well as to conduct geospatial analysis on public safety data. - Connect with data analysts and crime analysts internal and external to the city to facilitate a cooperative relationship that enhances support of public safety and facilitates and furthers investigative leads for law enforcement. - Participate in the maintenance of data integrity, validate results, identify potential issues and use appropriate strategies to resolve discrepancies or report issues. - Write queries to extract, clean, and validate data for reports, charts, and graphs. - Respond to ad hoc requests for information. - Conduct research and analysis on subjects’ histories, associates, group affiliations, addresses, vehicles, etc. - Monitor and collect data and intelligence -