Senior Fund Banking Executive Assistant
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Applications are accepted until the position is filled." Also remove EEO statements. Also remove "Know Your Rights." etc.
We need to preserve all substantive information. So we need to include:
- About the role? Not explicitly but we have "What You'll Be Doing" which is responsibilities. Could use heading "Responsibilities". Also "What We're Looking For" could be "Requirements" or "Qualifications". "What You'll Bring" could be "Skills". "Education & Experience" heading. "Licenses & Credentials". "Systems & Technology". "Compensation Range". Benefits: they mention "Other benefits and offerings include, but not limited to, discretionary bonuses, health / dental / vision / prescription insurance offerings, Stifel Total Health Connect, flexible spending accounts, tuition & certification assistance programs, paid time off, and much, much more!" Also earlier: "At Stifel we offer an entrepreneurial environment, comprehensive benefits package to include health, dental and vision care, 401k, wellness initiatives, life insurance, and paid time off." So we can combine benefits.
We must not create sections with filler like "commensurate with experience". The compensation range is given: Salary: USD $80,000.00/Yr. - USD $100,000.00/Yr. So we can include Pay section.
Schedule: not mentioned, so omit.
We need to ensure we don't include duplicated lines. The posting repeats some lines: "Let’s talk about how you can find your place here at Stifel, where success meets success." appears twice. We should include only once? Probably we can keep one instance in About Stifel section.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the Role
maybe not needed? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe short intro). But we have "Why Stifel" paragraph at start: "Why Stifel Stifel strives for a culture that puts its clients and associates first: a culture where everyone belongs, everyone is welcome, and everyone contributes to the success of our clients, their careers, and the firm as a whole. Let’s talk about how you can find your place here at Stifel, where success meets success." That's about company culture. Could be "About the role" or "About Stifel". Since they said About the role is a possible heading. We'll use About the role for that culture paragraph.
Then Responsibilities: from "What You'll Be Doing". We'll list bullet points.
Then Requirements/Qualifications: from "What We're Looking For". Could be Requirements.
Then Skills: from "What You'll Bring".
Then Education & Experience.
Then Licenses & Credentials.
Then Systems & Technology.
Then Pay: compensation range.
Then Benefits: list benefits.
Then About Stifel: maybe we already used About the role; we could have About Stifel as separate section describing company. But we might combine. The instruction says prefer a few substantive sections over many thin ones. We could merge About the role and About Stifel into one "About Stifel" section. But they gave example headings including About the role. We'll decide: Use About the role for the culture/intro paragraph. Then About Stifel for company overview? Might be thin. Better to have About Stifel as section with company overview, and maybe skip About the role. However we need to include the culture paragraph somewhere. Could put it under About Stifel.
Thus sections:
- About Stifel (includes culture paragraph and company overview)
- Responsibilities
- Requirements
- Skills
- Education & Experience
- Licenses & Credentials
- Systems & Technology
- Pay
- Benefits
Check if any section is empty: all have content.
Now we need to extract content precisely, preserving all substantive information, not inventing or summarizing away detail.
Let's extract each.
**About Stifel**: Combine the culture paragraph and company overview.
Culture paragraph: "Why Stifel Stifel strives for a culture that puts its clients and associates first: a culture where everyone belongs, everyone is welcome, and everyone contributes to the success of our clients, their careers, and the firm as a whole. Let’s talk about how you can find your place here at Stifel, where success meets success."
Company overview: "Stifel is more than 130 years old and still thinking like a start-up. We are a global wealth management and investment banking firm serious about innovation and fresh ideas. Built on a simple premise of safeguarding our clients’ money as if it were our own, coined by our namesake, Herman Stifel, our success is intimately tied to our commitment to helping families, companies, and municipalities find their own success. While our headquarters is in St. Louis, we have offices in New York, San Francisco, Baltimore, London, Frankfurt, Toronto, and more than 400 other locations. Stifel is home to approximately 9,000 individuals who are currently building their careers as financial advisors, research analysts, project managers, marketing specialists, developers, bankers, operations associates, among hundreds more. At Stifel we offer an entrepreneurial environment, comprehensive benefits package to include health, dental and vision care, 401k, wellness initiatives, life insurance, and paid time off."
Note: The benefits sentence duplicates benefits; we will later list benefits separately. But we can keep it in About Stifel as part of overview; it's okay.
We must remove duplicated lines: The phrase "Let’s talk about how you can find your place here at Stifel, where success meets success." appears twice (once in culture, once at end of company overview? Actually appears at end of company overview? The company overview ends with "At Stifel we offer an entrepreneurial environment..." not that phrase. The duplicate appears earlier in the culture paragraph and later after "About Stifel" maybe? Actually after the company overview they repeat "Let’s talk about how you can find your place here at Stifel, where success meets success." At the very end before EEO. We'll include only once.
Thus About Stifel paragraph will include culture sentence once, plus company overview.
Now Responsibilities: from "What You'll Be Doing". The paragraph: "The Senior Fund Banking Executive Assistant supports Fund Banking leadership, including Managing Directors, by providing advanced executive support and administrative leadership across the Fund Banking organization. This role serves as a trusted operational partner, anticipates leadership and client needs, coordinates high-impact activities, and promotes consistent, efficient administrative practices."
Then bullet list of duties: Actually the responsibilities are listed in bullet-like sentences after that? The posting: after that paragraph, there is a list:
- Provide advanced executive support to Fund Banking Managing Directors and other senior leaders, including management of highly complex calendars, scheduling, travel, and expenses.
- Serve as a trusted operational partner to Fund Banking leadership by anticipating needs, resolving issues, and coordinating priorities across multiple stakeholders.
- Lead the planning and execution of high-impact client meetings, leadership sessions, conferences, team events, and other Fund Banking engagements.
- Prepare, review, and coordinate complex correspondence, presentations, reports, meeting materials, and executive communications.
- Manage sensitive client, business, personnel, and financial matters with a high degree of discretion, judgment, and confidentiality.
- Establish and promote administrative processes, workflows, and best practices that improve consistency, service, and scalability across Fund Banking.
- Mentor and guide administrative professionals by sharing knowledge, coordinating coverage, and providing day-to-day support on complex matters.
- Coordinate onboarding, transitions, office logistics, access, and long-range administrative planning for Fund Banking leaders and team members.
- Build effective relationships with clients, prospects, sponsors, investors, internal partners, vendors, and service providers.
- Continuously evaluate administrative operations and recommend improvements that enhance efficiency, communication, and the client experience.
We need to put these in - .
Now Requirements: from "What We're Looking For". Actually that section is same as responsibilities? Wait the posting: after "What You'll Be Doing" there is "What We're Looking For". Then bullet list similar to responsibilities? Let's re-examine: The text:
"What You'll Be Doing The Senior Fund Banking Executive Assistant supports Fund Banking leadership, including Managing Directors, by providing advanced executive support and administrative leadership across the Fund Banking organization. This role serves as a trusted operational partner, anticipates leadership and client needs, coordinates high-impact activities, and promotes consistent, efficient administrative practices. What We're Looking For Provide advanced executive support to Fund Banking Managing Directors and other senior leaders, including management of highly complex calendars, scheduling, travel, and expenses. Serve as a trusted operational partner to Fund Banking leadership by anticipating needs, resolving issues, and coordinating priorities across multiple stakeholders. Lead the planning and execution of high-impact client meetings, leadership sessions, conferences, team events, and other Fund Banking engagements. Prepare, review, and coordinate complex correspondence, presentations, reports, meeting materials, and executive communications. Manage sensitive client, business, personnel, and financial matters with a high degree of discretion, judgment, and confidentiality. Establish and promote administrative processes, workflows, and best practices that improve consistency, service, and scalability across Fund Banking. Mentor and guide administrative professionals by sharing knowledge, coordinating coverage, and providing day-to-day support on complex matters. Coordinate onboarding, transitions, office logistics, access, and long-range administrative planning for Fund Banking leaders and team members. Build effective relationships with clients, prospects, sponsors, investors, internal partners, vendors, and service providers. Continuously evaluate administrative operations and recommend improvements that enhance efficiency, communication, and the client experience."
It seems the "What We're Looking For" section actually repeats the same bullet list as responsibilities? Actually the responsibilities paragraph earlier gave a summary, then the bullet list under "What We're Looking For" is the detailed duties. So we need to differentiate: Responsibilities = summary paragraph? Or we could treat the bullet list as Responsibilities and the earlier paragraph as overview. But the instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need Responsibilities section (list of duties). Requirements/Qualifications: maybe from "What You'll Bring"? Actually "What You'll Bring" is skills. "Education & Experience" is education/experience. "Licenses & Credentials". "Systems & Technology". So "What We're Looking For" might be considered Requirements (maybe same as responsibilities). But we already have responsibilities list. To avoid duplication, we could treat the summary paragraph as Responsibilities overview, and the bullet list as Requirements? However the bullet list is clearly duties. The "What We're Looking For" heading seems to be a mislabel; but content is duties. The "What You'll Bring" is skills/qualities. So we need to map:
- Responsibilities: bullet list from "What We're Looking For" (the detailed duties).
- Requirements: maybe from "Education & Experience"? Actually education/experience is separate. Requirements could be "Education & Experience" and "Licenses & Credentials" and "Systems & Technology". But the instruction gave example headings: Requirements, Qualifications, Skills. So we could have Requirements (education & experience), Qualifications (licenses & credentials, systems & technology), Skills (what you bring). But we need to follow instruction: use
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Applications are accepted until the position is filled." Also remove EEO statements. Also remove "Know Your Rights." etc. We need to preserve all substantive information. So we need to include: - About the role? Not explicitly but we have "What You'll Be Doing" which is responsibilities. Could use heading "Responsibilities". Also "What We're Looking For" could be "Requirements" or "Qualifications". "What You'll Bring" could be "Skills". "Education & Experience" heading. "Licenses & Credentials". "Systems & Technology". "Compensation Range". Benefits: they mention "Other benefits and offerings include, but not limited to, discretionary bonuses, health / dental / vision / prescription insurance offerings, Stifel Total Health Connect, flexible spending accounts, tuition & certification assistance programs, paid time off, and much, much more!" Also earlier: "At Stifel we offer an entrepreneurial environment, comprehensive benefits package to include health, dental and vision care, 401k, wellness initiatives, life insurance, and paid time off." So we can combine benefits. We must not create sections with filler like "commensurate with experience". The compensation range is given: Salary: USD $80,000.00/Yr. - USD $100,000.00/Yr. So we can include Pay section. Schedule: not mentioned, so omit. We need to ensure we don't include duplicated lines. The posting repeats some lines: "Let’s talk about how you can find your place here at Stifel, where success meets success." appears twice. We should include only once? Probably we can keep one instance in About Stifel section. We need to output only HTML fragment, no /, no markdown fences. Let's structure: