SENIOR MANAGER, PROGRAM FIDELITY & IMPLEMENTATION

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are and What We Believe" (organization description) maybe not needed as a heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content: Who We Are and What We Believe (organization description) – could be "About the role"? Actually "About the role" is about the job, not org. But we could treat "Who We Are and What We Believe" as "About the organization". Not in list but we can still use heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Probably we should stick to those headings if applicable. We have responsibilities (Primary Responsibilities, Secondary Responsibilities). We have qualifications (Required, Preferred). We have Benefits (listed). We have Pay (Compensation). We have Work Schedule (Schedule). We have maybe "Who We Are and What We Believe" could be omitted or placed under a brief intro

without heading. The instruction: 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. So we can include a brief intro paragraph about the organization without heading. Thus sections: Responsibilities (maybe split into Primary and Secondary but we can combine under Responsibilities). Qualifications (Required and Preferred). Benefits. Pay. Schedule. We must preserve all substantive information. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "How To Apply/Application Deadline:" etc – we should remove that. Also "Start Date: September 10th, 2026" maybe keep? It's substantive? It's not in the list of headings but could be placed in a paragraph. However instruction: include a section ONLY when posting has real specific content for it — never emit a heading followed by filler/placeholder text. Start date is specific; we could include it in a paragraph under maybe "Details". But not required heading. Could just include as a paragraph after intro. We must not invent or summarize away detail. So we need to keep all details: responsibilities percentages, etc. Let's extract. Intro paragraph: "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." Then Responsibilities: we have Primary Responsibilities with bullet-like sentences (some with percentages). We need to turn each duty into

