Senior Architect | Workplace

We need to output HTML fragment with sections: Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: - About the role: there is a paragraph after "At BHDP, we believe..." and "Role Summary". That's about the role. So we can have

About the role

with that prose. - Responsibilities: there is a list of responsibilities. So

Responsibilities

with

• items. - Qualifications: there is a list of qualifications (Bachelor of Architecture..., 12+ years, Licensed Architect, Advanced Revit knowledge, etc). So

  Qualifications

  with
  . - Skills: maybe we can extract skills from qualifications? The posting includes "Advanced Revit knowledge", "Advanced knowledge of production-ready visualization capabilities (SketchUp, Enscape, Lumion)", "Demonstrated capability to delegate, coach, and raise team performance", "Demonstrated initiative; sees challenges as opportunities", "Strong attention to detail", "Strong communication and collaboration within a team", "Models professional workplace behaviors: reliable follow-through, constructive feedback, and calm, solutions-oriented communication". Those could be considered skills. But we already have Qualifications section; maybe we can combine? The instruction says prefer a few substantive sections over many thin ones. Could we put skills under Qualifications? But they ask to use headings for Skills if content exists. We have skill-like content. Could create a Skills section with those bullet points. However we must not repeat content. The qualifications list includes some of those as separate bullet points. Might be okay to have both Qualifications and Skills sections, but we risk duplication. Better to combine qualifications and skills into one section? The headings list includes both Qualifications and Skills; we can decide to include only Qualifications if it covers skills. The qualifications list includes "Advanced Revit knowledge", "Advanced knowledge of production-ready visualization capabilities", "Demonstrated capability to delegate, coach, and raise team performance", "Demonstrated initiative; sees challenges as opportunities", "Strong attention to detail", "Strong communication and collaboration within a team", "Models professional workplace behaviors". Those are skills. So Qualifications section can contain those bullet points. So we may not need a separate Skills section. - Benefits: there is a paragraph: "Our comprehensive benefit package includes a competitive salary, medical, dental, vision, disability, flexible spending accounts, paid holidays, paid time off, and a 401(k)". So we have Benefits section. - Pay: Not explicitly stated; only "competitive salary" but no specific number. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have. Pay: we have only "competitive salary" which is vague but still states that there is a competitive salary. Is that considered stating pay? It says "competitive salary" but no specifics. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Does "competitive salary" count as stating them? It's a statement about pay but not a specific amount. Might be considered stating that there is a competitive salary, which is a pay detail. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive salary" is somewhat vague but not exactly filler; it's a statement that salary is competitive. I'd lean to include Pay section with that statement? But they said prefer a few substantive sections over many thin ones. Could combine Pay into Benefits? But Benefits already includes "competitive salary". Actually the benefits paragraph includes "competitive salary". So we could put that in Benefits section and not create separate Pay. That would avoid thin Pay section. - Schedule: The posting includes "Work Mode: Monday – Friday; 8:00 – 5:00; In-Office Monday – Thursday; Hybrid (remote or in-office) Friday". That's schedule info. So we can create Schedule section with that detail. - Also there is "FLSA: Exempt", "Work Mode", "Employment Type: Full-time". Those could be folded into a short

  maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph with location, FLSA, employment type, work mode maybe. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include location (Charlotte, NC), FLSA Exempt, Work Mode details, Employment Type Full-time. We can put that in a

  after the About the role heading maybe. We must not include boilerplate like EEO, legal, etc. Remove those. We must not repeat job title as heading. We must output only HTML fragment. Let's structure:

  About the role

  At BHDP, we believe great design does more than define spaces—it influences behavior, drives performance, and creates meaningful experiences. Guided by our purpose to Inspire People and Impact Results, By Design, we collaborate across architecture, interiors, strategy, and research to solve complex challenges in integrated ways. Here, your ideas matter, your voice is heard, and your work has the power to shape experiences that truly make a difference.

  Location: Charlotte, NC. FLSA: Exempt. Employment Type: Full-time. Work Mode: Monday – Friday; 8:00 – 5:00; In-Office Monday – Thursday; Hybrid (remote or in-office) Friday.

  Then Responsibilities:

  Responsibilities

  • Provides project-specific technical leadership by setting clear expectations, assigning ownership, and driving follow-through on high-risk decisions and deliverables.
  • Serves as the primary project technical expert and risk steward, ensuring decisions are documented and implemented consistently with BHDP standards, while supporting the PM with client-ready guidance on risks, options, and impacts.
  • Leads and enforces QA/QC at key milestones by setting clear team expectations and ensuring critical comments are resolved before issuance.
  • Assigns owners and due dates, drives follow-through to verified closure, and drives root-cause correction and project delivery standards reinforcement—serving as a trusted advisor by communicating key risks, options, and impacts to the Project Manager and client.
  • Delivers high-quality technical solutions efficiently on assigned projects by standardizing repeatable approaches and focusing effort on high-risk interfaces.
  • Reduces redesign/rework and protects fee and schedule through coordination, clear documentation, disciplined decision-making, and early issue resolution—preventing late-stage changes and supporting predictable client delivery.
  • Develops Architects and Designers on assigned projects through coaching that teaches the “why” via real-time feedback and live markups and reinforces growth through documented development goals and performance input.
  • Creates and reinforces reusable learning assets that measurably improve others’ quality, independence, while reducing repeat errors over time.
  • Ensures team compliance with BHDP delivery platforms and digital standards (Revit template discipline, model/sheet hygiene, and naming/issue protocols) and uses tools effectively (Bluebeam, issue/decision logs) to drive coordination, documentation clarity, and QA/QC closure.
  • Prevents workflow and tool breakdowns from creating rework, coordination drift, milestone delays, or client-facing surprises.
  Qualifications:

  Qualifications

  • Bachelor of Architecture degree (NAAB accredited program preferred)
  • 12+ years in the design and/or architecture industry
  • Licensed Architect
  • Advanced Revit knowledge – independently deliver defined drawing packages/projects and teach others on best practice.
  • Advanced knowledge of production-ready visualization capabilities (SketchUp, Enscape, Lumion)
  • Demonstrated capability to delegate, coach, and raise team performance
  • Demonstrated initiative; sees challenges as opportunities
  • Strong attention to detail
  • Strong communication and collaboration within a team
  • Models professional workplace behaviors: reliable follow-through, constructive feedback, and calm, solutions-oriented communication with co-workers and clients
  Benefits:

  Benefits

  Our comprehensive benefit package includes a competitive salary, medical, dental, vision, disability, flexible spending accounts, paid holidays, paid time off, and a 401(k), which aligns with our commitment to rewarding our high-performing professionals.

  Schedule:

  Schedule

  Monday – Friday; 8:00 – 5:00; In-Office Monday – Thursday; Hybrid (remote or in-office) Friday.

  We already included work mode in About the role paragraph; but we also have schedule section. Might be duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we include schedule section, we should not duplicate the same info elsewhere? It's okay to have it in both places? Might be considered duplication but not prohibited. However they said remove duplicated lines. So we should avoid duplicating the same sentence. We already included work mode details in the About the role paragraph. If we also create a Schedule section with same info, that's duplication. Better to not duplicate: we can put schedule info only in Schedule section and not repeat in About the role. But we need to include location, FLSA, employment type somewhere. We can put those in a short paragraph under About the role, and move schedule details to Schedule section. Thus: About the role paragraph: location, FLSA, employment type. Schedule section: the work mode details. Let's craft. About the role:

  At BHDP, we believe great design does more than define spaces—it influences behavior, drives performance, and creates meaningful experiences. Guided by our purpose to Inspire People and Impact Results, By Design, we collaborate across architecture, interiors, strategy, and research to solve complex challenges in integrated ways. Here, your ideas matter, your voice is heard, and your work has the power to shape experiences that truly make a difference.

  Location: Charlotte, NC. FLSA: Exempt. Employment Type: Full-time.

  Schedule section:

  Schedule

  Monday – Friday; 8:00 – 5:00; In-Office Monday – Thursday; Hybrid (remote or in-office) Friday.

  Now we have sections: About the role, Responsibilities, Qualifications, Benefits, Schedule. We should not include Pay section because we already mentioned competitive salary in Benefits; but we could keep it there. Benefits paragraph includes competitive salary. That's fine. Check for any other sections: Skills? Not needed. Check for any leftover substantive info: "Physical and Mental Demands" etc. That's boilerplate? It's about physical demands; could be considered substantive but it's generic. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical and Mental Demands might be considered boilerplate? It's not EEO but it's a generic description. Might be considered part of the job description; but it's not unique. However it's substantive info about demands. Should we keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep Physical and Mental Demands if it's substantive. It includes: Sustained attention to detail, Sitting/standing, Occasional lifting of 20 pounds or less, Ability to work in an open office environment. That's specific. We could create a section maybe "Physical and Mental Dem