Deal Administrator - Collateralized Loan Obligation (multiple levels)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate. Must preserve all substantive info. We need to parse the job posting. First, there is introductory paragraph about U.S. Bank mission etc. That's likely "About the role" or maybe "About the role" section. The posting includes "Job Description" then description of role, then "Key Responsibilities", then "Basic Qualifications", "Preferred Qualifications", then "Location Expectations", then "Benefits:", then "Pay Range". Also schedule info: hybrid/flexible schedule with in-office expectation of 3+ days per week, office location Chicago, IL. We need to map sections: - About the role: Could include the mission statement and description of role (the paragraph after Job Description). Should we include "Job Description" as about the role? Probably yes. - Responsibilities: from "Key Responsibilities" bullet list. - Requirements: maybe "Basic Qualifications" as requirements. - Qualifications: maybe "Preferred Qualifications" as qualifications? But they said sections: Requirements, Qualifications, Skills. We need to decide mapping. The posting has Basic Qualifications (required) and Preferred Qualifications (preferred). Could treat Basic as Requirements, Preferred as Qualifications. Skills could be derived from Preferred Qualifications (strong organizational skills, attention to detail, etc.) but we might also have a Skills section separate. However we should not create thin sections. Perhaps combine Skills into Qualifications or Requirements. But the instruction says use headings for those categories if content exists. We have content for Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay, Schedule. Also About the role. We should not create Skills unless there is distinct skill list. The Preferred Qualifications includes many skill-like items; we could put them under Skills. But then Qualifications would be empty? Better to put Preferred Qualifications under Qualifications, and maybe Skills under a separate heading if we can extract skill-specific items like proficiency in Microsoft Excel, strong computer navigation skills across Microsoft Office applications, etc. Those are skills. So we could have Skills section with those. Let's extract: About the role: The mission paragraph and description of role (the paragraph after Job Description up to "Key Responsibilities"). Responsibilities: bullet list under "Key Responsibilities". Requirements: Basic Qualifications: "Bachelor's degree in finance or related field, or equivalent work experience Typically less than two years of relevant work experience" Qualifications: Preferred Qualifications list: Strong organizational skills with exceptional attention to detail, Basic understanding of indenture documentation and analytical skills, Ability to manage multiple priorities, deadlines, and clients simultaneously, Effective written and verbal communication skills, Ability to interpret data and resolve discrepancies, High stress tolerance and resilience in a deadline‑driven environment, Proficiency in Microsoft Excel, Strong computer navigation skills across Microsoft Office applications Skills: maybe we could extract the specific technical skills: Proficiency in Microsoft Excel, Strong computer navigation skills across Microsoft Office applications. But those are already in Preferred Qualifications. Might be redundant. Better to not create Skills if it duplicates. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills section and put those under Qualifications. So we have sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay, Schedule. Now Benefits: list as given. Pay: "Pay Range: $25.77 - $34.33" Schedule: hybrid/flexible schedule: in-office expectation of 3 or more days per week, flexibility to work outside office location for other days. Office location Chicago, IL. We must not include boilerplate like EEO, E-Verify, etc. Also remove location expectations? We already used location in schedule. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information. Ensure we don't lose any details. Let's craft HTML:

About the role

At U.S. Bank, we’re on a journey to do our best. Helping the customers and businesses we serve to make better and smarter financial decisions and enabling the communities we support to grow and succeed. We believe it takes all of us to bring our shared ambition to life, and each person is unique in their potential. A career with U.S. Bank gives you a wide, ever-growing range of opportunities to discover what makes you thrive at every stage of your career. Try new things, learn new skills and discover what you excel at—all from Day One. This role has multiple levels, open to candidates with 0-5+ years of work experience. The successful candidate will be hired for the level of the position that aligns with their experience. Please note that the salary range provided corresponds to the lowest level of the position posted. U.S. Bank Global Corporate Trust Services is one of the largest providers of corporate trust services in the world. Our clients look to us for trustee, agency, escrow, document custody and money market issuing services via our 48 domestic offices and three international offices. The Collateralized Loan Obligation Group (CLO) is a division within Global Corporate Trust and Custody. CLOs are structured finance vehicles that issue both debt and equity liabilities, with the proceeds being used to buy a portfolio of collateral. Typical types of collateral include syndicated bank loans, corporate bonds, ABS, MBS, and Mezzanine debt. Investors can choose between a variety of risk return options. The CLO Deal Administrator helps keep CLO portfolios running smoothly by handling the day‑to‑day operational work behind the scenes. This role supports daily and monthly reporting, tracks cash and par positions, settles trades, funds bank loans, and reconciles accounts to ensure all portfolio activity is accurate and complete. The administrator works with established processes, communicates regularly with internal teams and external clients via email and phone, and helps respond to routine client inquiries. It’s a fast‑paced, detail‑focused role that provides hands‑on exposure to CLO structures while building a strong foundation in financial operations through training and on‑the‑job learning.

