Jobs · Massachusetts

Architecture - BIM Coordinator

HOK · Boston, MA · 3 wk ago
HybridFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Content: - Intro about HOK (company description) maybe "About the role"? Actually "About the role" could be description of role. The posting includes: "HOK's Boston office is seeking a Architectural BIM Coordinator. This person performs model management, quality control, training, and other BIM-related assignments based on input from the project team and guidance from Design Technology leadership." That's description of role. Could be placed under

About the role

with a paragraph. - Responsibilities: list bullet points after "Responsibilities". Let's extract: Responsibilities Helps develop and maintain a BIM execution plan. Organizes and maintains models for the assigned projects. Works closely with project team and assists to complete projects on aggressive schedules. Checks Revit models for clearances, potential conflicts, and relationships of the various parts to the whole and to one another. Helps project teams maintain efficient 3D models through training and reinforcement of best practices. Conducts BIM-based quality control reviews. Understands and implements various Revit add-ins for increasing team productivity. Coordinates project progress with regional Design Technology Manager. Implements and utilizes HOK Best Practices for all projects and processes. Actively seeks new knowledge related to design technology and regulations. Takes personal responsibility for fostering a green workplace through sustainable work practices. That's a list. - Education & Experience: includes requirements. Could be under

Requirements

or

Qualifications

. The posting has "Education & Experience" and also "Skills & Competencies". We need to decide sections. According to instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - About the role: description paragraph. - Responsibilities: list. - Requirements: maybe Education & Experience. - Qualifications: maybe Skills & Competencies? But they said "Qualifications" separate from Skills. Could treat Education & Experience as Requirements, and Skills & Competencies as Skills. Or we could combine. Let's follow typical: Requirements = education/experience; Skills = skills/competencies. - Benefits: there is a paragraph about benefits: "HOK invests in its people and communities... At HOK you’ll have a hybrid work environment, 10 paid holidays (including 2 floating holidays) and a minimum of 4 weeks of paid time off with a cash out option. HOK offers comprehensive medical, dental, and vision coverage, free mental wellness resources, life and AD&D coverage and short and long-term disability benefits. HOK supports your growing family by offering 4 weeks of paid parental leave and fertility coverage. HOK helps to fund your future financial needs with matching contributions to our 401(K) plan which includes a well-rounded investment menu as well as free guidance on retirement planning. Wherever you are in your career, HOK provides opportunities to learn, develop and utilize your skills. Continued learning is promoted through financial support and study prep for licensure exams, CEU credit opportunities, mentorship programs, and paid professional memberships." That's benefits. - Pay: not mentioned. So we should NOT include Pay section. - Schedule: not mentioned (no mention of full-time/part-time, hours). So omit. We also need to include maybe "Qualifications" if we have content. Could treat Skills & Competencies as Qualifications. But we already have Skills heading. Let's assign: - Requirements: Education & Experience. - Qualifications: maybe "Advanced knowledge of Revit and Rhino..." etc? Actually that is also part of Education & Experience. But we can split: Requirements = education/experience; Qualifications = skills/competencies. However the instruction list includes both Requirements and Qualifications as possible headings. We'll use both. Thus:

About the role

...

Responsibilities

    ...

Requirements

...

(Education & Experience)

Qualifications

    ...
(Skills & Competencies)

Benefits

...

