SENIOR MANAGER, PROGRAM CONTENT & STUDENT ENGAGEMENT
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content. The posting includes:
- Who We Are and What We Believe (mission) – could be "About the role"? Actually "About the role" is typical heading for description of role. But we have "Who We Are and What We Believe" describing organization. Could be "About the organization". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can adapt: Use "About the role" for the description of what you will do? Or we could use "About the organization" but not in list. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; we can use them if appropriate. We can also add other headings if needed? They said "include a section ONLY when the posting has real, specific content for it". So we can include sections like About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Possibly also "Philosophy" but not in list; maybe we can incorporate into About the role or Responsibilities. Better to stick to allowed headings.
Thus we need to map content:
- About the role: Could include "Who We Are and What We Believe" and "What You Will Do" summary? Actually "What You Will Do" is more like responsibilities. So maybe About the role includes mission and brief role overview. Then Responsibilities includes Primary and Secondary Responsibilities. Qualifications includes Required and Preferred qualifications. Skills maybe included within Qualifications or separate. Benefits includes Benefits. Pay includes Compensation. Schedule includes Work Schedule.
We must not repeat job title as heading. No Job ID.
We must use - for any list of duties/requirements/benefits. So for responsibilities list, we need to break into bullet points. The responsibilities are given as percentages and bullet-like paragraphs. We can convert each responsibility into
- . Similarly for qualifications: required and preferred can be bullet lists.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details: percentages, specifics like "Student Voice & Content Standards (25%)", etc. We need to keep them as text inside
- . Not to lose any detail.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit EEO etc. There's "How To Apply/Application Deadline: All applications must be submitted via Bottom Line’s Career Page . Please share your resume and cover letter. Start Date: September 10th, 2026". Application instructions should be removed. So we should drop the "How To Apply/Application Deadline" and "Please share your resume and cover letter." Also "Start Date: September 10th, 2026" maybe considered metadata; but it's substantive? It's a start date. Should we keep? It's not in the list of headings but could be placed in a short
maybe under About the role? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Start date is minor metadata; we could fold into a short
maybe under About the role or at end. But they said "include a section ONLY when the posting has real, specific content for it". Start date is specific content; we could include it as a paragraph under About the role or maybe a separate "Details" but not a heading. Safer to fold into a short
under About the role.
Compensation: They list "Compensation: Nat'l-$88,000 Chi/Hou-$96,800 Bos-$103,800 NY-$107,400". That's specific; we should include Pay section.
Benefits: They have "Benefits:" but no details after colon? Actually the text ends with "Benefits:" and then nothing. So there is no substantive benefit details. According to rule: never create Benefits section unless posting actually states them. Since there is no detail after "Benefits:", we should not include Benefits section. So we omit Benefits.
Work Schedule: They have "Work Schedule: Monday to Friday, 9a to 5p or 10a to 6p (local time ); flexibility may be requested. Additional hours as needed." That's specific; include Schedule section.
Philosophy: This is a list of attributes; could be considered Skills or Qualifications? Might be better to include under Qualifications or Skills. Since they said we can use Skills heading. We'll treat Philosophy as Skills (or maybe Qualifications). We'll put under Skills.
Now we need to ensure we don't create sections with filler. So we will include:
- About the role (contains mission description and brief role overview + start date maybe)
- Responsibilities (Primary and Secondary)
- Qualifications (Required and Preferred)
- Skills (Philosophy)
- Pay (Compensation)
- Schedule (Work Schedule)
We should not include Benefits.
Now we need to format.
We'll start with
About the role
. Then a containing the mission description and what you will do overview? Actually "What You Will Do" is more like responsibilities; but we can include a short summary there. However we must preserve ALL substantive information; we cannot omit details. So we need to include the full "Who We Are and What We Believe" paragraph and the "What You Will Do" paragraph (the first paragraph after that). Let's extract:
Who We Are and What We Believe: Founded in 1997, Bottom Line is a nationally recognized nonprofit organization with a mission to partner with degree-aspiring students from first-generation and low-income backgrounds as they get into college, graduate, and launch meaningful careers. For nearly 30 years, Bottom Line has provided consistent, one-on-one support to help students navigate the challenges of accessing and succeeding in college. We serve students from 9th grade through career launch through our signature programming in Massachusetts, New York City, Chicago, Ohio, Detroit, and Houston and scaled supports available nationwide. Our vision is to create a far-reaching ripple effect, launched by the transformative power of a college degree and a mobilizing first career, that uplifts individuals, families, and entire communities. When you join Bottom Line, you will become a part of a team that combines passion with expertise to advance equity and opportunity for degree-aspiring students. In our dynamic, results-driven environment, your contributions will help shape brighter futures and stronger communities.
What You Will Do: The Senior Manager of Program Content & Student Engagement owns Bottom Line's student-facing content and how students experience it, from voice and quality standards through publication and continuous improvement. This role writes and edits priority content, directs the writers, translators, and contributors who produce at volume, and uses engagement data and student feedback to continuously evolve the content library so it remains relevant and useful to students. This role partners with the Transformation team, which owns the platforms and technical systems behind the content, and works within the program vision and student milestones set by the Managing Director of Program Strategy & Fidelity.
We need to keep all that.
Then Responsibilities: Primary Responsibilities (with subheadings) and Secondary Responsibilities.
We need to convert each bullet into
- . The percentages are part of the responsibility description; we should keep them.
Primary Responsibilities:
- Student Voice & Content Standards (25%) Own the student-facing voice across all content and resources, ensuring students experience Bottom Line as consistent, relevant, and trustworthy wherever they encounter it. Maintain and evolve Bottom Line's student content standards, including style and content writing guidelines, so the full library reflects one coherent voice. Ensure the student content library and student-facing site remain accurate, current, and easy for students to navigate. Partner with the Transformation team, which owns the platforms and technical build, translating content and student-experience needs into platform requirements.
- Content Evolution & Continuous Improvement (15%) Monitor student engagement across content channels and translate findings into decisions about what to create, refresh, and retire. Conduct user testing with students, including through the National Youth Advisory Council, and apply insights to improve content quality and relevance. Maintain a regular cycle for reviewing content performance and reporting on results to program leadership.
- Content Creation & Editorial Direction (30%) Write and edit prioritization of college, career, and financial-aid content, including articles, resources, and campaign content, aligned to Bottom Line's voice and quality standards. Plan, assign, coordinate, and publish the annual content calendar across audiences and milestones, coordinating content, translation, and video production. Direct writers, translators, and freelance contributors, reviewing work to a consistent editorial standard. Manage and maintain student-facing content within the learning management system and across regional, journey, and milestone pages.
- Lead & Facilitate Bottom Line's National Youth Advisory Council (15%) Recruit, interview, and thoughtfully staff the Council with students who represent Bottom Line's target demographics. Develop the Council's projects and bodies of work, develop agendas, and lead monthly meetings. Share Council feedback and recommendations with the wider Bottom Line team. Partner with other teams across the organization including Transformation and Scaled Advising.
Secondary Responsibilities:
- Support New Programmatic Efforts & Partnerships (10%) Develop localized content in close partnership with staff leading partner and grant-specific efforts. Support educator engagement through the educator newsletter, resource maps, and referral campaigns.
- Organizational Support (5%) Partner with other teams across the organization including Transformation and Scaled Advising. Represent the Bottom Line brand in a positive light and take actions to increase brand awareness throughout the community. Follow trends and best practices in the field of college success and technology to support persistence efforts and inform evolving program design.
We need to keep all that.
Now Qualifications: Required and Preferred.
Required:
- Bachelor's degree or equivalent experience.
- 6 to 8 years of progressive experience creating and managing content for youth or young-adult audiences in a nonprofit, education, or media setting, including experience managing a content library or digital product and the engagement it drives.
- Strong writing and editing skills for teen and young-adult audiences, with a feel for the Bottom Line student voice. We would love to see writing samples or a portfolio.
- Strong strategic judgment and hands-on content skills: you use engagement data and student feedback to decide what to create, cut, or improve, shape content structure and goals, and personally write or edit the pieces that matter most.
- Comfort directing freelancers and vendors and partnering credibly across teams such as Transformation
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. The posting includes: - Who We Are and What We Believe (mission) – could be "About the role"? Actually "About the role" is typical heading for description of role. But we have "Who We Are and What We Believe" describing organization. Could be "About the organization". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can adapt: Use "About the role" for the description of what you will do? Or we could use "About the organization" but not in list. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; we can use them if appropriate. We can also add other headings if needed? They said "include a section ONLY when the posting has real, specific content for it". So we can include sections like About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Possibly also "Philosophy" but not in list; maybe we can incorporate into About the role or Responsibilities. Better to stick to allowed headings.
Thus we need to map content:
- About the role: Could include "Who We Are and What We Believe" and "What You Will Do" summary? Actually "What You Will Do" is more like responsibilities. So maybe About the role includes mission and brief role overview. Then Responsibilities includes Primary and Secondary Responsibilities. Qualifications includes Required and Preferred qualifications. Skills maybe included within Qualifications or separate. Benefits includes Benefits. Pay includes Compensation. Schedule includes Work Schedule.
We must not repeat job title as heading. No Job ID.
We must use - for any list of duties/requirements/benefits. So for responsibilities list, we need to break into bullet points. The responsibilities are given as percentages and bullet-like paragraphs. We can convert each responsibility into
- . Similarly for qualifications: required and preferred can be bullet lists.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details: percentages, specifics like "Student Voice & Content Standards (25%)", etc. We need to keep them as text inside
- . Not to lose any detail.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit EEO etc. There's "How To Apply/Application Deadline: All applications must be submitted via Bottom Line’s Career Page . Please share your resume and cover letter. Start Date: September 10th, 2026". Application instructions should be removed. So we should drop the "How To Apply/Application Deadline" and "Please share your resume and cover letter." Also "Start Date: September 10th, 2026" maybe considered metadata; but it's substantive? It's a start date. Should we keep? It's not in the list of headings but could be placed in a short
maybe under About the role? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Start date is minor metadata; we could fold into a short
maybe under About the role or at end. But they said "include a section ONLY when the posting has real, specific content for it". Start date is specific content; we could include it as a paragraph under About the role or maybe a separate "Details" but not a heading. Safer to fold into a short
under About the role.
Compensation: They list "Compensation: Nat'l-$88,000 Chi/Hou-$96,800 Bos-$103,800 NY-$107,400". That's specific; we should include Pay section.
Benefits: They have "Benefits:" but no details after colon? Actually the text ends with "Benefits:" and then nothing. So there is no substantive benefit details. According to rule: never create Benefits section unless posting actually states them. Since there is no detail after "Benefits:", we should not include Benefits section. So we omit Benefits.
Work Schedule: They have "Work Schedule: Monday to Friday, 9a to 5p or 10a to 6p (local time ); flexibility may be requested. Additional hours as needed." That's specific; include Schedule section.
Philosophy: This is a list of attributes; could be considered Skills or Qualifications? Might be better to include under Qualifications or Skills. Since they said we can use Skills heading. We'll treat Philosophy as Skills (or maybe Qualifications). We'll put under Skills.
Now we need to ensure we don't create sections with filler. So we will include:
- About the role (contains mission description and brief role overview + start date maybe)
- Responsibilities (Primary and Secondary)
- Qualifications (Required and Preferred)
- Skills (Philosophy)
- Pay (Compensation)
- Schedule (Work Schedule)
We should not include Benefits.
Now we need to format.
We'll start with
About the role
. Then a containing the mission description and what you will do overview? Actually "What You Will Do" is more like responsibilities; but we can include a short summary there. However we must preserve ALL substantive information; we cannot omit details. So we need to include the full "Who We Are and What We Believe" paragraph and the "What You Will Do" paragraph (the first paragraph after that). Let's extract:
Who We Are and What We Believe: Founded in 1997, Bottom Line is a nationally recognized nonprofit organization with a mission to partner with degree-aspiring students from first-generation and low-income backgrounds as they get into college, graduate, and launch meaningful careers. For nearly 30 years, Bottom Line has provided consistent, one-on-one support to help students navigate the challenges of accessing and succeeding in college. We serve students from 9th grade through career launch through our signature programming in Massachusetts, New York City, Chicago, Ohio, Detroit, and Houston and scaled supports available nationwide. Our vision is to create a far-reaching ripple effect, launched by the transformative power of a college degree and a mobilizing first career, that uplifts individuals, families, and entire communities. When you join Bottom Line, you will become a part of a team that combines passion with expertise to advance equity and opportunity for degree-aspiring students. In our dynamic, results-driven environment, your contributions will help shape brighter futures and stronger communities.
What You Will Do: The Senior Manager of Program Content & Student Engagement owns Bottom Line's student-facing content and how students experience it, from voice and quality standards through publication and continuous improvement. This role writes and edits priority content, directs the writers, translators, and contributors who produce at volume, and uses engagement data and student feedback to continuously evolve the content library so it remains relevant and useful to students. This role partners with the Transformation team, which owns the platforms and technical systems behind the content, and works within the program vision and student milestones set by the Managing Director of Program Strategy & Fidelity.
We need to keep all that.
Then Responsibilities: Primary Responsibilities (with subheadings) and Secondary Responsibilities.
We need to convert each bullet into
- . The percentages are part of the responsibility description; we should keep them.
Primary Responsibilities:
- Student Voice & Content Standards (25%) Own the student-facing voice across all content and resources, ensuring students experience Bottom Line as consistent, relevant, and trustworthy wherever they encounter it. Maintain and evolve Bottom Line's student content standards, including style and content writing guidelines, so the full library reflects one coherent voice. Ensure the student content library and student-facing site remain accurate, current, and easy for students to navigate. Partner with the Transformation team, which owns the platforms and technical build, translating content and student-experience needs into platform requirements.
- Content Evolution & Continuous Improvement (15%) Monitor student engagement across content channels and translate findings into decisions about what to create, refresh, and retire. Conduct user testing with students, including through the National Youth Advisory Council, and apply insights to improve content quality and relevance. Maintain a regular cycle for reviewing content performance and reporting on results to program leadership.
- Content Creation & Editorial Direction (30%) Write and edit prioritization of college, career, and financial-aid content, including articles, resources, and campaign content, aligned to Bottom Line's voice and quality standards. Plan, assign, coordinate, and publish the annual content calendar across audiences and milestones, coordinating content, translation, and video production. Direct writers, translators, and freelance contributors, reviewing work to a consistent editorial standard. Manage and maintain student-facing content within the learning management system and across regional, journey, and milestone pages.
- Lead & Facilitate Bottom Line's National Youth Advisory Council (15%) Recruit, interview, and thoughtfully staff the Council with students who represent Bottom Line's target demographics. Develop the Council's projects and bodies of work, develop agendas, and lead monthly meetings. Share Council feedback and recommendations with the wider Bottom Line team. Partner with other teams across the organization including Transformation and Scaled Advising.
Secondary Responsibilities:
- Support New Programmatic Efforts & Partnerships (10%) Develop localized content in close partnership with staff leading partner and grant-specific efforts. Support educator engagement through the educator newsletter, resource maps, and referral campaigns.
- Organizational Support (5%) Partner with other teams across the organization including Transformation and Scaled Advising. Represent the Bottom Line brand in a positive light and take actions to increase brand awareness throughout the community. Follow trends and best practices in the field of college success and technology to support persistence efforts and inform evolving program design.
We need to keep all that.
Now Qualifications: Required and Preferred.
Required:
- Bachelor's degree or equivalent experience.
- 6 to 8 years of progressive experience creating and managing content for youth or young-adult audiences in a nonprofit, education, or media setting, including experience managing a content library or digital product and the engagement it drives.
- Strong writing and editing skills for teen and young-adult audiences, with a feel for the Bottom Line student voice. We would love to see writing samples or a portfolio.
- Strong strategic judgment and hands-on content skills: you use engagement data and student feedback to decide what to create, cut, or improve, shape content structure and goals, and personally write or edit the pieces that matter most.
- Comfort directing freelancers and vendors and partnering credibly across teams such as Transformation
maybe under About the role? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Start date is minor metadata; we could fold into a short
maybe under About the role or at end. But they said "include a section ONLY when the posting has real, specific content for it". Start date is specific content; we could include it as a paragraph under About the role or maybe a separate "Details" but not a heading. Safer to fold into a short
under About the role. Compensation: They list "Compensation: Nat'l-$88,000 Chi/Hou-$96,800 Bos-$103,800 NY-$107,400". That's specific; we should include Pay section. Benefits: They have "Benefits:" but no details after colon? Actually the text ends with "Benefits:" and then nothing. So there is no substantive benefit details. According to rule: never create Benefits section unless posting actually states them. Since there is no detail after "Benefits:", we should not include Benefits section. So we omit Benefits. Work Schedule: They have "Work Schedule: Monday to Friday, 9a to 5p or 10a to 6p (local time ); flexibility may be requested. Additional hours as needed." That's specific; include Schedule section. Philosophy: This is a list of attributes; could be considered Skills or Qualifications? Might be better to include under Qualifications or Skills. Since they said we can use Skills heading. We'll treat Philosophy as Skills (or maybe Qualifications). We'll put under Skills. Now we need to ensure we don't create sections with filler. So we will include: - About the role (contains mission description and brief role overview + start date maybe) - Responsibilities (Primary and Secondary) - Qualifications (Required and Preferred) - Skills (Philosophy) - Pay (Compensation) - Schedule (Work Schedule) We should not include Benefits. Now we need to format. We'll start with
About the role
. Then acontaining the mission description and what you will do overview? Actually "What You Will Do" is more like responsibilities; but we can include a short summary there. However we must preserve ALL substantive information; we cannot omit details. So we need to include the full "Who We Are and What We Believe" paragraph and the "What You Will Do" paragraph (the first paragraph after that). Let's extract: Who We Are and What We Believe: Founded in 1997, Bottom Line is a nationally recognized nonprofit organization with a mission to partner with degree-aspiring students from first-generation and low-income backgrounds as they get into college, graduate, and launch meaningful careers. For nearly 30 years, Bottom Line has provided consistent, one-on-one support to help students navigate the challenges of accessing and succeeding in college. We serve students from 9th grade through career launch through our signature programming in Massachusetts, New York City, Chicago, Ohio, Detroit, and Houston and scaled supports available nationwide. Our vision is to create a far-reaching ripple effect, launched by the transformative power of a college degree and a mobilizing first career, that uplifts individuals, families, and entire communities. When you join Bottom Line, you will become a part of a team that combines passion with expertise to advance equity and opportunity for degree-aspiring students. In our dynamic, results-driven environment, your contributions will help shape brighter futures and stronger communities. What You Will Do: The Senior Manager of Program Content & Student Engagement owns Bottom Line's student-facing content and how students experience it, from voice and quality standards through publication and continuous improvement. This role writes and edits priority content, directs the writers, translators, and contributors who produce at volume, and uses engagement data and student feedback to continuously evolve the content library so it remains relevant and useful to students. This role partners with the Transformation team, which owns the platforms and technical systems behind the content, and works within the program vision and student milestones set by the Managing Director of Program Strategy & Fidelity. We need to keep all that. Then Responsibilities: Primary Responsibilities (with subheadings) and Secondary Responsibilities. We need to convert each bullet into