Inclusion Programs & External Partnerships Lead
Truist · Charlotte, NC · 1 mo ago
ConsultingFull-time
We need to output HTML fragment with sections: About the role? The posting includes description after "Please review the following job description:" and then paragraphs. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We have:
- About the role: The initial description: "As an Inclusion Programs & External Partnerships Lead, you’ll help turn enterprise priorities into programs and partnerships that strengthen teammate engagement, support a culture of belonging, and create business-aligned community impact. In this role, you will combine strategy, governance, program execution, relationship management, and measurement to deliver consistent, scalable outcomes across the enterprise." That's a prose paragraph.
- Responsibilities: The "What You’ll Do" and "Essential Duties And Responsibilities" sections. We can combine into a list of duties. The posting includes bullet-like sentences but not actual bullet list. We need to output
- for any list of duties/requirements/benefits. So we need to extract each duty as list items.
Duties listed:
- Lead the design, implementation, and ongoing management of enterprise programs that support business priorities, teammate experience, and organizational culture.
- Create governance frameworks, operating models, standards, decision rights, escalation paths, and success measures that enable responsible and consistent execution.
- Build and manage strategic relationships with community, nonprofit, civic, professional association, vendor, and enterprise partners to expand reach and deliver business-aligned impact.
- Translate strategy into repeatable processes, tools, documentation, reporting routines, and leader resources that strengthen accountability and program adoption.
- Lead the design, implementation, and management of enterprise programs that support business priorities, teammate experience, and community engagement. (some duplication)
- Develop governance frameworks, operating models, standards, decision rights, escalation paths, and measures of success.
- Establish repeatable processes, documentation, reporting routines, and operating practices that promote consistency, accountability, and responsible execution.
- Partner with senior leaders, business partners, and internal and external partners to align program priorities with enterprise goals and The Truist Way.
- Build relationships with business, community, nonprofit, civic, vendor, and enterprise partners to strengthen engagement and business-aligned impact.
- Lead cross-functional planning, project management, change readiness, communications, issue resolution, and impact reporting.
- Develop leader resources, presentations, talking points, and teammate-facing communications that support program adoption and execution.
- Use data to evaluate program effectiveness, risks, dependencies, operational progress, and business impact.
- Identify trends, risks, opportunities, and emerging needs; recommend solutions and continuous improvements.
- Lead matrixed project teams, as applicable.
We need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep all, even if duplicates? Might be okay to keep duplicates but could be considered redundant. However they said preserve all substantive information; duplicates are substantive? Might be considered duplication but still part of posting. Safer to keep them as they appear, but we could combine similar? Might be summarizing away detail. Better to keep each bullet as appears, even if similar.
But we need to output
- for any list of duties/requirements/benefits. So we can create a
- with each duty as
- . We'll include all listed duties.
- Requirements: The posting includes "Regular or Temporary: Regular Language Fluency: English (Required) Work Shift: 1st shift (United States of America)" and also "Position has in office expectations and can be located in our Atlanta, GA, or Charlotte, NC office. *****This is not a remote opportunity". Also maybe "Regular or Temporary: Regular". Also "Language Fluency: English (Required)". Also "Work Shift: 1st shift (United States of America)". Also location info. Also maybe "Regular or Temporary: Regular". We need to decide if these go under Requirements or maybe a separate section like "Details". The allowed headings are limited; we can put these under Requirements or maybe under About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can place location, shift, language fluency, regular/temporary under Requirements (or maybe a separate "Details" not allowed). Probably Requirements is appropriate for mandatory qualifications like language fluency, shift, location, regular/temporary.
But also there is "Required Qualifications:" list. That's more like qualifications. So we need separate sections: Requirements (maybe for mandatory baseline like language, shift, location) and Qualifications (for education/experience). Skills maybe separate? The posting includes skills within qualifications. Could put skills under Qualifications or separate Skills section if we have explicit skill list. There's a list of skills: "Strong project management, stakeholder management, consulting, communication, and change management skills", "Ability to build trusted relationships...", "Strong judgment, attention to detail, organizational skills, and ability to identify and escalate risks, dependencies, and opportunities", "Ability to synthesize complex information and translate strategy into practical programs, tools, processes, and reporting", "Proficiency with Microsoft Office applications and collaboration tools". Those could be under Skills.
Preferred Qualifications also could be under Qualifications (maybe separate Preferred Qualifications subsection). But we only have allowed headings; we could put both required and preferred under Qualifications heading, with sub-lists? But we must output only HTML fragment; we can include nested
- etc. We could have a
- . We'll list each duty as separate
- . Ensure we keep the exact phrasing from posting. Let's extract duties exactly as they appear in the "What You’ll Do" and "Essential Duties And Responsibilities". The posting repeats some. We'll list them as they appear, maybe deduplicate? But to preserve all substantive information, we should include duplicates as they appear. However that may be repetitive but still preserving. I'll include each bullet as separate
- exactly as they appear in the text, preserving order.
From "What You’ll Do":
- Lead the design, implementation, and ongoing management of enterprise programs that support business priorities, teammate experience, and organizational culture.
- Create governance frameworks, operating models, standards, decision rights, escalation paths, and success measures that enable responsible and consistent execution.
- Build and manage strategic relationships with community, nonprofit, civic, professional association, vendor, and enterprise partners to expand reach and deliver business-aligned impact.
- Translate strategy into repeatable processes, tools, documentation, reporting routines, and leader resources that strengthen accountability and program adoption.
From "Essential Duties And Responsibilities" (starting after "Following is a summary of the essential functions for this job."):
- Lead the design, implementation, and management of enterprise programs that support business priorities, teammate experience, and community engagement.
- Develop governance frameworks, operating models, standards, decision rights, escalation paths, and measures of success.
- Establish repeatable processes, documentation, reporting routines, and operating practices that promote consistency, accountability, and responsible execution.
- Partner with senior leaders, business partners, and internal and external partners to align program priorities with enterprise goals and The Truist Way.
- Build relationships with business, community, nonprofit, civic, vendor, and enterprise partners to strengthen engagement and business-aligned impact.
- Lead cross-functional planning, project management, change readiness, communications, issue resolution, and impact reporting.
- Develop leader resources, presentations, talking points, and teammate-facing communications that support program adoption and execution.
- Use data to evaluate program effectiveness, risks, dependencies, operational progress, and business impact.
- Identify trends, risks, opportunities, and emerging needs; recommend solutions and continuous improvements.
- Lead matrixed project teams, as applicable.
We'll include all.
Now Requirements:
Requirements
Regular or Temporary: Regular. Language Fluency: English (Required). Work Shift: 1st shift (United States of America). Position has in-office expectations and can be located in our Atlanta, GA, or Charlotte, NC office. This is not a remote opportunity.
Now Qualifications:Qualifications
thenRequired Qualifications:
- with each required qualification item.
Required qualifications list:
- Bachelor’s degree or equivalent education and related training
- 8 years of experience in enterprise program management, strategy, governance, teammate experience, community relations, corporate responsibility, human resources, communications, operations, or a related field
- Experience leading developing, implementing, and measuring enterprise programs of scale, governance routines, or operating models in a complex organization
- Strong project management, stakeholder management, consulting, communication, and change management skills
- Ability to build trusted relationships with senior leaders, business partners, community partners, nonprofit organizations, and cross-functional teams
- Strong judgment, attention to detail, organizational skills, and ability to identify and escalate risks, dependencies, and opportunities
- Ability to synthesize complex information and translate strategy into practical programs, tools, processes, and reporting
- Proficiency with Microsoft Office applications and collaboration tools
Qualifications
then within that we can haveRequired Qualifications:
then- etc, then
Preferred Qualifications:
then- . That seems okay.
Benefits: There's a "General Description of Available Benefits for Eligible Employees of Truist Financial Corporation:" paragraph describing benefits. So we need Benefits section with that prose.
Pay: Not mentioned. So we should NOT include Pay section.
Schedule: Not mentioned besides Work Shift: 1st shift. That's schedule info. Could be placed under Schedule section? The posting includes Work Shift: 1st shift (United States of America). That's schedule info. So we could create a Schedule section with that detail. However we also placed shift under Requirements earlier. We need to decide where to put shift. The instruction: include a section ONLY when the posting has real, specific content for it. So we have specific content for shift: "Work Shift: 1st shift (United States of America)". So we should create a Schedule section with that. Similarly location maybe not a heading; we could put location under About the role or Requirements? There's no heading for location. Could put under About the role as prose. But we already have About the role paragraph; we could append location info there. However the instruction: Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location and shift could be minor metadata folded into a short
. But we also have a Schedule heading allowed; we could put shift there. However they said prefer a few substantive sections over many thin ones. So maybe better to fold shift and location into About the role or Requirements rather than making many thin sections. But we already have Requirements for language fluency and regular/temporary. Adding shift there would make Requirements more substantive. So we can put shift and location under Requirements as a short paragraph. Thus we will have sections: - About the role (prose) - Responsibilities (list) - Requirements (prose covering language fluency, regular/temporary, location, shift) - Qualifications (with required and preferred sublists) - Skills (list) - Benefits (prose) We must not include Pay or Schedule sections. Now we need to ensure we don't include boilerplate like EEO, accommodation request, etc. Remove those. Also remove "If you want to apply..." etc. Now craft HTML. We'll start with
About the role
then...
. Include the initial description plus maybe location and remote note? We'll keep location and remote note in Requirements. About the role paragraph: combine the two sentences: "As an Inclusion Programs & External Partnerships Lead, you’ll help turn enterprise priorities into programs and partnerships that strengthen teammate engagement, support a culture of belonging, and create business-aligned community impact. In this role, you will combine strategy, governance, program execution, relationship management, and measurement to deliver consistent, scalable outcomes across the enterprise." Now Responsibilities:Responsibilities
- with each duty as
- . We'll include all listed duties.
- Requirements: The posting includes "Regular or Temporary: Regular Language Fluency: English (Required) Work Shift: 1st shift (United States of America)" and also "Position has in office expectations and can be located in our Atlanta, GA, or Charlotte, NC office. *****This is not a remote opportunity". Also maybe "Regular or Temporary: Regular". Also "Language Fluency: English (Required)". Also "Work Shift: 1st shift (United States of America)". Also location info. Also maybe "Regular or Temporary: Regular". We need to decide if these go under Requirements or maybe a separate section like "Details". The allowed headings are limited; we can put these under Requirements or maybe under About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can place location, shift, language fluency, regular/temporary under Requirements (or maybe a separate "Details" not allowed). Probably Requirements is appropriate for mandatory qualifications like language fluency, shift, location, regular/temporary.
But also there is "Required Qualifications:" list. That's more like qualifications. So we need separate sections: Requirements (maybe for mandatory baseline like language, shift, location) and Qualifications (for education/experience). Skills maybe separate? The posting includes skills within qualifications. Could put skills under Qualifications or separate Skills section if we have explicit skill list. There's a list of skills: "Strong project management, stakeholder management, consulting, communication, and change management skills", "Ability to build trusted relationships...", "Strong judgment, attention to detail, organizational skills, and ability to identify and escalate risks, dependencies, and opportunities", "Ability to synthesize complex information and translate strategy into practical programs, tools, processes, and reporting", "Proficiency with Microsoft Office applications and collaboration tools". Those could be under Skills.
Preferred Qualifications also could be under Qualifications (maybe separate Preferred Qualifications subsection). But we only have allowed headings; we could put both required and preferred under Qualifications heading, with sub-lists? But we must output only HTML fragment; we can include nested
- for any list of duties/requirements/benefits. So we can create a