Jobs · Finance · Missouri

Treasury Management Portfolio Manager II

Simmons Bank · Kansas City, MO · 6 days ago
FinanceFull-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - Position Summary (About the role) - Essential Duties And Responsibilities (Responsibilities) - Qualifications (Requirements) - Skills (could be part of Qualifications or separate) - Education And/or Experience (Qualifications) - Computer Skills (Skills) - Certificates, Licenses, Registrations (Qualifications) - Other Qualifications (including Physical Requirements) (Qualifications) - Other (miscellaneous) - Skills Training (Skills) - Equal Employment Opportunity Information (boilerplate - remove) Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use
  • for lists,

    for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, cookie/navigation/legal/scam-warning, duplicated lines, application instructions) - Include section ONLY when real, specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Now, let's structure: 1. About the role (Position Summary) - prose 2. Responsibilities (Essential Duties And Responsibilities) - list 3. Qualifications (Education And/or Experience, Certificates, Licenses, Registrations, Other Qualifications) - could combine into Qualifications section with sub-lists or separate? The rules say use headings like Qualifications, Skills, etc. I'll create a Qualifications section with subsections? But the rule says use

    for section headings. I think we should have a Qualifications heading and then list items. However, there are multiple subcategories: Education, Certificates, Other Qualifications. Could present as a list with sub-bullets or separate lists. Since the rule says use
    • for any list of duties/requirements/benefits, and

      for prose. I'll create a Qualifications section with a list that includes education, experience, certificates, other qualifications. But the posting has "Qualifications" as a heading, then "Skills", "Education And/or Experience", "Computer Skills", "Certificates, Licenses, Registrations", "Other Qualifications". I think we can combine into a Qualifications section with multiple lists or a single list with categories. However, the rule says "Use

      • for any list of duties/requirements/benefits". So we can have multiple
          under the same heading. Also there is "Skills" section (the first Skills list) and "Skills Training" at the end. The first Skills list appears under "Qualifications" heading? Actually the text: "Qualifications To perform this job successfully... The requirements listed below are representative of the knowledge, skill, and/or ability required. Skills Ability to perform tasks quickly and accurately...." So "Skills" is a subsection of Qualifications. Then "Education And/or Experience", "Computer Skills", "Certificates, Licenses, Registrations", "Other Qualifications". Then later "Skills Training Communication, Customer Service, Bank Products and Services, Telephone". That seems like a separate list of skills training. I'll create: - About the role (Position Summary) - Responsibilities (Essential Duties And Responsibilities) - Qualifications (with sub-lists: Skills, Education & Experience, Computer Skills, Certificates/Licenses, Other Qualifications) - Skills Training (maybe separate Skills section? But the rule says use headings like Skills. Could have a Skills section for the first skills list, but it's under Qualifications. I think better to have a Qualifications section that includes all qualification-related items, and a separate Skills section for the "Skills Training" list? However, the first skills list is labeled "Skills" and is part of qualifications. The "Skills Training" at the end is also skills. Might combine into one Skills section? But the rule says "Prefer a few substantive sections over many thin ones." So I'll create a Qualifications section that includes all the qualification details, and maybe a separate Skills section for the training list? But the training list is just a list of topics. Could be part of Qualifications. Let's examine the content: Position Summary: prose. Essential Duties And Responsibilities: list of bullet points (each line seems like a bullet). I'll make a
            with each as
          • . Qualifications: introductory sentence, then: - Skills (list of abilities) - Education And/or Experience (two items: Bachelors degree..., Five plus years...) - Computer Skills (MS Office programs) - Certificates, Licenses, Registrations (none listed? It says "Certificates, Licenses, Registrations" then "Other Qualifications (including Physical Requirements)" then list: Thorough knowledge..., Excellent professional..., Strong customer service..., Proficient computer... So Certificates section appears empty? Actually the text: "Certificates, Licenses, Registrations Other Qualifications (including Physical Requirements) Thorough knowledge of treasury management products..." It seems like "Certificates, Licenses, Registrations" is a heading with no content, then "Other Qualifications" has content. I'll include only the ones with content. Other: "Please note this job description is not designed to cover..." - this is boilerplate, but it's a note about the job description. Might be considered substantive? The rule says remove duplicated lines and application instructions. This is a disclaimer. I'll include it as a short

            maybe under a "Note" heading? But the rule says include section ONLY when real, specific content. This is a generic disclaimer. I'll drop it. Skills Training: list of topics. Could be a Skills section. Equal Employment Opportunity Information: boilerplate, remove. Now, headings: Use

            for section headings. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I'll map: - Position Summary -> About the role - Essential Duties And Responsibilities -> Responsibilities - Qualifications (including Skills, Education, etc.) -> Qualifications - Skills Training -> Skills (or maybe part of Qualifications). I'll make a separate Skills section for the training list. But the first Skills list is under Qualifications. I'll include it within Qualifications section as a sub-list. Let's structure HTML:

            About the role

            Position Summary Treasury Management Portfolio Manager II manages a defined Treasury Management portfolio of medium to high complexity. Associate will be responsible for collaborating with Treasury Management Officers (TMO), Bankers, and Market leadership to proactively manage existing customers, Treasury Management Implementation (TMI) to oversee facilitation of implementing banking services to existing customers, and work with Management Operations, Product, and/or Pricing to escalate and resolve problems for Commercial customers.

            Responsibilities

            • Fields escalated interactions with existing Treasury Management customers to assist with issues and concerns
            • Manage treasury portfolio of medium to high complexity
            • Identify opportunities to deepen existing customer relationships and cross sell TM products
            • Assists in customer training for new product lines
            • Clearly understand customer needs and expectations while delivering customer service in a knowledgeable, accurate and professional manner with the ability to deal effectively and tactfully with customers in handling complaints, problems, and general inquiries
            • Complete work in an efficient and accurate manner. Volume of work produced meets expectations. Plan, organize, and prioritize work to meet deadlines
            • Foster collaboration with other lines of business by building credibility and trust.
            • May accompany TMSC and/or TMI on customer calls
            • Ensures all departmental documents and activities are performed in compliance with applicable laws, regulations, policies and procedures as applicable to this position, including completion of required compliance training.
            • Performs other duties and responsibilities as assigned.

            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.

            Skills

            ? But rule says use

            for section headings. Should I use

            ? The rule says "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid

            but says use

            for section headings. I think we should keep only

            for main sections. Subsections could be

            but not required. However, the rule says "Output ONLY the HTML fragment". I'll use

            for main sections only. For subsections, I can use or just incorporate into lists. But the content has distinct categories. I could make separate

            for each? But that would create many thin sections. The rule says "Prefer a few substantive sections over many thin ones." So I'll keep Qualifications as one section with multiple lists, each preceded by a bold label or a

            ? The rule doesn't forbid

            . But to be safe, I'll use

            for main sections only, and within Qualifications, I'll use

            Skills

            then
              , etc. However, the rule says "Use
              • for any list of duties/requirements/benefits, and

                for prose." It doesn't say we can't use

                . I think using

                is okay as long as we don't create too many sections. But the instruction says "use

                for section headings". It doesn't say we cannot use other heading levels. I'll use

                for the main sections, and for subsections I'll use

                but that might be considered a section heading. Safer to avoid extra headings and just use bold labels. Let's do:

                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.

                Skills

                • Ability to perform tasks quickly and accurately.
                • Ability to operate in a team environment to accomplish shared goals.
                • Ability to solve practical problems and interpret a variety of instruction provided in written and/or oral form.
                • Ability to read and interpret documents such as procedures manuals, general business correspondence and/or journals or government regulations.
                • Ability to maintain effective interpersonal relationships with management and team members.
                • Ability to prioritize multiple demands in a high-pressure environment while maintaining professional demeanor
                • Ability to identify and resolve/escalate problems with minimal guidance

                Education and/or Experience

                • Bachelors degree or equivalent work experience
                • Five plus years of related experience; with at least four years of Treasury Management experience preferred.

                Computer Skills

                • MS Office programs

                Other Qualifications

                • Thorough knowledge of treasury management products
                • Excellent professional verbal and written communication skills
                • Strong customer service skills
                • Proficient computer navigation skills using a variety of software packages including Microsoft Office applications
                Note: Certificates, Licenses, Registrations had no content, so

Similar jobs