Responsibilities

• Serve as the primary operational contact for assigned CLO clients
• Perform frontline administration for CLO portfolios, ensuring accuracy and timeliness
• Reconcile cash, positions, and portfolio activity across accounts
• Apply and process wires (sending and receiving)
• Settle bank loan and bond trades and manage trade lifecycle activity
• Read and interpret deal notices and indenture-related documentation
• Book cash inflows and outflows and invest excess cash as directed
• Track asset attributes including accruals, ratings, and industry classifications
• Produce and distribute daily, monthly, and quarterly client and investor reports
• Communicate regularly with clients, portfolio managers, middle office teams, agents, and law firms
• Manage high volumes of information and email in a fast‑paced environment
• Identify, investigate, and resolve exceptions through analysis and problem‑solving
• Support analysts with reporting and investor deliverables

Requirements

Bachelor's degree in finance or related field, or equivalent work experience. Typically less than two years of relevant work experience.

Qualifications

• Strong organizational skills with exceptional attention to detail
• Basic understanding of indenture documentation and analytical skills
• Ability to manage multiple priorities, deadlines, and clients simultaneously
• Effective written and verbal communication skills
• Ability to interpret data and resolve discrepancies
• High stress tolerance and resilience in a deadline‑driven environment
• Proficiency in Microsoft Excel
• Strong computer navigation skills across Microsoft Office applications

Benefits

• Healthcare (medical, dental, vision)
• Basic term and optional term life insurance
• Short-term and long-term disability
• Pregnancy disability and parental leave
• 401(k) and employer-funded retirement plan
• Paid vacation (from two to five weeks depending on salary grade and tenure)
• Up to 11 paid holiday opportunities
• Adoption assistance
• Sick and Safe Leave accruals of one hour for every 30 worked, up to 80 hours per calendar year unless otherwise provided by law

Pay

Pay Range: $25.77 - $34.33

Schedule

The role offers a hybrid/flexible schedule, with an in-office expectation of 3 or more days per week and the flexibility to work outside the office location for the other days. Office location is in Chicago, IL.

Check we didn't include any boilerplate. We removed location expectations line about visa sponsorship etc. Good. We need to ensure we didn't miss any substantive info: The description about multiple levels, salary range corresponds to lowest level, etc. Included in About the role. Also note about "This position is not eligible for visa sponsorship, and does not support STEM OPT." That's location expectations but maybe considered substantive? It's about eligibility. The instruction says remove boilerplate, duplicated lines, application instructions. Visa sponsorship info might be considered location expectations but not boilerplate? It's specific to the role. However it's under "Location Expectations" paragraph. It says: "This position is not eligible for visa sponsorship, and does not support STEM OPT." That is substantive info about eligibility. Should we keep it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Visa sponsorship is not exactly those categories; it's about eligibility. Might be considered part of location expectations. I'd keep it maybe under Schedule or a separate note. But we already have Schedule section; we could add that info there. However the instruction says include a section ONLY when posting has real, specific content for it. We have schedule content; we can add visa note there. Let's add to Schedule paragraph: "This position is not eligible for visa sponsorship, and does not support STEM OPT." Thus Schedule paragraph becomes: "The role offers a hybrid/flexible schedule, with an in-office expectation of 3 or more days per week and the flexibility to work outside the office location for the other days. Office location is in Chicago, IL. This position is not eligible for visa sponsorship, and does not support STEM OPT." Check if any other substantive info: "If there’s anything we can do to accommodate a disability during any portion of the application or hiring process, please refer to our disability accommodations for applicants." That's more like application instruction/accommodation note; could be considered boilerplate? It's about disability accommodation; maybe keep? It's not exactly boilerplate but it's a standard statement. The instruction says remove application instructions. This is about accommodation request; could be considered application instruction. Safer to remove. Also "Review our full benefits available by employment status here." That's a link instruction; remove. Also "U.S. Bank is an equal opportunity employer..." that's EEO boilerplate; remove. Also "E-Verify..." remove. Also "The salary range reflects figures based on the primary location..." that's about pay; we already have pay range; could add note that actual range may differ based on location. That's substantive? It says actual range may differ based on location. Could add to Pay section. But we already have pay range; we could add a sentence: "The salary range reflects figures based on the primary location; the actual range may differ based on the location of the role." That's not boilerplate; it's