UMass at Amherst Fall 2026 Career Fair

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - About Kleinfelder: description of company. Could be "About the role"? Actually "About Kleinfelder" is company overview. Could be placed under a heading like "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We have "About Kleinfelder" which is about the company, not role. Could map to "About the role"? Might be okay but better to use "About the role" heading and put company description there? However instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use those headings if appropriate. The posting includes "Position Overview" which is about the role. So we can use "About the role" heading for Position Overview. We have "What We’re Looking For:" which includes qualifications, requirements, skills. Could split into Requirements, Qualifications, Skills. But we need to avoid thin sections. Might combine into one "Requirements" or "Qualifications". The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills? But we can embed skills within Requirements. We need to extract responsibilities: The bullet list under Position Overview? Actually after "Position Overview" there is description: "As an upcoming graduate or new graduate, you will have the opportunity to work on exciting projects, collaborate with experienced engineers, and develop your skills in a dynamic work environment. Our team is looking for candidates in Boston, MA, Manchester, NH, Portland, ME, Rocky Hill, CT, Springfield, MA, Worcester, MA, and other offices. Our team is looking for candidates in the following fields:" then list of fields with descriptions. Those could be responsibilities? They describe what you'll do in each field. Could treat as Responsibilities. We also have "What We’re Looking For:" which includes qualifications. Benefits: "Benefits of Working at Kleinfelder:" with bullet points. Pay: Salary range: $21.09 per hour to $35.22 per hour. Schedule: Not mentioned. So we should not create Schedule section. We must not include boilerplate like EEO, legal, etc. Remove those. We must preserve all substantive information: company description, position overview, locations, fields with descriptions, qualifications, benefits, salary range. We must not invent or summarize away detail. So we need to keep the specifics: list of locations, list of fields with their descriptions. We need to format using

headings,

