Institutional CRM & Data Analyst

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate like EEO etc. Also remove application instructions (none present). Must not create sections with filler like "commensurate with experience". Must only include sections when posting has real specific content. We need to parse the posting. Content: Intro paragraph about Franklin Templeton, mission, etc. Could be "About the role"? Actually the posting starts with description of company and role. Could treat as "About the role" section. Then "How You Will Add Value" with subheadings: Institutional CRM Data Management, Data Quality & Requirements, Cross-Functional Remediation & Enhancements, Documentation & Team Development. Those are responsibilities. Then "What Will Help You Be Successful" includes experience requirements, skills, etc. Could be Requirements, Qualifications, Skills. Then "Work schedule & location" includes hybrid schedule, commutable to offices. Then benefits description: Franklin Templeton offers employees a competitive and valuable range of total rewards—monetary and non-monetary — designed to support their well-being and recognize their time, talents, and results. Along with base compensation, employees are eligible for an annual discretionary bonus, a 401(k) plan with a generous match, and recognition rewards. We also offer a comprehensive benefits package, which includes a range of competitive healthcare options, insurance, and disability benefits, employee stock investment program, learning resources, career development programs, reimbursement for certain education expenses, paid time off (vacation / holidays / sick / leave / parental & caregiving leave / bereavement / volunteering / floating holidays) and a motivational wellbeing program. We expect the annual salary for this position to range between $90,000 - $110,000, depending on location and level of relevant experience, plus discretionary bonus. At Franklin Templeton, we believe your benefits should support your life, your goals, and your future. That’s why we offer a comprehensive Total Rewards package designed to help you thrive both personally and professionally. Highlights Of Our Benefits Include Paid Time Off: Three weeks of PTO in your first year Health Coverage: Competitive medical, dental, and vision insurance to support your well-being Retirement Savings: 401(k) plan with an 85% company match on pre-tax and/or Roth contributions, up to IRS limits Equity & Investing: Employee Stock Investment Plan (ESIP) with discounted share purchase opportunities Learning Education Assistance Program (LEAP): To support your ongoing growth and career advancement Employee Investment Benefits: Opportunity to purchase company funds with no sales charge Thus we have Pay (salary range) and Benefits details. Also schedule/hybrid. We need to decide sections: About the role (intro), Responsibilities (the "How You Will Add Value" bullet points), Requirements (maybe experience), Qualifications (maybe education? none), Skills (maybe SQL, Excel etc), Benefits, Pay, Schedule. We must not create sections with filler. Ensure each section has substantive content. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like specific tasks, etc. We must not repeat job title as heading. We must not include Job ID etc. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the EEO paragraph at end. Also drop any duplicated lines (maybe none). Now produce HTML. Let's craft sections:

  About the role

  At Franklin Templeton, we believe success is built through powerful partnerships. As a forward thinking asset manager, we build dynamic relationships with clients, understand their goals, and navigate complex markets together. We leverage cutting edge strategies and deep insights to unlock opportunities for long term wealth creation. Our talented, global teams bring expertise that is both broad and unique. From our welcoming, inclusive, and supportive culture to our globally diverse business, we offer opportunities not only to help you reach your potential, but also to contribute to our clients’ success. We are looking for an Institutional CRM & Data Analyst to join the Distribution Intelligence team with a focus on the Institutional business. This role independently owns recurring and project-based data-management processes for the client, contact, prospect, account, consultant, relationship, hierarchy, ownership, and coverage data mastered in CRM, ensuring that Institutional data is trusted, governed, and ready for use across business operations, reporting, and analytics. The ideal candidate will combine institutional asset-management experience with strong data-management, CRM, and analytical skills. This person will understand how institutional clients, consultants, accounts, relationships, contacts, and coverage are represented in CRM; translate business needs into data rules and controls; and partner effectively with Sales, Client Service, Product, Technology, and Reporting teams. Exposure to institutional datasets such as MMD and eVestment is preferred.

  That seems fine. Now Responsibilities: we have bullet points under "How You Will Add Value". We'll create a
  with each bullet as
  • . Need to preserve details. List: - Institutional CRM Data Management: Independently own BAU and mid-size data-management initiatives for Institutional CRM data, including client and contact updates, relationship and coverage maintenance, account and prospect data management, issue resolution, onboarding support, and project data readiness. Review, triage, and resolve CRM data questions raised by Institutional Sales and Client Service, clarifying ownership, hierarchy, account, contact, relationship, coverage, and data-entry issues. - Data Quality & Requirements: Define and execute data-quality rules, reconciliations, root-cause analysis, exception workflows, and validation evidence for assigned Institutional data domains. Evaluate and reconcile CRM data with institutional market, consultant, and client datasets, including MMD, eVestment, reporting outputs, and approved data extracts, to identify gaps and support governed enrichment. - Cross-Functional Remediation & Enhancements: Translate ambiguous business requests into clear field definitions, CRM requirements, business rules, test cases, acceptance criteria, and operational controls. Partner with CRM Product and Technology teams on enhancements by documenting current-state gaps, supporting solution design, completing UAT and release-readiness validation, and reviewing post-implementation results. Lead remediation cycles from issue intake through analysis, stakeholder alignment, correction, validation, communication, and closure. - Documentation & Team Development: Maintain SOPs, data dictionaries, process maps, control checklists, and user guidance; coach junior analysts on evidence standards, escalation judgment, data-quality checks, and stakeholder communication. We'll put each as
  • with the text. Now Requirements/Qualifications/Skills: The posting has "What Will Help You Be Successful" which includes experience, skills, etc. We could split into Requirements (experience), Qualifications (maybe education? none), Skills (technical). But we need to avoid empty sections. Let's see content: "5-8 years of relevant experience in data management, data governance, CRM, data operations, financial services, asset management, or related roles. Demonstrated institutional asset-management experience, including work with complex institutional client, consultant, account, organization, relationship, hierarchy, or coverage data. Hands-on experience managing CRM data and supporting sales or client-service users; experience with a CRM that serves as the client master is strongly preferred. Exposure to institutional data sources such as MMD, eVestment, or comparable consultant, market, or client datasets preferred. Intermediate SQL, strong Excel, and practical experience profiling and reconciling datasets, investigating root causes, and designing validation logic and data-quality controls. Ability to communicate with Institutional business users and Technology partners, converting business language into structured data requirements, test cases, and practical solutions. Demonstrated ability to own work independently, manage competing requests, support UAT and release validation, and improve repeatable processes." We could make a single section "Requirements" with a
    listing each bullet. Or we could split into Requirements (experience) and Skills (technical). But we need to avoid filler. Let's create a section "Requirements" with
    of all those points. That covers experience and skills. If we also want a separate "Skills" section, we would duplicate. Better to have one section "Requirements" that includes both experience and skills. The instruction says we can have sections like Requirements, Qualifications, Skills. But we can choose to only include those with real content. We have content for Requirements (experience and skills). We could also have a "Qualifications" section if there are any specific qualifications like degree etc. Not present. So we omit Qualifications. We could also have a "Skills" section if we want to separate technical skills, but that would split content and risk missing some. Safer to have one "Requirements" section. Now Benefits: we have a paragraph describing benefits plus highlights list. We'll create a
    for benefits list. We need to preserve all substantive info: The paragraph about total rewards, base compensation, annual discretionary bonus, 401(k) plan with generous match, recognition rewards, comprehensive benefits package includes healthcare options, insurance, disability benefits, employee stock investment program, learning resources, career development programs, reimbursement for certain education expenses, paid time off (list), motivational wellbeing program. Then salary range: $90,000 - $110,000 depending on location and level of relevant experience, plus discretionary bonus. Then highlights: Paid Time Off: Three weeks of PTO in your first year; Health Coverage: Competitive medical, dental, and vision insurance; Retirement Savings: 401(k) plan with an 85% company match on pre-tax and/or Roth contributions, up to IRS limits; Equity & Investing: Employee Stock Investment Plan (ESIP) with discounted share purchase opportunities; Learning Education Assistance Program (LEAP): To support your ongoing growth and career advancement; Employee Investment Benefits: Opportunity to purchase company funds with no sales charge. We should keep the paragraph and then a list of highlights. Now Schedule: "Work schedule & location This role works a hybrid schedule, commutable to our Pasadena (CA), Boston (MA), Stamford (CT) or San Mateo (CA) office." We'll create a section Schedule with that sentence. Now Pay: we have salary range mentioned in benefits paragraph. Could create a Pay section with that sentence. But we already included salary range in benefits paragraph. However the instruction says: "Prefer a few substantive sections over many thin ones." We could combine Pay and Benefits into one Benefits section that includes pay info. But we also have a separate Benefits section for benefits highlights. Could combine them: a Benefits section that includes both the description and the highlights, and also the salary range. That would be substantive. But we also have a Schedule section separate. Thus sections: About the role, Responsibilities, Requirements, Benefits (including pay and benefits), Schedule. We must not create Pay section separately if we include pay in Benefits. Check if we need to include Pay heading only if posting actually states them. It does state salary range, so we could include Pay. But we can also include it within Benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, so we could create them. But we also need to avoid many thin sections. However we have separate sections for Benefits and Pay maybe okay. But we also have Schedule. Could have three sections: Benefits, Pay, Schedule. That's three sections plus About, Responsibilities, Requirements = 6 sections. That's okay. But we need to ensure we don't repeat info. If we create Pay section with salary range, we should not also repeat it in Benefits. We can keep Benefits focusing on non-monetary benefits and highlights, and Pay section for salary range and bonus. Let's do that. Thus sections: - About the role (intro) - Responsibilities (How You Will Add Value