Senior Premier Banker Greater Phoenix Area

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. Content: - Intro about Wells Fargo (company description) – maybe part of "About the role"? Actually "About This Role" heading present. We can treat that as "About the role". It includes description of role, purpose, etc. - "In This Role You Will" bullet list of duties – that is responsibilities. - "Required Qualifications:" list – that's qualifications/requirements. - "Desired Qualifications:" list – could be skills or desired qualifications. - "Job Expectations:" includes schedule (Ability to work a schedule that will include most Saturdays) and licensing requirements etc. Also mentions FINRA etc. That's more qualifications/requirements. - Also mentions "This role requires FINRA Series 6 and Series 63 (or FINRA recognized equivalents), and State Insurance license(s) which must be active or completed within a designated timeframe." etc. - Also mentions "Obtaining and maintaining required FINRA licenses is necessary for continued employment." etc. - Also mentions "SAFE registration is required at the time of employment and Wells Fargo will initiate the process after your start date." - Also mentions "Loan Originators must meet LO/CFPB requirements..." etc. - Also mentions "This position is not eligible for Visa sponsorship" - Also mentions "Positions may not be available at all branch locations outlined in the posting." - Also mentions "Posting Locations:" list of addresses. - Also mentions "Posting End Date: 29 Sep 2026" - Also mentions "Job posting may come down early due to volume of applicants." - Also mentions "We Value Equal Opportunity" etc – that's EEO boilerplate, should be removed. - Also mentions "Drug and Alcohol Policy", "Wells Fargo Recruitment And Hiring Requirements", "Third-Party recordings are prohibited..." etc – boilerplate, remove. - Also "Reference Number R-574476-4" – minor metadata, fold into short p or drop. We need to preserve all substantive information: company description? The intro "Why Wells Fargo Are you looking for more? Find it here. At Wells Fargo, we're more than a financial services leader..." That's about company culture, benefits, etc. Could be considered part of "About the role" or maybe "Benefits"? It mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's benefits info. So we could include a Benefits section with that content. However we must not create Benefits unless posting actually states them. It does state benefits: "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." That's benefits description. So we can include Benefits section. Pay: Not mentioned specific salary, only "competitive compensation". That's vague but maybe considered placeholder? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive compensation" is somewhat vague but it's a statement about compensation. Is that considered placeholder? It's not a specific number, but it's a statement. The instruction says avoid filler/placeholder text like "commensurate with experience", "not specified", etc. "competitive compensation" could be considered vague but not exactly placeholder. However they said never create Pay section unless posting actually states them. It does state "competitive compensation". So we could include Pay section with that sentence. But we need to be careful: they might consider that as placeholder. However they gave examples of placeholder: "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive compensation" is not in that list. It's a statement. I'd include Pay section with that sentence. Schedule: They state "Ability to work a schedule that will include most Saturdays". That's a schedule requirement. So we can include Schedule section with that. Now we need to structure sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: Could be the "About This Role" paragraph describing role purpose, etc. Also maybe the company description? But company description is more about Wells Fargo benefits etc. Might fit Benefits. However "About This Role" is a heading in the posting. We'll use that content for About the role. - Responsibilities: The "In This Role You Will" bullet list. - Requirements: Could be the "Required Qualifications:" list. - Qualifications: Could be the "Desired Qualifications:" list (or maybe combine with Required). But we have both Required and Desired. We could put Required under Requirements, Desired under Qualifications. Or we could put Required under Qualifications and Desired under Skills. But we have Skills section also. The desired qualifications include things like experience recommending financial products, ability to source, manage book-of-business, coaching, communication, financial services industry experience, licensed position, FINRA exams, State Insurance license. Those are more qualifications/skills. Could treat Desired as Skills. But we also have Job Expectations (schedule, licensing). Those could be part of Requirements or Qualifications. We need to avoid duplication. Let's map: - Required Qualifications: 4+ years customer service experience, 3+ years building relationships, 3+ years recommending products/services. - Desired Qualifications: experience recommending financial products and translating goals, ability to source/acquire/deepen relationships, proven experience managing a book-of-business, documentation of planning conversations, consistent follow-through, experience coaching peers, ability to communicate clearly, listen with empathy, build credibility, financial services industry experience (consumer, home lending, business banking, investments), 3+ years in a licensed financial services position, completed FINRA Series 6 and 63 (or equivalents), State Insurance license(s). - Job Expectations: Ability to work schedule including most Saturdays, FINRA Series 6/63 required, State Insurance license required, SIE if after Sept 30 2018, Series 65 for certain states, obtaining/maintaining licenses necessary, SAFE registration required, loan originator requirements, not eligible for Visa sponsorship, positions may not be available at all locations. We could treat schedule as Schedule section. Licensing requirements could be part of Requirements or Qualifications. We need to preserve all substantive info. So we need to include schedule statement, licensing requirements, SAFE registration, visa sponsorship note, location list, posting end date. Where to put location list? Could be part of About the role? Or maybe a separate section? Not in the list of allowed headings. Could fold into a short p under About the role or maybe under Responsibilities? Probably best to include as a short p under About the role (or maybe under a separate "Locations" but not allowed). The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can fold location list into a short p. Similarly posting end date could be folded into a short p. We must not include boilerplate like EEO, drug policy, etc. Now we need to output HTML fragment with sections as needed. Let's decide which sections to include: - About the role: include the "About This Role" paragraph plus maybe company intro? The company intro includes benefits description; but we have Benefits section separate. So we can keep company intro in Benefits. Thus About the role: the paragraph starting "Wells Fargo is seeking a Senior Branch Premier Banker (SAFE) to play a pivotal role..." plus maybe the preceding sentence about "About This Role". We'll include that paragraph. - Responsibilities: the bullet list under "In This Role You Will". We'll convert each line to

