Senior Client Success Associate

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to parse the job posting. We need to extract: - About the role: description of role (first paragraph). Probably "You'll be a go-to resource..." etc. That is the role description. - Responsibilities: bullet list under "What You Will Own". That's responsibilities. - Requirements/Qualifications/Skills: The "What You Bring On Day One" list includes qualifications, skills, experience. Could be combined into Requirements or Skills. We need to decide sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate ones. Probably we need Requirements (or Qualifications) and Skills. But we should not create thin sections. Let's see content: "What You Bring On Day One" includes bullet points: Minimum of 3-5 years of client operations-related role..., Strong attention to detail..., Clear and confident communicator..., Intellectually curious..., Quick learner..., Team-focused mindset..., Experience with custodian platforms..., Comfortable working with programming languages..., A no task too small mindset. These are qualifications/skills. Could put under "Requirements" or "Qualifications". We'll choose "Requirements". Could also have "Skills" separate but might be thin. Better to combine into one section "Requirements". The instruction says prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements, Benefits, Pay. Also maybe Schedule? The posting mentions "This role is onsite in our SoHo, NYC office." That's schedule/location info. Could be under "Schedule" or maybe we can include location in About the role. Since schedule section only if posting actually states schedule details. It says onsite in SoHo, NYC office. That's location, not schedule (like full-time, hours). Could treat as Schedule? Might be better to include location in About the role paragraph. The instruction: include a section ONLY when posting has real, specific content for it. So we could add a "Location" heading? Not in allowed list. Allowed list includes Schedule. Could we treat location as Schedule? Not really. Better to omit Schedule section. Benefits: The posting includes "Why Join Vise" bullet list: Opportunity to make a significant impact..., Competitive salary and equity, Unlimited PTO and great benefits..., 401k plan..., Access to investment management..., Paid lunches..., Career growth... That's benefits. Also later they mention salary range and equity. So we have Benefits and Pay sections. Pay: They give salary range $110,000-130,000 per year, plus competitive equity package. Also mention actual compensation determined based on skills. So we have Pay. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We must not repeat job title as heading. So no heading for Senior Client Success Associate. We must not include Job ID etc. We must use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to include the description paragraphs as

  . For lists, we need to convert each bullet into

