Senior, Engineering Delivery Manager (EDM)

We need to output HTML fragment with sections only when there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. First, note: The posting includes "Job Details Please Note - Preferred location: Irvine, California. Remote candidates may be considered if they are out of the area". That's location info; we can put in a short

maybe under a generic heading? But we shouldn't create a heading for location unless we have a specific heading like "Location". Not in allowed headings list. So we can embed location in a paragraph maybe after a heading? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include location in a

maybe after a heading like "About the role"? But location is not about role. Could create a short

before sections. Probably we can include a

with location note. Now sections: - About the role: we have a paragraph describing main objective etc. We'll put that as

under

About the role

. - Responsibilities: The posting lists many responsibilities: "Engineering Execution Architecture", "Operating Cadence and Leadership Partnership", "Operational Processes and Continuous Improvement", "Tools and Reporting", "Interfaces and Stakeholders", "Manufacturing And Production Engineering". Those are subheadings within the description but we can treat them as bullet list items under Responsibilities. We need to preserve all substantive info. Could create a

with each responsibility as
• . Might be long but okay. - Requirements: The posting has "Required" bullet list: Extensive interdisciplinary background..., 7 years..., Extensive experience..., Demonstrated ability..., Advanced proficiency..., Extensive experience applying Six Sigma..., Demonstrated ability..., Strong executive communication..., Ability to influence... We'll list each as
• . - Qualifications: Not separate; maybe "Preferred" is separate. Could treat "Preferred Experience" as Qualifications? The instruction: Use headings for Qualifications if there is content. We have "Preferred Experience with large-scale BESS system integration..." That's a qualification (preferred). So we can put under

  Qualifications

  maybe with bullet. - Skills: Could list tools: MS Project, JIRA, Six Sigma CTQ, etc. But those are already in Required. Might be redundant. Better to not create Skills if content overlaps. But we could still create Skills if we have specific skill list not covered elsewhere. The Required includes "Advanced proficiency in MS Project and JIRA", "Extensive experience applying Six Sigma CTQ methods". Those are skills. Could put them under Skills. However we already used them in Required. To avoid duplication, we could keep them under Required and not create Skills. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Required and Qualifications into one section? But headings are prescribed; we can only use those headings if we have content. We could have Required and Qualifications both. - Benefits: The posting mentions "+ Benefits" after compensation range. No details. So we should NOT create Benefits section because no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "+ Benefits" but no detail. That's not specific content. So we should not create Benefits. - Pay: The posting includes "The compensation range for this role is between $165,000 - $195,000 + Benefits". That's specific pay range. So we should create a Pay section with that info. Use

  . - Schedule: No mention of schedule (full-time, etc). Not stated. So no Schedule section. Now we need to output HTML fragment only, no /. Use

  headings,

  • for lists,

    for prose. We need to include location note maybe as a

    before sections. Let's craft:

    Preferred location: Irvine, California. Remote candidates may be considered if they are out of the area.

    Then

    About the role

    with paragraph summarizing the role description. We need to preserve all substantive information; we can't summarize away detail. But we can condense into a paragraph that captures the main objective etc. However we must not invent or summarize away detail. Summarizing is allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we need to keep them. So we need to include all details from the About The Role section. That's lengthy. Could we put them as a

    with the whole block? That would preserve detail. Yes we can copy the text as a paragraph. That's okay. Similarly for Responsibilities we could list each bullet as

  • preserving the subheadings maybe as part of the li text. We need to avoid duplication: The About the role paragraph already includes some of the responsibilities; but we must preserve all info. If we also list responsibilities separately, we may duplicate some content. The instruction says preserve ALL substantive information; does not forbid duplication, but better to avoid redundancy? It didn't forbid duplication. However we should aim to not repeat same sentences. But we can keep the About the role as a high-level summary and then responsibilities as detailed list. That may be okay but some content may overlap. However the About the role paragraph includes sentences like "The main objective of this role is to identify technical gaps..." etc. The responsibilities list includes more detailed items. Overlap may be minimal. We'll try to keep About the role as a short paragraph that captures the main objective and overall purpose, but we need to preserve all substantive information; if we omit some details from that paragraph, we are summarizing away detail. So we need to include the full description of the role as given. That description is under "About The Role". It includes multiple paragraphs: The main objective..., This role turns..., The role partners closely..., then subheadings: Engineering Execution Architecture, Operating Cadence..., Operational Processes..., Tools and Reporting..., Interfaces..., Manufacturing And Production Engineering. So we should include all that as prose maybe with

    and maybe

    for subpoints? But the instruction says use
    • for any list of duties/requirements/benefits. The responsibilities are a list of duties; we can treat them as a list. The "About The Role" section includes prose plus subheadings that are essentially duty categories. So we could treat the whole thing as a list of duties. However we also need an "About the role" heading; maybe we put a short summary there, but then we risk losing detail. Better to treat the "About the role" heading as containing the prose description (the paragraphs) and then have a separate "Responsibilities" heading with a detailed list. That may duplicate some content but maybe acceptable. However to strictly preserve all info without summarizing away, we could put the entire "About The Role" block as a

      under About the role heading, and then also have Responsibilities heading with a list that maybe repeats some content but that's okay. The instruction didn't forbid duplication. But we should aim to avoid unnecessary duplication; but it's not prohibited. Given the complexity, I'll produce: -

      Preferred location: Irvine, California. Remote candidates may be considered if they are out of the area.

      -

      About the role

      [copy the entire About The Role block as a single paragraph? It contains line breaks and headings. We could preserve line breaks via
      or keep as is with

      and maybe
      for line breaks. Simpler: keep as a single paragraph with sentences separated by spaces. Might lose formatting but content preserved. We'll copy the text exactly as given, preserving line breaks via
      tags. Let's extract the About The Role block: "The main objective of this role is to identify technical gaps in engineering tasks to ensure scalable and predictable engineering execution. The Senior EDM owns the internal engineering execution architecture. This role turns high-level engineering objectives into a complete task breakdown with clear owners, dependencies, deliverables, and readiness criteria, ensuring there are no gaps or overlaps across disciplines. The role partners closely with PMO, which owns the integrated master schedule and external communications with customers and vendors, to ensure seamless execution of internal and external milestones. Engineering Execution Architecture Build and maintain the engineering work breakdown structure across systems, electrical, mechanical, controls, software, compliance, test, manufacturing readiness, and field readiness. Define clear scope boundaries, handoffs, and ownership to prevent gaps and duplicated work across teams. Create phase gate readiness criteria for key milestones such as requirements freeze, design freeze, build readiness FAT readiness, certification readiness, and release readiness. Translate engineering changes into task level impacts and provide schedule and resourcing inputs to PMO for baseline updates. Operating Cadence and Leadership Partnership Work directly with the Director of Engineering on task planning and scope checks, and highlight critical path risks early. Run a recurring engineering execution cadence including weekly progress reviews, dependency reviews, and risk issue decision tracking. Drive cross functional alignment on deliverables, sequencing, and acceptance criteria. Operational Processes and Continuous Improvement Design and implement operational processes to track and quantify engineering outcomes and execution efficiency. Establish a consistent operating system for engineering execution including WBS standards, JIRA structure, engineering RAID and decision logs, and milestone readiness reviews. Use Six Sigma CTQ to support structured trade-off decisions (scope, schedule, cost, risk) and to reduce rework and variability in engineering outputs. Define metrics, track trends, and lead continuous operational optimization with the Director of Engineering. Tools and Reporting Provide technical deliverable inputs and task breakdown at the level of detail required to manage dependencies and provide clean inputs to the PMO master schedule. Build and maintain a JIRA structure that reflects the WBS and supports traceable execution, including EPICs, Stories, definitions of completed, and clear ownership. Create concise technical executive readouts for progress, risks, decisions needed, and forecast to key milestones (with PMO) Interfaces and Stakeholders Director of Engineering PMO team for integrated schedule governance and external milestone coordination Engineering discipline leaders across hardware and software Compliance and certifications Quality and reliability Supply chain and manufacturing engineering Contract manufacturers and key vendors as needed for internal readiness planning Manufacturing And Production Engineering: Establish and enforce configuration control and ECN discipline. Provide technical oversight of contract manufacturers to ensure build quality and process adherence. Own unit level build, test, and quality readiness prior to release to execution teams." We'll put that inside

      with
      for line breaks. Then

      Responsibilities

      maybe we can skip because we already covered duties in About the role. But we need to follow instruction: Use
      • for any list of duties/requirements/benefits. The About the role block is not a list; it's prose with embedded lists. Could we convert to a list? Might be better to keep as prose and not create Responsibilities section to avoid duplication. However we need to include a section only when posting has real specific content for it. The posting does have responsibilities (the bullet-like items). So we should have a Responsibilities section with a list. But we already included them in About the role; duplication may be okay. I'll create Responsibilities as a
        with each major bullet as
        • (the subheadings and their sub-bullets). To preserve detail, we can include each line as separate
        • . That will be lengthy but okay. Similarly Requirements: we have a list under "Required". We'll make
          . Qualifications: we have "Preferred Experience..." as a bullet; we can make
          with that. Skills: Not needed. Pay:

          The compensation range for this role is between $165,000 - $195,000 + Benefits

          Now ensure we don't