Project Inspector - Seasonal

We need to output HTML fragment with sections: About the role? The description includes description paragraph about company, position overview, requirements, qualifications, compensation & benefits, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content for it. We need to map content. We have: - Description: At Clark Dietz... (company overview). Could be "About the role"? Actually "About the role" maybe includes position overview. We'll treat "About the role" as the position overview paragraph. - Responsibilities: The bullet list under Requirements? Actually the "Requirements" section includes duties: Provides inspection and documentation services..., Reads and interprets..., Performs site data collection..., Maintains detailed daily logs..., Collaborates..., Works productively..., Other duties as assigned. Those are responsibilities. So we can put them under

Responsibilities

with

• . - Requirements: The qualifications? Actually they have "Requirements" heading in the posting: "Requirements" then bullet list of duties. Then "Qualifications" heading then bullet list of qualifications. So we need separate sections: Requirements (maybe they want responsibilities) and Qualifications (education, experience). But the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map accordingly. Thus: - About the role: company description + position overview paragraph. - Responsibilities: list of duties (the bullet list under Requirements heading). Use
  • . - Requirements: maybe the qualifications? Actually they have "Requirements" heading then duties; but we already used that for responsibilities. However we could treat "Requirements" as the qualifications (education, experience). But they also have a separate "Qualifications" heading. The posting has both "Requirements" and "Qualifications". So we need to decide mapping. Given the instruction list includes both Requirements and Qualifications, we should keep both. So we need to extract content for each. From posting: Under "Requirements": bullet list of duties (inspection and documentation services...). That's more like responsibilities. Under "Qualifications": bullet list of education/skills: High School diploma..., Ability to read..., Proficiency..., Good organizational..., Must have valid driver’s license... Thus we can assign: - Responsibilities: the duties list (under Requirements heading). - Requirements: maybe the qualifications list? But they also have Qualifications heading. Could treat Requirements as the "Ability to read and interpret plans..." etc? Actually the qualifications list includes ability to read..., proficiency..., good organizational..., driver's license. That seems like requirements. The Qualifications heading includes education preferences. Hmm. Better: Use: - Requirements: the bullet list under "Requirements" (duties). But that seems odd. - Qualifications: the bullet list under "Qualifications" (education, skills, license). But then we have duplicate headings? The instruction says we can include a section only when posting has real specific content for it. So we can include both Requirements and Qualifications sections with appropriate content. Thus:

    Requirements

    • Provides inspection and documentation services on civil construction projects (roadway, bridge, and intersection improvements) for public sector clients.
    ... etc

    Qualifications

    • High School diploma or GED is required; A.S. degree in Construction Technology or a related field is preferred.
    • Ability to read and interpret plans and specifications, and perform inspection and documentation on road, bridge, and intersection improvements is preferred.
    • Proficiency with MS Office applications (Excel and Word) is required and experience with e-Builder, Primavera, CMMS, MISTIC, CEPS, and I-MIRS is desired.
    • Good organizational and communication skills with the ability to maintain detailed daily logs and follow through on outstanding punch list items.
    • Must have a valid driver’s license and be able to travel to project sites as needed.
    Now Benefits, Pay, Schedule: The posting includes "Compensation & Benefits Starting salary range: $30/hour Comprehensive benefits package plus 401(k) & ESOP with unlimited company match. Part-time and Seasonal Paid Time off Accrual." So we have Pay: $30/hour. Benefits: comprehensive benefits package plus 401(k) & ESOP with unlimited company match. Part-time and Seasonal Paid Time off Accrual. Schedule: Not explicitly stated; maybe part-time/seasonal? It mentions part-time and seasonal paid time off accrual, but not schedule. Could infer schedule is part-time/seasonal? But we should not create Schedule section unless posting actually states them. It does not state schedule like full-time, hours per week, shift. So we omit Schedule. We also have About the role: combine company description and position overview. Position Overview: "Clark Dietz is seeking a Project Inspector to work in our Lexington, KY office. This position will be providing construction phase services (inspection and documentation) for various projects around the Lexington area." Thus About the role section: combine the introductory paragraph about company and position overview. We need to avoid repeating job title as heading. Already not. We must remove boilerplate: EEO, etc. At end there is "Clark Dietz is an Equal Opportunity Employer..." and salary description repeated. Remove. Now produce HTML fragment:

    About the role

    At Clark Dietz, we're more than an engineering firm. We're employee-owners committed to improving the quality of life in the communities we serve. As an ENR Top 500 design firm with offices across Illinois, Indiana, Kentucky, Michigan, and Wisconsin, we provide transportation, civil, environmental, structural, mechanical, electrical, and construction engineering services that make a lasting impact. Clark Dietz is seeking a Project Inspector to work in our Lexington, KY office. This position will be providing construction phase services (inspection and documentation) for various projects around the Lexington area.

    Responsibilities

    • Provides inspection and documentation services on civil construction projects (roadway, bridge, and intersection improvements) for public sector clients.
    • Reads and interprets construction plans and documents, computes quantities and verifies measurements and layouts.
    • Performs site data collection and verifies existing conditions; assists with surveying.
    • Maintains detailed daily logs and submits progress reports and pay documentation.
    • Collaborates with other construction and design staff to complete projects on budget.
    • Works productively with all project stakeholders (contractor, owner, and residents) to resolve issues in a professional manner.
    • Other duties as assigned.

    Requirements

    • Provides inspection and documentation services on civil construction projects (roadway, bridge, and intersection improvements) for public sector clients.
    • Reads and interprets construction plans and documents, computes quantities and verifies measurements and layouts.
    • Performs site data collection and verifies existing conditions; assists with surveying.
    • Maintains detailed daily logs and submits progress reports and pay documentation.
    • Collaborates with other construction and design staff to complete projects on budget.
    • Works productively with all project stakeholders (contractor, owner, and residents) to resolve issues in a professional manner.
    • Other duties as assigned.
    But that duplicates responsibilities. Actually we need separate content for Requirements. The posting's "Requirements" heading is the duties list. So we should use that for Requirements. Then Responsibilities maybe we could also have same? But we need to avoid duplication? The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we put same list under both Responsibilities and Requirements, we are duplicating content, which is okay as it's preserving. But maybe better to assign Responsibilities as the duties list, and Requirements as the qualifications list? However then we lose the duties list under Requirements heading (which is present). But we could still keep duties list under Responsibilities and also include them under Requirements? That duplicates but preserves. However the instruction says "Prefer a few substantive sections over many thin ones." Duplication may be considered thin? Not sure. Better to follow the posting: Use Responsibilities for the duties list (makes sense). Use Requirements for the qualifications list (education, skills, license). Use Qualifications for maybe the preferred degree? Actually qualifications list includes both required and preferred. But we already used qualifications for skills. Hmm. Let's examine the posting again: "Requirements Provides inspection and documentation services on civil construction projects (roadway, bridge, and intersection improvements) for public sector clients. Reads and interprets construction plans and documents, computes quantities and verifies measurements and layouts. Performs site data collection and verifies existing conditions; assists with surveying. Maintains detailed daily logs and submits progress reports and pay documentation. Collaborates with other construction and design staff to complete projects on budget. Works productively with all project stakeholders (contractor, owner, and residents) to resolve issues in a professional manner. Other duties as assigned." "Qualifications High School diploma or GED is required; A.S. degree in Construction Technology or a related field is preferred. Ability to read and interpret plans and specifications, and perform inspection and documentation on road, bridge, and intersection improvements is preferred. Proficiency with MS Office applications (Excel and Word) is required and experience with e-Builder, Primavera, CMMS, MISTIC, CEPS, and I-MIRS is desired. Good organizational and communication skills with the ability to maintain detailed daily logs and follow through on outstanding punch list items. Must have a valid driver’s license and be able to travel to project sites as needed." Thus the "Requirements" are duties; "Qualifications" are education/skills/license. Thus we should map: - Responsibilities: maybe we could also have a Responsibilities section but we already used Requirements for duties. However the instruction list includes Responsibilities as a possible heading. We could still include Responsibilities with same content as Requirements? That seems redundant but maybe acceptable. However we could also treat Responsibilities as the duties list and Requirements as the qualifications list, and Qualifications as maybe the education/degree? But then we lose the distinction between required vs preferred. Given the instruction list includes both Requirements and Qualifications, we should have both sections with distinct content. So we need to assign content to each. Thus: - Requirements: duties list (as above). - Qualifications: education/skills/license list (as above). - Responsibilities: maybe we could also have a Responsibilities section but we could omit if we think it's redundant. However the instruction says include a section ONLY when the posting has real, specific content for it. If we omit Responsibilities, we are not violating because we don't have a heading with filler. But we might lose the duty list if we only put it under Requirements. But the duty list is already under Requirements, so we have covered it. So we can omit Responsibilities. Thus sections: About the role, Requirements, Qualifications, Benefits, Pay. We need to include Pay: $30/hour. Benefits: comprehensive benefits package plus 401(k) & ESOP with unlimited company match. Part-time and Seasonal Paid Time off Accrual. We should not include Schedule. Now produce HTML. Make sure to use

    for each section heading. Wrap each section's content in

    for prose,

    • for lists. About the role: prose paragraph. Requirements: list. Qualifications: list. Benefits: maybe a
      • for each benefit? Could be a

        but we have list of benefits: comprehensive benefits package plus 401(k) & ESOP with unlimited company match. Part-time and Seasonal Paid Time off Accrual. Could be two items. Pay:

        Starting