Product Manager, Advisor Services
Webull Financial · St. Petersburg, Florida, United States · 1 mo ago
Business Development$115k–$140k/yrFull-time
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, EEOC, etc. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph about Webull (maybe not needed? It's about company; could be part of About the role? The instruction: "About The Role & Team" heading. So we can create
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, EEOC, etc. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph about Webull (maybe not needed? It's about company; could be part of About the role? The instruction: "About The Role & Team" heading. So we can create About the role
and include that paragraph.
- Then bullet list of responsibilities: "In This Role, You Will" with bullet points.
- Then "The Skills You Bring" includes qualifications/requirements: bullet list.
- Then "What Makes You Stand Out" maybe also qualifications? Could be part of Requirements or Skills.
- Then "Why Webull?" includes benefits description.
- Then location and compensation: "This role is based in our St. Petersburg, FL Global HQ..." and compensation paragraph.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
- About the role: we have description of role and team. Good.
- Responsibilities: we have bullet list under "In This Role, You Will". Good.
- Requirements: maybe we have "The Skills You Bring" bullet list (experience, degree, etc.) Could be considered Requirements.
- Qualifications: maybe overlapping; but we could split: Requirements (experience, degree) and Qualifications (specific skills like understanding advisor workflows, ability to translate, etc.) However the instruction says prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section? But they ask to use headings for those if content exists. We need to decide.
We have "The Skills You Bring" which includes bullet points: Bachelor’s degree preferred with 6 to 8+ years experience; product management experience; strong understanding; ability to translate; proven ability to lead cross functional initiatives; strong analytical, communication, stakeholder management skills.
Then "What Makes You Stand Out": direct experience with RIA custody, advisor services, etc.; familiarity with advisor technology ecosystems; understanding of regulatory and operational requirements; product minded; comfortable building in evolving environment; sound judgment.
These could be considered Qualifications or Skills. Could combine into Skills section.
But we also have separate "Skills" heading maybe for skills like analytical, communication etc. However we can just have one Skills section covering both.
But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings only if we have content.
We have content for About the role, Responsibilities, Requirements (maybe combine The Skills You Bring), Qualifications (maybe combine What Makes You Stand Out), Skills (maybe we could treat as same as Requirements/Qualifications? Might be redundant). Benefits: we have Why Webull? benefits list. Pay: we have compensation range. Schedule: not mentioned (no schedule info). So we should not include Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
But we need to avoid duplication. Let's map:
- About the role: intro paragraph about role and team.
- Responsibilities: bullet list under "In This Role, You Will".
- Requirements: maybe the baseline requirements: Bachelor’s degree preferred with 6 to 8+ years experience; product management experience building or managing products within brokerage, custody, wealth management, advisor technology, fintech, or institutional financial services.
- Qualifications: maybe the deeper qualifications: strong understanding of advisor and investment workflows; ability to translate complex business, operational, regulatory, and technical requirements; proven ability to lead cross functional initiatives; strong analytical, communication, stakeholder management skills.
- Skills: maybe the standout items: direct experience with RIA custody, advisor services, portfolio management systems, broker-dealer and clearing infrastructure; familiarity with advisor technology and wealth management ecosystems (ACATs, model portfolios, rebalancing, fee billing, performance reporting, householding, advisor permissions, client portals); understanding of regulatory and operational requirements; product minded and execution focused; comfortable building in evolving environment; sound judgment and bias for action.
But there is overlap. Could combine Qualifications and Skills into one section called Skills. However the instruction says we can include sections only when posting has real specific content. It didn't forbid having both Qualifications and Skills if content distinct. We'll try to keep both but ensure not repetitive.
Let's extract precise bullet points.
From "The Skills You Bring":
- Bachelor’s degree preferred with 6 to 8+ years of relevant experience in financial services, fintech, technology, capital markets, wealth management, or a related field.
- Product management experience building or managing products or capabilities within brokerage, custody, wealth management, advisor technology, fintech, or institutional financial services.
- Strong understanding of advisor and investment workflows, including client onboarding, account structures, trading, portfolio management, reporting, billing, operations, and service processes.
- Ability to translate complex business, operational, regulatory, and technical requirements into clear product requirements, priorities, and execution plans.
- Proven ability to lead cross functional initiatives with Engineering, Design, Operations, Compliance, Legal, Risk, Sales, and client facing teams, including collaboration across global teams.
- Strong analytical, communication, and stakeholder management skills, with the ability to influence decisions, drive alignment, and communicate effectively with both senior leaders and technical teams.
From "What Makes You Stand Out":
- Direct experience with RIA custody, advisor services, portfolio management systems, or broker-dealer and clearing infrastructure.
- Familiarity with advisor technology and wealth management ecosystems, including workflows such as ACATs, model portfolios, rebalancing, fee billing, performance reporting, householding, advisor permissions, and client portals.
- Understanding of regulatory and operational requirements within a broker dealer or RIA environment, including supervision, disclosures, books and records, custody, and client communications.
- Product minded and execution focused, with the ability to simplify complex workflows into intuitive experiences while managing multiple priorities from concept through launch.
- Comfortable building in an evolving environment, where the product, operating model, and go to market approach are being developed in parallel.
- Sound judgment and a bias for action, with the ability to build trust across technical, commercial, regulatory, and advisor stakeholders while prioritizing what matters most for launch and scale.
Now responsibilities bullet list from "In This Role, You Will":
- Own the product strategy and roadmap for Advisor Services, building the platform that enables independent financial advisors to onboard, manage client accounts, trade, manage portfolios, handle billing, and access reporting and service tools.
- Define a differentiated advisor and client experience across web and mobile, including advisor dashboards, client and household views, account workflows, document management, approvals, and operational tasks.
- Translate advisor and business needs into clear product requirements, user stories, process flows, and prioritized roadmaps, partnering closely with Engineering, Design, Operations, Compliance, Risk, and other global teams.
- Build scalable capabilities that improve advisor efficiency and growth across onboarding, transfers, portfolio management, billing, reporting, and third-party integrations.
- Partner with Operations, Compliance, Legal, and Risk to embed scalable controls and workflows across custody, books and records, settlement, reconciliation, supervision, disclosures, recordkeeping, and client communications.
- Drive competitive positioning and continuous product improvement, staying current on leading advisor platforms, custodians, and wealth technology providers to identify market opportunities, differentiate the platform, and inform roadmap priorities.
Now About the role & team paragraph: "We are building Advisor Services, a modern custody and technology platform for RIAs, independent advisors, wealth managers, and affiliated advisor businesses. The unified platform will support advisors and their clients through digital account opening, custody, trading, portfolio management, billing, reporting, operational workflows, integrations, and a client-facing portal. This is a foundational product leadership role for building an industry leading offering inside Webull’s institutional ecosystem. The role requires a strong understanding of advisor workflows, brokerage and custody infrastructure, clearing operations, regulatory obligations, and modern product architecture. You will partner closely with Engineering, Professional Services, Sales, Compliance, Operations, and Risk to define and deliver a scalable platform for advisors and their clients."
We can include that as About the role.
Now Benefits: from "Why Webull?" paragraph: list of benefits.
- Comprehensive Health Coverage: 100% paid medical and dental insurance for employees and dependents, vision insurance, and more!
- Financial Support: 401(k) match, commuter benefits for NY positions, and short-term disability coverage.
- Work-Life Balance: Generous time off that increases with tenure, paid parental leave, personal days, sick time, volunteer days and company holidays.
- Wellness & Pet Care: Fitness and wellness benefits, plus pet insurance for your furry friends.
- Investing in Your Future: We provide tuition reimbursement to help you pursue relevant degrees, certifications, and training that align with your career goals.
- Dynamic Office Perks: Catered breakfast (every Monday) & lunches (every Friday), fully stocked kitchens, and monthly happy hours to connect and collaborate.
Also location: "This role is based in our St. Petersburg, FL Global HQ, where in-person collaboration fuels growth, mentorship, and innovation."
We could include location in About the role or maybe separate but not required. Since we have no Schedule heading, we can omit.
Pay: "At Webull, we’re committed to fair, equitable, and transparent compensation. The base salary range is $115,000 - 140,000 (Associate Director level) or $140,000 - 165,000 (Senior Associate Director level) annually, plus a discretionary bonus and full benefits. Final offers consider experience, location, and relevant qualifications."
We'll include Pay section.
Now we need to output HTML fragment only, with headings and - for lists,
for prose.
We must not repeat job title as heading. Not include Job ID etc.
We must not include boilerplate like EEOC statement.
We must not include navigation, cookie, legal, etc.
We must preserve all substantive information.
We need to decide on sections:
- About the role (
About the role
) with paragraph(s) containing the role description and maybe location? Could include location in same paragraph.
- Responsibilities (Responsibilities
) with ul li.
- Requirements (Requirements
) with ul li for baseline requirements (degree, experience, product management experience).
- Qualifications (Qualifications
) with ul li for deeper qualifications (understanding workflows, ability to translate, lead cross functional, analytical/communication skills).
- Skills (Skills
) with ul li for standout items (direct experience, familiarity, understanding regulatory, product minded, comfortable building evolving, sound judgment).
- Benefits (Benefits
) with ul li.
- Pay (Pay
) with p.
We should not include Schedule.
Check for any duplicated content: Ensure we don't repeat same bullet across sections. We'll split as described.
Now we need to ensure we preserve all substantive information: The intro about Webull mission etc. Might be considered part of About the role? The initial paragraph about Webull being leading digital brokerage platform etc. That's company overview, not role-specific. Could we include it in About the role? It's not about the role but about company. The instruction says we should preserve ALL substantive information. So we need to include that somewhere. Could be part of About the role section as a preamble. Or we could create a separate section like "About Webull" but not in allowed headings. Since only allowed headings are those list, we could incorporate into About the role as a brief intro. That seems acceptable.
Thus About the
- for lists,
for prose. We must not repeat job title as heading. Not include Job ID etc. We must not include boilerplate like EEOC statement. We must not include navigation, cookie, legal, etc. We must preserve all substantive information. We need to decide on sections: - About the role (
About the role
) with paragraph(s) containing the role description and maybe location? Could include location in same paragraph. - Responsibilities (Responsibilities
) with ul li. - Requirements (Requirements
) with ul li for baseline requirements (degree, experience, product management experience). - Qualifications (Qualifications
) with ul li for deeper qualifications (understanding workflows, ability to translate, lead cross functional, analytical/communication skills). - Skills (Skills
) with ul li for standout items (direct experience, familiarity, understanding regulatory, product minded, comfortable building evolving, sound judgment). - Benefits (Benefits
) with ul li. - Pay (Pay
) with p. We should not include Schedule. Check for any duplicated content: Ensure we don't repeat same bullet across sections. We'll split as described. Now we need to ensure we preserve all substantive information: The intro about Webull mission etc. Might be considered part of About the role? The initial paragraph about Webull being leading digital brokerage platform etc. That's company overview, not role-specific. Could we include it in About the role? It's not about the role but about company. The instruction says we should preserve ALL substantive information. So we need to include that somewhere. Could be part of About the role section as a preamble. Or we could create a separate section like "About Webull" but not in allowed headings. Since only allowed headings are those list, we could incorporate into About the role as a brief intro. That seems acceptable. Thus About the