. - Requirements: the "Required Qualifications:" list. - Qualifications: maybe we can combine Desired Qualifications and Job Expectations (licensing) into Qualifications? But we also have Skills section. Could treat Desired Qualifications as Skills. Let's decide: Skills: include items like "experience recommending financial products and translating customer goals into clear, actionable recommendations", "ability to proactively source, acquire, and deepen relationships", "proven experience managing a book-of-business", "experience coaching or supporting peers", "ability to communicate clearly and confidently, listen with empathy, and build credibility and trust quickly", "financial services industry experience in consumer, home lending, business banking, or investments". Those are skills. Qualifications: could include the Required Qualifications (years of experience) and maybe the licensing requirements (FINRA, insurance) as qualifications. But we already have Required Qualifications under Requirements. Might be overlapping. Better to follow the instruction: Use sections only when posting has real specific content. We have content for: - About the role (yes) - Responsibilities (yes) - Requirements (maybe Required Qualifications) - Qualifications (maybe Desired Qualifications) - Skills (maybe we can treat some as Skills) - Benefits (yes from company intro) - Pay (yes "competitive compensation") - Schedule (yes "Ability to work a schedule that will include most Saturdays") We need to avoid too many thin sections. But we have content for each. Let's assign: About the role: The paragraph describing the role purpose. Responsibilities: The bullet list under "In This Role You Will". Requirements: The "Required Qualifications:" list (4+ years customer service, 3+ years building relationships, 3+ years recommending products/services). Qualifications: The "Desired Qualifications:" list (experience recommending financial products, ability to source, manage book-of-business, coaching, communication, industry experience, licensed position, FINRA exams, insurance license). This is a list of qualifications. Skills: Could be overlapping with Qualifications. Maybe we can skip Skills and put those under Qualifications. But we have both sections allowed; we could decide to not include Skills if content is thin. However we have distinct skill items: communication, coaching, etc. Could be considered skills. But we already have Qualifications covering many. To avoid thin sections, maybe we combine Desired Qualifications and Skills into one section called Qualifications (or Skills). But we need to follow headings list; we can choose to omit Skills if we think it's not needed. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills and put those items under Qualifications. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to include location list and posting end date somewhere. Could fold into a short p under About the role or maybe under Responsibilities? Probably under About the role as a short p after the main paragraph. Also include note about visa sponsorship not eligible, positions may not be available at all locations. That's also minor metadata; we can fold into same short p. Now we need to ensure we don't include boilerplate like EEO, drug policy, etc. Let's extract the substantive paragraphs: Company intro: "Why Wells Fargo Are you looking for more? Find it here. 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