Technical Manager - Design and Delivery

We need to output HTML fragment with sections for headings: 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. Preserve all substantive info. We need to parse the posting. Content: - Intro about ACCIONA: description of company, mission, invitation. That could be "About the role"? Actually "About the role" maybe includes description of role and company. We'll put a

About the role

with paragraph(s) summarizing that. - Then responsibilities: many bullet points under "Job Description" sections: Engineering Management and Technical Delivery, Design Coordination and Integration, Engineering Quality and Compliance, Technical Risk and Issue Management, Stakeholder and Interface Coordination, Procurement, Construction, and Commissioning Support, Reporting and Performance Monitoring. Those are responsibilities. - Required Skills And Competencies: includes education, experience, skills list. - Benefits: "Acciona offers a competitive salary, relocation assistance where relocation is required and approved, 401(k) retirement plan, medical, dental, vision, life, short and long-term disability benefits, tuition reimbursement, paid time off, and more." - Pay: Not explicitly given beyond "competitive salary". That's vague; we should not create Pay section unless posting actually states them. It says "competitive salary" but no specifics. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specifics, so include Benefits. Pay we have only "competitive salary" which is vague but maybe considered stating? It says "competitive salary" which is a statement but not a number. The rule: 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. "competitive salary" is somewhat vague but it's a statement. Might be considered filler? It's not a specific number. Safer to not create Pay section. Similarly Schedule not mentioned. - Qualifications: maybe combine with Required Skills? The posting has "Required Skills And Competencies" which includes education and experience. Could treat as Qualifications. But we also have Skills separate list. We could have sections: About the role, Responsibilities, Qualifications, Skills, Benefits. We must not repeat job title. Use

