Project Manager, Civil Engineer- Land Development

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "Who We Are" (company description) but not a section heading we need? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes a job description: "As a Project Manager for Atwell's Civil Engineering group, you'll dive into diverse projects..." That's about the role. So we can have

About the role

with paragraph(s). Then Responsibilities: list bullet points. Then Benefits: list bullet points. Pay: there is "Compensation: Competitive Compensation packages Annual bonuses, spot bonuses and peer recognition awards 401K match - 1:1 up to 4% of compensation Tuition Assistance Student Loan Repayment Paid Licensing / Certification Fees and Renewals Financial Rewards for Obtaining Licensure Employee Referrals Annual Wellness Reimbursement ...". That's compensation details, so we can have Pay section. Schedule: not mentioned; we should not create Schedule unless present. Requirements/Qualifications/Skills: The posting does not list explicit requirements or qualifications; maybe implied but not explicit. So we should not create those sections unless there is real specific content. The "Engineering Software Whiz" etc could be considered Skills. There's a bullet list under Responsibilities that includes skills like AutoCAD Civil 3D, etc. But we could also create a Skills section if there is explicit skill list. The posting includes "Engineering Software Whiz: You'll be a pro with AutoCAD Civil 3D and various engineering software packages." That's a skill. Also "Project Collaboration", "Mentorship and Guidance", "Technical Guru", "Construction Support", "Future-Ready". Those are responsibilities. Could also treat some as skills. But we need to avoid thin sections. Probably better to have About the role, Responsibilities, Benefits, Pay. Possibly also Skills if we extract skill list. Let's see if there is explicit skill list: "Engineering Software Whiz: You'll be a pro with AutoCAD Civil 3D and various engineering software packages." That's one skill. Not a list. Could also infer "Project Management skills". But not explicit. Safer to not create Skills section unless we have clear list. The instruction: Prefer a few substantive sections over many thin ones. So we will include About the role, Responsibilities, Benefits, Pay. No Requirements, Qualifications, Skills, Schedule. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting: Who We Are (company description) maybe part of About the role? Actually "Who We Are" is company overview, not role. But we could include it in About the role? The instruction says use headings for sections like About the role, Responsibilities, etc. The "Who We Are" is not one of those headings, but we could incorporate it into About the role paragraph as background. However we must preserve all substantive information; we can include it in About the role paragraph. The job description also includes "Job Description: As a Project Manager...". We'll include that. We must remove boilerplate: Disclaimer about AI tools, Atwell does not accept unsolicited resumes, etc. Also remove "Atwell Benefits:" heading? We'll keep benefits content but not the heading "Atwell Benefits:" as it's not a heading we need; we will output

Benefits

and list. We need to format lists with