• . Let's extract content. About the role: The first paragraph: "Vise is hiring a Senior Client Success Associate to join our Account Management Team. You'll be a go-to resource for our financial advisor clients and a key part of Vise's operational core — working directly with custodians and acting as the liaison between clients and our Engagement Managers, Trading, and Investment Strategy teams to keep account onboarding, implementation, and day-to-day execution running smoothly. In this role, you'll learn our platform and internal systems inside out, monitor and handle client account activity, support trading operations, and maintain data accuracy across multiple tools. It's a strong fit for someone who thrives in a fast-paced environment, takes pride in operational excellence, and is eager to grow in fintech and investment management. This role is onsite in our SoHo, NYC office." We should keep that as a paragraph. Possibly split into multiple paragraphs? The instruction: use

  for prose. Could be one

  containing all that. That's fine. Responsibilities: Under "What You Will Own". The bullet points: - Support Engagement Managers and the Trading team in delivering a high-touch client experience by addressing inquiries related to trading, portfolio management, and onboarding - Manage the end-to-end portfolio proposal process, from intake through internal systems to advisor presentation and implementation support - Oversee daily trading workflows and time-sensitive client communications to ensure seamless execution and proactive issue resolution - Facilitate account onboarding, assignment, and maintenance workflows, while monitoring key custodian activity such as cash flows, restrictions, and closures - Maintain organized and accurate internal systems by aggregating client documentation and updating key data records - Coordinate recurring client deliverables, including billing invoices, quarterly reviews, and custom reporting - Act as a client advocate by partnering cross-functionally with Trading, Investment Operations, Finance, and Marketing to resolve issues and enhance service - Identify and contribute to scalable process improvements and special projects that elevate the overall client experience We need to output as

  • each. Requirements: Under "What You Bring On Day One". Bullets: - Minimum of 3-5 years of client operations-related role in wealth management, investment management, or a related financial services environment - Strong attention to detail with the ability to stay organized and prioritize in a fast-moving setting - Clear and confident communicator with excellent verbal and written communication skills both inside the organization, as well as externally with clients and other third parties - Intellectually curious, independently resourceful, and thrives in a goal-oriented environment - Quick learner who can adapt to new tools, processes, and product updates with ease - Team-focused mindset, eager to collaborate and take initiative with others to resolve problems - Experience with custodian platforms (such as Charles Schwab and Fidelity) is preferred - Comfortable working with programming languages and interfaces (such as SQL, Retool, and Snowflake) is a plus - A no task too small mindset We need to keep as list. Benefits: Under "Why Join Vise". Bullets: - Opportunity to make a significant impact at a hyper-growth fintech start-up - Competitive salary and equity - Unlimited PTO and great benefits, including $1 medical insurance - 401k plan with generous matching and self-directed brokerage account option - Access to investment management and free financial advice from one of our partner RIA firms - Paid lunches at our NYC office - Career growth and development opportunities Also later they mention "Through the internal and market data Vise has collected, we expect the salary range for this position to be $110,000-130,000 per year, plus a competitive equity package. Your actual compensation will be determined based on your skills, qualifications, and experience. In addition, Vise offers a wide range of comprehensive and inclusive employee benefits." That's more about pay and benefits. We'll handle Pay separately. Pay: Salary range $110,000-130,000 per year, plus competitive equity package. Also mention actual compensation determined based on skills, qualifications, experience. Also maybe mention equity package. We'll put that in a

    . We should not include boilerplate like EEO etc. At the end there is a paragraph about Vise description and diversity statement. That is "About Vise". That could be considered "About the company" but not in allowed headings. Could we include as "About Vise" under maybe "About the role"? But we already have About the role. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems we should stick to those headings. The "About Vise" description is not required but could be considered part of About the role? Might be extra but we could include as a

    under About the role? However the About the role currently is about the role; adding company description may be okay but not required. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the company description somewhere. If we don't have a heading for it, we could just add a

    after the sections without a heading? But they said use

    for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having other headings, but they gave examples. Probably we should include a section "About Vise" as a heading? Not in list but could be considered "About the role"? Might be okay to add a heading "About Vise" as

    but not in the examples. Safer to incorporate that description into the About the role paragraph? But that would mix role description with company overview, which may be okay as it's still substantive. However the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the expected headings. It doesn't say we cannot have other headings, but to be safe we could add a heading "About Vise" as

    but it's not in the list; risk of being considered incorrect. Better to avoid extra headings. We could include the company description as a

    after the sections without a heading. That would be prose, not a heading. That should be fine. Thus final HTML:

    About the role

    Vise is hiring a Senior Client Success Associate to join our Account Management Team. You'll be a go-to resource for our financial advisor clients and a key part of Vise's operational core — working directly with custodians and acting as the liaison between clients and our Engagement Managers, Trading, and Investment Strategy teams to keep account onboarding, implementation, and day-to-day execution running smoothly. In this role, you'll learn our platform and internal systems inside out, monitor and handle client account activity, support trading operations, and maintain data accuracy across multiple tools. It's a strong fit for someone who thrives in a fast-paced environment, takes pride in operational excellence, and is eager to grow in fintech and investment management. This role is onsite in our SoHo, NYC office.

    Responsibilities

    • Support Engagement Managers and the Trading team in delivering a high-touch client experience by addressing inquiries related to trading, portfolio management, and onboarding
    • Manage the end-to-end portfolio proposal process, from intake through internal systems to advisor presentation and implementation support
    • Oversee daily trading workflows and time-sensitive client communications to ensure seamless execution and proactive issue resolution
    • Facilitate account onboarding, assignment, and maintenance workflows, while monitoring key custodian activity such as cash flows, restrictions, and closures
    • Maintain organized and accurate internal systems by aggregating client documentation and updating key data records
    • Coordinate recurring client deliverables, including billing invoices, quarterly reviews, and custom reporting
    • Act as a client advocate by partnering cross-functionally with Trading, Investment Operations, Finance, and Marketing to resolve issues and enhance service
    • Identify and contribute to scalable process improvements and special projects that elevate the overall client experience

    Requirements