Director, Relationship Management

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. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Keep substantive info. Let's parse the posting. First paragraph: Vestwell description. That's about the company, maybe "About the role"? Actually "Who Are We Looking For?" is a heading but we need to map to sections. The content after that: description of role, responsibilities, etc. We need sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content fits each. From posting: - "Who Are We Looking For?" includes: State Auto-IRA programs expanding, Vestwell supports 15 different state programs and is looking for a Relationship Manager to work with our State Retirement Auto-IRA Programs Relationship Management team. At a high level, we’re looking for someone who has great communication and problem-solving skills, a proven ability to juggle multiple priorities at once, and an interest in being a part of this new and innovative public-private partnership to expand retirement access. That could be "About the role" summary. - "What Will You Be Doing?" includes bullet-like paragraphs describing duties. That's responsibilities. - Then "Requirements" heading with subheadings "The Necessities" and "The Extras". Those are requirements/qualifications/skills. We need to split into Requirements, Qualifications, Skills maybe. The posting lists: The Necessities: - A myriad of experience in a client-facing Retirement/Wealth Management/ Advisory, or as a Customer Success/ Relationship Manager - Able to understand and translate business goals into actionable and measurable initiatives - Experience in building relationships and garnering trust with executive decision makers and influencers - An understanding of government services, the financial industry, or financial service technologies - Capable of working collaboratively across multiple organizations - Comfortable with managing escalations and executing on success plans - Self-starter who is extremely organized and detail oriented - strategic and outside of the box thinker - Strategic problem-solving skills - Strong organizational, analytical, and prioritization skills - Excellent written and verbal communication skills - Strong skills with Office suite, including excel and PowerPoint The Extras: - Basic knowledge of project management, client onboarding experience including setting targets, KPIs, and reporting progress - Understanding and knowledge of state-administered Auto-IRA programs or experience working with other state programs, including governing boards and staff Also location: "This role will be based in Vestwell’s New York office, and will be part of Vestwell's hybrid in-office operation." Pay: "The expected base salary range for this position is $140K - $155K base. This position is eligible to participate in the Company Bonus Pool and is eligible to receive new hire equity in the Company." Benefits: "Employee Benefits We’re an innovative, high-growth company with an exciting future ahead. At Vestwell, we prioritize employee wellbeing through comprehensive health benefits, generous time off, and a dedicated Employee Wellbeing Committee. Our hybrid work model offers flexibility while providing access to our collaborative offices in Midtown Manhattan, Austin, King of Prussia, and Scottsdale. And, of course, as a company focused on helping people save for the future, we offer a competitive 401(k) plan." Schedule: Not explicitly given, but hybrid in-office operation implies schedule maybe hybrid. However we should only include Schedule if posting actually states it. It says "This role will be based in Vestwell’s New York office, and will be part of Vestwell's hybrid in-office operation." That indicates hybrid schedule. Could be considered schedule info. But we need to see if we should create a Schedule section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid in-office operation, which is schedule-related. So we can include Schedule with that detail. But we also have Benefits section already. Now we need to avoid duplication and boilerplate. Remove lines like "To learn more, visit vestwell.com", "Interview Process", "Please note that salary bands are based on NY...", "For your awareness you will only receive correspondence..." etc. Also remove EEO etc. We need to preserve all substantive information. So we keep description of Vestwell, role summary, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We need to use

