BIM Coordinator

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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Must not include sections with placeholder like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting does not mention specific pay amount or schedule details (like hours). It mentions "Full Time" but that's job type; schedule maybe implied but not explicit schedule details. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: there is a Benefits section with details. So we include Benefits. Pay: not stated specific compensation, only "Actual compensation will be determined based on factors...". That's vague; not a specific pay figure. Should we include Pay? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation will be determined based on factors, but not actual numbers. Likely we should not include Pay because it's not specific. Schedule: not stated beyond Full Time; but maybe we could include Schedule if they mention Full Time? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Job Type: Full Time, which is schedule type. Might be considered stating schedule. However they also say "Prefer a few substantive sections over many thin ones." Might be okay to include Schedule with Full Time. But they also said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Job Type could be considered minor metadata. I'd lean to not include Schedule section because it's not detailed. Benefits we definitely include. We need sections: About the role (maybe from first paragraph after job type?), Responsibilities, Requirements, Qualifications, Skills, Benefits. The posting includes Requirements (job requirements) and Responsibilities. It also includes some qualifications like Bachelor's degree etc. Could split into Requirements and Qualifications. Skills: maybe list specific tools proficiency etc. Could extract from requirements: Expert proficiency with Navisworks, strong working proficiency with Revit, experience with coordination platforms, hands-on experience with reality capture, working knowledge of digital layout workflows and robotic total stations, strong understanding of construction sequencing, communication skills, etc. That could be Skills. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all details from Responsibilities, Requirements, etc. We'll need to format as

