Relationship Banker - Team Lead - Jackson MS Market Interview Day
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The introductory paragraph after "Job Description". Actually the posting starts with some fluff about Regions, then "Job Description". The description: "At Regions, the Relationship Banker – Team Lead is responsible for meeting with customers and prospects both in person and on the phone to determine their financial needs, and meeting those needs by proactively offering appropriate products, services, and guidance to achieve their financial goals. In addition, the Relationship Banker – Team Lead is responsible for coaching a team of bankers and will oversee some branch activities in the Branch Manager’s absence. This role offers an exciting opportunity for candidates with retail or sales experience that are interested in a career with opportunities for growth, development, and upward mobility. Regions' mission is to make life better for our customers and communities, and we are looking for candidates committed to helping customers reach their financial goals by understanding and meeting customer needs. The successful candidate should be individually driven and competitive, as well as motivated to work as a team to achieve a common goal. This requires a candidate with strong communication and leadership skills as well as the ability to provide personalized customer service." We can put that under About the role. - Responsibilities: List of primary responsibilities bullet points. The posting lists many responsibilities in paragraph form separated by line breaks? It says "Primary Responsibilities" then a list of sentences each starting with a verb. We'll turn each into
headings and - for lists,
for prose.
We must not include markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ...
...
Requirements
- High School Diploma or GED
...
- Ability to work Saturdays as needed
...
- Registration with the Nationwide Mortgage Licensing System and Registry (NMLS)
Qualifications
- Bachelor’s degree (preferred)
- Supervisory/management experience (preferred)
Skills and Competencies
...
Benefits
...
Pay
Minimum Job Range Target: $44,905.90 USD; Median: $55,692.00 USD. This role is eligible for commission and formulaic incentive plans based on performance against defined metrics and goals.
Schedule
Full-time position.
We need to ensure we didn't include any boilerplate like EEO, etc.
Check that we didn't repeat job title as heading. Good.
Now verify we preserved all substantive information.
Let's extract all substantive info from posting:
- Intro fluff about Regions (maybe not needed? It's generic but could be considered About the role? The spec says preserve ALL substantive information; do NOT invent or summarize away detail. The intro fluff about Regions believing associates deserve more than just a job etc. Is that substantive? It's generic marketing fluff but still part of posting. Should we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The intro fluff is not boilerplate; it's part of the posting's marketing. Might be considered substantive? It's not about the role specifically. However the spec says "Prefer a few substantive sections over many thin ones." Could include it in About the role as prose. It's okay.
But we already wrote About the role paragraph starting with "At Regions, the Relationship Banker – Team Lead is responsible...". We omitted the earlier fluff about Regions believing associates deserve more than just a job. Should we include that? It's not about the role but about company culture. Might be considered substantive. To be safe, we could include a brief paragraph about Regions' belief etc. However the spec says "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 intro fluff is not metadata; it's descriptive. I'd include it in About the role before the role description.
Thus About the role paragraph could be:
At Regions, we believe associates deserve more than just a job. We believe in offering performance-driven individuals a place where they can build a career — a place to expect more opportunities. If you are focused on results, dedicated to quality, strength and integrity, and possess the drive to succeed, then we are your employer of choice. At Regions, the Relationship Banker – Team Lead is responsible for meeting with customers and prospects both in person and on the phone to determine their financial needs, and meeting those needs by proactively offering appropriate products, services, and guidance to achieve their financial goals. In addition, the Relationship Banker – Team Lead is responsible for coaching a team of bankers and will oversee some branch activities in the Branch Manager’s absence. This role offers an exciting opportunity for candidates with retail or sales experience that are interested in a career with opportunities for growth, development, and upward mobility. Regions' mission is to make life better for our customers and communities, and we are looking for candidates committed to helping customers reach their financial goals by understanding and meeting customer needs. The successful candidate should be individually driven and competitive, as well as motivated to work as a team to achieve a common goal. This requires a candidate with strong communication and leadership skills as well as the ability to provide personalized customer service.
That preserves all.
Now Responsibilities list we have.
Requirements list: include all items plus NMLS registration.
Check if any other requirements: "Ability to work Saturdays as needed" included. Also "This position requires the tracking of time for hours worked in excess of 40 per week and is eligible for overtime under the Fair Labor Standards Act." That's a requirement about overtime eligibility. Could be included as a requirement: "Eligible for overtime for hours worked over 40 per week under FLSA." Also "This position is incentive eligible." Could be a requirement? It's more about compensation. Might be included in Pay section. But we can add as a requirement: "Incentive eligible." However we already have incentive in Pay. Might be okay to include in Requirements as "Incentive eligible." But we
for prose. We must not include markdown fences. We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- High School Diploma or GED ...
- Ability to work Saturdays as needed ...
- Registration with the Nationwide Mortgage Licensing System and Registry (NMLS)
Qualifications
- Bachelor’s degree (preferred)
- Supervisory/management experience (preferred)
Skills and Competencies
-
...
Benefits
-
...
Pay
Minimum Job Range Target: $44,905.90 USD; Median: $55,692.00 USD. This role is eligible for commission and formulaic incentive plans based on performance against defined metrics and goals.
Schedule
Full-time position.
We need to ensure we didn't include any boilerplate like EEO, etc. Check that we didn't repeat job title as heading. Good. Now verify we preserved all substantive information. Let's extract all substantive info from posting: - Intro fluff about Regions (maybe not needed? It's generic but could be considered About the role? The spec says preserve ALL substantive information; do NOT invent or summarize away detail. The intro fluff about Regions believing associates deserve more than just a job etc. Is that substantive? It's generic marketing fluff but still part of posting. Should we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The intro fluff is not boilerplate; it's part of the posting's marketing. Might be considered substantive? It's not about the role specifically. However the spec says "Prefer a few substantive sections over many thin ones." Could include it in About the role as prose. It's okay. But we already wrote About the role paragraph starting with "At Regions, the Relationship Banker – Team Lead is responsible...". We omitted the earlier fluff about Regions believing associates deserve more than just a job. Should we include that? It's not about the role but about company culture. Might be considered substantive. To be safe, we could include a brief paragraph about Regions' belief etc. However the spec says "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 shortor drop it." The intro fluff is not metadata; it's descriptive. I'd include it in About the role before the role description. Thus About the role paragraph could be:
At Regions, we believe associates deserve more than just a job. We believe in offering performance-driven individuals a place where they can build a career — a place to expect more opportunities. If you are focused on results, dedicated to quality, strength and integrity, and possess the drive to succeed, then we are your employer of choice. At Regions, the Relationship Banker – Team Lead is responsible for meeting with customers and prospects both in person and on the phone to determine their financial needs, and meeting those needs by proactively offering appropriate products, services, and guidance to achieve their financial goals. In addition, the Relationship Banker – Team Lead is responsible for coaching a team of bankers and will oversee some branch activities in the Branch Manager’s absence. This role offers an exciting opportunity for candidates with retail or sales experience that are interested in a career with opportunities for growth, development, and upward mobility. Regions' mission is to make life better for our customers and communities, and we are looking for candidates committed to helping customers reach their financial goals by understanding and meeting customer needs. The successful candidate should be individually driven and competitive, as well as motivated to work as a team to achieve a common goal. This requires a candidate with strong communication and leadership skills as well as the ability to provide personalized customer service.
That preserves all. Now Responsibilities list we have. Requirements list: include all items plus NMLS registration. Check if any other requirements: "Ability to work Saturdays as needed" included. Also "This position requires the tracking of time for hours worked in excess of 40 per week and is eligible for overtime under the Fair Labor Standards Act." That's a requirement about overtime eligibility. Could be included as a requirement: "Eligible for overtime for hours worked over 40 per week under FLSA." Also "This position is incentive eligible." Could be a requirement? It's more about compensation. Might be included in Pay section. But we can add as a requirement: "Incentive eligible." However we already have incentive in Pay. Might be okay to include in Requirements as "Incentive eligible." But we