Knowledge & Operational Readiness Lead

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. No metadata like Job ID. Remove boilerplate, EEO, etc. Use

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

  for prose. We need to parse the posting. First, there is an intro paragraph: "Join us in building the future of finance..." etc. That's likely part of About the role? Actually there is a section "About the team + role". We can treat that as About the role. Then "What You’ll Do" is responsibilities. Then "What You Bring" is qualifications/requirements/skills. Then "What We Offer" includes benefits, pay, etc. We need to separate into sections: About the role (intro + team description), Responsibilities (What You’ll Do), Requirements (maybe combine What You Bring?), Qualifications (maybe same?), Skills (maybe part of What You Bring), Benefits (What We Offer benefits), Pay (base pay range), Schedule (in-person attendance expectation). We must not create sections with filler. Ensure each has content. Let's extract content. Intro: "Join us in building the future of finance. Our mission is to democratize finance for all. An estimated $124 trillion of assets will be inherited by younger generations in the next two decades. The largest transfer of wealth in human history. If you’re ready to be at the epicenter of this historic cultural and financial shift, keep reading." Then "About the team + role We are building an elite team, applying frontier technologies to the world’s biggest financial problems. We’re looking for bold thinkers. Sharp problem-solvers. Builders who are wired to make an impact. Robinhood isn’t a place for complacency, it’s where ambitious people do the best work of their careers. We’re a high-performing, fast-moving team with ethics at the center of everything we do. Expectations are high, and so are the rewards. The Platforms Knowledge Management team's mission is to ensure Robinhood associates and customers have clear, current, and compliant guidance at their fingertips. We own the knowledge ecosystem — taxonomy, governance, editorial standards, and content lifecycle — and partner closely with CX Strategy, Product, Operations, Compliance, Legal, and Quality to publish SOPs and reusable messaging that are easy to find and use. As a Knowledge & Operational Readiness Lead, you will own the full content and readiness lifecycle across multiple, more complex assigned functions — driving knowledge strategy, leading readiness programs, and making meaningful program-level decisions with limited outside support. You lead cross-functional collaboration across all of your functions simultaneously, influence Product, Engineering, Compliance, and CX partners at all levels, and develop colleagues within the team. This is a role for someone who is equally fluent in SOPs and go/no-go frameworks, and uses AI to rethink what's possible. This role is based in our Denver, CO and Westlake, TX office, with in-person attendance expected at least 3 days per week (W,Th,F) At Robinhood, we believe in the power of in-person work to accelerate progress, spark innovation, and strengthen community. Our office experience is intentional, energizing, and designed to fully support high-performing teams." We can split: About the role (first paragraph + team description). Then schedule info maybe separate. Responsibilities: "What You’ll Do" bullet list (actually sentences). Let's extract each duty as list items. List: - Own end-to-end content strategy and knowledge governance for assigned function(s): creation, maintenance, and continuous improvement of Help Center articles, SOPs, runbooks, playbooks, escalation paths, policy documentation, and support workflows - Lead readiness planning for product launches, policy updates, process changes, and operational initiatives — including go/no-go recommendations, risk registers, mitigation plans, and post-launch retrospectives - Lead cross-functional collaboration across all assigned functions simultaneously — influencing Product, Engineering, Operations, Customer Support, Compliance, Risk, and Training partners at all levels to drive alignment on readiness and content strategy - Establish content standards, information architecture, and governance frameworks that scale across functions and raise the bar for the team - Partner with Customer Support leadership to prepare frontline teams for launches; identify contact drivers and support risks before go-live and develop plans to minimize customer friction - Analyze metrics across assigned function(s) to identify patterns, inefficiencies, and improvement opportunities; drive post-launch reviews and lead improvement initiatives - Communicate readiness status, performance insights, and risks to stakeholders at all levels, from operational detail to executive-ready narratives - Guide, coach, and share functional expertise with colleagues within the team; influence parties inside and outside the department on knowledge management processes and practices - Use AI to tackle complex, domain-specific knowledge problems — not just speed up routine work. The bar: streamlined workflows, resolved bottlenecks, and consistently higher-quality outcomes delivered faster. We can make each a

