Executive Director, CIB Markets Senior Change Execution Lead
Wells Fargo · Charlotte, NC · 1 mo ago
Sales$139k–$217k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About This Role" and "In This Role, You Will". Also "Required Qualifications", "Desired Qualifications", "Job Expectations". Also "Salary Details". Also location maybe. We must not repeat job title as heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We have content for About the role (the paragraph about role). Responsibilities: the bullet list under "In This Role, You Will". Requirements: maybe "Required Qualifications". Qualifications: maybe "Desired Qualifications". Skills: maybe combine? Could have Skills section from desired qualifications? But we can treat Desired Qualifications as Skills. Benefits: none mentioned. Pay: Salary Details present. Schedule: none. Also Job Expectations maybe could be under Requirements? But we have a separate section maybe "Job Expectations". However the allowed headings list does not include Job Expectations; we must stick to those headings. So we need to map content to allowed headings. The instructions: "use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We have content for About the role (the paragraph about role). Responsibilities: the bullet list under "In This Role, You Will". Requirements: maybe "Required Qualifications". Qualifications: maybe "Desired Qualifications". Skills: maybe combine? Could have Skills section from desired qualifications? But we can treat Desired Qualifications as Skills. Benefits: none mentioned. Pay: Salary Details present. Schedule: none. Also Job Expectations maybe could be under Requirements? But we have a separate section maybe "Job Expectations". However the allowed headings list does not include Job Expectations; we must stick to those headings. So we need to map content to allowed headings. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. Probably we should use those exact headings when applicable. So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Possibly also Benefits if present (none). Schedule none.
We must not repeat job title as heading. Also not put Job ID etc.
We need to preserve all substantive information. So we need to include paragraphs and lists.
Let's extract content:
About This Role: "Wells Fargo is seeking a Senior Change Execution Lead (Executive Director level) in the Markets Business Solutions and Enablement function of Corporate & Investment Banking. Learn more about our career areas and lines of business at wellsfargojobs.com."
That's about the role.
Responsibilities: The bullet list after "In This Role, You Will". Let's capture each sentence as list items.
List items:
- Lead complex business and technology transformation programs from strategy through execution and business adoption, developing and delivering strategic solutions and roadmaps in partnership with CIB, Technology, Operations, Risk, Finance, and other key stakeholders.
- Direct the full project lifecycle for large-scale change initiatives, including current-state assessments, target-state operating model design, system implementations and upgrades, vendor evaluations, new product development, regulatory remediation, and process transformation.
- Ensure end-to-end solutions are effectively designed, integrated, governed, and controlled to achieve business objectives, satisfy stakeholder requirements, enhance operational effectiveness, mitigate risk, and drive efficiency.
- Drive executive decision-making by synthesizing complex information into clear, actionable insights, presenting strategic recommendations, solution options, and implementation considerations to senior leadership.
- Establish and oversee governance frameworks, operating models, and management reporting routines, while leading steering committees and other program forums.
- Proactively identify, assess, mitigate, and escalate key risks, issues, assumptions, and dependencies.
- Define and implement performance metrics to measure delivery effectiveness, program health, operational readiness, and business outcomes, ensuring accountability and transparency across initiatives.
- Ensure adherence to regulatory requirements, internal policies, risk and control standards, and enterprise change management frameworks throughout program execution.
- Build strong partnerships across business, technology, operations, finance, and control functions to align priorities, secure stakeholder commitment, resolve complex challenges, and drive successful outcomes.
Required Qualifications: "7+ years of Business Execution, Implementation, or Strategic Planning experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education"
Desired Qualifications: list of bullet-like sentences. Let's extract each as list items under Skills perhaps.
Desired Qualifications sentences:
- Strong knowledge and understanding of institutional broker/dealer trading practices across a vast array of products including, but not limited to, foreign exchange, fixed income, equities, and derivatives.
- Extensive experience designing and implementing complex business and technology solutions that integrate process, data, operating model, and technology changes to enable strategic business outcomes, platform modernization, and regulatory compliance initiatives.
- Experienced in leading transformational change initiatives across Corporate & Investment Banking (CIB), Operations, Risk, Finance, and Technology organizations, with hands-on expertise in business process analysis, target-state operating model design, and solution architecture.
- Ability to work and communicate effectively with business partners and broad set of stakeholders.
- Highly analytical and detail-oriented, with demonstrated ability to synthesize complex information.
- Ability to think strategically, be a self-starter, challenge the status quo, implement, and effectively deliver business objectives.
- Demonstrated expertise applying change management, process improvement, product development and project delivery methodologies including SDLC and Agile.
- Strong understanding of large-scale, complex technology environments, including cross-functional system architectures and interconnected business processes.
Job Expectations: list:
- This role is not eligible for VISA sponsorship
- Ability to travel as needed
- Willingness to work on-site in accordance with current office requirements
- Ability to work additional hours as needed
- This position is subject to FINRA background screening requirements. Candidates must successfully complete and pass a background check prior to hire.
- In accordance with FINRA rules, individuals who are subject to statutory disqualification are not eligible to be associated with a FINRA-registered broker-dealer.
- Successful candidates must also meet and comply with ongoing regulatory obligations, which include periodic screening and mandatory reporting of certain incidents.
- Specific compliance policies may apply regarding outside activities or personal investing; affected employees will be expected to provide information to the Wells Fargo Personal Account Dealing Team and abide by applicable policy requirements if hired.
- Information will be shared about expectations during the recruitment process.
We could put Job Expectations under Requirements? But we have separate headings: Requirements, Qualifications, Skills. Perhaps we put Job Expectations under Requirements (makes sense). Or we could add a separate section but not allowed headings. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning we can use those headings, but maybe we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those headings exactly. So we should map content to those headings. Job Expectations could go under Requirements (makes sense). Or we could create a Requirements section that includes both Required Qualifications and Job Expectations. But we also have Qualifications (desired) and Skills maybe overlapping. Let's decide:
- About the role: paragraph about role.
- Responsibilities: list of duties.
- Requirements: includes Required Qualifications + Job Expectations (maybe split into sublists? but we can just list).
- Qualifications: Desired Qualifications.
- Skills: maybe we could leave empty? Better to put Skills as maybe a subset of Desired Qualifications? But we already have Qualifications for desired. Could combine Qualifications and Skills? But we need to avoid empty sections. So we could put Desired Qualifications under Qualifications, and maybe Skills under Skills (but we have no separate skills list). Could we treat Desired Qualifications as Skills? Then we would have Qualifications for Required Qualifications and Skills for Desired Qualifications. That seems logical: Requirements = Required Qualifications + Job Expectations? Actually Required Qualifications is a qualification, not a requirement? But we can treat Requirements as Required Qualifications + Job Expectations. Qualifications could be Desired Qualifications. Skills maybe we could leave out or combine with Qualifications. But we need to avoid empty sections. Perhaps we can put Desired Qualifications under Skills, and keep Qualifications for Required Qualifications. Let's think: The heading list includes both Qualifications and Skills. So we can separate: Qualifications = Required Qualifications (maybe plus education etc). Skills = Desired Qualifications (knowledge, abilities). That seems reasonable.
Thus:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning we can use those headings, but maybe we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those headings exactly. So we should map content to those headings. Job Expectations could go under Requirements (makes sense). Or we could create a Requirements section that includes both Required Qualifications and Job Expectations. But we also have Qualifications (desired) and Skills maybe overlapping. Let's decide:
- About the role: paragraph about role.
- Responsibilities: list of duties.
- Requirements: includes Required Qualifications + Job Expectations (maybe split into sublists? but we can just list).
- Qualifications: Desired Qualifications.
- Skills: maybe we could leave empty? Better to put Skills as maybe a subset of Desired Qualifications? But we already have Qualifications for desired. Could combine Qualifications and Skills? But we need to avoid empty sections. So we could put Desired Qualifications under Qualifications, and maybe Skills under Skills (but we have no separate skills list). Could we treat Desired Qualifications as Skills? Then we would have Qualifications for Required Qualifications and Skills for Desired Qualifications. That seems logical: Requirements = Required Qualifications + Job Expectations? Actually Required Qualifications is a qualification, not a requirement? But we can treat Requirements as Required Qualifications + Job Expectations. Qualifications could be Desired Qualifications. Skills maybe we could leave out or combine with Qualifications. But we need to avoid empty sections. Perhaps we can put Desired Qualifications under Skills, and keep Qualifications for Required Qualifications. Let's think: The heading list includes both Qualifications and Skills. So we can separate: Qualifications = Required Qualifications (maybe plus education etc). Skills = Desired Qualifications (knowledge, abilities). That seems reasonable.
Thus:
About the role
About the role
Wells Fargo is seeking a Senior Change Execution Lead (Executive Director level) in the Markets Business Solutions and Enablement function of Corporate & Investment Banking. Learn more about our career areas and lines of business at wellsfargojobs.com.
Responsibilities
- ... ...
Requirements
7+ years of Business Execution, Implementation, or Strategic Planning experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
Job Expectations:
- This role is not eligible for VISA sponsorship
- Ability to travel as needed
- Willingness to work on-site in accordance with current office requirements
- Ability to work additional hours as needed
- This position is subject to FINRA background screening requirements. Candidates must successfully complete and pass a background check prior to hire.
- In accordance with FINRA rules, individuals who are subject to statutory disqualification are not eligible to be associated with a FINRA-registered broker-dealer.
- Successful candidates must also meet and comply with ongoing regulatory obligations, which include periodic screening and mandatory reporting of certain incidents.
- Specific compliance policies may apply regarding outside activities or personal investing; affected employees will be expected to provide information to the Wells Fargo Personal Account Dealing Team and abide by applicable policy requirements if hired.
- Information will be shared about expectations during the recruitment process.
Qualifications
Desired Qualifications:
- Strong knowledge and understanding of institutional broker/dealer trading practices across a vast array of products including, but not limited to, foreign exchange, fixed income, equities, and derivatives.
- Extensive experience designing and implementing complex business and technology solutions that integrate process, data, operating model, and technology changes to enable strategic business outcomes, platform modernization, and regulatory compliance initiatives.
- Experienced in leading transformational change initiatives across Corporate & Investment Banking (CIB), Operations, Risk, Finance, and Technology organizations, with hands-on expertise in business process analysis, target-state operating model design, and solution architecture.
- Ability to work and communicate effectively with business partners and broad set of stakeholders.
- Highly analytical and detail-oriented, with demonstrated ability to synthesize complex information.
- Ability to think strategically, be a self-starter, challenge the status quo, implement, and effectively deliver business objectives.
- Demonstrated expertise applying change management, process improvement, product development and project delivery methodologies including SDLC and Agile.
- Strong understanding of large-scale, complex technology environments, including cross-functional system architectures and interconnected business processes.
Pay
Salary Details $139,000-$217,000 (Charlotte only)
We should not include Benefits or Schedule sections. Check for any boilerplate: we removed EEO, legal, etc. Also removed "Posting address: 550 S. Tryon, Charlotte, NC 28202" maybe location is part of Pay? Could include location in About the role? Might be relevant but not required. The instruction: preserve ALL substantive information. The posting address is substantive. Should we include it? It's location. Could add a paragraph under About the role or maybe a separate section? Not in headings list. Could add awith location after About the role. Since we cannot add arbitrary headings, we can just add a
after About the role. That's fine. Also "Posting End Date 23 Sep 2026" and "Job posting may come down early due to volume of applicants." That's substantive but maybe considered metadata.