Engineering Automation Manager
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID etc. Remove boilerplate. We need to parse the posting for substantive content. Sections: - About the role: Could be the Job Summary paragraph(s). The posting includes "Job Summary" then description. So we can put that under About the role. - Responsibilities: "Major Responsibilities" with bullet points. - Requirements: maybe "Education And Experience Requirements" and "Required Knowledge And Skills". Could combine into Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include based on content. We have content for: - About the role (Job Summary) - Responsibilities (Major Responsibilities) - Requirements (Education And Experience Requirements) - Qualifications (maybe Required Knowledge And Skills could be Qualifications or Skills). Could split: Qualifications (education/experience) and Skills (knowledge/skills). But we have both. - Benefits: There's a "Total Rewards/Benefits" section with description but no specific benefits list. It says "robust benefits" but no list. The instruction: never create Benefits section unless posting actually states them. It does mention benefits generically but not specific. Probably we should not include Benefits because no concrete list. However there is a paragraph about benefits but not specific. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist but not specifics. Might be considered stating them? It says "we offer robust benefits". That's a statement but not enumerated. Safer to omit Benefits section. - Pay: Not mentioned. - Schedule: Not mentioned (Full-Time mentioned but not schedule details). Could we include Schedule? It says Full-Time but no schedule details. Probably omit. - Skills: Could be part of Required Knowledge And Skills. Could make a Skills section. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract: About the role (Job Summary): "The Engineering Automation Manager is a key leader in Bechtel’s data-centric delivery model and is responsible for the planning, deployment, and performance of the engineering application suite and engineering data Bechtle Projects. The role ensures that engineering tools, models, and data structures deliver the information required downstream for Procurement, Construction, and Startup teams. Assigned to the PIIM organization and reporting to the PIIM Manager, the Engineering Automation Manager leads the engineering automation team, including discipline automation leads, 3D/BIM model administrators, and engineering application specialists. The role is accountable for the configuration, integration, and adoption of Bechtel’s standard engineering applications, ensuring each tool is implemented to standard, certified in the Bechtel network environment, and connected to the project’s Common Data Environment (CDE). The Engineering Automation Manager works with Engineering management, discipline leads, 3rd-party engineering consultants, and Owner stakeholders to ensure engineering data, model, and deliverable requirements are defined, met, and properly integrated. The Manager establishes and maintains the engineering data structure, model standards, and reporting that support design quality, schedule certainty, and a clean handover of asset information. The position provides engineering-led integration across 3D Model Development, BIM coordination and clash management, 4D Integrated Schedule, 5D Integrated Cost, engineering document management, IS&T, and the use of automation and AI to improve engineering productivity on the project." We need to fix typo "Bechtle Projects" maybe it's "Bechtel Projects". Keep as is? Probably keep original text. Responsibilities: list under "Major Responsibilities". There are three bullet groups each with multiple sentences. We'll convert each sentence into
- for any list of duties/requirements/benefits. So we need to make a list. We can break each major responsibility into items.
Responsibilities items:
1. Engineering Application Suite Deployment & Integration: Lead the deployment and administration of Bechtel’s engineering application suite, including 3D/BIM model authoring and review tools (e.g., Autodesk Revit, AutoCAD, Navisworks; Bentley MicroStation), engineering data and document tools, and integration with Aconex, material management applications, Power Platform solutions, and Bechtel Data Mesh services, in alignment with the Project Automation Plan. Drive integration so engineering data flows seamlessly to downstream functions (3D model ↔ material take-off ↔ procurement ↔ schedule ↔ construction work packages), reflecting the project’s Level 1 Automation Diagram and AI-enablement opportunities.
2. Engineering Automation Team Leadership: Manage, supervise, and develop the engineering automation team, including staffing plans, work assignments, performance feedback, and succession for discipline automation leads and model administrators. Provide direction to discipline automation leads to deliver the best outcomes for design production, model maturity, and advanced work packaging (EWPs and IWPs). Coordinate closely with Engineering management and BIM Lead(s) at 3rd-party engineering consultants, design partners, and construction firms to align BIM Execution Plans, model federation, and exchange protocols.
3. Engineering Data, Model & Deliverable Quality: Ensure engineering implementation of the Project Information Model at each stage of design, meeting client information requirements, Bechtel information requirements, and industry-wide standards (e.g., ISO 19650). Define and enforce model standards, level of development (LOD), attribute requirements, and tag/numbering conventions for graphical and non-graphical engineering data. Establish model review, clash detection, and design-quality processes, and track model progress and maturity against the engineering schedule. Liaise with stakeholders to exchange engineering information and provide input into design requirements (level of detail and data attributes) needed for construction, commissioning, and operations.
4. Training, Innovation & AI Enablement: Ensure engineers, designers, and 3rd-party partners are trained on engineering applications, model standards, and related processes (CDE, 4D, 5D), including engagement with off-project subject-matter experts. Support the PIIM Manager to champion and implement engineering innovation, including design automation, rules-based design, scripting, and AI-enabled solutions that improve safety, quality, productivity, and customer satisfaction.
That seems fine.
Requirements: Education And Experience Requirements paragraph:
"Minimum of 5 years in a lead or supervisory role directing engineering automation, design technology, or BIM teams, with demonstrated ability to manage staff across multiple offices and 3rd-party partners."
We can put as
maybe. Qualifications: Required Knowledge And Skills paragraph: "Recognized degree in engineering or a related technical discipline with 13+ years of relevant experience, including 8+ years in engineering automation, digital engineering, or engineering application management on large EPC projects. Hands-on experience deploying, configuring, and administering 3D/BIM and engineering data applications (e.g., Autodesk Revit, AutoCAD, Navisworks; Bentley MicroStation), including catalogs, specifications, and model federation. Strong knowledge of engineering work processes across disciplines and how engineering data supports procurement, construction, advanced work packaging, and digital handover. Working knowledge of information management standards (e.g., ISO 19650), CDEs such as Aconex, and application-integration and configuration-management practices. Experience on semiconductor, advanced manufacturing, data center, or other mission-critical facility projects is strongly preferred; exposure to design automation, scripting, and AI tools is desirable. Excellent communication, leadership, and interpersonal skills, with the ability to influence without authority and explain new tools and work processes to all levels of the organization" We could split into Qualifications (education/experience) and Skills (knowledge/skills). But we already used Requirements for the 5 years lead experience. Could treat Requirements as the 5 years lead experience, Qualifications as the degree+13 years etc, Skills as the rest. However the instruction says we can use those headings; we should only include if real content. We have content for each. Thus: - Requirements: the 5 years lead/supervisory experience. - Qualifications: recognized degree + 13+ years experience, 8+ years in engineering automation etc. - Skills: hands-on experience, strong knowledge, working knowledge, experience preferred, excellent communication etc. We could also combine Qualifications and Skills but better to follow headings. Now Benefits: we have a paragraph about benefits but no specific list. The instruction: never create Benefits section unless posting actually states them. It does state they offer robust benefits, but not specific. I'd argue it's stating benefits exist, but not enumerated. Safer to omit Benefits. Pay: none. Schedule: we have Full-Time mentioned in metadata but not schedule details. Could we include Schedule? The posting says "Telework Type: Full-Time Office/Project Work Location: Houston, TX". That indicates full-time but not schedule details like hours. Probably omit Schedule. Now we need to output HTML fragment only, no /. Use
for each section heading. Structure:
About the role
Job Summary paragraph...
Responsibilities
- ... ...
Requirements
Minimum of 5 years ...
Qualifications
Recognized degree ...
Skills
Hands-on experience ...
We need to ensure we preserve all substantive info. Let's copy text exactly. Check for any duplicated lines: The posting includes "Learn more about our extraordinary teams building inspiring projects in our Impact Report." That's part of overview but not job-specific; maybe we can include in About the role? It's not directly about role but could be considered boilerplate? It's about company overview. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not boilerplate but maybe part of company overview. It's not directly about role but could be considered part of "About the role"? Might be okay to keep but it's not specific to role. However it's not duplicated. I'd keep it in About the role maybe as part of company overview. But the About the role section should be about the role; we could include a brief company overview if it's substantive. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that line if it's substantive. It's in the "Project Overview" section after the intro. Actually after the intro there is "Project Overview Bechtel’s Manufacturing & Technology (M&T) Business Unit is designing and building an Active Pharmaceutical Ingredient (API) Manufacturing Facility located at Generation Park in Houston, TX." That's substantive about the project. That should be included maybe under About the role or a separate section? There's no heading for Project Overview but we could include it under About the role as context. Thus About the role could combine the Job Summary and Project Overview. Let's extract Project Overview paragraph: "Bechtel’s Manufacturing & Technology (M&T) Business Unit is designing and building an Active Pharmaceutical Ingredient (API) Manufacturing Facility located at Generation Park in Houston, TX. M&T is an exciting and growing business unit that serves customers in the semiconductor, datacenter, life sciences, and electric vehicle markets. M&T strives to exceed our customer objectives through utilizing our agility, innovative technologies, and world class talent. M&T solves the industry's toughest challenges, building both our company and the world for the future. Headquartered in Reston, Virginia, the M&T global business unit also includes colleagues working in Arizona, Ohio, Texas, India, and additional project locations around the world." We should include that. Thus About the role will have two paragraphs: Project Overview and Job Summary. Now ensure we don't include any boilerplate like "Learn more about our extraordinary teams building inspiring projects in our Impact Report." That's a sentence after the intro before Project Overview. That is maybe promotional but still substantive? It