for section headings. Use

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

  for prose. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's craft sections:

  About the role

  Vestwell is the financial technology company powering the new savings economy. Our platform redefines how people save for the critical aspects of life across retirement, education, and healthcare savings needs. Today, Vestwell enables over 350,000 businesses and over 2M active savers, with over $50B in assets saved across all 50 states. Vestwell's platform serves a diverse clientele, including financial advisers, employers, third-party administrators, financial institutions, payroll providers, government agencies, and individual savers. Who Are We Looking For? State Auto-IRA programs have been expanding across the country as a way to increase access to retirement savings accounts for millions of private-sector workers. Vestwell currently supports 15 different state programs and is looking for a Relationship Manager to work with our State Retirement Auto-IRA Programs Relationship Management team. At a high level, we’re looking for someone who has great communication and problem-solving skills, a proven ability to juggle multiple priorities at once, and an interest in being a part of this new and innovative public-private partnership to expand retirement access.

  But we might split "Who Are We Looking For?" into About the role. That's okay. Now Responsibilities:

  Responsibilities

  • Work closely with state clients to understand their business objectives and develop success plans that enable Vestwell to meet those objectives.
  • Support existing State Retirement Auto-IRA Program clients to ensure execution on agreed upon deliverables, ongoing alignment of business objectives, and that state clients continuously receive and recognize value from the retirement platform.
  • Collaborate with the team in the development of success plans that enable Vestwell to meet Auto IRA goals.
  • Lead the relationship with some of our State partners, serving as their point person for Vestwell’s program administration of State Auto-IRA Programs.
  • Conduct regular State client meetings, proactively identifying risks and mitigations of issues as they arise, to ensure successful delivery of solutions according to clients’ needs and objectives.
  • Collaborate cross-functionally with Product, Engineering, Marketing, Technology, Finance, Operations, and Legal teams to communicate and ensure we meet needs, SLAs, and adherence to all requisite State Program administration requirements (e.g., introducing new product features, coordinating program launch strategies, managing response to escalated issues, etc.).
  • Ensure implementation of ongoing relationship strategies and initiatives are optimized to enable teams to achieve its State Plan launch and ongoing administration goals.
  • Design and execute success plans to optimize client relationships, adoption, and satisfaction with Vestwell.
  • Communicate with clients regularly through email, phone, online presentations, screen share and in-person meetings to understand their current needs and ongoing requirements.
  • Develop and maintain subject matter expertise on our products and services and industry compliance requirements to provide timely, professional, and knowledgeable customer support.
  • Assist Sales/Operations teams with RFP responses for new state program opportunities.
  Now Requirements: maybe combine Necessities and Extras as requirements. But we also have Qualifications and Skills sections. We could put Necessities under Requirements, Extras under Qualifications, and skills under Skills. However the posting lumps many skill-like items under Necessities (communication, Office suite, etc.). We could treat Necessities as Requirements, Extras as Qualifications, and maybe Skills as a separate list of specific skills (like Office suite, communication, etc.) but that would duplicate. Better to follow instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section? But we need to use headings only when posting has real specific content for it. The posting has "Requirements" heading with subheadings "The Necessities" and "The Extras". It does not have separate "Qualifications" or "Skills" headings. So we should only create sections that match those headings if they have content. We could create a

  Requirements

  and put the content from The Necessities and The Extras as lists. Then we could skip Qualifications and Skills sections because there is no explicit separate content. However the instruction says we can use those headings if there is content. Since there is no explicit Qualifications or Skills content separate, we should not create those sections to avoid thin/filler. Thus we will have:

  Requirements

  • A myriad of experience in a client-facing Retirement/Wealth Management/ Advisory, or as a Customer Success/ Relationship Manager
  • Able to understand and translate business goals into actionable and measurable initiatives
  • Experience in building relationships and garnering trust with executive decision makers and influencers
  • An understanding of government services, the financial industry, or financial service technologies
  • Capable of working collaboratively across multiple organizations
  • Comfortable with managing escalations and executing on success plans
  • Self-starter who is extremely organized and detail oriented
  • Strategic and outside‑of‑the‑box thinker
  • Strategic problem‑solving skills
  • Strong organizational, analytical, and prioritization skills
  • Excellent written and verbal communication skills
  • Strong skills with Office suite, including Excel and PowerPoint
  • Basic knowledge of project management, client onboarding experience including setting targets, KPIs, and reporting progress
  • Understanding and knowledge of state‑administered Auto‑IRA programs or experience working with other state programs, including governing boards and staff
  Now Benefits:

  Benefits

  We’re an innovative, high‑growth company with an exciting future ahead. At Vestwell, we prioritize employee wellbeing through comprehensive health benefits, generous time off, and a dedicated Employee Wellbeing Committee. Our hybrid work model offers flexibility while providing access to our collaborative offices in Midtown Manhattan, Austin, King of Prussia, and Scottsdale. And, of course, as a company focused on helping people save for the future, we offer a competitive 401(k) plan.

  Pay:

  Pay

  The expected base salary range for this position is $140K – $155K base. This position is eligible to participate in the Company Bonus Pool and is eligible to receive new hire equity in the Company.

  Schedule:

  Schedule

  This role will be based in Vestwell’s New York office and is part of Vestwell's hybrid in‑office operation.

  We should also maybe include location? Already in schedule. We need to ensure we didn't include boilerplate like "Please note that salary bands are based on NY and other similar metro areas and may differ based on where the role is ultimately hired." That's extra detail about pay but it's still substantive? It's a note about salary bands. Could be considered part of Pay. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that note as well. It's about pay. So we can add to Pay paragraph. Thus Pay paragraph