• . For About the role we can have

  paragraphs. Let's extract content: Who We Are: "Atwell, LLC is a bold leader in the consulting, engineering, and construction services industry, delivering a broad range of creative solutions to clients in the real estate & land development, and energy markets. We have a strong national presence and a diverse, award-winning project portfolio. Atwell is a privately owned company, with 2,000+ passionate team members across 75+ locations and growing!Atwell, LLC is a proud recipient of the following 2025 awards:Ten consecutive years in a row as a “Best Place to Work” by Zweig Group (#11)Recognized as #70 in the ENR Top 500 Design Firms, ranked in every regionRecognized in Crain's “Fast 50” as one of the fastest-growing companies (#14)Recognized as the 2025 ENR Design Firm of the year for the Southeastern US" We need to preserve that exactly, but we can format as paragraphs. Ensure we keep the awards list as separate sentences or maybe as a list? The instruction: use

  • for any list of duties/requirements/benefits. Awards list is not duties/requirements/benefits, but it's a list; we could still use
    • but not required. Safer to keep as paragraph with commas. But we need to preserve all info; we can keep as a paragraph. Job Description/About the role: "As a Project Manager for Atwell's Civil Engineering group, you'll dive into diverse projects of varying sizes and complexities. This is your chance to shape your career in a dynamic and entrepreneurial work environment." Responsibilities list: - Project Collaboration: You'll collaborate closely with production team, assisting them in drafting, reviewing, and finalizing preliminary and final site plans and construction documents. - Mentorship and Guidance: Take on a leadership role by guiding and assisting junior staff. Ensure that project-based tasks are executed accurately and efficiently, nurturing the talents of the next generation. - Technical Guru: Utilize your engineering prowess to prepare a wide range of reports, opinions, and recommendations. From hydrology/hydraulic studies to project schedules and storm sewer reports, your technical skills will shine. - Construction Support: Provide essential construction-related services and direct junior team members. From permit applications to quantity estimates, you'll play a pivotal role in turning plans into reality. - Engineering Software Whiz: You'll be a pro with AutoCAD Civil 3D and various engineering software packages. Your expertise will ensure that assignments are completed on time and within budget. - Future-Ready: This role isn't just about today; it's about tomorrow. Develop your Project Manager skills through training and mentoring, with the potential to grow into a Project Manager role. Note: The last bullet says "grow into a Project Manager role" but they are already Project Manager; maybe a typo but we keep. Benefits list (from Atwell Benefits): Work/Life: - Generous Paid Time Off - Paid Parental Leave - Flexible work schedules are available for some positions - Tenure Awards — Travel Vouchers to see the world based on your travel preferences Compensation: - Competitive Compensation packages - Annual bonuses, spot bonuses and peer recognition awards - 401K match - 1:1 up to 4% of compensation - Tuition Assistance - Student Loan Repayment - Paid Licensing / Certification Fees and Renewals - Financial Rewards for Obtaining Licensure - Employee Referrals - Annual Wellness Reimbursement for anything wellness related (Gym memberships, fitness tracker, home gym equipment, etc.) - Dependent Care Match ‘Atwell’ness: - Medical (BC/BS), Dental (Delta), and Vision (VSP) - Family Planning & IVF Benefits - Pet Insurance - Health Savings Account & Flex Spending Account options - Employer paid LTD, STD, and life insurance - Metlife Supplemental Benefits covering accident, hospitalization, and critical illness - Member Assistance Program (MAP) with complimentary counseling sessions, legal benefits, financial consultations, and work/life referral services We need to output as
      • under Benefits heading. Should we separate categories? Could keep as one list; but maybe better to keep as one list preserving all items. The instruction: use
        • for any list of duties/requirements/benefits. So we can make a single
          with all benefit items. However we might lose categorization but still preserve all items. It's okay. Pay section: from Compensation bullet list (the same as above? Actually the compensation list is part of Benefits section in the posting; but we separated Pay as compensation. The posting has "Compensation:" then list. So we will treat that as Pay section. Benefits section includes Work/Life and ‘Atwell’ness. So we need to split: Pay: compensation items; Benefits: Work/Life and ‘Atwell’ness items. Thus: Pay: - Competitive Compensation packages - Annual bonuses, spot bonuses and peer recognition awards - 401K match - 1:1 up to 4% of compensation - Tuition Assistance - Student Loan Repayment - Paid Licensing / Certification Fees and Renewals - Financial Rewards for Obtaining Licensure - Employee Referrals - Annual Wellness Reimbursement for anything wellness related (Gym memberships, fitness tracker, home gym equipment, etc.) - Dependent Care Match Benefits: Work/Life: - Generous Paid Time Off - Paid Parental Leave - Flexible work schedules are available for some positions - Tenure Awards — Travel Vouchers to see the world based on your travel preferences ‘Atwell’ness: - Medical (BC/BS), Dental (Delta), and Vision (VSP) - Family Planning & IVF Benefits - Pet Insurance - Health Savings Account & Flex Spending Account options - Employer paid LTD, STD, and life insurance - Metlife Supplemental Benefits covering accident, hospitalization, and critical illness - Member Assistance Program (MAP) with complimentary counseling sessions, legal benefits, financial consultations, and work/life referral services We could keep subheadings inside Benefits as

          or

          ? Not allowed; only

          for section headings. We could keep as paragraphs before lists. Eg

          Work/Life:

          then

          . That's acceptable. Now we need to output only HTML fragment, no markdown. Let's craft:

          About the role

          Atwell, LLC is a bold leader in the consulting, engineering, and construction services industry, delivering a broad range of creative solutions to clients in the real estate & land development, and energy markets. We have a strong national presence and a diverse, award-winning project portfolio. Atwell is a privately owned company, with 2,000+ passionate team members across 75+ locations and growing. Atwell, LLC is a proud recipient of the following 2025 awards: Ten consecutive years in a row as a “Best Place to Work” by Zweig Group (#11); Recognized as #70 in the ENR Top 500 Design Firms, ranked in every region; Recognized in Crain's “Fast 50” as one of the fastest-growing companies (#14); Recognized as the 2025 ENR Design Firm of the year for the Southeastern US.

          As a Project Manager for Atwell's Civil Engineering group, you'll dive into diverse projects of varying sizes and complexities. This is your chance to shape your career in a dynamic and entrepreneurial work environment.

          Responsibilities

          • Project Collaboration: You'll collaborate closely with production team, assisting them in drafting, reviewing, and finalizing preliminary and final site plans and construction documents.
          • Mentorship and Guidance: Take on a leadership role by guiding and assisting junior staff. Ensure that project-based tasks are executed accurately and efficiently, nurturing the talents of the next generation.
          • Technical Guru: Utilize your engineering prowess to prepare a wide range of reports, opinions, and recommendations. From