AVP, CIB COO Business Execution Consultant
Sales$77k–$121k/yrFull-time
We need to output only HTML fragment, using
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Must preserve all substantive info; do not invent or summarize away detail. Remove filler like "commensurate with experience", "not specified", etc. Do not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Salary Range and Benefits list. Also includes Job Expectations (travel, visa, onsite, hours, FINRA background). Those could be considered under Requirements or maybe a separate section? The allowed headings are limited to those list. We can put job expectations under Requirements or Qualifications? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have About this role (the paragraph after "About this role:"), we have responsibilities list (In this role, you will: ...). We have Required Qualifications and Desired Qualifications. We have Job Expectations (travel, visa, onsite, hours, FINRA). We have Benefits list. We have Pay (Salary Range). We have Schedule? Not explicitly; maybe work hours expectation (outside normal business hours as needed) could be schedule. But schedule is not given explicitly; we have "Willingness to work on-site in accordance with current office requirements. Ability to work outside of normal business hours as needed." That's schedule-ish. Could include Schedule section with that info. However we must not create Schedule unless posting actually states them. It does state ability to work outside normal business hours as needed, and on-site requirement. That's schedule info. So we can include Schedule.
We must not include filler like "commensurate with experience". Not present.
We must not include duplicated lines. Ensure we preserve all substantive info.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... paragraph ...
Responsibilities
Required Qualifications
Desired Qualifications
Job Expectations
maybe not allowed; but we could put under Requirements or Qualifications? The instruction says we can use those headings; but we could also add a section not listed? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Safer to map job expectations into Requirements or Qualifications? Could be under Requirements (since they are expectations). But we already have Required Qualifications and Desired Qualifications. Job Expectations could be placed under Requirements as a list? Might be okay.
Alternatively we could create a section "Requirements" and put both required qualifications and job expectations there. But we have separate Required Qualifications heading; we could keep that and put job expectations under Requirements (maybe as a separate Requirements
before Qualifications). However we have both Required Qualifications and Desired Qualifications; maybe we combine them into Qualifications? But the instruction includes Qualifications as a heading; we could have a single Qualifications section containing both required and desired. But we need to preserve all info; we can separate required and desired as subheadings? Not allowed? Could use but not specified. Better to keep Required Qualifications and Desired Qualifications as separate headings; they are plausible under the allowed list (Qualifications). Actually they said "Qualifications" as a heading; we could have Required Qualifications and Desired Qualifications as subheadings under Qualifications using or . But they didn't forbid other headings; they just gave examples. Safer to stick to the examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content:
- About the role: the paragraph after "About this role:".
- Responsibilities: the list after "In this role, you will:".
- Requirements: could include Required Qualifications + Job Expectations (travel, visa, onsite, hours, FINRA background). Could also include "Bachelors Degree or higher" etc? That's qualification. Actually education is qualification. So Requirements could be the mandatory items: 2+ years Business Execution, 2+ years Analytics, hands-on experience with data visualization tools, strong data analytics skills using Python/R/SQL, plus job expectations (travel, visa, onsite, hours, FINRA). That seems plausible.
- Qualifications: could include Desired Qualifications list (AI tools, large datasets, automation, credit markets experience, CIB experience, AI platforms, partnering skills, communication skills, Bachelors degree or higher in quantitative field). Actually Bachelors degree is also a qualification but appears under Desired? It's listed after Desired Qualifications: "Bachelors Degree or higher in quantitative field such as: mathematics, statistics, computer science, engineering, economics or similar". That seems like a qualification but maybe required? It appears after Desired Qualifications but not labeled as required; but it's likely a qualification. We'll treat it as part of Qualifications.
- Skills: maybe we could extract skills like Tableau/Power BI, Python, R, SQL, AI tools, etc. But we already covered those in qualifications. Could create Skills section for technical skills: Tableau/Power BI, Python, R, SQL, AI tools, etc. But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe better to have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Skip Skills.
- Benefits: list of benefits.
- Pay: Salary Range.
- Schedule: work expectations: willingness to work on-site, ability to work outside normal business hours as needed, travel up to 10%.
We also have FINRA background screening etc. That could be under Requirements.
We must not include boilerplate like EEO, visa sponsorship not available (that's a requirement). Actually "Visa Sponsorship is not available." That's a requirement; include under Requirements.
We must not include "Posting Location: Charlotte, NC: 550 South Tryon" maybe minor metadata; could fold into short p or drop. Probably drop as minor metadata.
We must not include "Posting End Date: 30 Sep 2026" etc; drop.
We must not include "Reference Number R-573029" drop.
We must not include "Learn more about the career areas and lines of business at wellsfargojobs.com." maybe drop as navigation.
We must not include "We Value Equal Opportunity" etc; drop.
We must not include "Applicants with Disabilities" etc; drop.
We must not include "Drug and Alcohol Policy" etc; drop.
We must not include "Wells Fargo Recruitment and Hiring Requirements:" etc; drop.
Now craft HTML.
We need to preserve all substantive info: let's extract.
About the role paragraph:
"Wells Fargo is seeking to hire a Junior Quantitative Analyst / Data Scientist to join the Credit Trading COO team within Corporate and Investment Banking (CIB), focused on building the data, analytics and automation layer that supports the Trading line of business. This is a hands-on build role rather than a pure analysis role where you will design dashboards, automate manual workflows, and apply AI tools to real business problems in close partnership with Trading, Sales, Technology, Operations, Risk, and Finance partners."
That's the substantive.
Responsibilities list (each bullet):
- Participate in a variety of assigned and ongoing business operations to ensure success in meeting business goals and objectives
- Identify opportunities for process improvement by conducting root cause testing of all compliance and business metrics
- Determine areas of strength or Business Execution opportunity within defined scope of work
- Review and research strategies and action plans to establish effective processes while meeting performance metrics and policy expectations
- Design, build and maintain dashboards and data visualizations (Tableau or equivalent) that give desk and COO leadership a clear, timely view of business performance, operating metrics and risk
- Automate recurring manual workflows such as data pulls, reconciliations and reporting packs, using Python, R and SQL to reduce turnaround time and operational risk
- Apply AI tools practically to streamline how the desks and the COO function operate, prototyping and proving out use cases end-to-end rather than in theory
- Partner with Trading, Sales, Technology and the wider Credit COO team to translate business questions into structured, data-driven analysis, from ad hoc requests through to production reporting
- Support the buildout of consistent data and reporting standards across Credit Trading, including common P&L and performance attributes across desks
- Build and deliver clear, decision-useful analysis and materials for leadership, and hand off or scale solutions that prove out in partnership with Technology
Required Qualifications (list):
- 2+ 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.
- 2+ years of Analytics, Data Science, or Quantitative Research experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education.
- Hands-on experience with data visualization tools (Tableau, Power BI or similar).
- Strong data analytics skills utilizing statistical or programming languages (Python, R or equivalent), and SQL.
Desired Qualifications (list):
- Practical experience using AI tools to solve real workflow problems; automation, generative AI or machine learning applied to a live business process rather than a research setting
- Experience working with large, complex datasets and turning them into reliable, repeatable reporting
- Prior experience automating or re-engineering a business process end-to-end, delivering across Technology, Operations, Risk or Compliance
- Credit markets or fixed income exposure (trading, desk strategy/analytics, portfolio trading support) with understanding of cash and derivative credit products
- Corporate & Investment banking experience
- Experience working with various AI platforms
- Strong partnering and collaboration skills
- Excellent verbal, written, and interpersonal communication skills with ability to articulate issues, risks, and proposed solutions to various levels of staff and management
- Bachelors Degree or higher in quantitative field such as: mathematics, statistics, computer science, engineering, economics or similar
Job Expectations (we will put under Requirements maybe):
- Ability to travel up to 10%.
- Visa Sponsorship is not available.
- Willingness to work on-site in accordance with current office requirements.
- Ability to work outside of normal business 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.
That's a