Jobs · Idaho

Relationship Banker LP (SAFE) - Ketchum, ID

Wells Fargo · Ketchum, ID · 1 mo ago
Full-time
We need to output HTML fragment with sections: About the role (maybe "About this role"), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About this role" paragraph, then "In this role you will:" list of duties (responsibilities). Then "Required Qualifications:" list, "Desired Qualifications:" list (these could be under Requirements or Qualifications). Also "Job Expectations:" includes schedule (most Saturdays) and licensing requirements. Benefits? The posting mentions "robust benefits, competitive compensation" in the intro "Why Wells Fargo". That's generic but maybe we can include Benefits section? It says "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." That's somewhat generic but still specific? It mentions benefits but not details. The instruction: never create Benefits section unless posting actually states them. It does state "robust benefits" but not specifics. Might be considered too vague? The instruction says: 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. It does state benefits exist, but not details. Is that enough? Probably we can include a Benefits section with the statement about robust benefits etc. However we need to avoid filler. The statement "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." is somewhat generic but still a statement. Could be acceptable. Pay: Not specified. No salary. So we should not include Pay. Schedule: It says "Ability to work a schedule that will include most Saturdays". That's specific enough for Schedule section. Thus sections: About the role (maybe heading About the role), Responsibilities, Requirements (maybe combine Required and Desired?), Qualifications (maybe separate?), Skills (maybe from Desired Qualifications?), Benefits, Schedule. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to remove boilerplate: EEO, legal, etc. Also remove "Why Wells Fargo" maybe? That's introductory but could be considered part of About the role? Actually "Why Wells Fargo" is a marketing blurb; we could include it as part of About the role? The instruction: "About this role:" is a section. The "Why Wells Fargo" could be considered part of company overview, but not required. We could include it as a paragraph before About the role? But we should not include navigation/legal/EEO etc. The "Why Wells Fargo" is not boilerplate; it's company description. Might be okay to keep as part of About the role? However the instruction says: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should have headings exactly those names if we include them. The posting has "About this role:" which maps to About the role. We'll use that heading. We need to include the content under About the role: the paragraph(s) after "About this role:" up to before "In this role you will:"? Actually the text: "About this role: Wells Fargo is seeking a Relationship Banker (SAFE) to join our National Branch Network, where trusted advice, disciplined growth, and long-term customer relationships define success. This role serves customers across all segments, including affluent customers, as the primary point of contact for everyday banking needs, products and services through scheduled appointments, lobby engagement, and proactive outreach. The role helps customers progress toward their financial goals through planning, digital engagement, and customized deposit, credit, and investment solutions. In addition, this role supports everyday banking activities such as opening accounts, handling service requests, and delivering a seamless experience that makes it easier for customers to manage their banking with confidence. Relationship Bankers will build credibility and loyalty by leading with curiosity and insight, turning meaningful discovery conversations into enduring customer partnerships. You will work in a collaborative branch environment, backed by one of the most recognized banking brands and ongoing coaching, while partnering with colleagues to meet customer needs through appropriate referrals. Success in this role is driven by strong relationship acumen, proactive customer engagement, and seamless collaboration with partners across Wealth, Home Lending, and Business Banking to deliver a differentiated customer experience. Wells Fargo recognizes and rewards the behaviors that create meaningful customer value and support customers in making informed financial decisions. This role is well suited for professionals who aspire to build a long-term career in financial services, deepen their consultative expertise, and support customers as their financial needs become more complex over time." That's a lot of prose. We'll put that in

    under

    About the role

    . Then Responsibilities: the list after "In this role you will:" includes bullet points (each line starts with a verb). We'll make
    • for each. Then Requirements: we have Required Qualifications and Desired Qualifications. Could combine under Requirements heading? Or separate Required and Desired? The instruction allows sections: Requirements, Qualifications, Skills. We could put Required Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe Skills under Skills? But Desired Qualifications includes many skill-like items. Could treat Desired Qualifications as Skills. However we need to preserve all info. Let's map: - Requirements: Required Qualifications (the bullet list) - Qualifications: Desired Qualifications (the bullet list) - Skills: maybe we could extract skill statements from Desired Qualifications? But that would be duplication. Better to put Desired Qualifications under Qualifications. Thus we will have:

      Requirements

      with
        of Required Qualifications.

        Qualifications

        with
          of Desired Qualifications. We might also have a Skills section? Not needed if we already have Qualifications. But we could also include Skills from Desired Qualifications that are skill-based. However to avoid duplication, we can skip Skills section. Benefits: we have statement about robust benefits etc. We'll put under

          Benefits

          with

          containing that sentence. Schedule: we have "Ability to work a schedule that will include most Saturdays". We'll put under

          Schedule

          with

          . We should not include Pay. We must not include Job ID etc. We must remove boilerplate: EEO, etc. Also remove "Posting End Date: 26 Sep 2026" maybe? That's metadata but not a heading; could be folded into a short

          or dropped. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it." So we could include a short

          for Posting End Date maybe. But it's minor metadata; we could drop it. Safer to drop it. Also remove "Reference Number R-577438". Drop. Also remove "Job Expectations:" section? That includes schedule and licensing requirements. We already captured schedule; licensing requirements are part of Requirements? Actually they are under Job Expectations: "Ability to work a schedule that will include most Saturdays" and then licensing requirements. The licensing requirements are part of Required Qualifications? They mention FINRA Series 6, 63, state insurance license etc. That is indeed a requirement. Should we include that under Requirements? The Required Qualifications list didn't include those; they are separate. We should include them as part of Requirements (maybe as additional bullet). So we need to incorporate licensing requirements into Requirements section. Thus Requirements bullets: from Required Qualifications (2+ years customer service, 1+ year assessing needs, 1+ year building relationships) plus licensing requirements: FINRA Series 6, Series 63 (or equivalents), state insurance license(s), SIE if after Sep 30 2018, Series 65 for certain states, etc. Also mention enhanced financial fitness and criminal background standards, etc. Also mention that obtaining and maintaining required FINRA licenses is necessary for continued employment. Also mention that Wells Fargo will begin FINRA review after offer accepted. Also mention SAFE registration required at time of employment and process after start date. Also mention Loan Originators must meet LO/CFPB requirements etc. Also mention credit report review etc. Also mention not eligible for Visa sponsorship. All these are requirements. We need to preserve all substantive information. So we need to include all those details. Thus Requirements section will be a list (maybe multiple

            groups? But we can just have one
              with all items. Similarly Desired Qualifications list includes many items; we will put those under Qualifications. Now we need to ensure we don't create headings with filler. All sections have real content. Now produce HTML fragment. Let's craft:

              About the role

              Wells Fargo is seeking a Relationship Banker (SAFE) to join our National Branch Network, where trusted advice, disciplined growth, and long-term customer relationships define success. This role serves customers across all segments, including affluent customers, as the primary point of contact for everyday banking needs, products and services through scheduled appointments, lobby engagement, and proactive outreach. The role helps customers progress toward their financial goals through planning, digital engagement, and customized deposit, credit, and investment solutions. In addition, this role supports everyday banking activities such as opening accounts, handling service requests, and delivering a seamless experience that makes it easier for customers to manage their banking with confidence. Relationship Bankers will build credibility and loyalty by leading with curiosity and insight, turning meaningful discovery conversations into enduring customer partnerships. You will work in a collaborative branch environment, backed by one of the most recognized banking brands and ongoing coaching, while partnering with colleagues to meet customer needs through appropriate referrals. Success in this role is driven by strong relationship acumen, proactive customer engagement, and seamless collaboration with partners across Wealth, Home Lending, and Business Banking to deliver a differentiated customer experience. Wells Fargo recognizes and rewards the behaviors that create meaningful customer value and support customers in making informed financial decisions. This role is well suited for professionals who aspire to build a long-term career in financial services, deepen their consultative expertise, and support customers as their financial needs become more complex over time.

              Responsibilities

              • Proactively acquire, manage, and grow a portfolio of consumer and business customer relationships
              • Lead discovery‑driven conversations to understand customer goals and deliver tailored banking and credit strategies that strengthen relationships, increase retention, and drive balanced growth across deposits, lending, and investments
              • Partner with a team of professionals across Wealth, Home Lending, and Business Banking to deliver integrated solutions by coordinating warm introductions, setting clear expectations, and taking personal ownership to convert qualified opportunities into closed outcomes
              • Champion digital adoption by educating customers on self-service and mobile banking options to elevate satisfaction, engagement, and service efficiency
              • Resolve account inquiries and service requests within authorized limits, documenting actions and setting follow-up plans that reinforce trust and ease
              • Demonstrate risk excellence through accurate documentation, sound judgment, timely issue escalation, and adherence to policies and regulations to support strong control outcomes

              Requirements

              • 2+ years of customer service experience, or equivalent demonstrated through work experience, training, military experience, education
              • 1+ year of assessing and meeting the needs of customers or helping with issue resolution, demonstrated through work or military experience
              • 1+ year of building and maintaining effective relationships with customers and partners
              • Must have or obtain FINRA Series 6 and Series

Similar jobs