• for lists,

  for prose. We must not repeat job title as heading. No job title given explicitly; but we can ignore. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's craft:

  About the role

  Position Overview: As an upcoming graduate or new graduate, you will have the opportunity to work on exciting projects, collaborate with experienced engineers, and develop your skills in a dynamic work environment. Our team is looking for candidates in Boston, MA; Manchester, NH; Portland, ME; Rocky Hill, CT; Springfield, MA; Worcester, MA; and other offices.

  Then responsibilities: maybe a heading

  Responsibilities

  with
  list of fields and descriptions. List: - Civil Engineering Support: civil engineering projects involving site development, land development, and construction management. Collaborate with multidisciplinary teams to ensure successful project execution. - Transportation Engineering: assist with the planning, design, and implementation of transportation infrastructure projects. Work on projects ranging from roadway design to traffic analysis and transportation systems planning. - Water/Wastewater Engineering: assist with design, analysis, and management of water and wastewater infrastructure projects. Work on projects that support environmental sustainability and community health. - Geotechnical Engineering: conduct site investigations and geotechnical analysis for construction projects. Assist with soil testing, foundation design, and slope stability assessments. - Environmental Engineering: assist with the design and implementation of environmental solutions, including water treatment, waste management, and sustainability projects. Support environmental assessments, regulatory compliance, and site remediation efforts. - Bridge Design & Engineering: contribute to the design, analysis, and maintenance of bridges and other critical structures. Apply engineering principles to ensure safety, efficiency, and structural integrity. We need to keep the exact phrasing? The posting says: "Civil Engineering Support civil engineering projects involving site development, land development, and construction management. Collaborate with multidisciplinary teams to ensure successful project execution." So we can keep that as a sentence. We'll put each as
  • . Then qualifications:

    Requirements

    maybe combine qualifications and skills. List: - Students pursuing a degree in civil engineering, environmental engineering, geotechnical engineering, or environmental science. - Recent graduates or individuals with up to 2 years of experience in any of the listed engineering fields. - Bachelor’s degree in civil engineering, environmental engineering, geotechnical engineering, environmental science, or related field. - Strong problem-solving skills, critical thinking, and a passion for engineering solutions. - Ability to work collaboratively in a team environment. - Excellent communication and interpersonal skills. - Desire to learn, grow, and develop professionally. We could also include "What We’re Looking For:" as heading. Then benefits:

    Benefits

    with list: - Professional Development: mentorship, training, opportunity to work on a variety of projects with experienced professionals. - Work-Life Balance: flexible work arrangements and supportive workplace culture. - Diversity & Inclusion: inclusive work environment where diverse perspectives and backgrounds are celebrated. - Career Advancement: opportunities to take on new responsibilities and advance career through hands-on experience and internal training. - Comprehensive Benefits Package: health insurance, retirement plans, paid time off, wellness programs, and more. We need to keep the exact phrasing? The posting says: "Professional Development: At Kleinfelder, we invest in your growth. We offer mentorship, training, and the opportunity to work on a variety of projects with experienced professionals." etc. We'll keep that. Pay:

    Pay

    with

    The expected salary range for the position is $21.09 per hour to $35.22 per hour.

    (We should preserve the note about Maryland Wage Transparency Law and Massachusetts Wage Transparency Act? The posting includes two lines: "The expected salary range for the position is displayed in accordance with the Maryland Wage Transparency Law. Final agreed upon compensation is based upon individual qualifications and experience." and later "The expected salary range for the position is displayed in accordance with the Massachusetts Wage Transparency Act. Final agreed upon compensation is based upon individual qualifications and experience. Salary range: $21.09 per hour to $35.22 per hour." We need to preserve all substantive information. So we should include both statements? They are somewhat redundant but both are substantive. We'll include both sentences and then the salary range. We must not include boilerplate like EEO, legal, etc. So we omit those. We also need to include the company description? Could be under About the role or maybe a separate

    About Kleinfelder

    but instruction only gave examples; we could still use

    About Kleinfelder

    as a heading if we want, but they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to stick to those examples. So we incorporate company description into About the role? Might be okay. But the company description is not about the role. However we could treat "About the role" as including both role and company overview. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical headings; we can use them if appropriate. The posting has "About Kleinfelder" which is about the company; we could still put that under About the role? Might be odd but acceptable. Alternatively we could create a heading "About Kleinfelder" but that's not in the examples; but they didn't forbid other headings. However they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as you should use those headings for those sections; you can also use other headings if needed? The examples are just examples. I'd stick to the given headings to be safe. Thus we need to fit company description somewhere. Could put it in a

    before the headings? The instruction: Output ONLY the HTML fragment. It didn't say we must have headings for everything. We could have a

    for company overview, then headings for sections. That seems fine. Thus:

    Kleinfelder is a leading National provider of engineering, architecture, and environmental services. With over 60 years of experience, we are dedicated to delivering high-quality, sustainable solutions for a variety of industries. From infrastructure to environmental projects, our work impacts communities and helps build a better future. We are proud of our collaborative culture, diverse teams, and commitment to innovation, which makes Kleinfelder a great place to grow your career.

    Then

    About the role

    with position overview. Then

    Responsibilities

    with list. Then

    Requirements

    with list. Then

    Benefits

    with list. Then

    Pay

    with p containing the salary statements and range. We must not include Schedule. Check for any other substantive content: "Following an offer, candidates will be required to satisfactorily complete employment reference checks, verification of professional licensure and/or educational credentials, a motor vehicle report (MVR), and a comprehensive background check." This is substantive info about hiring process. Should we include? It's not covered by headings but we could add a section like "Hiring Process" but not in examples. Could we add a

    Hiring Process

    ? The instruction didn't forbid other headings, but they gave examples. Might be okay to add a heading for that. However they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be read as you should use those headings for those sections; you can also use other headings if needed but they gave examples. Safer to include it under a heading like "Additional Information" but that's not in examples. Might be considered adding a thin section. However the instruction: "Prefer a few substantive sections over many thin ones." Adding a hiring process section might be thin but still substantive. Could we embed that info in Requirements or Benefits? Not really. Could embed in About the role? Might be okay to add a

    after Benefits before Pay. We need to preserve ALL substantive information. So we must include that hiring process detail somewhere. We could add a

    Hiring Process

    but that's not in the examples. However the instruction didn't say we cannot use other headings; it just gave examples. I'd say it's acceptable to add a heading for Hiring Process. But to be