Architectural Designer

We need to output HTML fragment with sections: About the role? The posting includes description: mission statement, position overview, responsibilities (listed), requirements, qualifications, maybe skills, benefits, pay, schedule. We need to include sections only if posting has real specific content. Let's parse. Content: - Mission statement: "To create a positive impact with the people who live, work and are involved in our communities." Could be part of About the role? Might be considered description. - Position Overview: Architectural Designer ... includes responsibilities bullet list. - Then list of responsibilities (multiple paragraphs). We can treat as Responsibilities section. - Requirements: includes qualification requirements bullet list. - Physical Demands and Work Environment: could be part of Requirements or maybe separate sections like "Physical Demands" and "Work Environment". But we only create sections if posting has real specific content. They have content. Could combine into a "Working Conditions" section? But spec says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate, but not limited? Probably we should stick to those. So we can map content to these headings. - About the role: could include mission statement and position overview paragraph. - Responsibilities: list of duties. - Requirements: maybe qualifications (education, experience). Could also include skills. - Qualifications: maybe same as Requirements? Might duplicate. We could split: Requirements = experience/education; Qualifications = skills/knowledge; Skills = software proficiency. But we need to avoid thin sections. Let's see what we have: Mission statement + position overview paragraph: good for About the role. Responsibilities: multiple bullet points (we can make

• ). Qualifications: education, experience, licensure, etc. Skills: software proficiency (Revit, Forma, SketchUp, Enscape, SpecLink/Specpoint, MS Office, Zenerate, etc.) plus communication, teamwork, leadership, attention to detail, etc. Benefits, Pay, Schedule: not mentioned. So we omit those sections. Physical Demands and Work Environment: not in allowed headings; we could maybe include under Requirements? But spec says we can use those headings only; we could omit if not fitting. However we must preserve ALL substantive information; we cannot drop physical demands and work environment. If we omit a section, we lose that info. We need to incorporate it somewhere else, maybe under a generic section like "Requirements" or "About the role". But we must not invent headings not listed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive list. So we can add other headings if needed, but better to stick to given ones. However we need to preserve physical demands and work environment; we could put them under a section like "Working Conditions" but that's not in list. Could we incorporate them into "Requirements" as part of job requirements? Possibly. But they are not requirements; they are job conditions. Could be part of "About the role". Might be okay. Thus we will create sections: About the role (mission + position overview + physical demands + work environment?), Responsibilities, Requirements (education/experience/licensure), Skills (software proficiency, communication, teamwork, leadership, attention to detail, etc.). We'll omit Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Now craft HTML. We'll start with

  About the role

  then

  mission statement + position overview paragraph + physical demands + work environment combined? Might be long but okay. Better: separate paragraphs. About the role: mission statement paragraph, then position overview paragraph, then physical demands paragraph, then work environment paragraph. Then Responsibilities:

  Responsibilities

  with each duty. Then Requirements:

  Requirements

  with education, experience, licensure, etc. Then Skills:

  Skills

  with software proficiencies, communication, teamwork, leadership, attention to detail, etc. Make sure to preserve all specifics. Let's extract details. Mission statement: "To create a positive impact with the people who live, work and are involved in our communities." Position overview paragraph: "The Annex Group is seeking qualified individuals searching for careers not jobs and can operate with a team first approach. If you are someone who wants to assist in our mission and make an impact, come join our team." Actually that's after mission statement? The text: "THE ANNEX GROUP’S MISSION STATEMENT To create a positive impact with the people who live, work and are involved in our communities. The Annex Group is seeking qualified individuals searching for careers not jobs and can operate with a team first approach. If you are someone who wants to assist in our mission and make an impact, come join our team. POSITION OVERVIEW: Architectural Designer Annex Design Standard Compliance & Updates Assist project architects and designers to ensure plans are in conformance with Annex standards, applicable codes, and fund-driven requirements for affordable (LIHTC) housing projects.Assist the preconstruction team with project milestone document review, preparation, and communication.Coordinate and collaborate on projects with internal and external teams, including architects, designers, engineers, and all consultants through the design process.Participate in regular Annex design standard revisions, creation and updates. Conceptual Design and Site Feasibility Studies Assist with conceptual studies and site due diligence with the development and preconstruction team during to determine a prospective site’s feasibility. Collaborate with Annex’s civil engineer to assist with site analysis, site due diligence, assess site conditions and building site design options. Architectural Production Standards Creation Develop, create, orchestrate, update, and manage Annex’s Revit and CAD graphic standards and templates.Develop, create, update, and manage Annex’s Revit family library.Assist with the development, creation and maintenance of Annex’s design standards and apartment unit standards. Architectural Construction Administration Review and answer project RFIs, submittals, shop drawings during construction administration where TAG serves as the AOR.Conduct site visits if/when appropriate to ensure design documents compliance and to collaborate on solutions to issues that arise during the construction process. Collaborate with external engineering consultants to ensure accuracy of plans, alignment with project goals, and timely submittals." So position overview includes many responsibilities already listed. But we also have separate responsibilities list after that? Actually the text after "POSITION OVERVIEW:" includes a long string that seems to be responsibilities. Then later there is a "Requirements" section. So we should treat the POSITION OVERVIEW as responsibilities. But we also have a separate "Responsibilities" heading? Not present. The text after POSITION OVERVIEW is basically a run-on list of duties. So we can treat that as Responsibilities. Thus About the role: mission statement + maybe brief intro about seeking individuals. But the intro "The Annex Group is seeking qualified individuals searching for careers not jobs and can operate with a team first approach. If you are someone who wants to assist in our mission and make an impact, come join our team." That's more about the role? Could be part of About the role. Thus About the role: mission statement + that intro paragraph. Responsibilities: the long list after POSITION OVERVIEW. We need to split that into bullet items. Let's parse the responsibilities string: "Assist project architects and designers to ensure plans are in conformance with Annex standards, applicable codes, and fund-driven requirements for affordable (LIHTC) housing projects. Assist the preconstruction team with project milestone document review, preparation, and communication. Coordinate and collaborate on projects with internal and external teams, including architects, designers, engineers, and all consultants through the design process. Participate in regular Annex design standard revisions, creation and updates. Assist with conceptual studies and site due diligence with the development and preconstruction team during to determine a prospective site’s feasibility. Collaborate with Annex’s civil engineer to assist with site analysis, site due diligence, assess site conditions and building site design options. Develop, create, orchestrate, update, and manage Annex’s Revit and CAD graphic standards and templates. Develop, create, update, and manage Annex’s Revit family library. Assist with the development, creation and maintenance of Annex’s design standards and apartment unit standards. Review and answer project RFIs, submittals, shop drawings during construction administration where TAG serves as the AOR. Conduct site visits if/when appropriate to ensure design documents compliance and to collaborate on solutions to issues that arise during the construction process. Collaborate with external engineering consultants to ensure accuracy of plans, alignment with project goals, and timely submittals." We need to split at periods that separate sentences. Some sentences are long but okay. Now Requirements section: after "Requirements QUALIFICATION REQUIREMENTS:" we have bullet list: - A minimum of 5 years of experience in Architecture. - NAAB accredited Bachelor’s in Architecture or Master’s in Architecture degree and on course for licensure and NCARB certification. - Strong proficiency in relevant architectural software. - Candidate must have experience with modeling in Autodesk Revit and managing Autodesk Forma Design Collaboration. - Experience with SketchUp, Enscape, SpecLink or Specpoint and Microsoft Office Suite preferred. - Ability to learn and utilize Zenerate feasibility study tool for land development. - Knowledge of building codes, zoning regulations, and industry standards related to multifamily design. - Demonstrated ability to balance design aesthetics with technical functionality and constructability. - Understanding of sustainable design principles and commitment to creating environmentally responsible projects. - Demonstrates exceptional attention to detail and organizational abilities. - Willingness to ask questions and learn from senior staff. - Proficient in effective communication and teamwork. - Maintains a positive outlook and embraces a collaborative team approach. - Proven leadership skills that cultivate collaboration among the internal and external team members - Must be willing to occasional travel for construction project inspections and related items. We also have Physical Demands and Work Environment sections after that. We'll incorporate them maybe under a "Working Conditions" heading but not in list. Could we add a section "Working Conditions"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "e.g." So we could add a section like "Working Conditions". However to be safe, we could fold them into Requirements or About the role. But they are substantive; we could add a section "Working Conditions". I think it's acceptable as it's not contradictory. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use others if needed. I'll add a section "Working Conditions" with Physical Demands and Work Environment. Now Skills section: we could extract skills from Requirements that are not education/experience: proficiency in software, communication, teamwork, leadership, attention to detail, etc. But we already have many in Requirements. To avoid duplication, we could keep Requirements as education/experience/licensure, and Skills as software and soft skills. However the Requirements list includes software proficiency etc. Might be better to split: Requirements = education/experience/licensure; Skills = software, tools, communication, teamwork, leadership, attention to detail, etc. Let's do that. Thus: Requirements: - Minimum 5 years experience in Architecture. - NAAB accredited Bachelor’s or Master’s in Architecture. - On course for licensure and NCARB certification. Skills: - Strong proficiency in relevant architectural software. - Experience with modeling in Autodesk