• . The percentages are part of duty description; we can keep them inside the li. Primary Responsibilities list items: - Operationalize and maintain the enterprise-wide program standards and fidelity expectations set with the Managing Director grounded in research‑based and culturally responsive practice, ensuring consistent, high-quality implementation across relational, virtual, scaled, and partner‑delivered modalities. (40%) - Ensure program materials are clear, implementable, and aligned to national standards, reducing complexity for staff and partners while supporting consistent implementation. - Coordinate cross‑functional alignment on model updates, partnering with Program Operations, Training & Learning, and Research, Analytics, and Evaluation (RAE) to operationalize the fidelity expectations set with the Managing Director, align on measures and data collection approaches, review implementation and outcomes insights, and ensure timely communication, training readiness, and evidence based program decision‑making. - Monitor program performance and generate actionable insights by analyzing qualitative and quantitative data; partner with the Impact team to assess effectiveness, inform strategic adjustments, and translate findings into clear decision-making and storytelling. - Ensure fidelity measures are usable, meaningful, and oriented toward improvement rather than compliance in partnership with the Program Operations team. - Operationalize the Managing Director's decisions on what must remain consistent in program delivery versus what can be adapted by program staff in a regional context and ensure these decisions are documented and monitored for effectiveness over time. Then Learning & Practice Standards (25%): - Translate the advising philosophy, model, and standards into practice expectations: what good advising looks like across the program, and what staff must know and be able to do. - Set the staff learning priorities, scope, and sequence, using fidelity and field data to target them. - Partner with T&L, who designs, builds, and delivers the training. - Partner with the Training & Learning team to ensure program training initiatives align with organizational training standards, evaluation practices, learning technologies, and training governance processes. - Serve as the Subject Matter Expert for program training initiatives with the Training & Learning team. - Provide content expertise, program requirements, and curriculum direction while partnering with the Training & Learning team on instructional design, training development, implementation, evaluation, and ongoing maintenance. - Own the advisor-facing curriculum: the guides and content that define what advisors do with students at each stage, grounded in the DEAL model and the Bottom Line Way. - Keep practice standards and curriculum current as the model evolves, feeding what the field and the data show back into them. Staff-Facing System & Implementation (25%): - Codify the program model, standards, and curriculum into clear, usable staff-facing assets: the program hub, manuals, playbooks, and the ‘how to do the job and why’ guidance, down to the granular level. - Package and route to the right teams: Program Operations (monitoring, real-time data, intervention), Training & Learning (learning priorities and content direction), and Product / Transformation (the NPC and LMS configuration the program needs). - Serve as the cross-functional connective tissue across these liaisons so the system stays coherent as it moves from design to delivery. - Run the fidelity loop operationally: track progress, strategize around results, and intervene or escalate when delivery drifts from the model. Secondary Responsibilities: Organizational Support – 10%: - Participate in facilitation of strategy and design sessions to inform evolving program strategy. - Follow trends and best practices in the field of college success and technology to support persistence efforts to inform evolving program design. - Advance Bottom Line’s mission and brand. - Maintain a “students first” perspective, actively building connections with colleagues across functions to build understanding of each other’s work, and more importantly, serve as the best possible advocate for our students and mission. - Work collaboratively with others on the National Team and with regional teams on shared projects, committees, and other opportunities. We could combine all responsibilities under one

  Responsibilities

  with a
  containing all items. Qualifications: Required and Preferred. Required list: - Bachelor's degree or equivalent experience. - 6-8 years of progressive experience in program design, implementation, or fidelity in a youth-serving, education, or nonprofit setting, including experience translating a program model into practice standards and guidance that staff can follow. - Demonstrated history of leading successful program partnerships, including communicating effectively with senior leaders and nonprofit professionals to find areas of commonality and achieve shared goals. - Experience building program standards, playbooks, or practice guidance that improved consistency of delivery across sites, regions, or teams. - Unwavering commitment to quality programs and excellence in organizational and project management, with the ability to achieve strategic objectives. - Experience owning advisor- or staff-facing curriculum and practice standards, partnering with a training function on delivery rather than delivering training directly. - Excellent organization, prioritization, and follow-through; comfortable holding multiple workstreams and partner relationships at once. - Change-management orientation; able to work through evolving program requirements, platform changes, and shifting priorities. - Strong cross-functional collaborator able to partner credibly with Program Operations, Training & Learning, RAE, regional Program leadership, and national leaders. - Work authorization required. - Demonstrated commitment to Bottom Line's Mission, Vision, and Core Values. Preferred list: - Experience with learning management platforms (for example, Canvas LMS). - Lived experience or deep professional relationships in first-generation college going and low-income communities. We'll put under

  Qualifications

  with two subheadings? Not required; we can just list all items, maybe separate required and preferred with

  but better to keep as list with indication. Could do

  Required:

  then
  etc. But instruction: Use
  • for any list of duties/requirements/benefits. So we can have separate lists for required and preferred, each preceded by a

    indicating. Benefits: The posting shows "Benefits:" but no details after colon? Actually after "Benefits:" line ends; maybe missing details. The text ends at "Benefits:" with no further content. So we should not create a Benefits section because no specific content. So omit Benefits. Pay: Compensation details: "Compensation: Nat'l-$88,000 Chi/Hou-$96,800 Bos-$103,800 NY-$107,400". That's specific. So we create

    Pay

    with a

    containing that. Schedule: "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. So

    Schedule

    with

    . We also have Direct Reports, Expected Travel etc. Those are minor metadata; we could fold into a short

    under maybe "Details". But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include a paragraph after schedule for Direct Reports, Expected Travel, etc. But not required heading. Could include as a

    after schedule. Let's craft HTML. Structure:

    Intro paragraph...

    Responsibilities

    ...

    Qualifications

    Required:

    ...

    Preferred:

    ...

    Pay

    Compensation: Nat'l-$88,000 Chi/Hou-$96,800 Bos-$103,800 NY-$107,400

    Schedule

    Work Schedule: Monday to Friday, 9a to 5p or 10a to 6p (local time); flexibility may be requested. Additional hours as needed.

    Direct Reports: None. Expected Travel: Approximately 1 to 2 trips per quarter to Bottom Line regions, Bottom Line staff convenings, and/or field events.

    Make sure to not include any extra markdown. Output only HTML fragment. Check for any repeated lines: we removed application instructions, start date, etc. Keep start date? Not included; it's minor metadata maybe could be included in a paragraph but not required. The instruction says fold minor metadata into a short

    or drop it. Start