We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive information. Let's extract exact text. About the role paragraph: "HOK's Boston office is seeking a Architectural BIM Coordinator. This person performs model management, quality control, training, and other BIM-related assignments based on input from the project team and guidance from Design Technology leadership." We should keep that exactly. Responsibilities list: each line as
  • . Ensure we keep punctuation. Education & Experience paragraph: "Associate degree in Building Information Modeling or architecture-related curriculum required; Bachelor degree in Architecture or technical certification in Building Information Modeling is preferred.Advanced knowledge of Revit and Rhino, with a focus in architecture and large projects, is required.Three plus years’ experience in building information modeling of architectural systems in Revit is preferred.LEED credential required within 12 months of employment." Note there are missing spaces after semicolons and periods. We'll preserve as is but maybe add spaces for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Changing spacing could be considered altering? Probably fine to keep as is but we could add spaces for readability but not change meaning. Safer to keep exactly as given, but we can add spaces after punctuation if they were missing originally? The original text: "Associate degree in Building Information Modeling or architecture-related curriculum required; Bachelor degree in Architecture or technical certification in Building Information Modeling is preferred.Advanced knowledge of Revit and Rhino, with a focus in architecture and large projects, is required.Three plus years’ experience in building information modeling of architectural systems in Revit is preferred.LEED credential required within 12 months of employment." There's missing space after "preferred." and after "required." and after "preferred." We'll keep as is. Skills & Competencies paragraph: "Basic knowledge of design techniques, tools, and principals involved in production of structural models, plans and details.Proficiency in Revit and Rhino required.Proficiency in Grasshopper and Dynamo preferred.Basic knowledge about sustainability, integrated design and LEED guidelines preferred.Organized and able to handle multiple responsibilities and projects to effectively meet deadlines.Ability to communicate both verbally and in writing.Ability to work in a team environment.Ability to learn and perform standard computer modeling functions using Revit and be able to identify and help work to resolve design conflicts." Again missing spaces after periods. We'll keep as is. Benefits paragraph: "HOK invests in its people and communities, supporting both personal and professional growth through every stage of life. At HOK you’ll have a hybrid work environment, 10 paid holidays (including 2 floating holidays) and a minimum of 4 weeks of paid time off with a cash out option. HOK offers comprehensive medical, dental, and vision coverage, free mental wellness resources, life and AD&D coverage and short and long-term disability benefits. HOK supports your growing family by offering 4 weeks of paid parental leave and fertility coverage. HOK helps to fund your future financial needs with matching contributions to our 401(K) plan which includes a well-rounded investment menu as well as free guidance on retirement planning. Wherever you are in your career, HOK provides opportunities to learn, develop and utilize your skills. Continued learning is promoted through financial support and study prep for licensure exams, CEU credit opportunities, mentorship programs, and paid professional memberships." We need to ensure we don't include boilerplate like EEO etc. At end there is "HOK is an EOE, including disability/vets." That's boilerplate EEO; we should remove. Also remove lines like "Application must include both resume and portfolio (or portfolio link)." That's application instruction; remove. Also remove "Many of our roles require the use of specific software. Please refer to the Required and Preferred Software & Skills for details." That's boilerplate. Also remove "The job duties and requirements that this document describes may be altered or supplemented at any time at the sole discretion of HOK." That's boilerplate. Also remove "To learn more about designing your career with HOK, explore our current job openings." That's application instruction. Also remove "Explore some of our recent work in the HOK 2026 Design Annual and see how we're shaping the future of design." That's maybe not boilerplate but could be considered promotional; but it's substantive? It's about company; maybe we can keep in About the role? But it's not about the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not boilerplate but it's more marketing; but it's not about the role. However we already have About the role paragraph; we could incorporate that line? It's not about the role, it's about company. Could be considered part of About the role? Might be okay to keep as part of About the role? But the instruction says preserve ALL substantive information; do not invent or summarize away detail. That line is substantive about company. However the About the role section we already have a paragraph; we could add another sentence. But we must not repeat job title as heading. It's fine. But we need to decide whether to include that line. It's not explicitly about the role but it's about HOK's work. Could be considered part of About the role (company context). I'd include it as another sentence in About the role paragraph. Thus About the role paragraph: combine the two sentences: "HOK's Boston office is seeking a Architectural BIM Coordinator. This person performs model management, quality control, training, and other BIM-related assignments based on input from the project team and guidance from Design Technology leadership. Explore some of our recent work in the HOK 2026 Design Annual and see how we're shaping the future of design." We need to keep punctuation. Now produce HTML. Structure:

    About the role

    HOK's Boston office is seeking a Architectural BIM Coordinator. This person performs model management, quality control, training, and other BIM-related assignments based on input from the project team and guidance from Design Technology leadership. Explore some of our recent work in the HOK 2026 Design Annual and see how we're shaping the future of design.

    Responsibilities

    • Helps develop and maintain a BIM execution plan.
    • Organizes and maintains models for the assigned projects.
    • Works closely with project team and assists to complete projects on aggressive schedules.
    • Checks Revit models for clearances, potential conflicts, and relationships of the various parts to the whole and to one another.
    • Helps project teams maintain efficient 3D models through training and reinforcement of best practices.
    • Conducts BIM-based quality control reviews.
    • Understands and implements various Revit add-ins for increasing team productivity.
    • Coordinates project progress with regional Design Technology Manager.
    • Implements and utilizes HOK Best Practices for all projects and processes.
    • Actively seeks new knowledge related to design technology and regulations.
    • Takes personal responsibility for fostering a green workplace through sustainable work practices.

    Requirements

    Associate degree in Building Information Modeling or architecture-related curriculum required; Bachelor degree in Architecture or technical certification in Building Information Modeling is preferred.Advanced knowledge of Revit and Rhino, with a focus in architecture and large projects, is required.Three plus years’ experience in building information modeling of architectural systems in Revit is preferred.LEED credential required within 12 months of employment.

    Qualifications

  • Similar jobs