Associate Director, Strategic Operations

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 as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Job Title: Associate Director, Strategic Operations Team: Insights & Strategic Planning Location: Hybrid in Chicago (IL) strongly preferred, Atlanta (GA), Newark (NJ), or New York (NYC) Employment Type: Full-time FLSA Classification: Exempt Start Date: ASAP About Braven: description. About The Role: description. What You'll Do: responsibilities broken into three categories with percentages. Requirements: Minimum Requirements and Preferred Qualifications. Work Demands: Ability to work in-person in locations, travel. Additional Requirements: Authorized to work in US, no visa sponsorship. Application & Interview Process: description but we should remove application instructions? The instruction says: Remove application instructions. So we should drop the "Application & Interview Process" section. Benefits Compensation and Benefits: includes salary ranges, benefits list. Location: description of hybrid schedule. We need to map to sections: About the role (maybe combine About Braven and About The Role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings exactly those strings? Probably yes. We need to include sections only if posting has real specific content. We have content for About the role: we can combine About Braven and About The Role into About the role section. Responsibilities: from What You'll Do. Requirements: Minimum Requirements. Qualifications: Preferred Qualifications. Skills: maybe technical skills list (Proficiency in Excel/Google Sheets and SQL, etc.) Could be part of Qualifications or Skills. We have a list of technical skills under Preferred Qualifications and also under "Your experiences have informed..." and "You have the following technical skills and knowledge:" So we can put those under Skills. Benefits: from Benefits Compensation and Benefits. Pay: salary ranges. Schedule: location/hybrid schedule (Work Demands and Location). Could be Schedule section. We must not create sections with filler like "commensurate with experience". We have actual salary ranges, so Pay section is valid. Schedule: we have location and hybrid schedule details. We must not include boilerplate like EEO etc. Remove that. We must not include application instructions. We must not repeat job title as heading. We must not put Job ID etc. We must preserve all substantive info. Let's extract substantive info: About Braven: "Braven is a national nonprofit that prepares promising college students to secure a strong first opportunity after college graduation through a career-accelerating program. We work with higher education and employer partners to offer a life-changing experience that begins with a semester-long course for college students, followed by support that lasts through graduation. Together, our ambition is to help rebuild the middle class and revitalize the American Dream." About The Role: "In order to achieve its ambition of serving 80,000-100,000 Fellows over the next decade, Braven is hiring an Associate Director, Strategic Operations, who will serve as the operational engine for the Insights & Strategy team and lead the process to report on priorities and goals at the organizational level. This role will own the Braven-wide rhythm and content of how we communicate progress on our goals to staff, leaders, and our national and regional boards; play a key role in the Insights & Strategy team's work to strengthen cross-functional coordination and partnership; and drive the internal operational rhythm of the Insights & Strategy team. You will be a designer of process, an expert on our priorities, and a trusted voice on our progress. This is a role for someone who excels at communication and writing, creating and owning high-quality operations and processes, and collaborating cross-functionally. You read context well, operate comfortably in ambiguity, demonstrate utmost discretion, and know how and when to take the next step without waiting to be asked. This role is on the Insights & Strategy team and reports directly to the Head of Insights & Strategy." We can combine. Responsibilities: three bullet categories with percentages and details. We need to format as

