Sector Leader - Mission Critical
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We have content about role: "HED is looking to add an experienced team member...". That's about the role. So we can have About the role
with paragraph summarizing that.
Responsibilities: The Essential Functions section lists responsibilities: Technical/Design Leadership, Sector Development and Business Growth, Thought Leadership and Mentorship, Chargeability and Engagement. So we can put those under Responsibilities.
Requirements: The posting includes "Requirements" heading with bullet list: Bachelor’s degree, Professional licensure, Minimum 15 years experience, etc. So we can put that under Requirements.
Qualifications: Might overlap with Requirements; but we have also "Preferred" LEED accreditation. Could treat as Qualifications. But we need to avoid thin sections. We could combine Requirements and Qualifications? But instruction says use those headings if content exists. We have both Requirements and maybe Qualifications (like LEED accreditation preferred, understanding of data center sector, client relationship skills, strong business skills, extensive knowledge, ability to motivate others, etc). Those are more like Skills/Qualifications. Could put them under Skills.
We have no explicit Benefits, Pay, Schedule. So we should not include those sections.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to preserve all substantive information. So we need to include all details from the posting.
Let's extract:
About the role: "HED is looking to add an experienced team member with a background in architecture and/or engineering who will be accountable for leading the Mission Critical sector, with a focus on data center projects, ensuring that the health of the entire project portfolio for the sector is in excellent condition. Also responsible for understanding and representing client requirements to the project teams."
About HED: description of team culture, values.
Essential Functions broken into categories:
Technical/Design Leadership:
- Lead or co-lead technical and design efforts on complex, multi-disciplinary projects.
- Elevate project quality through design reviews, cross-disciplinary collaboration, and quality control protocols.
- Solve complex technical challenges and advocate for buildable, sustainable, and innovative solutions.
- Provide mentorship to team members in technical delivery, integrated design, and documentation practices.
Sector Development and Business Growth:
- Contribute to pursuit strategies, sector planning sessions, and client engagement tactics with a developing ownership mindset.
- Lead select project pursuits and participate in cross-disciplinary teams to reinforce HED’s integrated design philosophy.
- Collaborate with sector and studio leadership to identify strategic priorities and support near-term growth initiatives.
- Support internal marketing and communications through storytelling, case studies, and showcasing design excellence.
Thought Leadership and Mentorship:
- Develop and publish sector-focused thought leadership content.
- Represent HED at local and regional industry events and conferences.
- Mentor emerging professionals in sector-specific practices and technical growth areas.
Chargeability and Engagement:
- Maintain a high level of project chargeability (~65-75%) while contributing meaningfully to business development, talent cultivation, and sector visibility.
Requirements:
- Bachelor’s degree in architecture or engineering is required.
- Professional licensure or board approved certification is required.
- Minimum 15 years of professional experience with a minimum of five years of Data Center design experience.
- LEED accreditation is preferred.
- Understanding of data center sector, client relationship skills and strong business skills.
- Extensive knowledge of all aspects of professional services from marketing through project close-out, including design and technical expertise.
- Ability to motivate others and develop teamwork; excellent writing and speaking skills, and strong organizational skills.
- Ability to work well with others under deadline situations.
- Detail-oriented, self-motivated, enthusiastic, and flexible.
- Strong business acumen.
- Professionalism, assertiveness, decisiveness, integrity, and the ability to lead and influence, as appropriate for a senior level position that is highly visible to clients and staff.
- Ability to interact appropriately in various business and social settings with all types of people.
- Models HED’s core values.
- Capable of performing all the duties of a project manager is required.
- Computer literate.
Physical Requirements:
- Prolonged periods of computer use and active participation in collaborative sessions.
- Frequent engagement in verbal, virtual, and written communication.
- Regular travel for client meetings, project reviews, and industry events.
Work Environment:
- We embrace a hybrid model that promotes both autonomy and collaboration.
- In-office presence supports mentoring, creative dialogue, and collective innovation.
- Sector Leaders are expected to actively contribute to firm culture and thought leadership through in-person engagement.
Other Duties:
- This description outlines primary responsibilities but is not exhaustive. Responsibilities may evolve with changing sector goals, project needs, and firm-wide priorities.
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications?, Skills? We have many details that could go under Requirements (education, licensure, experience, LEED preferred). Qualifications could be things like understanding of data center sector, client relationship skills, strong business skills, extensive knowledge, ability to motivate others, etc. Skills could be things like ability to motivate others, excellent writing/speaking, organizational skills, etc. But we might just put all under Requirements and maybe Skills. However we need to avoid thin sections. Let's think: The posting already has a "Requirements" heading. So we should use that heading for the bullet list under Requirements. Then we could have a separate "Skills" heading for abilities like ability to motivate others, excellent writing and speaking skills, strong organizational skills, ability to work well under deadline, detail-oriented, self-motivated, enthusiastic, flexible, strong business acumen, professionalism, assertiveness, decisiveness, integrity, ability to lead and influence, ability to interact appropriately, models core values, capable of performing PM duties, computer literate. That seems like a lot but could be considered Skills.
Qualifications could be things like LEED accreditation preferred, understanding of data center sector, client relationship skills, strong business skills, extensive knowledge of professional services. But those overlap with Skills. Might be better to combine Requirements and Qualifications into one section? But instruction says use those headings if content exists. We have content for Requirements (education, licensure, experience). We have content for Qualifications (LEED preferred, understanding of data center sector, client relationship skills, strong business skills, extensive knowledge). We have content for Skills (ability to motivate others, excellent writing/speaking, organizational skills, etc). We could create three sections: Requirements, Qualifications, Skills. That seems okay.
But we must ensure we don't create sections with filler like "commensurate with experience". We have real content.
We also need to include About HED description maybe under About the role? Or we could have a separate "About HED" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map About HED to About the role? Actually About the role is about the position, not the company. But we have both. We could include About the role paragraph (the first paragraph) and then maybe a separate paragraph about HED under same heading? Or we could add a second paragraph under About the role describing HED's culture. That seems acceptable: About the role section can contain both role description and company overview.
Thus:
About the role
HED is looking to add an experienced team member with a background in architecture and/or engineering who will be accountable for leading the Mission Critical sector, with a focus on data center projects, ensuring that the health of the entire project portfolio for the sector is in excellent condition. Also responsible for understanding and representing client requirements to the project teams.
We are a team that is full of ideas, experience, creativity, passionate opinions, insatiable curiosity, uncompromising integrity, commitment, and skill. Our culture is about aspiration, embracing change and challenges, listening to (and learning from) each other, encouraging continual learning, and inspiring collective growth. As an inclusive, integrated architecture and engineering practice, we value the diversity of perspectives, experiences, abilities, and expertise that advance both the work we do, and the world we share.
Then Responsibilities: list the four categories each with sub-items. Use- for each duty. Could nest? Probably just flat list of all duties. But we could group with headings inside? Not allowed; only h3 for section headings. So we can just list all duties as
- . Might be long but okay.
We need to preserve all substantive information. So we need to include each bullet.
Let's compile duties:
Technical/Design Leadership:
- Lead or co-lead technical and design efforts on complex, multi-disciplinary projects.
- Elevate project quality through design reviews, cross-disciplinary collaboration, and quality control protocols.
- Solve complex technical challenges and advocate for buildable, sustainable, and innovative solutions.
- Provide mentorship to team members in technical delivery, integrated design, and documentation practices.
Sector Development and Business Growth:
- Contribute to pursuit strategies, sector planning sessions, and client engagement tactics with a developing ownership mindset.
- Lead select project pursuits and participate in cross-disciplinary teams to reinforce HED’s integrated design philosophy.
- Collaborate with sector and studio leadership to identify strategic priorities and support near-term growth initiatives.
- Support internal marketing and communications through storytelling, case studies, and showcasing design excellence.
Thought Leadership and Mentorship:
- Develop and publish sector-focused thought leadership content.
- Represent HED at local and regional industry events and conferences.
- Mentor emerging professionals in sector-specific practices and technical growth areas.
Chargeability and Engagement:
- Maintain a high level of project chargeability (~65-75%) while contributing meaningfully to business development, talent cultivation, and sector visibility.
We'll output as
- each.
Requirements: bullet list:
- Bachelor’s degree in architecture or engineering is required.
- Professional licensure or board approved certification is required.
- Minimum 15 years of professional experience with a minimum of five years of Data Center design experience.
- LEED accreditation is preferred.
Qualifications: bullet list:
- Understanding of data center sector, client relationship skills and strong business skills.
- Extensive knowledge of all aspects of professional services from marketing through project close-out, including design and technical expertise.
Skills: bullet list:
- Ability to motivate others and develop teamwork; excellent writing and speaking skills, and strong organizational skills.
- Ability to work well with others under deadline situations.
- Detail-oriented, self-motivated, enthusiastic, and flexible.
- Strong business acumen.
- Professionalism, assertiveness, decisiveness, integrity, and the ability to lead and influence, as appropriate for a senior level position that is highly visible to clients and staff.
- Ability to interact appropriately in various business and social settings with all types of people.
- Models HED’s core values.
- Capable of performing all the duties of a project manager is required.
- Computer literate.
Physical Requirements and Work Environment: These are not in allowed headings but could be included under Responsibilities? Or maybe we could add a section "Working Conditions"? Not allowed. The instruction says use headings only from list; we should not create other headings. So we need to incorporate Physical Requirements and Work Environment somewhere else, maybe under Responsibilities as additional items? Or we could add a paragraph under About the role? But they are substantive; we must preserve all substantive information. We could add them as
paragraphs after the sections, without a heading?
- each.
Requirements: bullet list:
- Bachelor’s degree in architecture or engineering is required.
- Professional licensure or board approved certification is required.
- Minimum 15 years of professional experience with a minimum of five years of Data Center design experience.
- LEED accreditation is preferred.
Qualifications: bullet list:
- Understanding of data center sector, client relationship skills and strong business skills.
- Extensive knowledge of all aspects of professional services from marketing through project close-out, including design and technical expertise.
Skills: bullet list:
- Ability to motivate others and develop teamwork; excellent writing and speaking skills, and strong organizational skills.
- Ability to work well with others under deadline situations.
- Detail-oriented, self-motivated, enthusiastic, and flexible.
- Strong business acumen.
- Professionalism, assertiveness, decisiveness, integrity, and the ability to lead and influence, as appropriate for a senior level position that is highly visible to clients and staff.
- Ability to interact appropriately in various business and social settings with all types of people.
- Models HED’s core values.
- Capable of performing all the duties of a project manager is required.
- Computer literate.
Physical Requirements and Work Environment: These are not in allowed headings but could be included under Responsibilities? Or maybe we could add a section "Working Conditions"? Not allowed. The instruction says use headings only from list; we should not create other headings. So we need to incorporate Physical Requirements and Work Environment somewhere else, maybe under Responsibilities as additional items? Or we could add a paragraph under About the role? But they are substantive; we must preserve all substantive information. We could add them as