University of Michigan ECRC Department Career Day

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Let's parse posting. Content: - Title: University of Michigan Students & Recent Graduates Electrical | Mechanical | Structural | CAD - The Opportunity: description. - Position Summary: description. - Tell Us What Interests You: with subcategories: Electrical Engineering Potential Areas Of Interest..., Mechanical..., Structural..., CAD/BIM... - Qualifications: bullet list. - Life at Tetra Tech: The Perks Of Working At Tetra Tech Include: list of benefits. - About Tetra Tech: description. - Additional Information: Organization: 200 IEW (maybe minor metadata). We need to map to sections: About the role (maybe Position Summary). Responsibilities: not explicitly listed; maybe not present. Requirements: maybe Qualifications. Skills: maybe not explicit. Benefits: The Perks list. Pay: not mentioned. Schedule: not mentioned. Thus we include sections: About the role (Position Summary), Requirements (Qualifications), Benefits (Perks). Possibly also Skills? Not explicit. Could include "Skills" from Qualifications but better to keep as Requirements. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information. So we need to include the content from The Opportunity, Position Summary, Tell Us What Interests You (list of areas), Qualifications bullet list, Benefits list, About Tetra Tech description, Additional Information maybe as a short p. We must not invent or summarize away detail. Must preserve all specifics. We need to format using

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which content is list vs prose. The Opportunity: prose. Position Summary: prose. Tell Us What Interests You: includes heading and then bullet-like list of areas per discipline. Could be formatted as

  • each area? The text: "Electrical Engineering Potential Areas Of Interest May Include: Power distributionLow- and medium-voltage systemsMotor controlInstrumentation and controlsSCADA infrastructureLighting and groundingElectrical equipment and facility design". It's a run-on list without commas. We need to preserve all detail; we could split by commas? But original lacks commas. Safer to keep as a single sentence? But we need to use
    • for any list of duties/requirements/benefits. This is a list of potential areas of interest; could treat as list. However the original text is not clearly separated; we could still make each item as
    • but we need to infer separation. Might be risky to invent separation. Better to keep as prose

      preserving the exact text. The instruction: "Use

      • for any list of duties/requirements/benefits". This is a list of potential areas of interest, which could be considered a list of requirements? Not exactly duties/requirements/benefits. It's more like description. Safer to keep as

        . Qualifications: bullet list: "Candidates should have: Interest in developing a career in engineering, design, water, wastewater, utilities, or infrastructureStrong technical and problem-solving skillsAttention to detailAbility to work collaboratively with engineers, designers, and project teamsEffective written and verbal communication skillsInterest in continuing to develop technical expertise within their chosen discipline For engineering students and graduates, completion of the FE exam or interest in pursuing EIT certification is encouraged where applicable." Again it's a run-on list without punctuation. We could keep as

        preserving exact text. Or we could split into items but risk altering. Safer to keep as

        . Benefits: "The Perks Of Working At Tetra Tech Include: Comprehensive and market-competitive benefits.Merit-based financial rewards.Flexibility and company-wide commitment to work/life balance.Collaborative team atmosphere that values the contributions of all employees.Learning and development opportunities for ongoing professional growth." Again run-on. Could keep as

        or split into

        • . Since it's a list of benefits, we could treat as list. The instruction says use
          • for any list of duties/requirements/benefits. So we should make a
            • for benefits. However we need to preserve all detail; we can split by periods? The text uses periods to separate items: "Comprehensive and market-competitive benefits.Merit-based financial rewards.Flexibility and company-wide commitment to work/life balance.Collaborative team atmosphere that values the contributions of all employees.Learning and development opportunities for ongoing professional growth." We can split on '.' and trim. That yields items. That seems reasonable and preserves detail. About Tetra Tech: prose. Additional Information: "Organization: 200 IEW" - minor metadata; we can fold into short

              or drop. Probably include as

              . We must not include EEO boilerplate etc. Remove that. Now produce HTML fragment. Structure:

              About the role

              ... (The Opportunity + Position Summary? Actually About the role could combine The Opportunity and Position Summary. But we need to avoid duplication. Could put both in same

              or separate

              s. The instruction: use

              for prose. So we can have multiple

              under section. We need to include all substantive info. Let's parse: The Opportunity paragraph: "University of Michigan Students & Recent Graduates Electrical | Mechanical | Structural | CAD The Opportunity Tetra Tech is looking to connect with University of Michigan students and recent graduates interested in launching their careers across engineering, infrastructure, facilities, utilities, and multidisciplinary design. This posting gives you the opportunity to tell us more about your technical interests, academic background, preferred career path, and the types of engineering challenges you would like to solve. Our engineers work across disciplines to support the design, analysis, and delivery of critical infrastructure and facilities. Projects may involve electrical systems, mechanical equipment, structural systems, civil infrastructure, utilities, treatment facilities, transportation-related infrastructure, industrial facilities, and other complex engineering environments. Whether you already know the technical specialty you want to pursue or are still exploring different engineering paths, we want to learn more about what interests you." Position Summary: "This posting serves as an early-career talent pipeline for University of Michigan students and recent graduates interested in engineering opportunities with Tetra Tech. Our Recruiting team will review your academic background, technical experience, and career interests against available and upcoming positions. If you are selected to move forward, a member of our Recruiting team will contact you with information about the specific Tetra Tech position or positions that may align with your experience and interests. At that time, we will provide additional details regarding the role, including responsibilities, qualifications, office location, work arrangement, and project team. Submission to this talent pipeline does not represent an application to one specific position or guarantee an interview or employment." Tell Us What Interests You: heading then list of areas. We could make a section "Areas of Interest" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. We can put the "Tell Us What Interests You" content under About the role or Requirements? Probably Under About the role as description. Or we could create a section "Requirements" for Qualifications, and "Skills" maybe for areas of interest? But better to follow instruction: only use those headings if we have real specific content. We have content for About the role (The Opportunity + Position Summary + Tell Us What Interests You). We have content for Requirements (maybe Qualifications). We have content for Benefits (Perks). We have content for Skills? Not explicit. Could treat Qualifications as Requirements, and Skills maybe not needed. Thus we will have sections:

              About the role

              ... (combine The Opportunity, Position Summary, Tell Us What Interests You)

              Requirements

              ... (Qualifications)

              Benefits

              • Comprehensive and market-competitive benefits
              • Merit-based financial rewards
              • Flexibility and company-wide commitment to work/life balance
              • Collaborative team atmosphere that values the contributions of all employees
              • Learning and development opportunities for ongoing professional growth

              About Tetra Tech paragraph.

              Organization: 200 IEW

              We must not include extra headings like About Tetra Tech; but we can include its prose under About the role? No, it's separate. Could we add another

              like "About Tetra Tech"? Not in allowed list. The instruction says use

              for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should only use those headings. So we should not create a heading for About Tetra Tech. Instead we can incorporate its prose under About the role? But that would mix company description with role description. However we could put it as a

              without a heading; that's allowed. 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 says use

              for section headings (e.g., those). It might be okay to use other headings but they gave examples. Safer to stick to those headings only. So we will not add a heading for About Tetra Tech; we will just include its description as a

              after the Benefits section, maybe under a generic heading? But we need a heading for each section; we could put it under About the role as well, but that may be mixing. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide if About Tetra Tech content qualifies for a section. It does not match any of the allowed headings exactly, but we could treat it as "About the role"? Not really. Could we treat it as "Requirements"? No. Could we treat it as "Skills"? No. Could we treat it as "Benefits"? No. Could we treat it as "Pay"/"Schedule"? No. Thus maybe we should not include a heading for About Tetra Tech; we can just include its prose as a

              without a heading. The instruction didn't say every

              must be under a heading; just that we should use

              for section headings. So we can have

              elements not under any heading? Probably okay. But typical HTML fragment would have headings and paragraphs. We'll just put the About Tetra Tech paragraph after Benefits, without a heading. Similarly, Additional Information "Organization: 200 IEW" can be a

              . Now we need to ensure we preserve all substantive information. Let's extract exact text. The Opportunity paragraph: Let's copy exactly from posting: "University of Michigan Students & Recent Graduates Electrical | Mechanical | Structural | CAD The Opportunity Tetra Tech is looking to connect with University of Michigan students and recent graduates interested in launching their careers across engineering, infrastructure, facilities, utilities, and multidisciplinary design. This posting gives you the opportunity to tell us more about your technical interests, academic background, preferred career path, and the types of engineering challenges you would like to solve. Our engineers work across disciplines to support the design, analysis, and delivery of critical infrastructure and facilities. Projects may involve electrical systems, mechanical equipment, structural systems, civil infrastructure, utilities, treatment facilities, transportation-related infrastructure, industrial facilities, and other complex engineering environments. Whether you already know the technical specialty you want to pursue or are still exploring different engineering paths, we want to learn more about what interests you."