• for any list of duties/requirements/benefits. So each bullet under responsibilities should be
• . The percentages maybe part of text. We'll produce

  Responsibilities

  then
  with items. But we have subcategories: Organizational Progress Monitoring & Reporting (40%), Cross-Functional Partnership & Coordination (30%), Insights & Strategy Team Operations and Coordination (30%). Each has multiple bullet points. We could either make each subcategory as a
  • containing nested
    ? The instruction: Use
    • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll keep simple: each main bullet as
    • and include the details inside. We'll need to preserve all details. Let's list responsibilities: Organizational Progress Monitoring & Reporting (40%): - Design, own, and continuously improve the infrastructure to prepare progress updates for stakeholders. - Regular deliverables include but are not limited to: * Project managing and packaging quarterly progress-to-goal (PTG) memos for Braven's national board, leadership, and staff * Drafting region-specific progress updates on priorities for regional board meetings * Preparing regular updates to Braven leadership and staff on organizational priorities and goals * Pull, analyze, and/or visualize data independently to support progress monitoring * Build relationships with relevant partners for this work (e.g., executive owners of priorities) * Establish expertise and serve as a thought partner on questions and situations related to org-wide progress monitoring Cross-Functional Partnership & Coordination (30%): - Act as trusted liaison to the leaders of the Product, Systems, and External Affairs teams in changing the operating model for how they work together - Design and help execute a regular central team regional team feedback structure at the Alignment Team level (Braven's leadership team) - Support the Head of Insights & Strategy to lead two internal councils (Data Governance Council and AI Advisory Council) and one external council (Labor Market & Economic Advisory Council) Insights & Strategy Team Operations and Coordination (30%): - Own the coordinated operational rhythm of the two halves of the team (Insights and Strategy), including annual planning and goal-setting, quarterly alignment, and weekly coordination - Design and plan team stepbacks and other meetings in support of the Head of Insights & Strategy and the Senior Director of Insights, from creating the agenda through post-meeting follow-up - Own knowledge management for the Strategy half of the team, maintaining shared and organized documentation and ensuring process clarity - Lead or support capacity-building and systems/process-building projects for primarily the Strategy half of the team - For all of the above responsibilities, use AI in responsible, smart, and human-valuing ways to continuously improve the effectiveness and efficiency of your work. Now Requirements: Minimum Requirements: - BA/BS in a quantitative field or work experience that demonstrates expertise in quantitative analysis - At least 3 years of relevant experience - Extensive experience writing and presenting compelling data-driven narratives for internal and external audiences - Proficiency in Excel/Google Sheets and SQL Preferred Qualifications: - Demonstrated experience using AI effectively and responsibly to make an actual impact on outcomes - Proficiency in SQL - Experience designing and building dashboards and visualizations (Tableau preferred) - Strong strategic thinking skills, including a proven ability to bring clarity to ambiguous solutions - Ability to take initiative to solve challenges and tap into opportunities; ability to make complex tasks simple by applying clear logic and processes to component steps - Excellent time management and prioritization skills, which allow you to manage your own time and energy and seek the right help to complete multiple projects well and on time - Demonstrated attention to detail, known for checking and double-checking your work - Learner's mindset, which you use to master new tools, software, and ways of working - Strong collaboration skills. You seek to understand others' problems and use your own perspective to solve problems together - You have the following technical skills and knowledge: * Proficiency in Google Suite, Slack, and Jira * Proficiency in Salesforce * Proficiency in Python or R - Your experiences have informed your belief in Braven's mission and have prepared you to work with or for Braven's student Fellow population - Please know that no one ever meets 100% of the preferred qualifications. If much of this describes you, we encourage you to apply. (This is encouraging but not substantive? It's more of a note; we can keep as part of Preferred Qualifications maybe as a paragraph.) We need to separate Requirements and Qualifications sections. Requirements = Minimum Requirements. Qualifications = Preferred Qualifications. Skills: maybe we can extract technical skills list from Preferred Qualifications and the "You have the following technical skills and knowledge:" as Skills section. But we already have Qualifications includes those. However the instruction lists Skills as a possible heading. We could put technical skills under Skills, and keep Qualifications for soft skills etc. But we must not duplicate content. We need to preserve all substantive info; we can split. Better: Requirements (minimum), Qualifications (preferred), Skills (technical). Let's do that. Thus: Requirements (

      Requirements

      ): - BA/BS in a quantitative field or work experience that demonstrates expertise in quantitative analysis - At least 3 years of relevant experience - Extensive experience writing and presenting compelling data-driven narratives for internal and external audiences - Proficiency in Excel/Google Sheets and SQL Qualifications (

      Qualifications

      ): - Demonstrated experience using AI effectively and responsibly to make an actual impact on outcomes - Experience designing and building dashboards and visualizations (Tableau preferred) - Strong strategic thinking skills, including a proven ability to bring clarity to ambiguous solutions - Ability to take initiative to solve challenges and tap into opportunities; ability to make complex tasks simple by applying clear logic and processes to component steps - Excellent time management and prioritization skills, which allow you to manage your own time and energy and seek the right help to complete multiple projects well and on time - Demonstrated attention to detail, known for checking and double-checking your work - Learner's mindset, which you use to master new tools, software, and ways of working - Strong collaboration skills. You seek to understand others' problems and use your own perspective to solve problems together - Your experiences have informed your belief in Braven's mission and have prepared you to work with or for Braven's student Fellow population - Please know that no one ever meets 100% of the preferred qualifications. If much of this describes you, we encourage you to apply. Skills (

      Skills

      ): - Proficiency in SQL (listed also in Requirements but we can keep) - Proficiency in Google Suite, Slack, and Jira - Proficiency in Salesforce - Proficiency in Python or R But note SQL appears in both Requirements and Skills; we can keep it in Requirements and also mention in Skills but maybe redundant. To avoid duplication, we could keep SQL only in Requirements and not repeat in Skills. However the instruction says preserve ALL substantive information; duplication is okay if it's in original. But we can avoid duplication by not repeating. However the original listed SQL under Minimum Requirements and also under Preferred Qualifications (Proficiency in SQL). So it's mentioned twice. We could keep both but it's okay. To keep it simple, we can include SQL under Requirements and also under Skills (might be considered duplication but it's still substantive). Might be okay. Better to follow original: Requirements includes SQL; Preferred Qualifications includes Proficiency in SQL; Skills includes Proficiency in Google Suite, Slack, Jira, Salesforce, Python/R. We'll keep SQL in both. Now Benefits: from Benefits Compensation and Benefits. We need to capture: - Compet