• for any list of duties/requirements/benefits. For prose, use

  . For headings use

  . We must not include boilerplate like EEO, legal, etc. So cut after "We value diverse perspectives..." maybe stop before EEO. Also remove "IE US Operations Inc., the employing entity..." etc. Also remove E-Verify etc. Also remove privacy statement. We need to include location, department, reporting to, work location type? That's metadata; maybe fold into a short

  under About the role? The instruction: do not put as heading. Could include a paragraph with location, department, reporting, remote. Let's craft About the role: combine the description about IREN and role summary. Use prose. Responsibilities: list each bullet from Responsibilities section. Use

  • . Requirements: list each bullet from Job Requirements. Use
    • . Qualifications: maybe Bachelor's degree etc. Could be separate but we could combine with Requirements? But we need to follow headings only if real content. We have both Requirements and Qualifications distinct. We'll create Qualifications heading for Bachelor's degree etc. Skills: list specific tools and proficiencies. Benefits: list benefits from Benefits section. We must not include Pay or Schedule sections. Let's extract details. About the role: IREN is a vertically integrated AI Cloud provider... Reporting to the Manager, VDC, the BIM Coordinator is the on-the-ground integration point... With 100% renewable energy... We believe that human progress is invaluable... (maybe include that). Also include location Texas, department Innovation, reporting to Manager, VDC, work location type remote. We'll put that in a paragraph. Responsibilities: list as given: - BIM Execution Ownership - Own and administer the project BIM Execution Plan (BEP) — establishing the coordination schedule, model exchange cadence, federation structure, and sign-off gates for the project, and holding all parties accountable to it. - Manage the federated project model in Navisworks, controlling model versioning, publishing coordinated baselines, and ensuring every stakeholder is working from current, trusted model data. - Chair project coordination meetings, tracking clash and issue resolution to closure with clear ownership and deadlines, and escalating systemic issues to the internal VDC team and project leadership when needed. - Interdisciplinary Clash Detection & Resolution - Run the project's interdisciplinary clash detection program — federating mechanical, electrical, and CSA models, executing structured clash tests against agreed tolerances and priorities, and facilitating resolution between disciplines before work is released to the field. - Validate that resolved clashes are closed in updated models and maintain clash trending metrics that give project leadership visibility into coordination health. - Reality Capture & As-Built Verification - Plan and execute LIDAR scanning of construction activities at defined milestones, registering point clouds back into the Navisworks federated model to verify installed work against the coordinated design. - Run updated clash detection against captured as-built conditions — identifying deviations, out-of-tolerance installations, and downstream conflicts created by field changes early enough to correct them at minimal cost. - Maintain the scan-to-model workflow so the project closes out with an accurate as-built model suitable for commissioning and handover to operations. - Digital Layout & Field Enablement - Facilitate the use of digital layout tools (e.g., robotic total stations) to set out structure, hangers and supports, sleeves and penetrations, equipment anchor points, and other key elements of the installation directly from the coordinated model. - Prepare and quality-check layout points and field packages exported from the model, and support trade crews in adopting model-based layout so installation matches coordinated geometry the first time. - Stakeholder Coordination - Coordinate daily with design teams, trade contractors, and internal VDC team members — onboarding project partners to IREN's VDC requirements, resolving modeling and data exchange issues, and keeping coordination moving at the pace of construction. - Feed project lessons learned — recurring clash patterns, workflow friction, scan findings — back to the corporate VDC team and discipline BIM Specialists so standards improve across the business. We'll flatten into
      • items; each bullet can be a
      • . Could group but fine. Requirements: list: - Minimum 8+ years of experience in BIM/VDC coordination on construction projects, with data center, mission-critical, or heavy industrial experience strongly preferred; site-based coordination experience is essential. - Expert proficiency with Navisworks for federation and clash management, and strong working proficiency with Revit; experience with coordination platforms (e.g., BIM 360/ACC, Navisworks, Revizto) is strongly preferred. - Hands-on experience with reality capture — planning LIDAR scans, registering point clouds, and integrating them into coordination workflows — using tools such as ReCap, Cyclone, or equivalent. - Working knowledge of digital layout workflows and robotic total stations (e.g., Trimble, Leica, Topcon) and preparing model-derived layout data for field use. - Strong understanding of construction sequencing and multi-trade installation practices, with the field presence and communication skills to run coordination meetings and hold trade partners accountable constructively. - Bachelor's degree in Engineering, Construction Management, or a related discipline, or equivalent practical experience; role is site-based with travel between project sites as required. Qualifications: maybe separate Bachelor's degree? But we already included in Requirements. Could treat Requirements as experience, Qualifications as education. Let's split: Requirements: experience items (first 5). Qualifications: Bachelor's degree etc. But the instruction: Prefer a few substantive sections over many thin ones. Might be okay to combine. However we have headings for Requirements and Qualifications both defined. We'll keep both if they have distinct content. Let's define: Requirements (experience): - Minimum 8+ years of experience in BIM/VDC coordination on construction projects, with data center, mission-critical, or heavy industrial experience strongly preferred; site-based coordination experience is essential. - Expert proficiency with Navisworks for federation and clash management, and strong working proficiency with Revit; experience with coordination platforms (e.g., BIM 360/ACC, Navisworks, Revizto) is strongly preferred. - Hands-on experience with reality capture — planning LIDAR scans, registering point clouds, and integrating them into coordination workflows — using tools such as ReCap, Cyclone, or equivalent. - Working knowledge of digital layout workflows and robotic total stations (e.g., Trimble, Leica, Topcon) and preparing model-derived layout data for field use. - Strong understanding of construction sequencing and multi-trade installation practices, with the field presence and communication skills to run coordination meetings and hold trade partners accountable constructively. Qualifications: - Bachelor's degree in Engineering, Construction Management, or a related discipline, or equivalent practical experience. - Role is site-based with travel between project sites as required. Skills: maybe list specific tools: Navisworks, Revit, BIM 360/ACC, Revizto, ReCap, Cyclone, robotic total stations (Trimble, Leica, Topcon), LIDAR scanning, digital layout, clash detection, etc. But we already covered many in Requirements. Could still create Skills heading summarizing proficiencies: Expert proficiency with Navisworks, strong working proficiency with Revit, experience with coordination platforms (BIM 360/ACC, Navisworks, Revizto), hands-on experience with reality capture tools (ReCap, Cyclone), working knowledge of digital layout workflows and robotic total stations (Trimble, Leica, Topcon), strong understanding of construction sequencing, communication skills, etc. Might be redundant but okay. Benefits: list: - Compensation: Actual compensation will be determined based on factors such as experience, qualifications, and market data for the region. Total Compensation package may be inclusive of annual incentive bonus, equity (long-term incentive). Relocation (as applicable and based on successful candidate circumstances) - Health & Wellness: 100% company paid health insurance premiums (medical, dental, and vision) for employees, 75% company paid coverage for dependents; Company-paid short-term and long-term disability insurance; Voluntary life, critical illness, and accident coverage available; Health Savings Accounts (HSA) – when combined with the High Deductible Health Plan; Employee Assistance Program and wellness resources - Retirement & Financial Wealth: 401(k) retirement plan with company match; Access to financial planning and legal services - Time Off & Leave Programs: Paid Time Off (PTO) and paid holidays - Growth & Development: Internal skills training and advancement pathways; Professional development to support certifications, continuing education, or role related training - Community & Culture: Company events and team-building activities; We value diverse perspectives and believe that skills can be developed. We should not include the EEO etc. Now produce HTML fragment. We'll start with

        About the role

        then

        ...

        . Then

        Responsibilities

        ...
        . Then

        Requirements

        ...
        . Then

        Qualifications

        ...
        . Then

        Skills

        ...
        . Then

        Benefits

        ...
        . Make sure no extra text. Let's craft the About the role paragraph: include IREN description, role summary, location, department,