Graduate Electrical Engineer- 2027
Mott MacDonald · The Woodlands, TX · 1 wk ago
EngineeringFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title. No Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The initial paragraph about Mott MacDonald, mission, etc. Could be considered "About the role". We'll include a
.
Requirements: "To be considered for this 2027 opportunity, here’s what you’ll need:" then bullet list: Bachelor’s or Master’s Degree in Electrical Engineering, or related field Preferred: successful completion of EIT exam, or ability to take EIT exam within 12 months (only for engineering positions) 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 "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.
Qualifications: Might overlap with Requirements; but we can treat Requirements as qualifications. However we have separate headings for Requirements and Qualifications. The posting doesn't have a separate "Qualifications" section distinct from Requirements; but we could treat the degree etc as Qualifications and the skills as Skills. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But the instruction says use headings for those if present. Since the posting doesn't explicitly label them, we need to decide if we should create both. The posting includes both educational/degree requirements and skills. Could map: Qualifications = education, certifications; Skills = abilities. We'll create Qualifications heading for degree and EIT preference. Skills heading for the list of skills (creative thinking, communication, resilient mindset, relationship building, collaborative spirit). Also include work authorization maybe under Requirements? But we could put under Qualifications as well. However we need to avoid duplication.
Better: Use Requirements for the bullet list starting with "To be considered..." which includes degree, EIT, interest, etc. Then Skills for the list of skills (creative thinking, communication, resilient mindset, ability to build relationships, collaborative spirit). But the bullet list already includes those skills. Might be duplication. Let's examine the bullet list:
- Bachelor’s or Master’s Degree in Electrical Engineering, or related field
- Preferred: successful completion of EIT exam, or ability to take EIT exam within 12 months (only for engineering positions)
- 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
Thus the list includes both qualifications and skills. If we split, we might duplicate content. Better to have one section, maybe "Requirements" covering all. Then we could omit Qualifications and Skills headings to avoid thin sections. But the instruction says use those headings if present; they are not explicitly present as separate headings, but we could still create them if we have content. However "Prefer a few substantive sections over many thin ones." So better to have fewer sections. We'll combine into Requirements (or Qualifications). Which heading is more appropriate? The list includes education, experience, skills. Could be "Requirements". We'll use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title. No Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: The initial paragraph about Mott MacDonald, mission, etc. Could be considered "About the role". We'll include a About the role
with paragraphs summarizing but must preserve all substantive info, not invent or summarize away detail. However we can keep the prose as is, but we need to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the content but can rephrase? Probably we should keep the original sentences but we can combine into paragraphs. Must not omit any substantive info. That's tricky: we need to keep all details but can format.
We need to decide what constitutes substantive info vs boilerplate. Boilerplate includes cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also "Equal opportunity is the law..." etc is EEO boilerplate, should be removed. Also "Applicants must be authorized to work for any employer in the US..." maybe not boilerplate? It's a requirement about work authorization; could be part of Requirements. We'll keep that.
Also "Location(s): The Woodlands, TX, US Contract Type: Regular (US only) Work Pattern: Full Time Market: Energy Discipline: Electrical Job Ref: 16606 Recruiter Contact: Coryanna DeGannes" - location info is substantive; we need to include location maybe in a short paragraph. Not a heading.
Also "Benefits & Rewards" section: we need Benefits heading.
Also "Individual pay is determined based on several factors such as work location, education, experience, and unique skills." That's Pay info but vague; we should not create Pay section unless posting actually states them. It does state that pay is determined based on factors, but not specific numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (individual pay determined based on factors). That's still stating something about pay, albeit not specific. Should we include Pay section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay, so we could include a Pay section with that sentence. However also "Prefer a few substantive sections over many thin ones." Might be better to incorporate pay info into Benefits or About? But they said to use headings for Benefits, Pay, Schedule if present. Since there is a statement about pay, we can include a Pay section with that sentence.
Schedule: The posting mentions hybrid working policy, must be able to reliably commute, and "Collaboration at Our Core" describes hybrid approach: minimum three days per week in office. That's schedule info. So we can include Schedule section with that.
Now Responsibilities: list of duties: "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'll put each as
Requirements
and put the list. Now Benefits: we have a paragraph about benefits. We'll putBenefits
with that paragraph. Pay: we have sentence about individual pay determined based on factors. We'll putPay
with that sentence. Schedule: we have hybrid policy: must be able to reliably commute, minimum three days per week in office. We'll putSchedule
with that info. About the role: we have initial paragraphs describing Mott MacDonald, Blueprint program, etc. We'll putAbout the role
with those paragraphs. Now we need to remove boilerplate: EEO statements, "Equal opportunity is the law..." etc, "English versionSpanish versionChinese version", "All qualified applicants will receive consideration..." etc. Also "Location(s): The Woodlands, TX, US Contract Type: Regular (US only) Work Pattern: Full Time Market: Energy Discipline: Electrical Job Ref: 16606 Recruiter Contact: Coryanna DeGannes" - we need to keep location info but not as heading. We'll incorporate location into About or maybe a short paragraph after About. We'll keep location as a short p. Also "Applicants must be authorized to work for any employer in the US, as Mott MacDonald is unable to provide sponsorship at this time." We'll keep that in Requirements. Now we need to ensure we don't repeat job title. Not needed. Now produce HTML fragment: only the elements, no or . We'll output something like:About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
...
Pay
...
Schedule
...
We need to ensure we preserve all substantive info. Let's extract the About the role content. Original text: "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." Then later: "Build your career while helping shape what comes next. At Mott MacDonald, you will be encouraged to explore your potential, share your ideas, and make meaningful contributions from the start. Learning and development experiences that support your career goalsDedicated mentorship and guidance from experienced professionalsEmployee Resource Groups that help build connection and communityMeaningful opportunities to learn, contribute, and grow every day Bring your curiosity, compassion, and drive to make a difference. If you are ready to join a collaborative engineering consultancy where your perspective is valued, your development is supported, and you are empowered to lead with integrity, we would love to hear from you." We need to preserve all that. There's a missing space between "goalsDedicated" etc. We'll keep as is but maybe add space for readability? But we must not invent or summarize away detail; we can keep the exact text. However we can fix obvious typos? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Fixing missing space could be considered altering but not inventing. Safer to keep as is. We'll combine into a couple paragraphs. Now Responsibilities list: we need to keep each item exactly as in posting: "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". Ensure we keep punctuation. Now Requirements list: we need to include all bullet items exactly. Let's list them: - Bachelor’s or Master’s Degree in Electrical Engineering, or related field - Preferred: successful completion of EIT exam, or ability to take EIT exam within 12 months (only for engineering positions) - Demonstrated interest in your chosen field through previous internships, volunteering opportunities, or organization memberships - Creative thinking skills, with a methodical and pragmatic approach