Masonry Mechanic I

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Keep substantive info. Let's parse the posting. Content: - Intro: "Nature and Variety of Work Come join our team! Prince George’s County Government provides a dynamic and inclusive workplace where employees can thrive, learn, and grow across its 30 diverse agencies, all dedicated to serving the County's residents with essential resources and services. Nestled just minutes away from Washington, DC, Prince George's County combines urban vibrancy with serene surroundings, offering an ideal setting to live, work, and enjoy life. The Prince George's County Department of Public Works & Transportation (DPW&T) is currently seeking highly qualified applicants to fill a Masonry Mechanic I (Masonry Mechanic 1A) grade A11/12 position in the Office of Highway Maintenance." - About The Position: "This is an entry level manual concrete / cement work accomplished in conjunction with the construction and repairs of residential sidewalks and curb and gutter, and driveway aprons. Work is performed under general supervision in accordance with departmental policies, rules, and regulations." - About The Agency: description of DPW&T responsibilities. - Examples of Work: list of duties. - Qualifications: Minimum Qualifications and Preferred Qualifications. - Additional Information: Salary Range Transparency (mention salary range but not actual numbers). Tentative Interview Dates (but that's application instruction? It's date info; maybe we can include under a section? The instruction says remove application instructions. Interview dates maybe considered application instruction? Probably remove. Job Location: Forestville, MD. Conditions of Employment: list of requirements (training, protective apparel, preemployment checks, essential employee, snow and ice control). Eligibility to Work: immigration, E-Verify. Internal applicants info. EEO statement (remove). So we need to keep substantive info: location, conditions of employment, maybe salary range (though not specific numbers). The instruction: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD') and never create Pay/Schedule/Benefits sections unless the posting actually states them." Salary range: they say "Salary Range Transparency: The salary range listed in this announcement reflects the anticipated offer range for this position. Offers made within this range are based on qualifications, experience, and internal equity." No actual numbers given. That's vague but still says there is a salary range listed (though not shown). It's not a specific number; but it's still stating that there is a salary range. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that there is a salary range listed, but not the actual numbers. Is that considered stating them? It says "The salary range listed in this announcement reflects the anticipated offer range". It implies there is a range listed, but we don't see it in the text. Possibly the original posting had a range but omitted here. Since we don't have actual numbers, we might avoid creating a Pay section because we don't have concrete info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that there is a salary range listed, but we don't have the numbers. Might be safer to omit Pay section. Schedule: Not mentioned. Benefits: Not mentioned. So we likely will have sections: About the role (maybe combine About The Position and About The Agency?), Responsibilities (Examples of Work), Qualifications (Minimum and Preferred), maybe Additional Information (Location, Conditions of Employment). Could also have Skills? Not explicitly listed but could infer from qualifications. Better to stick to sections we have content for. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. So no heading like "Masonry Mechanic I". Good. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, except boilerplate. Let's extract substantive sections: Intro paragraph about workplace, location, agency. Could be under "About the role" or maybe a general intro. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and put the intro + About The Position + About The Agency? Might be too much but okay. Better: "About the role" could include description of the position and agency. Then "Responsibilities" for Examples of Work. Then "Qualifications" for Minimum and Preferred. Then maybe "Additional Information" not a standard heading but we could use "About the role" again? Not allowed to create new headings beyond those listed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should stick to those. We can omit sections we don't have content for. Thus we need to map content to these headings: - About the role: includes nature of work, agency description, position description. - Responsibilities: list of duties (Examples of Work). - Qualifications: Minimum and Preferred qualifications. - Skills: maybe we could extract from qualifications? But we don't have explicit skills list; we could treat qualifications as skills? Might be thin. Better to omit Skills if no explicit content. - Benefits: none. - Pay: none specific. - Schedule: none. - Requirements: maybe same as Qualifications? The list includes Requirements as a possible heading. Could use Requirements for eligibility/conditions? But we have Qualifications heading already. Could use Requirements for conditions of employment (training, protective apparel, essential employee, etc.). That seems appropriate. Thus we can have:

  About the role

  ... intro + About The Position + About The Agency ...

  Responsibilities

  • ... each duty ...

  Qualifications

  Minimum Qualifications: ...

  Preferred Qualifications: ...

  Requirements

  Conditions of Employment: ... (list)

  Job Location: Forestville, MD

  Eligibility to Work: ... (immigration, E-Verify)

  Maybe also include "Internal applicants" info? That's about internal applicants rights; could be considered requirement? Might be considered boilerplate? It's specific to internal applicants; maybe keep as part of Requirements. We must not include EEO statement. Remove that. Also remove "ONLY ONLINE APPLICATIONS WILL BE ACCEPTED" (application instruction). Remove "Tentative Interview Dates". Remove "Salary Range Transparency" maybe we can keep as part of Requirements? It's about pay but not specific; maybe we can omit because it's vague. But it's substantive: says salary range listed in announcement reflects anticipated offer range. Could be considered Pay section but we don't have numbers. Might be better to omit Pay section entirely. We must preserve ALL substantive information; does that include the salary range transparency statement? It's substantive but not specific numbers. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that there is a salary range listed (though not shown). I'd argue we should include a Pay section with the statement that a salary range is listed and offers based on qualifications etc. But we don't have the actual range; still it's stating that there is a range. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state that there is a salary range listed (the announcement reflects the anticipated offer range). So we could include a Pay section with that statement. However, the instruction also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The statement "The salary range listed in this announcement reflects the anticipated offer range for this position. Offers made within this range are based on qualifications, experience, and internal equity." is not filler; it's actual content. So we could include Pay section with that paragraph. Similarly, Schedule: none. Benefits: none. Thus we could have Pay section. But we already have Qualifications and Requirements; adding Pay may be okay. Let's decide to include Pay section with that statement. Now we need to ensure we don't repeat job title as heading. Not using it. Now we need to strip boilerplate: EEO, navigation, cookie, legal, scam-warning, duplicated lines, application instructions. Let's rewrite content. First, gather About the role content: - "Nature and Variety of Work Come join our team! Prince George’s County Government provides a dynamic and inclusive workplace where employees can thrive, learn, and grow across its 30 diverse agencies, all dedicated to serving the County's residents with essential resources and services. Nestled just minutes away from Washington, DC, Prince George's County combines urban vibrancy with serene surroundings, offering an ideal setting to live, work, and enjoy life. The Prince George's County Department of Public Works & Transportation (DPW&T) is currently seeking highly qualified applicants to fill a Masonry Mechanic I (Masonry Mechanic 1A) grade A11/12 position in the Office of Highway Maintenance." - About The Position: "This is an entry level manual concrete / cement work accomplished in conjunction with the construction and repairs of residential sidewalks and curb and gutter, and driveway aprons. Work is performed under general supervision in accordance with departmental policies, rules, and regulations." - About The Agency: "The Department of Public Works and Transportation (DPW&T) is responsible for nearly 2,000 miles of County-maintained roadways that range from rural to urban classifications. The transportation infrastructure includes 900 bridges, as well as shoulders, sidewalks, curbs/gutters, stormwater management facilities, driveway aprons and nearly 3,000 acres of grassy area -- all of which are maintained by staff of the Department. DPW&T’s workforce keeps the County’s various services moving by performing a myriad of activities which include removing snow and ice from County-maintained roadways, upgrading traffic signals, installing streetlights, clearing fallen trees, unclogging drainage inlets and maintaining stormwater management facilities, as well as performing roadway repairs ranging from potholes and sidewalk trip hazards to bridge repairs and resurfacing projects and more." Combine into a paragraph or multiple paragraphs. Use

  for prose. Now Responsibilities: list of duties from "Examples of Work". Let's extract each bullet: - Performs routine and less complex cement/brick finishing duties associated with the trade; - Removes old concrete, sets forms, mixes, places, and finishes new concrete - Places and other expansion joints in sidewalks, curb & gutter, and driveways - Smooth and levels cement surfaces using trowels and other tools - Applies a finishing coat of cement to surfaces of the streets, sidewalks, bridgework and other concrete work - Measures dimensions to calculate quantities of materials needed - Draws from Stock and procures materials, tools, equipment, and supplies for each concrete maintenance project - Assists in