Banking Center Manager II

The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it appropriately. First, I need to identify the sections: 1. Summary/About the role - there's a "Summary" section 2. Essential Duties And Responsibilities - this has multiple subsections: Strategic leadership, Sales and business development, Client Experience, Team management, Compliance and risk management, Operational efficiency, Other job-related duties 3. Supervisory Responsibilities 4. Qualifications - includes education, computer skills, certificates/licenses, background check requirements 5. About Us - company description 6. Benefit Highlights - list of benefits I should use

for section headings. The rules say: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Now, let me structure the HTML. I'll start with the Summary as "About the role" or "Summary". The posting has "Summary" as a heading. I'll use

  About the role

  or

  Summary

  . The example says "About the role". I'll use "About the role". Then Responsibilities: The posting has "Essential Duties And Responsibilities" with subsections. I could make each subsection a separate list under a main Responsibilities heading, or make each subsection its own heading. The rule says use

  for section headings like Responsibilities. But there are multiple sub-areas. I think I should have a main

  Responsibilities

  and then perhaps subheadings? But the rule only mentions

  for section headings. It doesn't mention subheadings. However, the content has clear subsections. I could use

  for subsections? But the instruction says use

  for section headings. It doesn't forbid other heading levels, but to keep it simple, maybe I should treat each major area as a separate section with

  . But the example list includes "Responsibilities" as a section heading. The posting has "Essential Duties And Responsibilities" as a major section with multiple bullet points grouped under subheadings. I think I'll create a

  Responsibilities

  and then for each sub-area, I'll create a

  or just use

  with bold? But the rule says use

  • for any list of duties. The subsections are essentially categories of duties. I could make each sub-area a separate
    with a heading. Since the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)", it implies those are the main sections. But the posting has more granular sections. I think I should follow the posting's structure but map to the suggested headings where appropriate. Let me map: - Summary -> About the role - Essential Duties And Responsibilities -> Responsibilities (with subsections) - Supervisory Responsibilities -> could be part of Responsibilities or separate. It's a distinct section. - Qualifications -> Qualifications (or Requirements) - Computer And Office Equipment Skills -> Skills - CERTIFICATES, LICENSES, REGISTRATIONS -> could be part of Qualifications - Background check and SAFE Act -> part of Qualifications - About Us -> About the company (maybe not a standard heading but we can include) - Benefit Highlights -> Benefits The rule says: include a section ONLY when the posting has real, specific content for it. So I'll include sections that have content. I'll create: 1.

    About the role

    with the summary paragraph. 2.

    Responsibilities

    with the essential duties. Since there are subsections, I'll use

    for each sub-area? But the instruction doesn't mention

    . However, it's semantic HTML, using

    for subsections is fine. But to be safe, I could use

    for each sub-area? That would create many

    headings. The example list includes "Responsibilities" as one heading. I think I'll keep one

    Responsibilities

    and then for each sub-area, I'll use a

    Strategic leadership

    followed by
    . That's acceptable. Alternatively, I could make each sub-area a separate

    but that might be too many. The rule says "Prefer a few substantive sections over many thin ones." So I'll group under Responsibilities. Similarly, Supervisory Responsibilities could be a separate

    Supervisory responsibilities

    or part of Responsibilities. It's a distinct section in the posting. I'll make it a separate

    Supervisory responsibilities

    . Qualifications: includes education, computer skills, certificates, background check. I'll make

    Qualifications

    and include all. Skills: Computer skills could be a separate Skills section, but it's part of qualifications. I'll include under Qualifications. Benefits: Benefit Highlights ->

    Benefits

    About Us: This is company description. Could be

    About the company

    but not in the example list. The rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). "About the company" is not listed, but it's substantive content. I'll include it as

    About the company

    . Now, remove boilerplate: "Equal Opportunity Employer/Protected Veterans/Individuals with Disabilities This employer is required to notify all applicants of their rights pursuant to federal employment laws. For further information, please review the Know Your Rights notice from the Department of Labor." That's EEO boilerplate, remove. Also remove "Follow Us Facebook X formerly Twitter LinkedIn Instagram YouTube" - navigation/social. Remove "More -- FirstHorizon.com/First-Horizon-National-Corporation/Careers/Our-Benefits" - link. Remove "Location: Onsite at the location listed in the job posting." - that's metadata, maybe fold into a short

    ? The rule says fold minor metadata into a short

    or drop it. I'll include a brief note in About the role or a separate line. The posting starts with "Job Description Location: Onsite at the location listed in the job posting." That's location info. I'll include a

    in About the role: "Location: Onsite at the location listed in the job posting." Now, let's write the HTML. I'll structure:

    About the role

    Location: Onsite at the location listed in the job posting.

    This position is responsible for the overall sales, production, profitability and regulatory compliance of a banking center. It is also the responsibility of this position to ensure the banking center delivers quality, accurate, and timely customer service.

    Responsibilities

    Strategic leadership

    • Coach, lead and manage banking center team to ensure all strategic initiatives are executed effectively.
    • Model and demonstrate First Horizon Bank (Firstpower) culture.
    • Promote a positive work culture by increasing and supporting associate engagement.
    • Represent the company in a professional manner, including being involved in the local market/community through civic organizations or community groups.

    Sales and business development

    • Implement and coach advice driven sales process.
    • Provide one-on-one coaching, inspect, and recognize sales activities and behaviors.
    • Establish and nurture relationships with key clients and partners to expand the client base.
    • Proactively collaborate with and refer to key line of business partners to lead and promote effective One Team partnerships.
    • Business development of market area through proactive sales calls, networking, and participation in local activities to achieve goals and priorities.

    Client Experience

    • Deliver excellent client experiences consistently and promptly resolve client issues effectively.

    Team management

    • Recruit, train, develop, and retain a high-performing Retail banking center team.
    • Lead, grow, coach, and motivate associates to execute banking center routines effectively, aligning with our Purpose, Values, and Action to deliver financial guidance and support.
    • Provide regular coaching, feedback, and performance evaluations to banking center team members.
    • Foster a collaborative and inclusive work environment that promotes teamwork and professional growth.

    Compliance and risk management

    • Collaborate with market operations and sales leadership to ensure compliance with bank regulations, policies, procedures, risk management, internal controls, and the First Horizon code of ethics, while ensuring all associates on the team complete required training.
    • Implement effective risk management practices to minimize potential financial and operational risks.

    Operational efficiency

    • Lead and manage operational excellence for the banking center.
    • Monitor operational metrics and implement improvements as needed.
    • Partner with Retail Operations team to address operational concerns.
    • Responsible for controlling operational and administrative expenses.

    Other job-related duties and special duties as assigned

    Supervisory responsibilities

    Directly responsible for directing, coordinating, and evaluating designated units or certain personnel in accordance with the organization's policies and applicable laws. Responsibilities may include interviewing, hiring, and training employees; planning, assigning, and directing work; assessing performance, providing regular feedback and coaching; providing pay change recommendations; disciplining employees; addressing complaints and resolving problems.

    Qualifications

    To perform this job successfully, an individual must be able to perform each essential duty satisfactorily. The requirements listed below are representative of the knowledge, skill, and/or ability required. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.

    • Bachelor's degree (B. A.) from four-year college or university; or two to four years related experience and/or training; or equivalent combination of education and experience.

    Computer and office equipment skills

    • Microsoft Office suite, Salesforce

    Certificates, licenses, registrations

    • None required

    As part of