Senior Project Architect

We need to output HTML fragment with sections: About the role? The posting includes intro about HDR culture, then role description. We need headings for sections present: maybe "About the role", "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". Must only include sections if posting has real specific content. Let's parse content: - Intro: "At HDR, our employee-owners..." that's about company culture, could be "About the role"? Actually it's about company. Could be "About HDR" but not in allowed headings. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for introductory description of role and company culture. - Responsibilities: bullet list of duties after "In the role of Senior Project Architect, we'll count on you to:" then many items. Those are responsibilities. - Requirements: there are "Preferred Qualifications" and "Required Qualifications". Could combine into Requirements or Qualifications sections. Allowed headings: Requirements, Qualifications. We need decide. Probably use "Qualifications" for both required and preferred? But we have both sections. Could split: "Required Qualifications" and "Preferred Qualifications" but not allowed headings. Could use "Qualifications" for required, and maybe "Preferred Qualifications" as a subsection? Not allowed. Better to use "Requirements" for required qualifications, and "Preferred Qualifications" maybe as part of Skills? But we have Skills heading allowed. Could put software skills under Skills. Let's map: - Required Qualifications: Bachelor's degree, 10 years experience, Registered Architect, MS Office, excellent written/communication, analytical/problem-solving, proficient in Autodesk Revit, familiarity with related tools, demonstrated graphic presentation skills, experience preparing/layout architectural contract documents and specifications, strong knowledge of codes and good planning skills, attitude/commitment to employee-owned culture. - Preferred Qualifications: Master's degree, Registered Architect in CA, experience on large-scale health projects in CA, OSHPD-1 and OSHPD-3 projects, sustainable design/LEED desired but not required, knowledge of Photoshop, Illustrator, SketchUp, 3-D Studio Max not required, Rhino and Grasshopper experience required? Actually says "Rhino and Grasshopper experience Required Qualifications"? Wait reading: "Knowledge of Photoshop, Illustrator, SketchUp and 3-D Studio Max but not required.Rhino and Grasshopper experience Required Qualifications". It seems Rhino and Grasshopper experience is required? Actually ambiguous. The line: "Knowledge of Photoshop, Illustrator, SketchUp and 3-D Studio Max but not required.Rhino and Grasshopper experience Required Qualifications". Probably they meant Rhino and Grasshopper experience required. We'll treat as required skill. Thus we can have Skills section for software: Autodesk Revit, Rhino, Grasshopper, Photoshop, Illustrator, SketchUp, 3-D Studio Max, MS Office. But we also have "Excellent written and communication skills", "Excellent analytical and problem-solving skills", "Demonstrated graphic presentation skills". Those could be Skills as well. Thus we can have Skills section. Benefits: described: comprehensive benefits package includes medical, dental, vision, short and long-term disability, life insurance, employee assistance program, paid time away, parental leave, paid holidays, retirement savings plan with employer match, employee referral bonus, tuition reimbursement. Pay: "$105,000- $157,000" for Los Angeles and San Diego, CA. Schedule: "Full-time". Also Employee Status: Regular. Thus we have sections: About the role (intro), Responsibilities (list), Qualifications (maybe combine required and preferred?), Skills (software and soft skills), Benefits, Pay, Schedule. We must not repeat job title as heading. Use

