Lead Security Governance Partner - Assurance

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. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "The application window will close November 1, 2026" maybe considered metadata? It's not a section heading; could be placed in a short

maybe. But we need to preserve all substantive info. The closing date is substantive? Possibly yes. But we can include it in a short

maybe under a generic heading? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can put the application window closing date in a

. Also job location: "The primary work location for this role is Berwyn, PA or Remote with either a hybrid work or remote model." That's location info; could be a short

. Also "About Envestnet" is a section; we can treat as About the role? Actually "About Envestnet" is about company; but we have heading "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The posting includes "About Envestnet" and "The Team You’ll Join". That could be under About the role. Also "How You’ll Contribute" is responsibilities. Then "What You’ll Need To Bring" is requirements/qualifications/skills. Then "Nice-to-Haves" maybe skills. Then "Why You’ll Enjoy Working at Envestnet" maybe benefits? But we have Benefits, Pay, Schedule sections. The posting includes "Our Investment in You" with base salary range and benefits. So we can put Pay section with salary range, Benefits section with list of benefits. Schedule? Not mentioned; maybe hybrid/remote model could be schedule? It's about work location, not schedule. Could treat as Schedule? But schedule usually refers to hours. Not present. So we omit Schedule section if no specific content. Also we must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay (salary range) and Benefits (list). So include those. We must not include boilerplate like EEO, recruitment fraud, etc. Remove those. We need to preserve all substantive information: details about responsibilities, requirements, qualifications, skills, benefits, pay, location, application closing date, etc. We must not invent or summarize away detail. So we need to keep the bullet points as they are, but we can format as

