Regional Sales Consultant - East Territory

We need to output HTML fragment with sections: use

for headings like About the role, Responsibilities, Requirements, Qualifications, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Role Overview (maybe "About the role"?), Primary Responsibilities, Position Requirements (Qualifications And Experience), Skills & Competencies, About the Organization (maybe not needed). No explicit Benefits, Pay, Schedule. So we should include sections: About the role (maybe from Role Overview), Responsibilities (Primary Responsibilities), Requirements (maybe combine Position Requirements and Qualifications And Experience?), Qualifications (maybe separate?), Skills (Skills & Competencies). The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - About the role: from Role Overview paragraph(s). - Responsibilities: from Primary Responsibilities bullet list. - Requirements: maybe from Position Requirements? Actually "Position Requirements" heading present. Could be Requirements. - Qualifications: from Qualifications And Experience. - Skills: from Skills & Competencies. - Benefits, Pay, Schedule: none, so omit. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EOE statement, etc. Also remove "Req Number BUS-26-00018" maybe minor metadata; we can fold into short p or drop. Probably drop. We need to preserve all substantive info. Use

• for any list of duties/requirements/benefits. For prose use

  . For sections we need headings

  . Inside each section we can have

  or

  . We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Let's extract content. Role Overview paragraph(s): "The Regional Sales Consultant is responsible for driving growth within the Primerica channel by building and deepening trusted relationships with financial advisors, increasing adoption of Meeder's investment solutions, and expanding assets under management across the territory. This role serves as a consultative partner to advisors, leveraging a strong understanding of Meeder's full product suite to identify opportunities, deliver impactful sales presentations, and help advisors achieve better client outcomes. In the short term, success is measured by establishing advisor relationships, generating sales activity, and growing product awareness within the territory. Over the long term, the Regional Sales Consultant will strengthen Meeder's market presence, drive sustained asset growth, and become a valued resource to advisors by consistently delivering investment insights and solutions that support their business objectives." That's prose. Primary Responsibilities list: each sentence seems a bullet. Let's list them: - Develop and execute a strategic territory business plan to increase advisor engagement and adoption of Meeder's managed account solutions, grow assets under management, and achieve established sales and activity goals. - Build and deepen trusted relationships with Primerica financial advisors through consistent in-person and virtual engagement, proactive outreach, and exceptional ongoing support. - Partner closely with the Internal Consultant as a coordinated territory team to develop advisor relationships, prioritize opportunities, execute territory strategies, share advisor intelligence, and maximize territory production. - Utilize a consultative discovery process to understand each advisor's business, client base, challenges, goals, and pain points before recommending investment solutions, resources, or strategies that address their specific needs. - Educate and guide advisors on managed account investing, Meeder's investment strategies, portfolio positioning, and appropriate solution usage, helping advisors build the knowledge and confidence necessary to effectively communicate investment solutions to their clients. - Demonstrate strong capital markets and investment knowledge and translate market developments, economic trends, portfolio positioning, and investment concepts into clear, practical guidance that advisors with varying levels of investment knowledge can understand and apply in client conversations. - Identify and develop growth opportunities by expanding relationships with existing advisors, engaging new advisors, and helping advisors identify appropriate opportunities within their practices. - Deliver a differentiated level of advisor service by responding quickly, anticipating needs, creatively solving problems, providing thoughtful solutions, and consistently following through on commitments. - Maintain deep knowledge of Meeder's investment philosophy and strategies, competitive positioning, and the Primerica managed accounts platform, and collaborate with Investments, Marketing, National Accounts, Operations, and Sales leadership to provide accurate, relevant, and coordinated advisor support. - Effectively manage the territory and sales pipeline, including advisor segmentation and prioritization, CRM documentation, scheduling, budget-conscious travel, and adherence to regulatory, compliance, and company policies. That's a list. Position Requirements: maybe heading "Requirements". Content: "Req Number BUS-26-00018" (metadata) then "Position Requirements". Actually after that there is "Qualifications And Experience". Let's parse: "Req Number BUS-26-00018 Position Requirements Qualifications And Experience Bachelor’s degree in Business, Finance, Marketing, Economics, or a related field; an equivalent combination of education and relevant industry experience may be considered.5+ years of successful consultative sales, advisor consulting, or relationship management experience within investment management or financial services, with demonstrated success developing advisor relationships and growing assets.FINRA Series 6 or 7 license required; Series 65 preferred or ability to obtain within the required timeframe.Demonstrated knowledge of capital markets, investment products, portfolio construction, asset allocation, and managed account solutions, with the ability to discuss market and investment concepts credibly with financial advisors.Experience working with the Primerica platform and advisor network, or a comparable financial advisor distribution channel, preferred; existing Primerica advisor relationships are highly valued.CIMA®, CFP®, CPWA®, BFA™, CFA®, or other relevant professional designation preferred.Proficiency with CRM systems, Microsoft Office applications, and investment research and analysis tools such as Morningstar and Zephyr." So we need to split into Requirements and Qualifications. The heading "Position Requirements" maybe corresponds to Requirements. Then "Qualifications And Experience" is Qualifications. But the text after "Position Requirements" directly goes into qualifications. There's no separate bullet list; it's just prose. We'll treat Requirements as maybe short statement? Actually there is no separate list for requirements besides the qualifications. Could combine? But instructions: use headings for Requirements and Qualifications separately if content exists. We have content for both? The "Position Requirements" heading is present but no distinct content separate from qualifications. Might be considered same. To be safe, we could make a Requirements section with the same content? But that would duplicate. Better to treat "Position Requirements" as the heading for the qualifications block. Then we could have Qualifications section maybe redundant. However we have also "Skills & Competencies" separate. Thus we could have sections: About the role, Responsibilities, Requirements (which includes the qualifications list), Skills. Or we could split Requirements (maybe short) and Qualifications (the list). But there is no explicit short requirement separate. Given the instruction: "Prefer a few substantive sections over many thin ones." So we can combine Requirements and Qualifications into one section maybe called "Requirements". But they said use headings for Requirements, Qualifications etc. If we combine, we would lose a heading. But we could still have both headings with same content? That would be thin duplication. Better to follow the posting: there is "Position Requirements" and then "Qualifications And Experience". So we can make two sections: Requirements (maybe short statement? Actually there is no separate short statement; but we could treat the first sentence before the list as the requirement? There is none). However we could still create a Requirements section with the same content as Qualifications, but that would be duplication. Might be okay but not ideal. Alternatively, we could treat "Position Requirements" as the heading for the block that includes the qualifications list, and then skip Qualifications heading because content already covered. But then we would not have a Qualifications heading, violating the instruction to use headings for those sections if they exist. However the instruction says: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to include all. It says "include a section ONLY when the posting has real, specific content for it". So if the posting does not have distinct content for Qualifications separate from Requirements, we could omit Qualifications heading. But the posting does have "Qualifications And Experience" heading with content. So we should include Qualifications section with that content. The Requirements section maybe could be empty? But we have "Position Requirements" heading with no separate content besides the qualifications. However the text after "Position Requirements" is the qualifications. So we could treat that as the Requirements section content, and then Qualifications section maybe duplicate? Actually the heading "Qualifications And Experience" appears right after "Position Requirements" without a break. So likely the posting intended: Position Requirements: Qualifications And Experience: then the list. So it's just one combined heading. So we can make one section called "Requirements" (or "Qualifications") and include the content. To follow the instruction, we could choose "Requirements" as heading and include the qualifications list. Or we could choose "Qualifications". Which is more appropriate? The content is clearly qualifications. I'd choose "Qualifications". But then we would miss the "Requirements" heading. However the instruction says we can include a section only when posting has real specific content for it. The posting does have "Position Requirements" heading, but the content under it is the qualifications. So we could treat that as the Requirements section content. But then we would also have a Qualifications heading with same content? That seems redundant. Given the instruction to prefer few substantive sections over many thin ones, I'd combine into one section called "Qualifications" (or "Requirements") and include the list. I think "Qualifications" is more accurate. Let's do that. Thus sections: - About the role (h3) with p containing role overview. - Responsibilities (h3) with ul li list. - Qualifications (h3) with ul li list (each requirement as li). - Skills (h3) with ul li list (skills & competencies). We must not include Benefits, Pay, Schedule. Now we need to extract qualifications list items. The qualifications paragraph is a run-on sentence with semicolons. We need to split into logical items. Let's parse: "Bachelor’s degree in Business, Finance, Marketing, Economics, or a related field; an equivalent combination of education and relevant industry experience may be considered." "5+ years of successful consultative sales, advisor consulting, or relationship management experience within investment management or financial services, with demonstrated success developing advisor relationships and growing assets." "FINRA Series 6 or 7 license required; Series 65 preferred or ability to obtain within the required timeframe." "Demonstrated knowledge of capital markets, investment products, portfolio construction, asset allocation, and managed account solutions, with the ability to discuss market and investment concepts credibly with financial advisors." "Experience working with the Primerica platform and advisor network, or a comparable financial advisor distribution channel, preferred; existing Primerica advisor relationships are highly valued." "CIMA®, CFP®, CPWA®, BFA™, CFA®, or other relevant professional designation preferred." "Proficiency with CRM systems, Microsoft Office applications, and investment research and analysis tools such as Morningstar and Zephyr." We'll make each as li. Skills & Competencies list: each bullet preceded by bold heading. Let's extract: - Consultative Selling & Discovery – Asks thoughtful questions, listens actively, uncovers advisor needs and pain points, and connects those needs to appropriate solutions rather than leading with products. - Investment & Capital Markets Acumen – Demonstrates strong knowledge of capital markets, asset allocation, portfolio construction, investment strategies, and managed account solutions; translates complex investment and market information into clear, relevant guidance for financial advisors. - Advisor Education & Development – Educates and guides advisors across varying levels of investment knowledge, adapting the level and style of communication to build understanding, confidence, and more effective client conversations. - Relationship Building & Trust – Develops credibility and long-term advisor relationships through consistency, responsiveness, sound judgment, genuine interest in the advisor’s business, and reliable follow-through. - Exceptional