• . Requirements/Qualifications/Skills: "What You Bring" list. Extract: - Experienced individual contributor with advanced knowledge of knowledge management and content strategy, and practical experience across multiple related job areas — typically 4-5+ years of relevant experience - Proven track record of independently owning multiple, more complex functions end-to-end and making meaningful program-level decisions with limited outside support - Deep knowledge management and content strategy background: governance, information architecture, content lifecycle, and knowledge base operations - Leads cross-functional collaboration and influences Product, Engineering, Compliance, and CX partners across all levels across multiple, more complex assigned functions - Executive-level communication: able to move between granular operational detail and leadership-ready narratives depending on the audience - Strong project management skills; comfortable holding multiple complex workstreams simultaneously without losing quality - Uses AI to tackle hard, domain-specific problems — not just to speed up work but to rethink what's possible - Active FINRA licenses where functionally necessary; deep subject matter expertise in assigned function(s) We can split into Requirements (experience, track record, deep background, leads cross-functional, executive communication, project management, uses AI, FINRA licenses). Skills maybe subset: AI usage, FINRA, etc. But we can just have Requirements and Skills combined? The instruction: use headings for sections like Requirements, Qualifications, Skills. We need to decide which to include based on content. We have both experience and qualifications. Could put Requirements for experience and track record, Qualifications for deep knowledge background, Skills for cross-functional collaboration, communication, project management, AI usage, FINRA. But we must avoid thin sections. Better to combine into one section "Requirements" that includes all. However they ask to prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (covering what you bring), Benefits, Pay, Schedule. That's 6 sections. Benefits: from "What We Offer". Extract bullet-like sentences: - Challenging, high-impact work to grow your career. - Performance-driven compensation with multipliers for outsized impact, bonus programs, equity ownership, and 401(k) matching. - Best-in-class benefits to fuel your work, including 100% paid health insurance for employees with 90% coverage for dependents. - Lifestyle wallet — a highly flexible benefits spending account for wellness, learning, and more. - Employer-paid life & disability insurance, fertility benefits, and mental health benefits. - Time off to recharge including company holidays, paid time off, sick time, parental leave, and more! - Exceptional office experience with catered meals, events, and comfortable workspaces. - In addition to the base pay range listed below, this role is also eligible for bonus opportunities + equity + benefits. We can make each a
• under Benefits. Pay: Base pay range details. Provide the ranges per zone. Should we list them? Yes. Provide as
  • maybe each zone. Or a paragraph. Use
    • for list. Schedule: In-person attendance expected at least 3 days per week (W,Th,F). Also mention based in Denver, CO and Westlake, TX office. That's schedule/location. We'll put schedule. Now produce HTML fragment with

      headings and appropriate

      or

      • . We must not include any extra text like explanations. Let's craft. First section: About the role. Combine intro and team description into maybe two paragraphs? Use

        for prose. Could split into two

        but okay. We'll put:

        About the role

        Join us in building the future of finance. Our mission is to democratize finance for all. An estimated $124 trillion of assets will be inherited by younger generations in the next two decades. The largest transfer of wealth in human history. If you’re ready to be at the epicenter of this historic cultural and financial shift, keep reading.

        We are building an elite team, applying frontier technologies to the world’s biggest financial problems. We’re looking for bold thinkers. Sharp problem-solvers. Builders who are wired to make an impact. Robinhood isn’t a place for complacency, it’s where ambitious people do the best work of their careers. We’re a high-performing, fast-moving team with ethics at the center of everything we do. Expectations are high, and so are the rewards. The Platforms Knowledge Management team's mission is to ensure Robinhood associates and customers have clear, current, and compliant guidance at their fingertips. We own the knowledge ecosystem — taxonomy, governance, editorial standards, and content lifecycle — and partner closely with CX Strategy, Product, Operations, Compliance, Legal, and Quality to publish SOPs and reusable messaging that are easy to find and use. As a Knowledge & Operational Readiness Lead, you will own the full content and readiness lifecycle across multiple, more complex assigned functions — driving knowledge strategy, leading readiness programs, and making meaningful program-level decisions with limited outside support. You lead cross-functional collaboration across all of your functions simultaneously, influence Product, Engineering, Compliance, and CX partners at all levels, and develop colleagues within the team. This is a role for someone who is equally fluent in SOPs and go/no-go frameworks, and uses AI to rethink what's possible. This role is based in our Denver, CO and Westlake, TX office, with in-person attendance expected at least 3 days per week (W,Th,F). At Robinhood, we believe in the power of in-person work to accelerate progress, spark innovation, and strengthen community. Our office experience is intentional, energizing, and designed to fully support high-performing teams.

        But note schedule mention appears here; we might move schedule to its own section. However the schedule sentence is part of this paragraph. We could keep it here but then schedule section would be duplicate. Better to separate schedule: remove schedule sentence from About the role and put in Schedule section. Let's edit About the role to exclude the schedule sentence. Thus About the role paragraph ends before "This role is based...". We'll keep location maybe but not schedule. We'll keep location as part of About the role? Could keep location but not schedule. The instruction: Schedule section only if posting actually states them. It does state in-person attendance expected at least 3 days per week. So we will have Schedule section. Thus About the role will include location but not schedule. We'll keep "This role is based in our Denver, CO and Westlake, TX office." as part of About the role. Now Responsibilities:

        Responsibilities

        with each duty as
        • . Requirements:

          Requirements

          with each item from What You Bring. Benefits:

          Benefits

          with each benefit. Pay:

          Pay

          with each zone range. Schedule:

          Schedule

          In-person attendance expected at least 3 days per week (Wednesday, Thursday, Friday).

          We must not include boilerplate like