for each section heading. We need to use

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

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points as they are, not condense. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is some EEO text about Top Employer certification, diversity, etc. That is boilerplate? It's about company awards and diversity statement. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The diversity statement is EEO-related. So we should remove that paragraph about Top Employer certification and diversity invitation. Also remove any duplicated lines. Thus we keep only the substantive job description. Let's extract sections: About the role: The initial paragraph about ACCIONA mission and invitation. Also maybe the sentence "The Technical Manager supports the Technical Lead..." That's more role description. Could be part of About the role. We'll craft About the role paragraph(s): - ACCIONA is a global company, leading in the development of regenerative infrastructure that creates a positive impact on society. Our workforce consists of more than 65,000 professionals, present in more than 40 countries across the five continents, all contributing in our mission to design a better planet. Are you a passionate individual who wants to make a difference, promote sustainable development, and find solutions to the biggest global challenges including climate change, overpopulation, and water scarcity? Come and join us in building the infrastructure our planet needs to achieve a sustainable future. - The Technical Manager supports the Technical Lead in the management and execution of engineering and technical activities for the WIFA Long-Term Water Augmentation Project. This role is responsible for coordinating multidisciplinary engineering efforts, managing day-to-day technical delivery, overseeing engineering consultants and discipline leads, and ensuring project technical activities are completed in accordance with project requirements, quality standards, technical procedures, schedules, and budget objectives. That seems good. Responsibilities: list all bullet points under each subheading. We'll combine into a single

  with each duty as
  • . Must preserve all details. Let's list them: From Engineering Management and Technical Delivery: - Manage the day-to-day execution of engineering and technical activities in support of project objectives. - Coordinate engineering efforts across treatment, conveyance, intake/discharge, pumping, storage, and operational systems. - Implement technical strategies, standards, procedures, and engineering directives established by the Technical Lead. - Monitor engineering progress and ensure technical deliverables are completed on schedule and in accordance with project requirements. - Support development and execution of engineering work plans, resource plans, and technical schedules. - Identify and elevate significant technical issues requiring Technical Lead review and direction. Design Coordination and Integration: - Coordinate multidisciplinary engineering teams, consultants, and discipline leads to ensure integrated project delivery. - Manage the preparation, review, tracking, and distribution of engineering deliverables, including: - Technical studies and reports - Design packages - Drawings and specifications - Design calculations - Hydraulic and process modeling inputs and outputs - Facilitate interdisciplinary design reviews and ensure timely resolution of review comments. - Coordinate technical interfaces among design disciplines and project stakeholders. - Support implementation of design management and document control processes. Engineering Quality and Compliance: - Support the Technical Lead in implementing engineering QA/QC programs and technical review procedures. - Monitor compliance with project engineering standards, design criteria, and quality requirements. - Coordinate technical reviews to verify consistency, completeness, and constructability of engineering deliverables. - Ensure engineering activities comply with applicable regulatory requirements, industry standards, and project specifications, including: - AWWA - ASTM - NFPA - OSHA - Arizona regulatory requirements Technical Risk and Issue Management: - Track and manage technical risks throughout planning, design, construction, and commissioning phases. - Support maintenance of technical risk registers and mitigation action plans. - Coordinate evaluations of: - Design alternatives - Constructability considerations - Operational impacts - Maintainability requirements - Lifecycle cost implications - Facilitate timely resolution of technical issues affecting project performance, schedule, or cost. Stakeholder and Interface Coordination: - Coordinate closely with: - Discipline Leads - Engineering Managers - Construction Management - Commissioning Teams - Procurement Personnel - O&M Representatives - Environmental and Permitting Teams - Facilitate technical coordination meetings, workshops, and interface reviews. - Support technical communications with WIFA representatives, consultants, contractors, suppliers, and regulatory stakeholders. - Maintain technical action item logs and ensure follow-through on assigned commitments. Procurement, Construction, and Commissioning Support: - Coordinate technical support activities related to procurement and vendor management. - Assist in the review of vendor proposals, technical submittals, equipment selections, and shop drawings. - Support construction teams by coordinating engineering responses to field issues, RFIs, and technical queries. - Assist commissioning teams with testing, startup, system integration, and operational readiness activities. - Coordinate technical support during project handover and transition to operations. Reporting and Performance Monitoring: - Prepare technical reports, engineering dashboards, and project performance updates. - Monitor engineering KPIs, design progress, and technical deliverable status. - Provide regular updates to the Technical Lead regarding: - Engineering progress - Technical risks - Resource requirements - Interface challenges - Critical technical issues - Support forecasting and management of engineering workloads and staffing requirements. That's a lot; we need to keep them as list items. For sub-bullets (like under "including:"), we could either keep them as part of the parent
  • using commas or separate
    inside? The instruction: Use
    • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can keep nested
      for sub-items. That would preserve detail. Similarly for Required Skills And Competencies: we have education, experience, skills list. Let's parse Required Skills And Competencies: - Bachelor’s degree in Civil, Mechanical, Chemical, Environmental, or related Engineering discipline, master’s degree preferred. - Proven experience of progressively responsible technical experience on large water, wastewater, or conveyance infrastructure programs. - Skills - Enterprise‑level technical judgment. - Multidisciplinary coordination and systems thinking. - Risk‑based decision making. - Clear communication with executive, technical, and regulatory stakeholders. - Focus on long‑term operational performance and asset integrity. We could treat "Skills" as a subsection under Qualifications or separate Skills section. We have both Qualifications and Skills sections possible. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications (education/experience) and Skills (the list). We'll need to decide. We have Required Skills And Competencies heading includes both education/experience and skills. We could split: Qualifications: education and experience. Skills: the list. Thus:

      Qualifications

      • Bachelor’s degree in Civil, Mechanical, Chemical, Environmental, or related Engineering discipline, master’s degree preferred.
      • Proven experience of progressively responsible technical experience on large water, wastewater, or conveyance infrastructure programs.

      Skills

      • Enterprise‑level technical judgment.
      • Multidisciplinary coordination and systems thinking.
      • Risk‑based decision making.
      • Clear communication with executive, technical, and regulatory stakeholders.
      • Focus on long‑term operational performance and asset integrity.
      Benefits: we have a sentence: "Acciona offers a competitive salary, relocation assistance where relocation is required and approved, 401(k) retirement plan, medical, dental, vision, life, short and long-term disability benefits, tuition reimbursement, paid time off, and more." We should not include Pay section; but Benefits we can list each benefit as
      • . However the sentence includes "competitive salary" which is pay; but we are putting it in Benefits. Might be okay but we could separate salary as part of Benefits? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specifics; we can include Benefits section. The sentence includes "competitive salary" which is pay info; but we are not making a separate Pay section. It's okay to include salary within Benefits? Might be considered mixing. But we could keep Benefits as list of benefits excluding salary? However the sentence lumps them together. To preserve ALL substantive information, we should include the sentence as is, maybe as a

        rather than list. But instruction: Use

        • for any list of duties/requirements/benefits. So we could turn the benefits into a list. However the phrase "competitive salary" is part of that list. If we make Benefits section, we include salary as a benefit item. That's okay. Thus:

          Benefits

          • Competitive salary
          • Relocation assistance where relocation is required and approved
          • 401(k) retirement plan
          • Medical
          • Dental
          • Vision
          • Life
          • Short and long-term disability benefits