Advisor Directed Program Senior Specialist

We need to output HTML fragment with sections: headings

for sections present. We need to parse the posting. Content: - "What You'll Be Doing": description paragraphs and bullet list? Actually it's prose sentences. We can treat as

maybe multiple paragraphs. No explicit bullet list. - "What We're Looking For": list of duties/responsibilities (bullet-like sentences). Could be turned into

• . - "What You'll Bring": list of qualifications/skills. - "Education & Experience": list. - "Licenses & Credentials": list. - "Systems & Technology": list. - "About Stifel": prose. - Also maybe "Benefits" mentioned: "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." That's benefits info. So we should include a Benefits section. - Pay/Schedule not present, so omit. We need to not repeat job title as heading. No Job ID. We need to remove boilerplate: EEO etc. The line "Stifel is an Equal Opportunity Employer." should be removed. Also remove navigation/cookie etc none. We need to preserve all substantive info. We need to use

  for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can use headings that match content: maybe "What You'll Be Doing" could map to Responsibilities. "What We're Looking For" maybe Responsibilities as well? Actually "What We're Looking For" is duties. Could combine? But we need to follow instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those standard headings if applicable. But we can also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those exact headings when appropriate. So we need to map content to those headings. We have: - About the role: could be "What You'll Be Doing" (description). So

  About the role

  . - Responsibilities: maybe "What We're Looking For" (duties). So

  Responsibilities

  . - Requirements: maybe "What You'll Bring" (skills/knowledge). Could be Requirements or Qualifications. We have Education & Experience separate. Could treat "What You'll Bring" as Qualifications/Skills. But we also have Education & Experience, Licenses & Credentials, Systems & Technology. We need to avoid thin sections. So we could combine some. Let's think: The posting includes sections: What You'll Be Doing (role description), What We're Looking For (responsibilities), What You'll Bring (qualifications/skills), Education & Experience, Licenses & Credentials, Systems & Technology, About Stifel (company overview), Benefits. We could map: - About the role: What You'll Be Doing. - Responsibilities: What We're Looking For. - Qualifications: What You'll Bring (maybe also Education & Experience? but we can separate). - Requirements: Education & Experience (maybe also Licenses & Credentials). But we need to decide. Better to follow typical job posting: About the role (summary), Responsibilities (duties), Requirements (education/experience/licenses), Qualifications (skills), Benefits. But the instruction list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have multiple headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to avoid empty sections. Let's assign: - About the role: What You'll Be Doing paragraph. - Responsibilities: What We're Looking For list. - Qualifications: What You'll Bring list (skills/knowledge). - Requirements: Education & Experience, Licenses & Credentials, Systems & Technology combined? Could be separate but risk thin. Maybe combine into Requirements with sublists? But we need to use
  • for any list. Could have multiple
    under same heading. We could do:

    Requirements

    • Bachelor's degree
    • 5+ years of investment industry experience
    • Leadership or team management experience preferred
    • Series 7, 63 and 65 (Series 66 in lieu of 63 and 65) within 12 months of hire
    • Proficient in Microsoft Excel, Word, PowerPoint, and Outlook
    • Familiarity with one or more project management applications preferred
    • Experience with data analytics/presentation tools (e.g., Tableau) preferred
    That covers education, experience, licenses, systems. Then Skills: maybe we could separate "What You'll Bring" as Skills. But Qualifications vs Skills ambiguous. We could treat "What You'll Bring" as Qualifications (knowledge, abilities). And Skills maybe not needed. But we have both Qualifications and Skills in list; we can include both if we have content. We could make:

    Qualifications

    from What You'll Bring (knowledge, abilities). That includes: Knowledge of brokerage and investment advisory industries; ability to use logic and reasoning; excellent customer service; exceptional verbal/written communication; process-oriented mindset; understanding of operational and regulatory considerations; ability to act independently; commitment to collaborative work; ability to organize/prioritize; ability to consider costs/benefits. That's a list. Then Skills maybe we could omit if no distinct content. But we have Systems & Technology already covered in Requirements. So we could skip Skills heading. But the instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications, Requirements, Benefits. That's 5 sections. Let's map: - About the role: What You'll Be Doing (paragraph). - Responsibilities: What We're Looking For (list). - Qualifications: What You'll Bring (list). - Requirements: Education & Experience, Licenses & Credentials, Systems & Technology (list). - Benefits: Benefits paragraph from About Stifel (benefits). Also maybe include entrepreneurial environment etc. We need to exclude boilerplate: "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." That's benefits. Also we have About Stifel description (history, locations). That's not benefits but could be About the company. But we already have About the role. Could we add a section About the company? Not in list. Might be considered extra but we could incorporate into About the role? Probably better to include as a separate section "About Stifel" but not in prescribed headings. However instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but gives examples. Safer to stick to those. Thus we could incorporate the About Stifel description into About the role? Not ideal but maybe we can add a brief paragraph under About the role about the company. However the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Could add a section "About the company" but not in list; risk being considered extra but maybe okay. However they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The e.g. suggests those are examples, not exclusive. So we can add other headings like About Stifel. Thus we can have:

    About the role

    ...What You'll Be Doing...

    Responsibilities

    ...What We're Looking For...

    Qualifications

    ...What You'll Bring...

    Requirements

    ...Education & Experience, Licenses & Credentials, Systems & Technology...

    About Stifel

    ...company overview...

    Benefits

    ...benefits...

    We must not include Pay/Schedule. Now we need to ensure we don't include boilerplate like EEO line. Remove that. Also remove any duplicated lines. Let's extract the text. Original: "What You'll Be Doing The Advisor Directed Programs Sr. Specialist works on all aspects of the team's respective advisory programs. The Sr. Specialist collaborates with the Program Manager, Financial Advisors (FAs), Compliance, Advisory Operations, and other groups inside and outside Stifel. The primary goal of the program management team is to provide highly competent support to Stifel Financial Advisors through the efficient and effective management of Advisor Directed advisory programs. Success in this role requires an engaged, proactive communicator who is comfortable picking up the phone to work directly with Financial Advisors and their staff, including when conversations are complex or difficult. The Sr. Specialist also brings a process-oriented mindset, identifying opportunities to re-imagine legacy processes and develop clearer, more efficient ways of working. The Sr. Specialist fosters a respectful and joyful team culture." We'll put that as a paragraph(s). Could split into two paragraphs for readability but one is fine. "What We're Looking For Provides day-to-day support to Financial Advisors and their staff through responsive service and proactive outreach, including phone conversations involving complex, sensitive, or difficult issues. Maintains a thorough understanding of Advisory Programs from an operational, compliance, and analytical point of view and applies this knowledge to recommend changes or enhancements to programs and processes. Collaborates with the Program Manager on monitoring and analyzing Advisor Driven programs. Develops FA & Client communications related to Advisory Program changes and/or disclosure items. Helps oversee the development and maintenance of department standard operating procedures and ensures processes are clearly documented, practical, and consistently applied. Evaluates existing workflows and legacy processes, partners with stakeholders to identify root causes and opportunities for improvement, and helps design and implement more efficient, scalable, and sustainable solutions. Handles escalated issues and serves as a subject matter expert on cross-functional teams. Works closely with various teams within the organization to implement program enhancements/projects. Assists Program Manager with project management across team initiatives. Communicates clearly and collaborates effectively with stakeholders across the Firm to advance projects, resolve issues, and build alignment. Interacts with Advisory Operations and Advisory Compliance to resolve issues regarding accounts, fees, trading, and other issues. Reviews all Advisory Program marketing and support materials to ensure they are accurate and made available promptly. Coordinates with the Advisory Marketing team to ensure appropriate program information is shared with FAs and recruits." We'll make each sentence as
    • maybe. "What You'll Bring Knowledge of brokerage and investment advisory industries. Ability to use logic and reasoning to identify the strengths and weaknesses of alternative solutions, conclusions, or problem approaches. Excellent customer service and relationship-management skills, with a willingness to think critically and creatively when solving problems. Exceptional verbal and written communication skills, including the confidence and judgment to proactively contact Financial Advisors and their staff by phone and navigate complex or difficult conversations professionally. Process-oriented mindset with the ability to assess current-state workflows, challenge legacy practices constructively, and translate ideas into clear, practical process improvements. Understanding of operational and regulatory considerations in developing advisory program solutions. Ability to act independently, exercise sound judgment, and take ownership of issues through resolution to meet team objectives. Commitment to collaborative work and building consensus across disparate groups of stakeholders. Ability to organize, prioritize, and manage multiple tasks and projects while maintaining clear, timely communication with stakeholders. Ability to consider the relative costs and benefits of potential actions." Make each as
    • . "Education & Experience Minimum Required: Bachelor's degree Minimum Required: