DirectJobHub
Jobs · Finance · Pennsylvania

Bilingual Spanish Personal Banker North Phila District

Wells Fargo · Philadelphia, PA · 1 mo ago
FinanceFull-time
We need to produce HTML fragment with sections for headings: 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, etc. Must not include placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's see content: There's a "Why Wells Fargo" intro, then "About this role", then bullet list of duties (In this role you will: ...). Then "Required Qualifications", "Desired Qualifications", "Job Expectations". There's also posting locations, posting end date, etc. There's no explicit Benefits, Pay, Schedule details except schedule mention: "Ability to work a schedule that will include Saturdays". That's schedule info. Also maybe "Job Expectations" includes schedule. There's no explicit benefits or pay. So we should include sections: About the role (maybe from "About this role" paragraph), Responsibilities (the bullet list under "In this role you will:"), Requirements (maybe combine Required Qualifications and Desired Qualifications? Actually Required Qualifications and Desired Qualifications are separate; we could have Requirements section for required, and Qualifications for desired? But spec says we can use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. We have: About the role: paragraph after "About this role:" describing role. Responsibilities: bullet list of duties. Requirements: Required Qualifications (6+ months interacting with customers, bilingual Spanish/English). Qualifications: Desired Qualifications list. Skills: maybe we could extract skills from desired qualifications? But we could also put skills as separate if we have content. The desired qualifications list includes many skill-like items: prior experience in financial services, building trust-based relationships, initiating outreach, comfort with digital tools, ability to identify needs, collaborate, follow policies. Those could be considered Skills. But spec says we can include Skills section only if posting has real specific content for it. We could treat Desired Qualifications as Qualifications section, and maybe Skills not needed. However we have both Required Qualifications and Desired Qualifications; we could map Required Qualifications to Requirements, Desired Qualifications to Qualifications. Skills maybe not needed. Schedule: we have "Ability to work a schedule that will include Saturdays". That's schedule info. So we can include Schedule section with that sentence. Benefits, Pay: not present, so omit. We must not include boilerplate like EEO, etc. Also remove posting locations? The posting location list is substantive info (locations). Should we preserve? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the posting locations. Where to put them? Could be part of About the role? Or maybe a separate section like "Locations". But we only allowed headings from list. Could we put them under About the role as a paragraph? Probably we can include them in About the role section as a paragraph after description. But About the role heading is for section headings like About the role, Responsibilities, etc. The content under About the role can include prose and maybe a list of locations. However the spec says use
  • for any list of duties/requirements/benefits, and

    for prose. So we can put locations as a

    • list under About the role? Might be okay. But we need to decide if it's a list of duties/requirements/benefits. Locations are not duties/requirements/benefits, but still a list. The instruction says use
      • for any list of duties/requirements/benefits. It doesn't forbid using
        • for other lists, but says for those specific types use that. Safer to use

          for prose and maybe separate lines? Could just put them as a

          with commas. But preserving all info: we could list them as a

          • anyway; it's not prohibited. I'll use
            • for locations. Also posting end date: "Posting End Date: 28 Sep 2026 *Job posting may come down early due to volume of applicants." That's substantive info; we could include under About the role or maybe a separate metadata paragraph. Since we cannot create a heading for Job ID etc, we can fold minor metadata into a short

              or drop it. The posting end date is minor metadata; we can include in a short

              under About the role or maybe after. We'll include a short paragraph. We must remove boilerplate like "We Value Equal Opportunity", EEO statements, drug policy, etc. Also remove "Reference Number". Also remove "Based on timing, not all branch locations may have openings." That's maybe part of locations; we can keep that note. Now construct HTML. Structure:

              About the role

              Wells Fargo is seeking an Associate Personal Banker (SAFE) to join our National Branch. In this frontline role, you will build relationships with customers by supporting everyday banking needs through in‑branch interactions, scheduled conversations, and proactive outreach. You will learn about customers’ goals and connect them to the right banking products, services, and digital tools to help them manage their finances with confidence. You will support account openings, service requests, and credit applications while working closely with branch teammates to deliver a consistent, high-quality customer experience. Success is driven by strong relationship building, sound judgment, and the ability to balance service with growth. As a member of a leading financial institution, this role provides a strong foundation for long-term career growth and mobility, supported by Wells Fargo’s training and coaching.

              Locations:

              • 700 Adams Ave, Philadelphia, PA 19124
              • 1837 E Alleghany Ave., Philadelphia, PA 19134
              • 3400 Aramingo Ave, Philadelphia, PA 19134
              • 2401 W Cheltenham Ave Wyncote, PA 19095
              • 5458 Germantown Ave., Philadelphia, PA 19144
              • 161 S Easton Road Glenside, PA 19038
              • 2843 N Broad St, Philadelphia, PA 19132
              • 1246 E Hunting Park Ave, Philadelphia, PA 19124
              • 7782 Crittenden Street Philadelphia, PA 19118
              • 601 W Erie Ave, Philadelphia, PA 19140
              • 101 E. Olney Ave., Philadelphia, PA 19120
              • 6918 Ridge Ave., Philadelphia, PA 19128

              Posting End Date: 28 Sep 2026 (may come down early due to volume of applicants).

              Then Responsibilities:

              Responsibilities

              • Build lasting customer relationships through proactive, meaningful conversations that support financial well-being and deepen engagement
              • Lead discovery-driven conversations to understand customer needs and connect them with relevant banking products, services, and solutions
              • Drive branch growth by identifying opportunities, promoting solutions, and making appropriate referrals to meet customer and business goals
              • Support everyday banking needs, including new account openings, service requests, and credit applications
              • Perform cash handling and teller line activities, accurately processing transactions while maintaining compliance and operational standards
              • Demonstrate comfort using and adopting digital tools and technologies to enhance the customer experience and support evolving banking needs
              • Deliver accurate, compliant service while exercising sound judgement within defined risk controls
              • Collaborate with branch teammates to coordinate seamless handoffs to licensed bankers or other specialists, ensuring customers are connected to the right expertise
              Then Requirements:

              Requirements

              • 6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
              • Bilingual speaking and listening proficiency in Spanish/English
              Then Qualifications (Desired):

              Qualifications

              • Prior experience in financial services or a highly regulated, customer-facing role, demonstrating comfort with structured processes, accuracy, and service expectations
              • Experience building trust-based customer relationships through active listening, follow-up, and consistent engagement
              • Comfort initiating outreach (calls, emails, or other channels) to strengthen relationships and identify opportunities to support customer needs
              • Demonstrated comfort with digital tools and technology, with the ability to quickly learn new systems and confidently guide customers in adopting capabilities that enhance their banking experience
              • Ability to identify customer needs and connect them to appropriate solutions, including referrals when additional expertise is needed
              • Proven ability to collaborate with teammates and partners to resolve needs and deliver a seamless customer experience
              • Demonstrated ability to follow policies and regulations while identifying and escalating risk concerns
              Then Schedule:

              Schedule

              Ability to work a schedule that will include Saturdays.

              We should not include Benefits or Pay. Check for any leftover boilerplate: we removed EEO, drug policy, etc. Also removed "Why Wells Fargo" intro? That is substantive but maybe could be considered part of About the role? The "Why Wells Fargo" is more about company; we could incorporate into About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

              or drop it." The "Why Wells Fargo" is not a heading; it's prose. Should we keep it? It's substantive info about company. The instruction says preserve ALL substantive information. So we should keep it. Where to place? Could be part of About the role section as an introductory paragraph before the role description. So we can add a paragraph at start of About the role: "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 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 five on the 2026 LinkedIn Top Companies list of best workplaces “to grow your career” in the U.S. Join us!" That's a lot but it's substantive. We'll include as

              . Thus About the role will have two paragraphs: first the Why Wells Fargo, second the role description. We must ensure we don't include any placeholder like "robust benefits, competitive compensation" - that's okay as it's from posting. It's not a placeholder like "commensurate with experience". It's actual statement. Now produce final HTML fragment. Check for any remaining boilerplate: "Posting Location(s): Insert posting address(es)" we removed that label and just list addresses. Good. We removed "Based on

Similar jobs