Graduate Advisory Specialist - 2027

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Intro paragraph about Mott MacDonald, purpose, etc. Could be "About the role" or maybe "About the role" is not explicit but we can treat as overview. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections accordingly. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove lines like "Equal opportunity is the law..." etc. Also remove "Applicants must be authorized to work for any employer in the US..." maybe that's a requirement? It's a requirement about work authorization; could be part of Requirements. But it's also a legal statement; but it's a requirement. The instruction says remove EEO/equal-opportunity boilerplate. The line about authorized to work is not EEO but a requirement; we can keep it under Requirements. We need to include sections only when posting has real specific content. Let's extract: About the role: The initial paragraphs describing the role, purpose, Blueprint program, etc. That's substantive. Responsibilities: list: "Your responsibilities may include: Designing engineering solutions Conducting and monitoring site inspections Joining project and client meetings Refining technical designs and documentation Analyzing reports and specifications Exploring project and client management Leveraging digital tools and innovation Driving sustainable outcomes Building connections through our Early Career Professionals Network" We need to put each as

. Requirements: "To be considered for this 2027 opportunity, here’s what you’ll need:" then bullet list: Bachelor’s or Master’s Degree in Construction Management, or related field; Preferred: successful completion of EIT exam, or ability to take EIT exam within 12 months; Demonstrated interest in your chosen field through previous internships, volunteering opportunities, or organization memberships; Creative thinking skills, with a methodical and pragmatic approach to problem solving; Proficient communication and presentation skills to engage confidently with clients and colleagues; Resilient, solution-oriented mindset, with a focus on continuous growth and delivering value; Ability to build and maintain relationships and rapport with internal and external stakeholders; Collaborative spirit and commitment to teamwork. Also location: "This position is located in Seattle, WA. You must be able to reliably commute to our office in this location, per our hybrid working policy." Could be part of Requirements or maybe a separate section like Location? Not in list of allowed headings. Could fold into Requirements or maybe a short p under About the role? Probably include as part of Requirements (or maybe a separate "Location" not allowed). We'll include in Requirements as a bullet. Qualifications: Might overlap with Requirements. The posting doesn't have a separate Qualifications section besides the requirements. Could we create Qualifications section with same content? Might be duplicate. Better to not create Qualifications if no distinct content. The instruction: include a section ONLY when the posting has real, specific content for it. So we should not create Qualifications if not distinct. Skills: Could be extracted from requirements: Creative thinking skills, communication, etc. But those are already in Requirements. Could we create Skills section? Might be redundant. Better to keep only one section for requirements/skills. The allowed headings include Skills, but we need to decide. The posting includes "Creative thinking skills... Proficient communication and presentation skills... Resilient, solution-oriented mindset... Ability to build and maintain relationships... Collaborative spirit". Those are skills. Could create a Skills section with those bullet points, and Requirements section for education and experience. But we must not invent or summarize away detail; we can split. Let's see: The posting says "To be considered for this 2027 opportunity, here’s what you’ll need:" then list includes degree, EIT, demonstrated interest, creative thinking skills, communication skills, resilient mindset, ability to build relationships, collaborative spirit. So we could separate into Requirements (education, EIT, demonstrated interest) and Skills (the rest). That seems reasonable. Benefits: There's a "Benefits & Rewards" section with details: stake and voice, personal and group performance bonuses, comprehensive benefits package: medical, dental, vision, FSA/HSA, company-paid life insurance, short-term and long-term disability, competitive 401(k) with company matching, paid time off, paid holidays, caregiver leave, employee referral bonuses, professional registration and membership reimbursements, tuition assistance. Also maybe other benefits. So we should include Benefits section. Pay: "The expected salary for this position is $69,000 - $85,000 Individual pay is determined based on several factors such as work location, education, experience, and unique skills." So we include Pay section. Schedule: There's "Collaboration at Our Core" describing hybrid approach: minimum three days per week in the office. That's schedule info. So we can include Schedule section. We must not include boilerplate like EEO, etc. Also remove "Location(s): Seattle, WA, US Contract Type: Regular (US only) Work Pattern: Full Time Market: Various Discipline: Project programme and commercial management Job Ref: 17166 Recruiter Contact: Faiqa Shahid". That's metadata; we can drop or fold into short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include a short p at end with location and contract type maybe. But we already have location in Requirements. Could include a short p after sections: "

Location: Seattle, WA. Contract type: Regular (US only). Work pattern: Full Time.

" That's minor metadata. We must not repeat the job title as a heading. The job title is not given explicitly; but we can ignore. Now produce HTML fragment:

