Designer IB

We need to output HTML fragment with sections: About the role (maybe heading "About The Role" but we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "About The Role" then "Here's What You'll Do" (responsibilities) then "Here's What You'll Need" (requirements/qualifications/skills). Also benefits: mention "For a general overview of our benefits, please visit our careers page at ..." That's a link but not specific benefits; we should not create Benefits section unless posting actually states them. It only says refer to careers page; no specific benefits listed, so we should not create Benefits section. Pay and Schedule not present, so omit. We need to preserve all substantive information, remove boilerplate: navigation, EEO, scam warning, etc. Also remove duplicated lines. We need to keep the firm description? The posting includes "About Our Firm", "About Working Here". Those are not in the prescribed headings list but could be considered as part of role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings for those sections; but we can also include other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but likely we should stick to those. However we need to preserve all substantive information; we could include the firm description under a heading like "About The Firm" but not in list; maybe we can incorporate into About the role section? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine About the role, Responsibilities, Requirements, Qualifications, Skills into sections. The posting already has "About The Role" then responsibilities then requirements. We could make sections: About the role (maybe short paragraph), Responsibilities (ul), Requirements (ul) which includes education, experience, skills, etc. Could also separate Qualifications and Skills but we can combine. We must not repeat job title as heading. No Job ID. We must output only HTML fragment, no /, no markdown fences. Let's extract substantive content: About The Role: "This position will have a design/technical focus and be a member of our multi-disciplinary team, collaborating with design and technical leadership and will be an integral part of project teams. Under the direct supervision of a Licensed Architect and project leadership the primary responsibilities will include the following:" That's prose. Then "Here's What You'll Do" list: bullet points (we need to convert to

• ). Items: - Working as part of a multi-disciplinary team, provide architectural support to the Project Architect or Project Designer in the design, selection, coordination, and detailing of architectural materials and systems. - Build physical building models. - Produce architectural documentation under the guidance of the Project Architect, Project Manager or Project Designer. - Participate in preparation of graphics materials and images for client presentations. - Participate in research initiatives as directed by the Project Architect or Project Manager. - Assist project leadership in all activities during conceptual design through construction documents. - Participate in the architectural design process in a support role. - Review shop drawing submittals under the direction of the Project Architect. - Respond to client’s questions and comments with supervisory guidance. - Work in the REVIT model to produce plans, elevations and sections under the guidance of the Project Architect or Project Designer. - Communicate with other disciplines to ensure coordination of project documents. - Attend project team meetings and participate in project presentations. - Perform other duties as assigned. Then "Here's What You'll Need": list: - Bachelor or Master’s degree in Architecture or related field required. - Bachelor or Master’s degree in Architecture from an accredited program preferred. - Minimum 2 years of related professional experience required. - Actively pursuing Architectural Registration in the United States preferred. - Strong creative design portfolio is essential as are strong communication, teamwork, presentation, graphics, organizational skills and the ability to handle multiple projects. - Demonstrates independent judgment in handling responsibilities at this level. - Proficiency with Revit, Enscape, Bluebeam, Microsoft Office, and Adobe Creative Suite required. Then "For a general overview of our benefits, please visit our careers page at https://www.cannondesign.com/careers/benefits" - we should not create Benefits section because no specifics. Could we include a

  with that link? Possibly under About the role or a separate "Benefits" but we shouldn't create Benefits heading if no specific benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states benefits exist but refers to page; does that count as stating them? It says "For a general overview of our benefits, please visit our careers page". That's a statement that benefits exist but not detailing them. I'd interpret that as not enough to create a Benefits section with specifics. Safer to omit Benefits section entirely, but we could include a

  under About the role or a separate "Benefits" paragraph without heading? 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 we should follow that pattern. If we don't have specific benefits, we should not create a Benefits heading. So we can omit that sentence entirely? But we must preserve ALL substantive information. The sentence about benefits is substantive? It's a pointer to benefits page. Might be considered substantive. We could include it as a

  under About the role or maybe under a separate "Benefits" paragraph without heading? But the instruction says to use

  for section headings (list). It doesn't say we cannot have

  without heading. So we could add a

  after the sections that mentions benefits link. That would preserve info without creating a Benefits heading. That seems okay. Then "About Our Firm" and "About Working Here" and DEI etc. Those are boilerplate? They are substantive about firm but maybe not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Our Firm" and "About Working Here" are not exactly boilerplate; they describe firm culture. Might be considered substantive. Should we keep them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep them. But we need to format them. They are not in the prescribed headings list, but we could treat them as part of About the role or maybe a separate section like "About The Firm". However 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 we could still use

  for "About Our Firm" and "About Working Here". However they said "e.g." meaning examples, not exhaustive list. So we can use

  for other headings as needed. But we should prefer few substantive sections over many thin ones. So maybe combine "About Our Firm" and "About Working Here" into a single section like "About CannonDesign". That would be substantive. Let's extract the substantive paragraphs: About Our Firm: "CannonDesign is a design practice where strategy, experience, architecture, engineering, and social impact converge. We don’t just dream up solutions — we create and bring them to life in ways to solve some of the biggest challenges facing our clients and the society. At the heart of everything we do is Living-Centered Design, a bold commitment to using our talents to not just improve the world but to truly reshape it for the better. It’s more than a philosophy — it’s who we are, and it drives us to make a meaningful, lasting difference every day." About Working Here: "We are relentless in our pursuit of client adoration (not simply satisfaction). Consistent delivery of the best service is what we are about. We are committed to ensuring our practice provides equal opportunities for all employees, as we strive to connect with communities around us and focus on the future of design. We support equity, diversity, and inclusion efforts that benefit all employees through the leadership of our DEI Council, our Employee Resource Groups which are open to everyone, and other community initiatives. We’re about communication and transparency here. If you want to talk to someone about an idea you have, or a challenge that needs addressing, we’re ready for you." Then there is scam warning and application instructions etc which we need to remove. Also "Please note that candidates can only apply to our positions on our company Careers site. It's not uncommon for scammers to create positions that look legitimate on other sites; never enter your information or apply for CannonDesign positions on any platform. Should an issue arise that you feel we should be aware of, please contact us. Please provide your resume and portfolio when applying. As a condition of employment, all employees are expected to complete mandatory training, including compliance training, within required timeframes and adhere to our internal policies and our Code of Conduct." This includes application instructions and scam warning; we should remove. Then EEO statement: "CannonDesign is an Equal Opportunity Employer...." Remove. Thus we keep: About The Role paragraph, Responsibilities list, Requirements list, Benefits link paragraph, About Firm/Working Here combined. Now format:

  About the role

  This position will have a design/technical focus and be a member of our multi-disciplinary team, collaborating with design and technical leadership and will be an integral part of project teams. Under the direct supervision of a Licensed Architect and project leadership the primary responsibilities will include the following:

  Responsibilities

  • Working as part of a multi-disciplinary team, provide architectural support to the Project Architect or Project Designer in the design, selection, coordination, and detailing of architectural materials and systems.
  • Build physical building models.
  • Produce architectural documentation under the guidance of the Project Architect, Project Manager or Project Designer.
  • Participate in preparation of graphics materials and images for client presentations.
  • Participate in research initiatives as directed by the Project Architect or Project Manager.
  • Assist project leadership in all activities during conceptual design through construction documents.
  • Participate in the architectural design process in a support role.
  • Review shop drawing submittals under the direction of the Project Architect.
  • Respond to client’s questions and comments with supervisory guidance.
  • Work in the REVIT model to produce plans, elevations and sections under the guidance of the Project Architect or Project Designer.
  • Communicate with other disciplines to ensure coordination of project documents.
  • Attend project team meetings and participate in project presentations.
  • Perform other duties as assigned.

  Requirements

  • Bachelor or Master’s degree in Architecture or related field required.
  • Bachelor or Master’s degree in Architecture from an accredited program preferred.
  • Minimum 2 years of related professional experience required.
  • Actively pursuing Architectural Registration in the United States preferred.
  • Strong creative design portfolio is essential as are strong communication, teamwork, presentation, graphics, organizational skills and the ability to handle multiple projects.
  • Demonstrates independent judgment in handling responsibilities at this level.
  • Proficiency with Revit, Enscape, Bluebeam, Microsoft Office, and Adobe Creative Suite required.

  For a general overview of our benefits, please visit our careers page at https://www.cannondesign.com/careers/