Project Assistant

We need to output HTML fragment with sections: About the role? Actually we have description includes "ABOUT US", "About This Opportunity", "YOUR DAY-TO-DAY", "YOU’RE READY FOR THIS ROLE IF YOU HAVE", "What We Offer", "PHYSICAL ENVIRONMENT". Also there is "EEO STATEMENT", "VISA AND SPONSORSHIP" which are boilerplate to remove. Also "Description" header maybe not needed. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt headings to match content. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? It says e.g., meaning examples, but we should use those headings where appropriate. We need to include a section only when posting has real specific content. So we need to map content to these headings. We have: - About the role: could be "About This Opportunity" and maybe "ABOUT US"? But "About the role" likely corresponds to description of the role. We'll put that as

About the role

with paragraph summarizing the opportunity. - Responsibilities: corresponds to "YOUR DAY-TO-DAY" (Project Coordination, Document Control & Reporting, Office Operations). We'll list as

• items. - Requirements: could be "YOU’RE READY FOR THIS ROLE IF YOU HAVE" includes education, experience, skills. We'll put as
  • . - Qualifications: maybe overlapping with Requirements; but we could treat Requirements as experience/skills, Qualifications as education/certifications. However we can combine. The instruction says prefer few substantive sections over many thin ones. So we might combine Requirements and Qualifications into one section? But they ask to use those headings if we have content. We could have both but ensure they have content. Let's see: Requirements could be experience and skills; Qualifications could be education and certifications. We have both. - Skills: maybe we could list specific skills like MS Office, ACC, etc. But we already have them in Requirements. Could create Skills section for technical proficiencies. - Benefits: "What We Offer" includes Culture & Recognition, Pay, Ownership & Retirement, Benefits & Wellbeing, Perks & Projects. We can split into Benefits, Pay, etc. But we need to include Pay and Benefits sections only if posting actually states them. It does: Pay, Ownership & Retirement (weekly pay, competitive salary, bonus incentives, ESOP, 401k). Benefits & Wellbeing (free healthcare plan option plus medical, dental, vision, life, disability, paid parental leave, etc). Perks & Projects (rewards including pro sports tickets, fitness memberships, travel vouchers, paid work anniversary sabbaticals, award-winning projects). So we could have sections: Pay, Benefits, Perks (maybe not in list). The instruction gave examples: Benefits, Pay, Schedule. Schedule not present, so omit. We also have "PHYSICAL ENVIRONMENT" which is not in the list but we could treat as maybe "Requirements"? But it's about physical demands. Could be included under Requirements or maybe a separate section not in list but we could still use

    Physical Environment

    ? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings and maybe incorporate physical environment into Requirements or Qualifications? Probably better to include as part of Requirements (since it's a requirement). But we could also add a separate section if we want, but risk deviating. I'd incorporate physical demands into Requirements or maybe a separate "Working Conditions" but not in list. I'd add to Requirements. Now we need to remove boilerplate: EEO STATEMENT, VISA AND SPONSORSHIP, also maybe "Description" header, "ABOUT US" maybe we keep as part of About the role? Actually "ABOUT US" is company overview, not role. Could be omitted as not directly about role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." It didn't say to drop company overview. But we need to preserve ALL substantive information. The company overview is substantive about Okland. Should we include? Possibly under About the role? Might be okay to include a brief paragraph about the company under About the role. But the heading "About the role" expects role description. Could we have two sections: About the company and About the role? Not in list. Might be okay to include company overview as a paragraph before the role description, but not as a heading. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. To be safe, we could include a

    with company overview before the role section. Thus output:

    Okland is a commercial general contractor and construction management company with more than 1,500 team members, delivering complex projects across healthcare, semiconductor, higher education, sports, hospitality, and other specialized markets. Founded in 1918 in Salt Lake City, we have grown for more than a century and operate throughout Utah, Arizona, and Idaho.

    Then

    About the role

    with paragraph about opportunity. Then

    Responsibilities

    with ul. Then

    Requirements

    with ul (education, experience, skills, physical demands). Then

    Qualifications

    maybe we could list preferred qualifications like associate's degree, coursework, certifications, experience with ACC etc. But we already included those in Requirements. To avoid duplication, maybe we treat Requirements as experience and skills, Qualifications as education/certifications. Let's split: Requirements: experience (2+ years admin, project coordination, office support, preferably construction; supporting project management teams; ability to work independently, maintain confidentiality, collaborate; ability to walk sites, occasional overtime). Qualifications: education (high school diploma or equivalent required; associate's degree, coursework, or certifications in business, construction, or related field a plus); proficiency in Microsoft Office Suite, particularly Word and Excel, with experience performing data entry, preparing reports, maintaining project records; experience with construction technology platforms such as Autodesk Construction Cloud (ACC), Autodesk Build, Bluebeam, or similar document management systems is preferred. Skills: maybe communication, problem-solving, organizational skills; ability to maintain confidentiality; etc. But we already covered. Could combine. Given instruction to prefer few substantive sections over many thin ones, maybe we combine Requirements and Qualifications into one section called Requirements. But they ask to use those headings if we have content. I'd create both but ensure they have distinct content. Let's define: - Requirements: experience and ability to work in construction environment (2+ years admin, supporting project teams, ability to walk sites, occasional overtime, ability to work independently, maintain confidentiality, collaborate). - Qualifications: education and technical proficiencies (high school diploma or equivalent; associate's degree or coursework in business/construction a plus; proficiency in MS Office; experience with ACC, Autodesk Build, Bluebeam). - Skills: communication, problem-solving, organizational skills; ability to maintain confidentiality; etc. But that overlaps. Maybe better: Requirements = experience + skills; Qualifications = education + certifications. Then Skills could be omitted. But we need to include Skills section only if we have specific skill list not covered elsewhere. We have MS Office, ACC, etc. Those could be under Skills. Let's allocate: - Requirements: experience (2+ years admin, project coordination, office support, preferably construction; supporting project management teams; ability to work independently, maintain confidentiality, collaborate; ability to walk sites, occasional overtime). - Qualifications: education (high school diploma or equivalent required; associate's degree, coursework, or certifications in business, construction, or related field a plus). - Skills: proficiency in Microsoft Office Suite (Word, Excel); experience with Autodesk Construction Cloud (ACC), Autodesk Build, Bluebeam, or similar document management systems; strong communication, problem-solving, organizational skills; ability to maintain confidentiality. That seems distinct. Now Benefits: we have Pay, Ownership & Retirement, Benefits & Wellbeing, Perks & Projects. We'll create:

    Pay

    with paragraph: Weekly pay, competitive salary and bonus incentives, ESOP employee ownership, and an industry-leading 401(k) with a 6% employer match.

    Benefits

    with ul: Free healthcare plan option plus medical, dental, vision, life, and disability coverage; paid parental leave; financial wellness tools; Employee Assistance Program; mental health support. Maybe also include Perks? Not in list but could be added as another section but not required. Could incorporate into Benefits as additional items: rewards including pro sports tickets, fitness memberships, travel vouchers, paid work anniversary sabbaticals, award-winning projects recognized by AIA, ENR, and AGC. We'll add to Benefits ul. Now we need to ensure we don't include boilerplate: EEO STATEMENT, VISA AND SPONSORSHIP, also maybe "PHYSICAL ENVIRONMENT" we incorporated into Requirements? We didn't include physical demands. We should include physical demands somewhere. Could add to Requirements as a bullet: Ability to periodically walk active construction sites, support project documentation efforts, and work occasional overtime to meet project demands. Also physical demands: regularly sit, talk/hear; frequently use hands; occasionally reach, climb/balance, stoop/kneel/crouch/crawl; occasionally lift up to 20 pounds; specific vision abilities include close vision and color vision; frequently inspect project; exposed to ongoing construction and various weather conditions; noise level moderate to loud. That's a lot but we should preserve all substantive information. We'll add those as bullet(s) under Requirements. Now we need to ensure we don't repeat content. Let's craft. Now produce HTML fragment. We'll start with company overview paragraph. Then

    About the role

    paragraph. Then

    Responsibilities

    with ul. Then

    Requirements

    with ul (including experience, physical demands, etc.) Then

    Qualifications

    with ul (education) Then

    Skills

    with ul (technical proficiencies, communication, etc.) Then

    Pay

    paragraph. Then

    Benefits

    with ul (including perks). Make sure no empty sections. Let's write. Check for any duplicated lines: we need to avoid repeating same info. Now craft content. Company overview paragraph: Okland is a commercial general contractor and construction management company with more than 1,500 team members, delivering complex projects across healthcare, semiconductor, higher education, sports, hospitality, and other specialized markets. Founded in 1918 in Salt Lake City, we have grown for more than a century and operate throughout Utah, Arizona, and Idaho. About the role paragraph: Okland is seeking a motivated and detail‑oriented administrative professional who thrives in a fast‑paced construction environment and enjoys supporting project teams through coordination, communication, and document management. The Project Assistant plays a key role in keeping project operations organized while gaining exposure to construction processes, field operations, and project management fundamentals. This role is designed as a developmental steppingstone along the Project Engineer to Project Manager career path, making it an excellent opportunity