Expression of Interest for Engineering Graduate- LA Tech

We need to output HTML fragment with sections: About Us? Actually "About Us" is a section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings like "About Us", "Purpose", "Responsibilities", "Qualifications", "What We Offer", "Moving forward together"? But we should only include sections when posting has real specific content. The content includes "About Us", "Purpose", "Responsibilities", "Qualifications", "What We Offer", "Moving forward together". However "Moving forward together" is more about culture/values; could be considered a section but not in the list of allowed headings. The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings where applicable. The posting includes "About Us" which is similar to "About the role"? Not exactly. Could treat "About Us" as "About the role"? Might be okay. But we also have "Purpose" which is not in list; maybe we can omit or incorporate into About the role? The instruction: "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 which sections to include based on content. We have substantive content for: - About Us (company overview) - Purpose (program description) - Responsibilities (list) - Qualifications (list) - What We Offer (benefits/program details) - Moving forward together (culture/values) maybe could be considered "Benefits"? Not exactly. We could map: - About Us ->

About Us

(or About the role) - Purpose -> maybe incorporate into About Us? Could be separate

Program Purpose

but not in list. Might be okay to use

Purpose

as heading. - Responsibilities ->

Responsibilities

with

• - Qualifications ->

  Qualifications

  with
  • (though qualifications includes paragraphs and bullet-like lines; we can convert each line to
  • ) - What We Offer -> could be

    Benefits

    (since it's about what they offer). The content includes program details, mentorship, etc. That fits Benefits. - Moving forward together -> maybe not needed; could be omitted or included as part of Benefits? It's about culture/values; maybe we can include as

    Culture & Values

    but not in list. Safer to omit if not matching allowed headings? The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. I'd include only those that map. Thus sections: About Us (or About the role), Purpose (maybe not needed), Responsibilities, Qualifications, Benefits. We need to preserve all substantive information, not invent or summarize away detail. Use

    for prose,

    • for lists. We must not repeat job title as heading (not present). No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment. Let's extract content: About Us paragraph: "Worley is a global company of energy, chemicals and resources experts headquartered in Australia. We partner with our customers to deliver projects and create value across the life of their assets. We specialize in consulting, engineering, procurement and construction across the project lifecycle, with services extending through to operations and decommissioning. Leveraging extensive experience and AI-enabled delivery, we support customers in navigating complexity as they meet today’s needs and transition to more sustainable solutions." Purpose paragraph: "The Worley Graduate Development Rotational Program is designed to accelerate the growth of high-potential early career professionals through structured, hands-on experience across multiple areas of our business. The program spans 2 years and includes two structured rotations, providing exposure across engineering and project delivery, project services, and field operations. Throughout the program, participants may complete rotations in a mix of office and field-based environments. This approach provides a holistic understanding of how complex projects are executed from concept through completion. Working under the guidance of experienced professionals and mentors, graduates apply their academic knowledge in real-world settings while building skills across disciplines. Each rotation is intentionally designed to develop technical expertise, business and commercial acumen, project controls literacy, and an understanding of risk, safety, and stakeholder and client management. Through exposure to diverse teams, projects, and industries, participants gain insight into how cross-functional collaboration drives successful project outcomes. The program emphasizes practical experience, continuous learning, and leadership development; equipping graduates with the foundational skills and perspective needed to thrive in dynamic, project-based environments and build a long-term career with Worley." Responsibilities list: bullet points after "Responsibilities – Graduate Rotational Program". Each line starts with a bold? Actually they are sentences. We'll convert each line to
    • . Need to preserve all. List: - Support the delivery of projects across Engineering, Project Services, and Construction to meet company, customer, and regulatory requirements, on time, within budget, and to required quality standards. - Complete structured rotations across key functions, gaining practical experience across the full project lifecycle from concept through execution and handover. - Contribute to discipline specific activities during each rotation, which may include: Engineering: Supporting technical studies, design development, calculations, and preparation of engineering deliverables. Project Services: Assisting with project controls activities such as scheduling, cost tracking, estimating, and reporting. Construction / Field Services: Supporting field execution, site coordination, commissioning activities, and contractor oversight. - Collaborate with multidisciplinary teams, building strong working relationships with engineers, project managers, field personnel, and other stakeholders. - Assist in the preparation and review of project documentation, including reports, specifications, schedules, and vendor or contractor deliverables. - Participate in project meetings, design reviews, and site activities to ensure alignment with project objectives, safety requirements, and quality standards. - Identify issues or risks within assigned tasks, propose solutions, and escalate as appropriate. - Apply and promote health, safety, environmental, and quality standards across all activities, including field-based assignments. - Engage in structured learning, mentorship, and regular performance feedback to support development across technical, commercial, and leadership capabilities. - Demonstrate adaptability, accountability, and a proactive approach to learning in a fast-paced project environment. - Undertake other responsibilities as required to support project and business needs. Note there is a nested list under "Contribute to discipline specific activities during each rotation, which may include:" with three sub-items. We need to preserve that structure. Could make a
      inside
      • for that. Qualifications section: includes paragraphs and bullet-like lines. Content: "What You Will Bring Technical and Industry Experience Internship, co-op, or early work experience in engineering, project delivery, construction, or a related technical/operational environment (preferred). Foundational technical knowledge aligned to your field of study (e.g., engineering, project management, construction, supply chain, environmental, or related disciplines). Demonstrated ability to apply academic learning to real-world problems through coursework, projects, or practical job experience. Exposure to industry tools, systems, or software relevant to your discipline (e.g., design, analysis, project controls, data, or planning tools). Proficiency with the Microsoft Office Suite (Word, Excel, PowerPoint, Outlook). Strong analytical and problem-solving capabilities, with a willingness to learn and adapt across multiple functions. Effective communication and teamwork skills, with the ability to collaborate in diverse, cross-functional environments. Education – Qualifications, Accreditation, Training Bachelor’s degree in a relevant discipline such as Engineering, Project Management, Construction Management, Supply Chain, Environmental, or a related field from a recognized institution. Academic focus aligned to one or more areas of the Engineering, Procurement, Construction Management project lifecycle (e.g., engineering design, project delivery, project controls, supply chain, construction, or operations). Progress toward, or eligibility for, relevant professional certifications or registrations (e.g., Engineer-in-Training (EIT), Professional Engineer (PE), or discipline-specific certifications), where applicable. Demonstrated commitment to continuous learning and professional development." We can treat each line after headings as
      • . The headings "Technical and Industry Experience" and "Education – Qualifications, Accreditation, Training" could be inside
      • or separate

        . But we need to preserve all info; we can make a

        with
        • items, and within some
        • we can include for subheadings. What We Offer section: "What We Offer A structured 2-year rotational program where our early careers programs are designed to grow your skills, expand your thinking, and connect you with a network of passionate people. Meaningful, hands-on experience across engineering and project delivery, project services, and construction and field environments. Exposure to high-impact projects and global teams, building a deep understanding of how complex projects are delivered. Development of core skills that matter such as technical excellence, project controls, business and commercial awareness, and leadership. A connected experience through Worley’s global graduate community, mentorship, and ongoing learning. A clear path forward into a long-term career with Worley, aligned to your strengths and our future needs." We can make
          • for each. Moving forward together section: maybe we can omit as not in allowed headings. But it's substantive content about culture. Could be considered "Benefits"? Not really. Safer to include as a separate section with heading

            Culture & Values

            but not in list. The instruction says "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are those. I'd include it as

            Culture & Values

            to preserve content. However the instruction also says "Prefer a few substantive sections over many thin ones." So maybe we can merge culture into Benefits? But it's distinct. Given the instruction to include a section ONLY when posting has real specific content for it, we have that content. So we should include it. Use a heading like

            Culture & Values

            . That seems okay. Now produce HTML. Structure:

            About Us

            ...

            Purpose

            ...

            Responsibilities

            • Support the delivery of projects across Engineering, Project Services, and Construction to meet company, customer, and regulatory requirements, on time, within budget, and to required quality standards.
            • Complete structured rotations across key functions, gaining practical experience across the full project lifecycle from concept through execution and handover.
            • Contribute to discipline specific activities during each rotation, which may include:
              • Engineering: Supporting technical studies, design development, calculations, and preparation of engineering deliverables.
              • Project Services: Assisting with project controls activities such as scheduling, cost tracking, estimating, and reporting.
              • Construction / Field Services: Supporting field execution, site coordination, commissioning activities, and contractor oversight.
            • Collaborate with multidisciplinary teams, building strong working relationships with engineers, project managers, field personnel, and other stakeholders.
            • Assist in the preparation and review of project documentation, including reports, specifications, schedules