Senior Director, Program Operations & Product Enablement
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to extract content from posting.
First, identify sections:
- About the role: The posting includes "About The Opportunity" and "In This Role, You Will". Could combine as About the role. Provide prose.
- Responsibilities: The bullet list under "In This Role, You Will" with percentages and subpoints. Those are responsibilities. Should be list items.
- Requirements: The "About You" section lists qualifications: 8-10+ years experience etc. Those are requirements/qualifications. Could separate Requirements and Qualifications? The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content fits each.
We have:
- Requirements: maybe the mandatory qualifications: 8-10+ years experience, 3+ years people management, etc.
- Qualifications: maybe the "strong plus" items? Or we could combine.
- Skills: maybe list of proficiencies: Salesforce, Microsoft Suite, etc.
- Benefits: The posting includes "What We Offer" and "A Thoughtful Approach To Compensation" includes salary range. Also mention benefits? Not explicit benefits like health, retirement. There's "We’re a self-sustaining nonprofit that believes in fair and competitive compensation...". No explicit benefits list. So we should not create Benefits section unless posting actually states them. It does not list specific benefits like health insurance, 401k, etc. So we should omit Benefits.
- Pay: The posting includes salary range: $104,000 - $165,000. So we can include Pay section with that info.
- Schedule: The posting mentions remote role, occasional travel 6-8 times a year. Also mentions hybrid option for those near offices. Could be considered schedule? It mentions location and travel. Could include Schedule section with remote/hybrid and travel expectation.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from each section.
Let's parse content:
About The Team: description of BigFuture team, mission, reach, etc. Could be part of About the role? Probably "About the role" could include description of team and opportunity.
But we need to avoid duplication. We'll create sections:
About the role
with prose summarizing the role: includes description of team, opportunity, mission, etc. Must not invent; we can copy relevant sentences.
We need to include all substantive info: The About The Team paragraph, About The Opportunity paragraph, maybe also the mission statement later? The mission appears later: "Mission Clearing a path for all students to own their future." That's also substantive. Could include in About the role or separate? Probably part of About the role.
We'll include that.
Responsibilities: The bullet list under "In This Role, You Will" with percentages and subpoints. We'll turn each main bullet (Program Ownership & Strategic Leadership (30%), etc.) into list items, maybe with sub-bullets? The instruction: Use - for any list of duties/requirements/benefits. So we can have nested lists? Probably okay to have
- with inner
. We'll keep simple: each main responsibility as - and include its subpoints as separate
- indented? Could just include them as part of the same
- text. To preserve detail, we could include subpoints as separate
- under a nested
. That's still a list.
We'll do:
- Program Ownership & Strategic Leadership (30%)
- Act as the program manager and policy leader for the full RES portfolio (Search, Connections™, and related features)
- Lead and manage the design and execution of annual subscription model including pricing and packaging strategy for existing and future product launches or enhancements
- Serve as the primary subject matter expert for enrollment solutions products, features, and subscription mechanics
- Manage and direct annual subscription launch process and operations ahead of July 1 Subscription Year start including pilot launch and tracking (when necessary), documentation, internal Customer Success & Sales training, order opening window, eligibility, commercial incentives
... similarly for other sections.
We need to keep all subpoints.
Next, Requirements: The "About You" section includes many bullet-like sentences. We'll extract each requirement as list item.
List:
- 8-10+ years’ experience in program management within a SaaS or product organization, including significant experience in Higher Education EdTech, with deep subject-matter expertise in subscription-based product models, specifically pricing, packaging, and lifecycle management
- Experience in higher education enrollment management, recruitment, and admissions is a strong plus
- 3+ years of recent, direct people management experience
- Strong organizational and prioritization skills, with the ability to lead multiple initiatives independently and collaboratively
- Strong analytical skills, with demonstrated experience translating usage, revenue, and customer behavior data (including cohort analysis) into actionable product and business recommendations
- Experience designing and governing policy, contract, or compliance frameworks, ideally in partnership with Legal, involving eligibility rules, terms of service, or data privacy standards
- Demonstrated success managing complex, cross-functional operational workflows (such as billing, provisioning, or order management) under firm deadlines
- Experience managing third-party vendor relationships and contract negotiations, including performance governance and forward-looking portfolio planning
- Skilled in developing training, enablement, and internal or customer-facing communications to support product launches or major transitions
- Excellent written and verbal communication skills, with experience presenting to senior leadership or executive stakeholders
- Proficiency in Salesforce, Microsoft Suite, Zoom, Slack, Jira, Confluence
- A strategic and inclusive leadership style: you set clear priorities, build effective team structures, plan for future needs, and foster a culture of belonging
- A proven ability to drive performance and growth: you set high expectations, deliver real-time, evidence-based feedback, and coach team members to take smart risks, stretch their skills, and achieve meaningful impact
- The ability to travel 6-8 times a year to College Board offices or on behalf of College Board business
Also there are "All Roles At College Board Require" list: passion for expanding educational and career opportunities and mission-driven work; Authorization to work in the United States for any employer; Curiosity and enthusiasm for emerging technologies, with a willingness to experiment with and adopt new AI-driven solutions and comfort learning and applying new digital tools independently and proactively.; Clear and concise communication skills, written and verbal; A learner's mindset and a commitment to growth: welcoming diverse perspectives, giving and receiving timely, respectful feedback, and continuously improving through iterative learning and user input; A drive for impact and excellence: solving complex problems, making data-informed decisions, prioritizing what matters most, and continuously improving through learning, user input, and external benchmarking; A collaborative and empathetic approach: working across differences, fostering trust, and contributing to a culture of shared success.
These could be considered Requirements or Qualifications. We'll split: Requirements = mandatory experience/skills; Qualifications = maybe the "All Roles At College Board Require" list? Or we could treat them as Qualifications. The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide what goes where.
We have Skills: proficiency in specific tools (Salesforce, Microsoft Suite, Zoom, Slack, Jira, Confluence). Also maybe "Strong organizational and prioritization skills" etc could be skills. But we already have many skill-like items in About You.
We could assign:
- Requirements: the experience-based items (8-10+ years, 3+ years people management, experience in higher ed enrollment etc.) plus maybe the ability to travel.
- Qualifications: the "All Roles At College Board Require" list (passion, work authorization, curiosity, communication skills, learner's mindset, drive for impact, collaborative approach).
- Skills: the technical proficiencies (Salesforce, Microsoft Suite, Zoom, Slack, Jira, Confluence) plus maybe "Strong analytical skills" etc? But analytical skills could be considered skill. However we already used analytical in Requirements? We could move analytical to Skills. But we need to preserve all info; we can duplicate? Better not duplicate. Let's think.
We have many bullet-like items in About You that are a mix of experience, skills, abilities. To avoid over-splitting, we could just have one Requirements section containing all the About You items (including the All Roles requirements). Then we could have Skills section for the specific tool proficiencies. Qualifications maybe omitted if not distinct. But we need to follow instruction: we can include sections only when posting has real specific content. If we don't have distinct content for Qualifications, we omit it.
Thus:
- About the role: prose.
- Responsibilities: list.
- Requirements: list (including experience, people management, analytical, policy design, cross-functional workflows, vendor management, training development, communication, leadership style, drive for growth, travel ability, plus All Roles requirements: passion, work authorization, curiosity, communication skills, learner's mindset, drive for impact, collaborative approach). Note communication skills appears twice; we can keep once.
- Skills: list of proficiencies: Salesforce, Microsoft Suite, Zoom, Slack, Jira, Confluence.
- Pay: salary range.
- Schedule: remote/hybrid and travel expectation (maybe already in Requirements travel). But schedule could mention remote role, hybrid option, occasional travel 6-8 times a year. We'll include schedule section.
We must not repeat job title. Not include Job ID.
We must not include boilerplate like EEO etc. The posting includes "All Roles At College Board Require" which we included.
We must not include application instructions, process, etc. So we omit "About Our Process" and "What We Offer" beyond pay? Actually "What We Offer" includes compensation and benefits talk; we extracted pay. The rest of that paragraph is generic about compensation philosophy; we could include in Pay section maybe as prose. But we should not invent. The paragraph: "We’re a self-sustaining nonprofit that believes in fair and competitive compensation, grounded in your qualifications, experience, impact, and the market. A Thoughtful Approach To Compensation The hiring range for this role is $104,000 - $165,000.Your exact salary will depend on your location, experience, and how your background compares to others in similar roles at College Board.We aim to make our best offer upfront—rooted in fairness, transparency, and market data.We adjust salaries by location to ensure fairness, no matter where you live. You’ll have open, transparent conversations about compensation, benefits, and what it’s like to work at College Board throughout your hiring process. Check out our careers page for more."
We can include that as prose in Pay section, plus the range.
We should not include "Check out our careers page for more." That's maybe boilerplate? It's part of the offering but not essential? It's not boilerplate like legal; it's a reference. Might be okay to keep. But we can keep it.
We must not include "About College Board" etc? That's generic but still substantive about mission. Could be part of About the role. We'll include mission statement.
Now produce HTML.
We'll start with About the role
then with combined prose.
Let's craft prose:
"College Board’s BigFuture team supports students in making post‑high‑school decisions, reaching over seven million students each year with a free resource for college, scholarship, and career exploration. The Recruitment & Enrollment Solutions (RES) team works with more than 1,200 higher education
for prose. We need to extract content from posting. First, identify sections: - About the role: The posting includes "About The Opportunity" and "In This Role, You Will". Could combine as About the role. Provide prose. - Responsibilities: The bullet list under "In This Role, You Will" with percentages and subpoints. Those are responsibilities. Should be list items. - Requirements: The "About You" section lists qualifications: 8-10+ years experience etc. Those are requirements/qualifications. Could separate Requirements and Qualifications? The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content fits each. We have: - Requirements: maybe the mandatory qualifications: 8-10+ years experience, 3+ years people management, etc. - Qualifications: maybe the "strong plus" items? Or we could combine. - Skills: maybe list of proficiencies: Salesforce, Microsoft Suite, etc. - Benefits: The posting includes "What We Offer" and "A Thoughtful Approach To Compensation" includes salary range. Also mention benefits? Not explicit benefits like health, retirement. There's "We’re a self-sustaining nonprofit that believes in fair and competitive compensation...". No explicit benefits list. So we should not create Benefits section unless posting actually states them. It does not list specific benefits like health insurance, 401k, etc. So we should omit Benefits. - Pay: The posting includes salary range: $104,000 - $165,000. So we can include Pay section with that info. - Schedule: The posting mentions remote role, occasional travel 6-8 times a year. Also mentions hybrid option for those near offices. Could be considered schedule? It mentions location and travel. Could include Schedule section with remote/hybrid and travel expectation. We must not create sections with filler like "commensurate with experience". We have actual content. We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from each section. Let's parse content: About The Team: description of BigFuture team, mission, reach, etc. Could be part of About the role? Probably "About the role" could include description of team and opportunity. But we need to avoid duplication. We'll create sections:
About the role
with prose summarizing the role: includes description of team, opportunity, mission, etc. Must not invent; we can copy relevant sentences. We need to include all substantive info: The About The Team paragraph, About The Opportunity paragraph, maybe also the mission statement later? The mission appears later: "Mission Clearing a path for all students to own their future." That's also substantive. Could include in About the role or separate? Probably part of About the role. We'll include that. Responsibilities: The bullet list under "In This Role, You Will" with percentages and subpoints. We'll turn each main bullet (Program Ownership & Strategic Leadership (30%), etc.) into list items, maybe with sub-bullets? The instruction: Use- for any list of duties/requirements/benefits. So we can have nested lists? Probably okay to have
- with inner
- . We'll keep simple: each main responsibility as
- and include its subpoints as separate
- indented? Could just include them as part of the same
- text. To preserve detail, we could include subpoints as separate
- under a nested
- . That's still a list.
We'll do:
- Program Ownership & Strategic Leadership (30%)
- Act as the program manager and policy leader for the full RES portfolio (Search, Connections™, and related features)
- Lead and manage the design and execution of annual subscription model including pricing and packaging strategy for existing and future product launches or enhancements
- Serve as the primary subject matter expert for enrollment solutions products, features, and subscription mechanics
- Manage and direct annual subscription launch process and operations ahead of July 1 Subscription Year start including pilot launch and tracking (when necessary), documentation, internal Customer Success & Sales training, order opening window, eligibility, commercial incentives
... similarly for other sections.
We need to keep all subpoints.
Next, Requirements: The "About You" section includes many bullet-like sentences. We'll extract each requirement as list item.
List:
- 8-10+ years’ experience in program management within a SaaS or product organization, including significant experience in Higher Education EdTech, with deep subject-matter expertise in subscription-based product models, specifically pricing, packaging, and lifecycle management
- Experience in higher education enrollment management, recruitment, and admissions is a strong plus
- 3+ years of recent, direct people management experience
- Strong organizational and prioritization skills, with the ability to lead multiple initiatives independently and collaboratively
- Strong analytical skills, with demonstrated experience translating usage, revenue, and customer behavior data (including cohort analysis) into actionable product and business recommendations
- Experience designing and governing policy, contract, or compliance frameworks, ideally in partnership with Legal, involving eligibility rules, terms of service, or data privacy standards
- Demonstrated success managing complex, cross-functional operational workflows (such as billing, provisioning, or order management) under firm deadlines
- Experience managing third-party vendor relationships and contract negotiations, including performance governance and forward-looking portfolio planning
- Skilled in developing training, enablement, and internal or customer-facing communications to support product launches or major transitions
- Excellent written and verbal communication skills, with experience presenting to senior leadership or executive stakeholders
- Proficiency in Salesforce, Microsoft Suite, Zoom, Slack, Jira, Confluence
- A strategic and inclusive leadership style: you set clear priorities, build effective team structures, plan for future needs, and foster a culture of belonging
- A proven ability to drive performance and growth: you set high expectations, deliver real-time, evidence-based feedback, and coach team members to take smart risks, stretch their skills, and achieve meaningful impact
- The ability to travel 6-8 times a year to College Board offices or on behalf of College Board business
Also there are "All Roles At College Board Require" list: passion for expanding educational and career opportunities and mission-driven work; Authorization to work in the United States for any employer; Curiosity and enthusiasm for emerging technologies, with a willingness to experiment with and adopt new AI-driven solutions and comfort learning and applying new digital tools independently and proactively.; Clear and concise communication skills, written and verbal; A learner's mindset and a commitment to growth: welcoming diverse perspectives, giving and receiving timely, respectful feedback, and continuously improving through iterative learning and user input; A drive for impact and excellence: solving complex problems, making data-informed decisions, prioritizing what matters most, and continuously improving through learning, user input, and external benchmarking; A collaborative and empathetic approach: working across differences, fostering trust, and contributing to a culture of shared success.
These could be considered Requirements or Qualifications. We'll split: Requirements = mandatory experience/skills; Qualifications = maybe the "All Roles At College Board Require" list? Or we could treat them as Qualifications. The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide what goes where.
We have Skills: proficiency in specific tools (Salesforce, Microsoft Suite, Zoom, Slack, Jira, Confluence). Also maybe "Strong organizational and prioritization skills" etc could be skills. But we already have many skill-like items in About You.
We could assign:
- Requirements: the experience-based items (8-10+ years, 3+ years people management, experience in higher ed enrollment etc.) plus maybe the ability to travel.
- Qualifications: the "All Roles At College Board Require" list (passion, work authorization, curiosity, communication skills, learner's mindset, drive for impact, collaborative approach).
- Skills: the technical proficiencies (Salesforce, Microsoft Suite, Zoom, Slack, Jira, Confluence) plus maybe "Strong analytical skills" etc? But analytical skills could be considered skill. However we already used analytical in Requirements? We could move analytical to Skills. But we need to preserve all info; we can duplicate? Better not duplicate. Let's think.
We have many bullet-like items in About You that are a mix of experience, skills, abilities. To avoid over-splitting, we could just have one Requirements section containing all the About You items (including the All Roles requirements). Then we could have Skills section for the specific tool proficiencies. Qualifications maybe omitted if not distinct. But we need to follow instruction: we can include sections only when posting has real specific content. If we don't have distinct content for Qualifications, we omit it.
Thus:
- About the role: prose.
- Responsibilities: list.
- Requirements: list (including experience, people management, analytical, policy design, cross-functional workflows, vendor management, training development, communication, leadership style, drive for growth, travel ability, plus All Roles requirements: passion, work authorization, curiosity, communication skills, learner's mindset, drive for impact, collaborative approach). Note communication skills appears twice; we can keep once.
- Skills: list of proficiencies: Salesforce, Microsoft Suite, Zoom, Slack, Jira, Confluence.
- Pay: salary range.
- Schedule: remote/hybrid and travel expectation (maybe already in Requirements travel). But schedule could mention remote role, hybrid option, occasional travel 6-8 times a year. We'll include schedule section.
We must not repeat job title. Not include Job ID.
We must not include boilerplate like EEO etc. The posting includes "All Roles At College Board Require" which we included.
We must not include application instructions, process, etc. So we omit "About Our Process" and "What We Offer" beyond pay? Actually "What We Offer" includes compensation and benefits talk; we extracted pay. The rest of that paragraph is generic about compensation philosophy; we could include in Pay section maybe as prose. But we should not invent. The paragraph: "We’re a self-sustaining nonprofit that believes in fair and competitive compensation, grounded in your qualifications, experience, impact, and the market. A Thoughtful Approach To Compensation The hiring range for this role is $104,000 - $165,000.Your exact salary will depend on your location, experience, and how your background compares to others in similar roles at College Board.We aim to make our best offer upfront—rooted in fairness, transparency, and market data.We adjust salaries by location to ensure fairness, no matter where you live. You’ll have open, transparent conversations about compensation, benefits, and what it’s like to work at College Board throughout your hiring process. Check out our careers page for more."
We can include that as prose in Pay section, plus the range.
We should not include "Check out our careers page for more." That's maybe boilerplate? It's part of the offering but not essential? It's not boilerplate like legal; it's a reference. Might be okay to keep. But we can keep it.
We must not include "About College Board" etc? That's generic but still substantive about mission. Could be part of About the role. We'll include mission statement.
Now produce HTML.
We'll start with
About the role
thenwith combined prose. Let's craft prose: "College Board’s BigFuture team supports students in making post‑high‑school decisions, reaching over seven million students each year with a free resource for college, scholarship, and career exploration. The Recruitment & Enrollment Solutions (RES) team works with more than 1,200 higher education
- Program Ownership & Strategic Leadership (30%)
- with inner