About the role

... paragraphs ...

We need to preserve all substantive information from the intro paragraphs. Let's copy them but remove any boilerplate like "At Mott MacDonald, we believe engineering is about more than solving problems; it is about shaping a future that is inclusive, resilient, and sustainable. As we expand across the US and Canada, we are inviting passionate individuals to join a purpose-driven journey powered by brilliant people. As trusted consultants, we partner with clients to solve complex challenges, deliver sustainable solutions, and create lasting impact for the communities they serve. From the moment you join our team, you will work alongside experienced engineering consultants, project managers, subject matter experts, mentors, and peers who champion integrity, teamwork, excellence, and innovation. You will build your technical skills while developing the mindset of a consultant; contributing to meaningful work, collaborating to achieve better outcomes, and growing with support every step of the way. As a participant in Blueprint, our new graduate program, you will embark on a structured three-year development journey designed in collaboration with an award-winning learning provider. The program combines immersive learning experiences with required development sessions to build the professional, commercial, and personal effectiveness skills graduates need to thrive and lead in our business." That's all substantive. Then responsibilities list. Then Requirements section: maybe split into Education/Experience and Skills. Let's do:

Requirements

• Bachelor’s or Master’s Degree in Construction Management, or related field
• Preferred: successful completion of EIT exam, or ability to take EIT exam within 12 months
• Demonstrated interest in your chosen field through previous internships, volunteering opportunities, or organization memberships

Skills

• Creative thinking skills, with a methodical and pragmatic approach to problem solving
• Proficient communication and presentation skills to engage confidently with clients and colleagues
• Resilient, solution-oriented mindset, with a focus on continuous growth and delivering value
• Ability to build and maintain relationships and rapport with internal and external stakeholders
• Collaborative spirit and commitment to teamwork

But we also have location and commuting requirement. Could add to Requirements as a bullet: "Located in Seattle, WA; must be able to reliably commute to the office per hybrid working policy." Add that bullet. Now Benefits section:

Benefits

• Personal and group performance bonuses
• Comprehensive benefits package: medical, dental, and vision coverage
• FSA and HSA accounts
• Company-paid life insurance
• Short-term and long-term disability coverage
• Competitive 401(k) plan with company matching
• Paid time off and paid holidays
• Caregiver leave
• Employee referral bonuses
• Professional registration and membership reimbursements
• Tuition assistance for continued learning and career development

Pay section:

Pay

The expected salary for this position is $69,000 - $85,000. Individual pay is determined based on work location, education, experience, and unique skills.

Schedule section:

Schedule

Hybrid working policy with a minimum of three days per week in the office; collaboration-focused in‑office culture.

Now minor metadata p: maybe include location and contract type again? Already location in Requirements. Could add a short p: "

Location: Seattle, WA. Contract type: Regular (US only). Work pattern: Full Time.

" But that duplicates location. Might be okay as minor metadata. But we already have location in Requirements; duplication may be okay but we should avoid duplication? The instruction: remove duplicated lines. So we should not duplicate location. So we can omit that p, or we can include only contract type and work pattern not already mentioned. Contract type and work pattern not mentioned elsewhere. So we can add a short p: "

Contract type: Regular (US only). Work pattern: Full Time.

" Now ensure we didn't include any boilerplate like EEO, etc. We removed those lines. Check for any leftover boilerplate: The text included "Equal opportunity is the law..." etc. We removed. Also removed "Applicants must be authorized to work for any employer in the US, as Mott MacDonald is unable to provide sponsorship at this time." That's a requirement about work authorization; we might want to keep it under Requirements. It's substantive. Let's add a bullet: "Must be authorized to work for any employer in the US (no sponsorship available)." Add to Requirements list. Now check if any other content: "Build your career while helping shape what comes next..." etc. That's more promotional; could be part of About the role or maybe a separate section? It's more about encouragement. Could be included in About the role paragraph. We'll incorporate into About the role after the program description. Let's craft About the role paragraph(s) combining all introductory paragraphs plus the later motivational paragraphs. We'll produce:

About the role

At Mott MacDonald, we believe engineering is about more than solving problems; it is about shaping a future that is inclusive, resilient, and sustainable. As we expand across the US and Canada, we are inviting passionate individuals to join a purpose-driven journey powered by brilliant people. As trusted consultants, we partner with clients to solve complex challenges, deliver sustainable solutions, and create lasting impact for the communities they serve. From the moment you join our team, you will work alongside experienced engineering consultants, project managers, subject matter experts, mentors, and peers who champion integrity, teamwork, excellence, and innovation. You will build your technical skills while developing the