Senior Manager, Project & Engineering Management

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. We need to parse the posting. Sections present: - About Zimpro And Lummus Modular (maybe "About the role"? Actually "About Zimpro And Lummus Modular" is description of business. Could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. The posting includes "About Zimpro And Lummus Modular". That's about the business, not exactly "About the role". But we could treat as "About the role". However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if appropriate. The posting includes "Job Summary". That could be "About the role". Also "Strategic Priorities" maybe part of responsibilities? Could be separate but not in list. We should only include sections when posting has real specific content. We have content for: - About the role: could include "Job Summary" and maybe "About Zimpro And Lummus Modular". We'll combine. - Responsibilities: "Key Responsibilities" with subpoints. - Requirements: "Job Requirements" includes Basic Qualifications. - Qualifications: "Preferred Qualifications" maybe also "Leadership Competencies" and "Key KPIs / Success Measures". Those could be qualifications or skills. But we have separate sections for Skills, Benefits, Pay, Schedule. The posting does not mention Benefits, Pay, Schedule explicitly. So we should not include those sections. - Skills: Could include "Leadership Competencies" maybe as skills. But they said use Skills section for skills. The posting includes "Leadership Competencies". That could be considered skills. Also "Key KPIs / Success Measures" maybe not skills. We'll decide. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all content from the posting except boilerplate. We must not create sections with filler like "not specified". So we will include sections only where we have content. Thus we will have:

About the role

with content: maybe combine "Job Summary" and "About Zimpro And Lummus Modular". Also maybe "Strategic Priorities"? That could be part of responsibilities but we can include under About the role? Better to keep responsibilities separate. Let's extract: Job Summary paragraph: "The Senior Manager - Project & Engineering Management serves as the senior technical and execution leader for Zimpro and Lummus Modular. The role leads project engineering and execution from FEED through commissioning, provides project management oversight, and drives value engineering, standardization, supplier development and third-party engineering governance. Working directly with clients, EPC partners, design centers and fabrication partners, the incumbent ensures that the project portfolio is delivered safely, on schedule, within budget." About Zimpro And Lummus Modular paragraph: "Zimpro and Lummus Modular are growth platforms within Lummus Technology that deliver advanced water treatment, modular process solutions and sustainable technology applications for energy and industrial clients. With an expanding pipeline of large capital projects, the businesses require disciplined engineering execution, cost transparency, standardization and a scalable global delivery model to convert commercial opportunities into safe, profitable and repeatable project outcomes." Strategic Priorities bullet list: "Build the engineering execution capacity required to convert a growing capital-project pipeline into delivered, profitable work. Drive value engineering, installed-cost transparency and measurable cost-out across the technology portfolio. Standardize and commercialize most technologies into repeatable, tiered packages that reduce engineering hours and proposal cycle time. Expand and qualify the supplier, fabrication and engineering-partner base in India and other cost-competitive locations. Establish robust governance for outsourced engineering while preserving design integrity, quality, schedule and cost performance. Build a high-performing, multicultural engineering organization with strong technical capability, resource flexibility and succession depth." We could put Strategic Priorities under About the role or Responsibilities. Since it's about what the role will drive, maybe under Responsibilities. But we already have Key Responsibilities section with sub-sections. Might be better to put Strategic Priorities under About the role as context. Now Responsibilities: "Key Responsibilities" with subheadings: Project Management and Delivery Leadership, Project Engineering Execution, Value Engineering and Cost Ownership, Standardization and Commercialization, Supplier Base Expansion and Third-Party Governance, Team and Cross-Entity Leadership. Each has bullet points (actually sentences). We need to output as

• for any list of duties/requirements/benefits. So we need to convert each responsibility bullet into list items. The subheadings could be

  ? But instruction only says use

  for section headings. It didn't forbid other headings, but we should avoid extra headings? It 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 to keep simple we could just make each responsibility as a list item without subheadings, but we might lose structure. However we must preserve ALL substantive information; we can keep subheadings as plain text inside

  or as . Probably acceptable to keep them as part of list item text. Thus for Responsibilities we will have

  Responsibilities

  then

  with each responsibility as
  • containing the description. Similarly Requirements: "Job Requirements" includes Basic Qualifications bullet list. We'll output

    Requirements

    then
    with each qualification. Qualifications: "Preferred Qualifications" bullet list. Also "Leadership Competencies" maybe considered skills or qualifications. But we have Skills section; we could put Leadership Competencies under Skills. Also "Key KPIs / Success Measures" maybe not needed as a section; could be part of Qualifications? But they are success measures, not qualifications. Could be omitted? But we must preserve ALL substantive information. So we need to include them somewhere. Perhaps we can include them under Qualifications as additional bullet points, or under Skills. Since they are not qualifications but performance metrics, maybe we can put them under a separate section like "Success Measures" but not in allowed headings. The instruction says we should prefer a few substantive sections over many thin ones, and only include sections when posting has real specific content. It lists example headings but not limited to those? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings if applicable. It doesn't forbid other headings, but to be safe we could incorporate KPIs into Qualifications or Skills. However they are not qualifications; they'd be misrepresenting. But maybe we can treat them as "Skills" (like metrics). But better to create a section "Key KPIs / Success Measures" as

    Key KPIs / Success Measures

    even though not in the example list. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as needed. So we can add a section for KPIs. Similarly we might have "Leadership Competencies" as Skills. Thus sections: - About the role (h3) - Responsibilities (h3) - Requirements (h3) - Qualifications (h3) (Preferred Qualifications) - Skills (h3) (Leadership Competencies) - Key KPIs / Success Measures (h3) (maybe rename to Success Measures) We must not include Benefits, Pay, Schedule as they are not present. Now we need to extract content precisely. Let's copy the relevant paragraphs. About Zimpro And Lummus Modular: "Zimpro and Lummus Modular are growth platforms within Lummus Technology that deliver advanced water treatment, modular process solutions and sustainable technology applications for energy and industrial clients. With an expanding pipeline of large capital projects, the businesses require disciplined engineering execution, cost transparency, standardization and a scalable global delivery model to convert commercial opportunities into safe, profitable and repeatable project outcomes." Job Summary: "The Senior Manager - Project & Engineering Management serves as the senior technical and execution leader for Zimpro and Lummus Modular. The role leads project engineering and execution from FEED through commissioning, provides project management oversight, and drives value engineering, standardization, supplier development and third-party engineering governance. Working directly with clients, EPC partners, design centers and fabrication partners, the incumbent ensures that the project portfolio is delivered safely, on schedule, within budget." Strategic Priorities (list): - Build the engineering execution capacity required to convert a growing capital-project pipeline into delivered, profitable work. - Drive value engineering, installed-cost transparency and measurable cost-out across the technology portfolio. - Standardize and commercialize most technologies into repeatable, tiered packages that reduce engineering hours and proposal cycle time. - Expand and qualify the supplier, fabrication and engineering-partner base in India and other cost-competitive locations. - Establish robust governance for outsourced engineering while preserving design integrity, quality, schedule and cost performance. - Build a high-performing, multicultural engineering organization with strong technical capability, resource flexibility and succession depth. Now Responsibilities: Project Management and Delivery Leadership: "Provide project management leadership, including schedule tracking, progress reporting, resource planning and proactive escalation of cost, quality or timeline risks. Maintain budget and commercial discipline, including project-cost visibility, basic financial analysis, change control and cost-risk assessment. Ensure compliance with process safety, quality assurance, non-conformance and engineering-governance requirements." Project Engineering Execution: "Serve as the senior engineering lead for large capital projects across Zimpro and Lummus Modular, with accountability from FEED through detailed engineering, procurement support, fabrication, construction and commissioning. Coordinate and review multidisciplinary inputs across process, mechanical, electrical, and controls, as well as external subcontractors, to ensure complete, integrated and on-schedule deliverables. Interface directly with end users and EPC partners, lead scope-of-work development and technical negotiations and resolve complex execution issues." Value Engineering and Cost Ownership: "Lead value engineering across the technology portfolio, identifying design simplification, specification optimization and cost-out opportunities without compromising safety, performance or reliability. Build and maintain a fact-based understanding of true installed cost across the offering, closing cost-visibility gaps and improving estimating, pricing and margin decisions." Standardization and Commercialization: "Lead the standardization and commercialization of the portfolio, moving from predominantly custom-engineered designs to repeatable, configurable and tiered package solutions. Create reusable engineering standards, design modules and execution playbooks that reduce non-conformance, engineering hours and cycle time." Supplier Base Expansion and Third-Party Governance: "Expand and qualify the supplier and fabrication base in India and other strategic locations to improve cost competitiveness. Review vendor quotations and purchase requisitions for compliance with project specifications and technical requirements. Define scope boundaries, technical guardrails, quality protocols and performance controls for third-party engineering firms and fabrication partners." Team and Cross-Entity Leadership: "Build and lead multicultural, cross-functional engineering teams across global design centers, regional offices and outsourced partners. Optimize resource utilization across concurrent projects and provide technical mentoring and development to junior and mid-level engineers. Promote collaboration, accountability, knowledge sharing and continuous improvement across Zimpro, Lummus Modular and the broader sustainable technologies portfolio." Now Requirements (Basic Qualifications): - Bachelor's degree in Mechanical Engineering, Chemical Engineering or a comparable engineering discipline. - At least 10 to 15 years of experience managing complex engineering and capital projects across oil and gas