for each section heading. We must use

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

  . We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, etc. Remove duplicated lines. We need to ensure we include all substantive info from posting. Let's extract sections: About the role: The introductory paragraphs about HDR culture, employee-owners, welcoming environment, diversity, impact, story link, each role makes difference, read further to learn how you could help make great things possible. Also maybe include the link? The link is "Watch Our Story: ' https://www.hdrinc.com/our-story'". Should we keep? It's substantive? It's a link to story. Probably keep as part of About the role. Thus About the role content: combine those paragraphs. Responsibilities: list each duty after "In the role of Senior Project Architect, we'll count on you to:" then items separated by line breaks. Let's list them: - Lead a multidiscipline team and perform layout and detailing on architectural projects - Independently coordinate work of a multidiscipline team through multiple phases of a project - Establish owner/client and internal meetings, and participate in reviews with various governing agencies for code compliance - Conduct work sessions at project site in conjunction with Project Manager and other disciplines - Coordinate workload of team members through multiple phases to complete documents on schedule - Review architectural documents for areas of conflict with all disciplines - Perform QA/QC and technical reviews - Write and edit architectural specifications - Coordinate with and assist affected disciplines with addenda, RFIs, CPRs and change orders - Incorporate agreed-upon changes into project documents - Lead projects in a dual management role as needed - Provide construction contract administration as needed - Perform other duties as needed We should keep all. Qualifications: Could split required and preferred but we have only Qualifications heading allowed. We could include both required and preferred under Qualifications, maybe separate with

  headings? Not allowed to add extra headings. Could use

  to label "Required Qualifications:" and "Preferred Qualifications:" inside the Qualifications section. That's okay. Thus under

  Qualifications

  , we have

  Required Qualifications:

  then
  list of required items. Then

  Preferred Qualifications:

  then
  list. But we must not invent headings; using

  with bold is fine. List required qualifications: - Bachelor's degree in Architecture or closely related field - Minimum of 10 years experience - Registered Architect - Experience with Microsoft Office (Word, Excel, Project Schedule) - Excellent written and communication skills - Excellent analytical and problem-solving skills - Proficient in use of Autodesk Revit and familiarity with related tools and process - Demonstrated graphic presentation skills - Must have experience in preparation and layout of architectural contract documents and specifications - Strong knowledge of codes and good planning skills - An attitude and commitment to being an active participant of our employee-owned culture is a must Also Rhino and Grasshopper experience? The line: "Knowledge of Photoshop, Illustrator, SketchUp and 3-D Studio Max but not required.Rhino and Grasshopper experience Required Qualifications". Likely Rhino and Grasshopper experience is required. So add: - Rhino and Grasshopper experience Also maybe "Experience on OSHPD-1 and OSHPD-3 projects" is preferred, not required. Preferred qualifications list: - Master's degree in Architecture - Registered Architect in the State of California - Experience on large-scale health projects in California - Experience on OSHPD-1 and OSHPD-3 projects - Experience and/or interest in sustainable design/LEED desired but not required - Knowledge of Photoshop, Illustrator, SketchUp and 3-D Studio Max (not required) – we can note as preferred but not required. We'll include them as preferred. Skills section: Could include software skills and soft skills. But we already have some in qualifications. To avoid duplication, maybe we put software skills under Skills, and keep qualifications focused on education/experience/licensure. However the instructions: "Use

  • for any list of duties/requirements/benefits". So we can have Skills section for list of skills (software, etc.). We'll include: - Autodesk Revit (proficient) - Rhino and Grasshopper - Photoshop, Illustrator, SketchUp, 3-D Studio Max (knowledge) - Microsoft Office (Word, Excel, Project Schedule) - Graphic presentation skills - Written and communication skills - Analytical and problem-solving skills But note some of these overlap with qualifications. Might be duplication but okay as long as we preserve info. However we risk repeating same content in two sections; but instructions say preserve ALL substantive information; duplication is okay if it's in original? The original had them in qualifications; not separate skills section. But we can still create Skills section to satisfy allowed headings if we have content. However we must not create a section unless posting has real specific content for it. The posting does mention skills like "Excellent written and communication skills", "Excellent analytical and problem-solving skills", "Proficient in use of Autodesk Revit", "Demonstrated graphic presentation skills", "Knowledge of Photoshop, Illustrator, SketchUp and 3-D Studio Max", "Rhino and Grasshopper experience". So we have specific content for skills. So we can create Skills section. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Now Benefits: list as
    . Benefits items: - medical - dental - vision - short and long-term disability - life insurance - employee assistance program - paid time away - parental leave - paid holidays - retirement savings plan with employer match - employee referral bonus - tuition reimbursement Also note: "Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits." Could include as a note

    . Pay: "$105,000- $157,000" for Los Angeles and San Diego, CA. Also note "The expected compensation range for this position depends upon skills, experience, education and geographical location." Include as

    . Schedule: "Full-time". Also Employee Status: Regular. Could include as

    "Schedule: Full-time (Regular employee status)". Or separate. We must not include boilerplate like EEO, etc. Now produce HTML fragment. We need to wrap each section in

    heading then content. For About the role: include paragraphs. Let's craft:

    About the role

    At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we work to weave diversity, equity, and inclusion into our work and foster a sense of belonging throughout the company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story. Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world.

    That's good. Responsibilities:

    Responsibilities

    with each duty. Qualifications:

    Qualifications

    Required Qualifications:

    list required.

    Preferred Qualifications:

    list preferred. Skills:

    Skills

    list skills. Benefits:

    Benefits

    list benefits.

    Note: Stated benefits are for full-time regular positions; temporary and part-time roles