Senior Engineer, Engineering Governance

We need to output HTML fragment with sections: About the role? The posting includes "At Enbridge, we are committed..." That's about the company, maybe "About the role" or "About Enbridge". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract sections: About the role (maybe "About Enbridge" or "About the role"? The posting begins: "At Enbridge, we are committed to delivering safe, reliable energy while driving financial excellence and innovation. We are seeking a Senior Engineer, Engineering Governance to join our team! In this role, you will provide subject matter expertise..." That's about the role. So we can have

  About the role

  with paragraph(s) describing role. Responsibilities: The "What You Will Do" bullet list. We'll create

  Responsibilities

  with
  • each bullet. Requirements/Qualifications: The "Who You Are" bullet list includes education, experience, registration, etc. Could be split into Requirements and Qualifications but we can combine? The instruction says prefer a few substantive sections over many thin ones. We could have

    Qualifications

    with list. Or separate Requirements and Qualifications if both have content. The "Who You Are" includes both qualifications (degree, experience, registration) and skills (ability to build relationships, prioritize, etc). Could split: Requirements (education, experience, registration) and Skills (abilities). But we can also just have one Qualifications section with all bullet points. However they said use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. It does have qualifications (degree, experience, registration). It also has skills (abilities). It also has Benefits described. It also has Salary range (Pay). It does not have explicit Schedule (though mentions FlexWork hybrid model). That could be considered Schedule? The posting mentions "Enbridge’s FlexWork hybrid work model offers eligible employees at the Manager level and below the option to work from home on Wednesdays and Fridays, opt for a compressed workweek schedule, or have flexible start and end times." That's schedule/flexibility info. So we could include a Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO statement, application instructions, etc. Also remove "Posting End Date October 05, 2026 Employee Type Regular-Full time Union/Non This is a non-union position". That's metadata; we can fold into a short

    or drop. Probably drop it as not substantive? It's metadata about posting; but we can include a short

    with that info? 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

    with that metadata at top. But they also say "Prefer a few substantive sections over many thin ones." Might be okay to include a short paragraph for metadata. However they also said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The metadata lines are not exactly boilerplate but could be considered minor metadata. I'd include a short

    at start: "Posting End Date: October 05, 2026. Employee Type: Regular-Full time. Union/Non: This is a non-union position." That's fine. Now we need to preserve all substantive information. Let's extract. About the role paragraph(s): - "At Enbridge, we are committed to delivering safe, reliable energy while driving financial excellence and innovation. We are seeking a Senior Engineer, Engineering Governance to join our team! In this role, you will provide subject matter expertise in the development and implementation of engineering governance that standardizes how projects are executed across our business units and regional locations in Canada and the United States. You will lead the creation and continuous improvement of governance documents, collaborate with diverse project stakeholders, facilitate training, and promote a consistent, fit-for-purpose approach throughout the project lifecycle. Bring your project expertise and passion for continuous improvement to help shape a more consistent and effective approach to project execution across Enbridge!" - Also note: "Note This position is not eligible for relocation / international relocation." That's a note about relocation eligibility. Should we include? It's substantive. Could be part of About the role or a separate note. We'll include as a sentence in About the role paragraph. Responsibilities (What You Will Do): List: - Establish and maintain governance for engineering activities throughout the project lifecycle across Enbridge business units and locations in Canada and the United States. - Develop, update, and harmonize procedures, standards, guides, deliverable templates, and other governance documents that support consistent project execution. - Identify opportunities to streamline workflows, optimize processes, and implement practical, fit-for-purpose governance solutions. - Represent the Engineering Management Office at workshops, business initiatives, and stakeholder reviews, leading discussions and making informed decisions on proposed changes. - Facilitate virtual and in-person training and awareness sessions for new or updated governance documents, tools, and applications. - Collaborate with project teams and functional partners across procurement, contracts, project management, quality, construction, and commissioning while mentoring peers and communicating complex information to technical and non-technical audiences. Qualifications (Who You Are): List: - Bachelor’s degree in engineering, preferably Pipeline, Civil, or Electrical Engineering from an accredited university. - 6+ years of oil and gas industry experience, including work on projects of varying types, scopes, and sizes. - Registered member with APEGA as P. Eng. in the Province of Alberta. If in the US, preference is to have a PE. - Good understanding the complete project lifecycle, engineering deliverables, and the interfaces between engineering and other project functions. - Ability to build productive relationships with stakeholders across business units and effectively facilitate reviews, workshops, training sessions, and decision-making discussions. - Effectively prioritize competing responsibilities, manage multiple assignments, meet tight deadlines, and take ownership of your work with minimal supervision. - Demonstrate strong verbal, written, presentation, and documentation skills, with the ability to explain complex issues clearly to technical and non-technical audiences and proficiency using Microsoft Office applications. Skills? The above includes abilities; but we could separate Skills as a section for abilities like "Ability to build productive relationships..." etc. However we already have them in Qualifications. To avoid thin sections, we could keep Qualifications only. Working Conditions: includes office environment, minimal travel, passport required, physical requirements, mental requirements. Could be a section "Working Conditions". But not in the list of headings given; but we could still use

    Working Conditions

    if we want. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. We could add other headings if needed. However they said "Prefer a few substantive sections over many thin ones." So maybe we incorporate working conditions into About the role or Qualifications? Might be better to have a separate section "Working Conditions" as it's substantive. But we need to decide. Benefits: described in detail. We'll have

    Benefits

    with
    • each benefit. Pay: Salary range: "$100,000 – $140,000/year USD for U.S. locations based upon the candidate’s experience, skills, and internal equity." Also note about compensation policies. We'll have

      Pay

      with paragraph. Schedule: FlexWork hybrid work model details. We'll have

      Schedule

      with paragraph. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We need to remove EEO boilerplate at end: "At Enbridge, we are dedicated to our core value of Inclusion..." etc. Remove. Also remove "Information For Applicants" etc. Now construct HTML. Start with maybe a

      for metadata. Then

      About the role

      with

      containing the paragraphs. Then

      Responsibilities

      with
      • ... Then

        Qualifications

        with
        • ... Then

          Benefits

          with
          • ... Then

            Pay

            with

            ... Then

            Schedule

            with

            ... Optionally

            Working Conditions

            if we want. But we might incorporate physical/mental requirements into Qualifications? Might be better to have Working Conditions. But we already have many sections; maybe we can combine Working Conditions into About the role? However it's quite detailed. The instruction says prefer a few substantive sections over many thin ones. We have About, Responsibilities, Qualifications, Benefits, Pay, Schedule = 6 sections. Adding Working Conditions makes 7. Could be okay but maybe we can drop Working Conditions and fold into About the role or Qualifications. However physical requirements and mental requirements are substantive and not covered elsewhere. Could be placed under About the role as additional paragraph. Let's do that: after the About role paragraph(s), add another paragraph about working conditions. Thus we have About the role covering role description, note about relocation, working conditions (office environment, travel, physical/mental requirements). That keeps sections fewer. Now we need to ensure we don't miss any substantive info: The note about relocation eligibility: "Note This position is not eligible for relocation / international relocation." We'll include that in About the role. Now check for duplicated lines: The posting had some duplicated lines? Not sure. Now produce HTML. We must not include markdown fences. Just raw HTML. Let's craft. Metadata paragraph:

            Posting End Date: October 05, 2026. Employee Type: Regular-Full time. Union/Non: This is a non-union position.

            Then

            About the role

            with

            containing multiple sentences. We'll combine into one

            maybe with line breaks? Could be multiple

            but okay. Content: "At Enbridge, we are committed to delivering safe, reliable energy while driving financial excellence and innovation. We are seeking a Senior Engineer, Engineering Governance to join our team! In this role, you will provide subject matter expertise in the development and implementation of engineering governance that standardizes how projects are executed across our business units and regional locations in Canada and the United States. You will lead the creation and continuous improvement of governance documents, collaborate with diverse project stakeholders, facilitate training, and promote a consistent, fit-for-purpose approach throughout the project lifecycle. Bring your project expertise and passion for continuous improvement to help shape a more consistent and effective approach to project execution across Enbridge! Note: This position is not eligible for relocation or international relocation.