Personal Banker II
- .
- Requirements: The "We’re excited to talk to you if" bullet list (requirements). Let's extract each:
- You have a HS Diploma or equivalent
- You have two years of retail banking sales experience or other relevant experience
- You have reliable transportation and ability to work branch hours, including weekends and some evenings
- You have the ability to obtain a NMLS registration within 90 days
- You have the ability to learn products, services, and procedures quickly and accurately
- You have basic math skills and ability to problem solve while operating within established risk parameters/tolerances
- You have demonstrated ability to make personal connections, engage and educate customers, ask open-ended questions, and listen to establish trust and build lasting relationships
- You have strong business development capabilities for proactively growing your own personal book of business by successfully using campaign offers, prospecting leads, service-to-sales conversations as well as leveraging centers of influence for referrals.
- You thrive in a high-energy, sales-driven team, and leverage daily coaching and feedback to polish your sales outcomes
- You use your expert product knowledge and conversation skills to build upon your customers' needs and make a true difference in their financial lives
- You communicate in a compelling manner, project a positive image, and enjoy solving problems and creating positive outcomes
- You demonstrate attention to detail whether completing documents or explaining features and benefits
- You enjoy coaching others as a sales mentor
These are requirements/qualifications. The posting also has "Bonus points if You have a college degree or military equivalent strongly preferred" and "You are bilingual". Those could be qualifications or preferred qualifications. We'll treat them under Qualifications maybe.
- Qualifications: Could include "Bonus points if You have a college degree or military equivalent strongly preferred" and "You are bilingual". Also maybe "Targeted compensation for this opening" etc not qualification.
- Skills: Could be derived from responsibilities and requirements but we need a Skills section only if posting has specific content. The posting mentions product knowledge, conversation skills, business development capabilities, etc. Might be considered skills. However we need to decide if we only include if there is real specific content. There is mention of "You have the ability to learn products, services, and procedures quickly and accurately", "basic math skills", "ability to problem solve", "demonstrated ability to make personal connections", "strong business development capabilities", "use your expert product knowledge and conversation skills", "communicate in a compelling manner", "project a positive image", "enjoy solving problems", "attention to detail", "enjoy coaching others". These could be skills. But we already have Requirements covering many. The instruction: Prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section? But they ask to use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content.
We have:
- About the role: yes.
- Responsibilities: yes.
- Requirements: yes (the list).
- Qualifications: maybe the bonus points and bilingual.
- Skills: maybe we could extract explicit skill statements: "You have basic math skills and ability to problem solve", "You have demonstrated ability to make personal connections, engage and educate customers, ask open-ended questions, and listen", "You have strong business development capabilities", "You use your expert product knowledge and conversation skills", "You communicate in a compelling manner, project a positive image, and enjoy solving problems and creating positive outcomes", "You demonstrate attention to detail", "You enjoy coaching others as a sales mentor". Those could be skills. However they overlap with requirements. Might be better to put them under Skills and keep Requirements as the hard requirements (education, experience, transportation, NMLS, etc). Let's see.
The "We’re excited to talk to you if" list includes both hard requirements and soft skills. Could split: Requirements = education, experience, transportation, NMLS registration, ability to learn quickly, basic math skills, problem solving. Qualifications = demonstrated ability to make connections, business development capabilities, thrive in high-energy team, use expert product knowledge, communication, attention to detail, coaching others. Bonus points = college degree, bilingual.
But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section called Requirements (or Qualifications). But they ask to use headings for those specific names if we include them. We could include only Requirements and Qualifications if we have content for both. Let's see if we can split meaningfully.
Requirements (mandatory): HS Diploma or equivalent, two years retail banking sales experience or other relevant experience, reliable transportation and ability to work branch hours including weekends/evenings, ability to obtain NMLS registration within 90 days, ability to learn products/services/procedures quickly and accurately, basic math skills and ability to problem solve within risk parameters.
Qualifications (preferred/desired): demonstrated ability to make personal connections, engage and educate customers, ask open-ended questions, listen to establish trust and build lasting relationships; strong business development capabilities for proactively growing personal book of business using campaign offers, prospecting leads, service-to-sales conversations, leveraging centers of influence; thrive in high-energy sales-driven team, leverage daily coaching and feedback to polish sales outcomes; use expert product knowledge and conversation skills to build upon customers' needs and make a true difference; communicate in a compelling manner, project a positive image, enjoy solving problems and creating positive outcomes; demonstrate attention to detail whether completing documents or explaining features and benefits; enjoy coaching others as a sales mentor; Bonus points: college degree or military equivalent strongly preferred; bilingual.
That seems reasonable.
Skills: Could be derived but maybe we can omit Skills section to avoid thin section. However we have explicit skill statements like "basic math skills", "ability to problem solve", "demonstrated ability to make personal connections", etc. Those are already in Requirements/Qualifications. So we can skip Skills.
Benefits: The posting includes a paragraph about benefits: "UMB offers competitive and varied benefits to eligible associates, such as Paid Time Off; a 401(k) matching program; annual incentive pay; paid holidays; a comprehensive company sponsored benefit plan including medical, dental, vision, and other insurance coverage; health savings, flexible spending, and dependent care accounts; adoption assistance; an employee assistance program; fitness reimbursement; tuition reimbursement; an associate wellbeing program; an associate emergency fund; and various associate banking benefits. Benefit offerings and eligibility requirements vary."
That's substantive. So include Benefits.
Pay: The posting includes compensation details: "Targeted compensation for this opening The posted salary range reflects the broadest standard range for this role, including all locations. The anticipated compensation for this specific opening is $22-23/hr. This position was posted on 09/21/2026. The application deadline for this position is 45 days from the posting date unless filled earlier. Compensation Range $44,685 - $65,736 The posted compensation range on this listing represents UMB’s good faith and reasonable estimate based on its budget and what it expects to be the starting pay for this role, but the actual compensation may vary by geographic location, experience level, and other job-related factors."
We need to include Pay section only if posting actually states them. It does. So include Pay with the specifics: anticipated compensation $22-23/hr, annual range $44,685 - $65,736, posted date, application deadline maybe? But Pay section should focus on compensation. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include Pay with the compensation details. Should we include posting date and deadline? Those are not pay but could be included in a short paragraph maybe under Pay or maybe we could drop them as metadata. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So posting date and deadline could be minor metadata; we could fold into a short
under Pay or maybe we could drop them. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the posting date and deadline somewhere. Could be a short
after Pay section or maybe under About the role? Better to include a short
with that info, maybe under a generic "Details" but we don't have a heading for that. Could just include a
after Pay section with that info. The instruction says we can fold minor metadata into a short
or drop it. So we can include a short
with posting date and deadline. Schedule: Does posting mention schedule? It mentions "ability to work branch hours, including weekends and some evenings". That's about schedule. So we could include a Schedule section with that detail. However the schedule is also part of Requirements (transportation and ability to work branch hours). But we could still have a Schedule section if we have specific content. The posting does not give explicit schedule like "Monday-Friday 9-5" etc. It just says ability to work branch hours including weekends and some evenings. That's somewhat schedule-related. Could include Schedule section with that detail. However we might avoid thin section. But we have that detail; we could put it under Requirements (already have). But we already have a Requirements section with that detail. So we might not need separate Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Skills? but we can skip. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:
About the role
... (the about role paragraph(s)).
Responsibilities
- Asking