Senior Branch Product Support Representative - Consumer Core

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract substantive info. Let's parse the posting. Content: - About this role: description about Wells Fargo, mission, etc. That's "About the role". Should include paragraphs. - Then "In this role, you will :" list of duties. That's responsibilities. - Then "Training and Schedule :" includes training details, schedule (full-time, hours, Saturday required, etc). That's schedule and maybe training. - Then "Required Qualifications :" list. - Then "Desired Qualifications:" list. - Then "Job Expectations" bullet points. - Then "This position offers a hybrid work schedule." (maybe schedule/benefits? It's schedule detail.) - Then "This position is not eligible for Visa sponsorship." - Then "Posting Locations: 4101 Wiseman Blvd – San Antonio, TX 78251" - Then "Required location listed above" - Then note about posting may come down early etc (boilerplate, remove). - Then EEO etc (remove). - Then Drug and Alcohol Policy etc (remove). - Then Wells Fargo Recruitment and Hiring Requirements (remove). - Then Reference Number (remove). We need to keep all substantive info, but remove boilerplate/legal/EEO etc. We need to decide sections: - About the role: include the introductory paragraph(s) about Wells Fargo mission, etc. - Responsibilities: the list of duties after "In this role, you will :" - Requirements: maybe combine Required Qualifications and Job Expectations? But we have separate headings: Requirements, Qualifications, Skills. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: yes. - Responsibilities: yes. - Requirements: maybe the "Required Qualifications" and "Job Expectations" (these are requirements). Could also include "Required location" etc. - Qualifications: maybe "Desired Qualifications" (these are qualifications). Or we could treat Required Qualifications as Requirements, Desired as Qualifications. - Skills: maybe the skill items within Desired Qualifications (PC skills, problem-solving, communication, etc). Could also extract from responsibilities. - Benefits: The posting mentions "robust benefits, competitive compensation, and programs designed to help you find work life balance and well-being." Also mentions "extensive benefits and resources". Also mentions "Living the Well Life means you’re supported in life, not just work. It means having robust benefits, competitive compensation, and programs designed to help you find work life balance and well-being." Also mentions "You’ll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow." Also mentions LinkedIn award. So we have benefits info. - Pay: Not explicitly stated. No salary range. So we should NOT create Pay section. - Schedule: we have schedule details: full-time 40 hours, weekday hours 10am-7pm CT, Saturday 10am-4pm CT, potential Sunday, working every Saturday required to start, training schedule, hybrid work schedule. So we can create Schedule section. We must not create sections with filler like "commensurate with experience". Avoid. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep specifics: e.g., "Support Branch Product Support and seek ways to improve processes within established procedures", etc. We'll need to put each duty as

under

. Similarly for qualifications: list items. We need to avoid repeating job title. We need to output only HTML fragment, no /, no markdown. Let's craft. First, About the role: combine the paragraphs about Wells Fargo mission, Living the Well Life, etc. Also maybe the first sentence "About this role: Wells Fargo is seeking Senior Branch Product Support Representatives in Banker Connection Consumer Core as part of Consumer Banking and Lending (CBL). Learn more about the career areas and lines of business at wellsfargojobs.com. Are you looking for more? Find it here." That's also about the role. We'll include that. But we need to avoid fluff like "Learn more about the career areas and lines of business at wellsfargojobs.com. Are you looking for more? Find it here." That's maybe navigation/link; but it's substantive? It's a link to more info; but it's not essential. Might be considered boilerplate? It's not EEO but it's a promotional link. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is navigation/link to wellsfargojobs.com; could be considered navigation. Safer to remove that line. Also "Are you looking for more? Find it here." is similar. Thus About the role paragraph: start with "Wells Fargo is seeking Senior Branch Product Support Representatives in Banker Connection Consumer Core as part of Consumer Banking and Lending (CBL)." Then the mission statements. We'll keep: "At Wells Fargo, we're more than a financial services leader – we’re a global trailblazer committed to driving innovation, empowering communities, and helping our customers succeed. We believe that a meaningful career is much more than just a job – it’s about finding all of the elements to help you thrive, in one place. Living the Well Life means you’re supported in life, not just work. It means having robust benefits, competitive compensation, and programs designed to help you find work life balance and well-being. You’ll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow. And we’re recognized for it – Wells Fargo once again ranked in the top three – making us the #1 financial services employer – on the 2025 LinkedIn Top Companies list of best workplaces “to grow your career” in the U.S. Join us!" That seems good. Now Responsibilities: list each duty after "In this role, you will :". Let's extract: - Support Branch Product Support and seek ways to improve processes within established procedures - Support branch employees and internal business partners by delivering exceptional internal customer experience while taking inbound calls; - Provide expertise, resources, and procedural support to internal partners, enabling them to make recommendations on products and services that best align to the customer's needs. - Perform moderately complex customer support tasks to include consumer branch policy and procedure review with a focus on accuracy and risk mitigation - Receive direction from leaders and escalate non-routine questions while developing the knowledge to understand function, policies, procedures, and compliance requirements. - Interact with immediate team on less complex information as well as internal customers, primarily branch employees, to deliver first contact resolution and support for critical transactions. - Regularly receive direction from supervisor and escalate questions and issues to more experienced roles. - Establish, develop, and maintain positive business relationships with internal partners. - Perform routine administrative, transactional, operational, and customer support tasks. - Deliver first contact resolution for critical transactions that may include wire transactions, fiduciary account and owner creation/maintenance, official bank check reviews, and special account questions and maintenance, seeking guidance from more experienced peers when necessary. - Proactively provide feedback to time sensitive requests related to outages, issues, and updates. - Provides recommendations and information needed to update policies and procedures. Note: some sentences have semicolons; we can treat each as separate bullet. Now Training and Schedule section: we need to separate training details and schedule details. Could combine under Schedule heading? But we have separate headings for Schedule and maybe Benefits. Training could be part of Schedule or maybe Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Training could be part of Schedule (since schedule includes training hours). Or we could create a separate "Training" heading but not in list; better to put under Schedule. Thus Schedule section: include: - We are hiring for full-time positions, 40 hours a week. - Weekday hours are between 10:00am - 7:00pm (CENTRAL TIME) and Saturday hours are 10:00am - 4:00 pm (CENTRAL TIME), with the potential to expand to Sunday hours. - Working every Saturday is required to start with the opportunity for some Saturdays off in the future. - Shifts are assigned based on business need. - Training classes start 11/02/2026 in San Antonio, TX. - Training hours will be 8:30am - 5:00pm (Central Time), Monday-Friday. - You are required to attend the full duration of this paid 7 to 8 weeks of training. - This position offers a hybrid work schedule. Also note: "This position is not eligible for Visa sponsorship." That's not schedule; maybe put under Requirements? Could be a requirement (eligibility). Could be placed under Requirements as a note. Now Required Qualifications: list: - 2+ years of Branch or Customer Service experience or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education Desired Qualifications: list: - 1+ years of financial customer service experience - Complex problem-solving skills - Good PC skills with the aptitude to learn new systems quickly - Ability to navigate multiple systems and applications to research and identify current business documentation and procedures - Ability to effectively listen and elicit information - Good verbal, written, and interpersonal communication skills - Strong attention to detail and accuracy skills - Ability to work effectively in structured but flexible, adaptable and changing, call center environment Job Expectations: list: - Ability to work shifts within the business hours of operation as outlined above - Must be able to attend full duration of required training period We could merge Job Expectations into Requirements or Qualifications. Since we have Requirements and Qualifications headings, we could put Required Qualifications under Requirements, and Desired Qualifications under Qualifications. Job Expectations could also go under Requirements (as they are expectations). We'll include them under Requirements as additional items. Now Skills: we could extract skill items from Desired Qualifications that are skills: complex problem-solving, PC skills, ability to navigate systems, ability to listen, communication skills, attention to detail, ability to work in call center environment. Could also include from responsibilities: delivering exceptional internal customer experience, providing expertise, etc. But to avoid duplication, we can list skills as bullet list under Skills heading, pulling from Desired Qualifications. But we must not invent or summarize away detail; we need to preserve all substantive information. If we put skills as a separate section, we need to ensure we are not omitting any other substantive info that belongs elsewhere. The Desired Qualifications list includes both experience and skills. If we move the skill items to Skills section, we need to keep the experience items (1+ years financial customer service experience) somewhere else, maybe under Qualifications (desired qualifications). But we already have Qualifications heading for desired qualifications; we could keep the whole Desired Qualifications under Qualifications heading, and not create a separate Skills section. However the instruction says we can use Skills heading if there is real specific content for it. We could decide to not create Skills section to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine Desired Qualifications under Qualifications heading, and not create Skills unless we have enough distinct skill content beyond what's already in Qualifications. Since Desired Qualifications includes both experience and skills, we can keep them together under Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We need to ensure we don't create Pay section (no pay info). Benefits section: we have robust benefits, competitive compensation, programs for work-life balance, rewarded for investing