• . Must not omit any bullet. Let's extract sections. First, location and application date: we can put a short

  at top: "Job Location: Berwyn, PA or Remote with hybrid or remote model. Application window closes November 1, 2026." Then About the role: combine "About Envestnet" and "The Team You’ll Join". Provide prose. Responsibilities: from "How You’ll Contribute" bullet list (the long paragraph with many sentences). Actually it's a paragraph with many sentences separated by periods. We could treat each sentence as a list item? The instruction: Use

  • for any list of duties/requirements/benefits. The responsibilities are not explicitly bulleted but are a series of sentences. Could we keep as

    with sentences? The instruction says use

    • for any list of duties/requirements/benefits. If it's not a list, we can keep as

      . But we could also split into list items for clarity, but that might be inventing structure. Safer to keep as

      preserving original sentences. Requirements: from "What You’ll Need To Bring" includes several paragraphs: first paragraph about relevant experience, performance rating, experience in regulated financial services, familiarity with frameworks, strong cross-functional communication. That's requirements. Then "Nice-to-Haves" is separate list of nice-to-haves; could be under Skills or Qualifications? The heading Skills could contain nice-to-haves. Qualifications could contain required qualifications. Let's map: - Requirements: mandatory experience etc. - Qualifications: maybe certifications? But we have Nice-to-Haves includes certifications. Could treat Qualifications as required qualifications (like education? not mentioned). Since no explicit qualifications, maybe we combine Requirements and Qualifications? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Requirements (mandatory). For Qualifications, we could put the nice-to-haves as Qualifications? But Qualifications usually refers to required qualifications. However we have no explicit qualifications besides experience. Could we put the nice-to-haves under Skills? The heading Skills is appropriate for nice-to-haves (certifications, frameworks). Let's decide: Section "Requirements": mandatory experience, performance rating, regulated financial services experience, knowledge of frameworks, cross-functional communication. Section "Skills": nice-to-haves (8-10 years experience, 2-4 years supporting..., certifications, familiarity with Insider Threat Matrix, knowledge of SaaS/cloud, etc.) We could also have "Qualifications" maybe empty; better to omit. Now Benefits: list from "We provide a comprehensive suite of benefits - subject to Envestnet’s plan eligibility rules - that support your overall well-being including, medical insurance, paid time off (PTO), 401k company match, paid parental leave, education reimbursement, disability coverage and mental health & wellness support." We can make

      • each benefit. Pay: base salary range $138,000 to $170,000. Also mention incentive component. So we can put that. Schedule: not present, omit. Now we need to ensure we don't include boilerplate like "Our Investment in You" heading; we already extracted pay and benefits from that section. Also we need to remove "Sponsorship This position is not open to candidates requiring visa sponsorship" - that's substantive? It's a requirement about visa sponsorship. Should we preserve? It's substantive info about eligibility. The instruction: preserve ALL substantive information. So we need to include that. Where? Could be under Requirements or a separate note. Could add a short

        under Requirements: "This position is not open to candidates requiring visa sponsorship." Also "Please visit our benefits page on our career site to learn more." That's a reference; could be included in Benefits section as a note. Also "Our Commitment to Inclusion & Belonging" is EEO boilerplate; remove. Recruitment Fraud section: remove. Now we need to output only HTML fragment, no markdown fences. Let's craft. Start with

        for location and closing date. Then

        About the role

        with

        containing About Envestnet and The Team You’ll Join combined. Then

        Responsibilities

        with

        containing the How You’ll Contribute paragraph. Then

        Requirements

        with

        containing the What You’ll Need To Bring mandatory paragraphs plus visa sponsorship note. Then

        Skills

        with
        • for each nice-to-have item. Then

          Benefits

          with
          • for each benefit. Then

            Pay

            with

            containing salary range and incentive note. We must not repeat job title. Check that we haven't missed any substantive info: The "About Envestnet" paragraph includes details about adaptive WealthTech, $7.0 trillion platform assets, over one third of financial advisors, etc. Must keep. "The Team You’ll Join" paragraph: details about Enterprise Cybersecurity team, partnering, etc. Keep. "How You’ll Contribute" paragraph: many sentences; keep as is. "What You’ll Need To Bring": first paragraph about relevant experience, performance rating, experience in regulated financial services, familiarity with frameworks, strong cross-functional communication. Keep. Second paragraph: Nice-to-Haves list: we need to keep each bullet as list items. We also need to keep the sentence: "Employees must have achieved a performance rating of "Meets Expectations" or higher in the most recent appraisal cycle." That's in the first paragraph. Also "Experience in a regulated financial services environment (wealth management, banking, insurance, payments, technology, or FinTech), with working knowledge of cybersecurity controls, data protection, IAM, cloud security, incident response, security monitoring, and AI-related risk considerations." Keep. "Familiarity with industry frameworks such as NIST CSF, NIST SP 800-53, NIST AI RMF, SOC 1/SOC 2, CIS Critical Security Controls, SEC Regulation S-P, and applicable privacy requirements." Keep. "Strong cross-functional communication and analytical skills — able to influence without direct authority, translate risk/control concepts for technical and non-technical audiences, and produce clear assessment summaries, evidence requests, findings, and remediation tracking materials." Keep. Now Nice-to-Haves: - "8–10 years of experience in information security, security governance, technology risk, cybersecurity assurance, internal audit, compliance, security operations, privacy, or related risk management functions." - "2–4 years of experience supporting cybersecurity control assessments, audit readiness, evidence collection, risk assessments, human risk management, security awareness, insider risk, or data protection activities." - "CISSP, CISM, CRISC, CISA, Certified Fraud Examiner, GCFA, GCIH, GCFE, or related GIAC certification." - "Familiar with the Insider Threat Matrix framework concepts, including motive, means, preparation activities, infringement techniques, and anti-forensics as an investigative taxonomy." - "Knowledge of SaaS service architecture frameworks, cloud security services (Azure, AWS) and cyber defense tools." We'll put each as

          • . Benefits list: medical insurance, paid time off (PTO), 401k company match, paid parental leave, education reimbursement, disability coverage and mental health & wellness support. We could also note "subject to Envestnet’s plan eligibility rules". Keep as part of intro sentence. Pay: "This role offers a base salary range of $138,000 to $170,000. The range listed represents a good-faith estimate of base salary compensation for this position and does not include incentive compensation, equity or benefits. Individual pay will be determined based on factors including, but not limited to, relevant experience, skills, education, certifications, and geographic location, in accordance with applicable pay transparency laws. This role is eligible for an additional incentive component as part of the total rewards package." We'll keep that as

            . Now ensure we didn't include any boilerplate: removed EEO, recruitment fraud, sponsorship note we kept (visa sponsorship). Also removed "Please visit our benefits page on our career site to learn more." Could keep as a note under Benefits. Let's include that as a

            after benefits list: "For more details, please visit our benefits page on our career site." Now check for any duplicated lines: we have not duplicated. Now output HTML. Make sure to use proper escaping for any special characters like & etc. In text we have "PTO" fine. Use & for "and"? It's okay as plain text. We'll produce:

            Job Location: Berwyn, PA or Remote with hybrid or remote model. Application window closes November 1, 2026.

            About the role

            About Envestnet Envestnet is an adaptive WealthTech company that is redefining the future of wealth management by helping advisors meet the moment with its comprehensive technology, actionable insights,