January 2027 BES Fellowship for Founding School Leaders - Workforce Development Schools in Atlanta
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "To Apply" etc. Also remove the Massachusetts lie detector test line (legal). Also remove "Please note that Fellows may begin assignments prior to Fellowship orientation." maybe part of Additional Information but it's application instruction? It's more info; but it's not boilerplate. However it's about process; maybe keep? It's not application instruction exactly but could be considered part of Additional Information. We'll keep substantive info.
We must preserve all substantive information. So include details about fellowship: training year, follow on support, etc. Also include compensation details: $110,000 grant, healthcare reimbursement, travel, moving expenses, reimbursements for school design expenses, opportunity to apply for BES start-up fund awards.
Additional Information: timeline Jan 2027-Dec 2027, grant disbursements end Dec 2027, authorization timeline may extend, BES will work with Fellows to identify additional funding, etc.
We must not create sections with filler like "commensurate with experience". Not present.
We need to decide which headings to use: "About the role" maybe not present; we have "Who We Are" (could be About the organization). Could use "About BES" but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The posting has "Who We Are" (We) Are", "What You’ll Do", "What You Bring", "Qualifications", "Compensation And Benefits", "Additional Information". We could map: "Who We Are" -> maybe "About the role"? Not exactly. But we could use "About the organization" but not in list. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings if applicable. However we can also use other headings if they better match? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those headings when appropriate. If content doesn't match exactly, we could still use those headings if they fit. For "Who We Are" maybe "About the role" is not accurate. Could use "About the organization" but not in list. Might be okay to use "About the role" as a heading for description of the fellowship? The role is Fellowship for Founding School Leaders. So "About the role" could describe the fellowship overall. That seems okay.
"What You’ll Do" maps to Responsibilities.
"What You Bring" could be Skills or Requirements? Could be Skills. We'll use Skills.
"Qualifications" stays Qualifications.
"Compensation And Benefits" maps to Benefits and Pay. Could split: Benefits and Pay. But we have both compensation and benefits. We could make a Benefits section and maybe Pay subsection? But we need to avoid thin sections. Could combine into Benefits (including pay). But instruction says create Pay/Schedule/Benefits sections only if posting actually states them. It states compensation ($110k grant) and benefits (healthcare reimbursement, travel, moving, etc). So we could have a Pay section for the $110k grant and a Benefits section for the rest. Or combine. Safer to have both Pay and Benefits.
"Additional Information" could be maybe Schedule? Not exactly. Could be Additional Information but not in list. Could omit if not needed? But it contains substantive info about timeline, etc. We could put it under a heading like "Additional Information" even if not in list; but instruction says use those headings (e.g...). Might be okay to use Additional Information as heading, but they didn't forbid other headings. Safer to include a heading like "Additional Information" as h3.
We must not include application instructions: "To Apply", "Applications Are Reviewed..." etc. Remove those lines.
Also remove "Please note that Fellows may begin assignments prior to Fellowship orientation." That's part of Additional Information but maybe considered application instruction? It's about process; but it's still substantive. Might keep.
We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The Massachusetts lie detector test line is legal boilerplate; remove.
Now craft HTML.
Structure:
About the role
Fellowship for Founding School Leaders- Atlanta BES seeks a Fellow for our Fellowship program to serve as a founding school leader in Atlanta. This BES Fellowship offers highly motivated leaders committed to transforming education the rigorous, multi-year training needed to design, found, and lead a high-achieving school that meets the unique needs of its community. BES welcomes applicants from the Atlanta region for new public charter schools and aligned with authorizer priorities, with particular interest in leaders aiming to found schools in the Gwinnett county area. For regions with significant charter presence, applicants will be required to make a strong case for how a new proposed charter school will be viable and meet the needs of the community.
Who We Are
maybe not needed if we used About the role. But we already have Who We Are content. Could incorporate into About the role? But we have separate paragraph for Who We Are. Might be better to have a section "About BES". But instruction didn't list that. However we could still include a heading "About BES". Not prohibited. But to follow instruction, maybe we merge Who We Are content into About the role? But About the role already includes some description; we could add more. However we must preserve all substantive information; we can put it in About the role paragraph.
Thus we can omit separate Who We Are heading.
Next Responsibilities:
Responsibilities
- Intensive training year: over 300 hours of coursework on school design, leadership, governance, community engagement, diversity, equity, and inclusion.
- Conduct in-depth studies of effective schools across the nation and complete residencies at high-performing schools.
- Develop a charter application and establish a founding board.
- Planning year (year two): partner with a BES coach to refine project management and leadership skills, hire founding staff, recruit students, solidify school vision.
- Follow On Support: dedicated coaching and cohort-based training to bridge transition from founder to school leader.
- Years three and four (first two operational years): welcome inaugural class, coach teachers, use data to drive academic success.
- Second year of operation: deepen academic focus, serve growing student population, build leadership capacity for future growth, foster empowered mission-aligned team.
- Year three of operation and beyond: opt-in to other leadership and professional development opportunities from BES to support school and strengthen leadership bench.
Skills
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "To Apply" etc. Also remove the Massachusetts lie detector test line (legal). Also remove "Please note that Fellows may begin assignments prior to Fellowship orientation." maybe part of Additional Information but it's application instruction? It's more info; but it's not boilerplate. However it's about process; maybe keep? It's not application instruction exactly but could be considered part of Additional Information. We'll keep substantive info. We must preserve all substantive information. So include details about fellowship: training year, follow on support, etc. Also include compensation details: $110,000 grant, healthcare reimbursement, travel, moving expenses, reimbursements for school design expenses, opportunity to apply for BES start-up fund awards. Additional Information: timeline Jan 2027-Dec 2027, grant disbursements end Dec 2027, authorization timeline may extend, BES will work with Fellows to identify additional funding, etc. We must not create sections with filler like "commensurate with experience". Not present. We need to decide which headings to use: "About the role" maybe not present; we have "Who We Are" (could be About the organization). Could use "About BES" but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The posting has "Who We Are" (We) Are", "What You’ll Do", "What You Bring", "Qualifications", "Compensation And Benefits", "Additional Information". We could map: "Who We Are" -> maybe "About the role"? Not exactly. But we could use "About the organization" but not in list. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings if applicable. However we can also use other headings if they better match? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those headings when appropriate. If content doesn't match exactly, we could still use those headings if they fit. For "Who We Are" maybe "About the role" is not accurate. Could use "About the organization" but not in list. Might be okay to use "About the role" as a heading for description of the fellowship? The role is Fellowship for Founding School Leaders. So "About the role" could describe the fellowship overall. That seems okay.
"What You’ll Do" maps to Responsibilities.
"What You Bring" could be Skills or Requirements? Could be Skills. We'll use Skills.
"Qualifications" stays Qualifications.
"Compensation And Benefits" maps to Benefits and Pay. Could split: Benefits and Pay. But we have both compensation and benefits. We could make a Benefits section and maybe Pay subsection? But we need to avoid thin sections. Could combine into Benefits (including pay). But instruction says create Pay/Schedule/Benefits sections only if posting actually states them. It states compensation ($110k grant) and benefits (healthcare reimbursement, travel, moving, etc). So we could have a Pay section for the $110k grant and a Benefits section for the rest. Or combine. Safer to have both Pay and Benefits.
"Additional Information" could be maybe Schedule? Not exactly. Could be Additional Information but not in list. Could omit if not needed? But it contains substantive info about timeline, etc. We could put it under a heading like "Additional Information" even if not in list; but instruction says use those headings (e.g...). Might be okay to use Additional Information as heading, but they didn't forbid other headings. Safer to include a heading like "Additional Information" as h3.
We must not include application instructions: "To Apply", "Applications Are Reviewed..." etc. Remove those lines.
Also remove "Please note that Fellows may begin assignments prior to Fellowship orientation." That's part of Additional Information but maybe considered application instruction? It's about process; but it's still substantive. Might keep.
We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The Massachusetts lie detector test line is legal boilerplate; remove.
Now craft HTML.
Structure:
About the role
About the role
Fellowship for Founding School Leaders- Atlanta BES seeks a Fellow for our Fellowship program to serve as a founding school leader in Atlanta. This BES Fellowship offers highly motivated leaders committed to transforming education the rigorous, multi-year training needed to design, found, and lead a high-achieving school that meets the unique needs of its community. BES welcomes applicants from the Atlanta region for new public charter schools and aligned with authorizer priorities, with particular interest in leaders aiming to found schools in the Gwinnett county area. For regions with significant charter presence, applicants will be required to make a strong case for how a new proposed charter school will be viable and meet the needs of the community.
Who We Are
maybe not needed if we used About the role. But we already have Who We Are content. Could incorporate into About the role? But we have separate paragraph for Who We Are. Might be better to have a section "About BES". But instruction didn't list that. However we could still include a heading "About BES". Not prohibited. But to follow instruction, maybe we merge Who We Are content into About the role? But About the role already includes some description; we could add more. However we must preserve all substantive information; we can put it in About the role paragraph. Thus we can omit separate Who We Are heading. Next Responsibilities:Responsibilities
- Intensive training year: over 300 hours of coursework on school design, leadership, governance, community engagement, diversity, equity, and inclusion.
- Conduct in-depth studies of effective schools across the nation and complete residencies at high-performing schools.
- Develop a charter application and establish a founding board.
- Planning year (year two): partner with a BES coach to refine project management and leadership skills, hire founding staff, recruit students, solidify school vision.
- Follow On Support: dedicated coaching and cohort-based training to bridge transition from founder to school leader.
- Years three and four (first two operational years): welcome inaugural class, coach teachers, use data to drive academic success.
- Second year of operation: deepen academic focus, serve growing student population, build leadership capacity for future growth, foster empowered mission-aligned team.
- Year three of operation and beyond: opt-in to other leadership and professional development opportunities from BES to support school and strengthen leadership bench. Skills
- Ability to lead, manage, and motivate a team towards results; commitment to serve as a school leader in the community for at least 10 years.
- Self-awareness and humility: growth mindset, continuous desire to improve, eager to give, take, and implement feedback with humility in real time.
- Commitment to community: experience in the proposed community, strong organizational partnerships, ability to gain and factor in community input.
- Diversity, equity, and inclusion in action: school model primarily serves students from under-sourced communities, anti-racist lens, success with similar populations, responsiveness to community needs.
- Commitment to excellence for all students: clear vision for school, ability to discuss key elements in detailed, compelling, direct manner; accountability for results; belief that all students can achieve at high levels.
Qualifications
- Bachelor’s degree required; Master’s or Professional degree preferred.
- Minimum 8 years of professional experience, with instructional or instructional leadership experience required.
- At least 2 years managing and supervising adults in a PreK-12 setting required; 2 years of school leadership experience preferred.
- Commitment to serving as a school leader in the proposed community for at least 10 years required.
- Ability to establish and activate local connections to support school enrollment.
- Strong preference for candidates with at least 2-3 years of experience living or working in the proposed school region, especially those with strong ties to the community.
- Clear, compelling rationale for the proposed school location.
- Experience in career-connected learning and/or existing workforce partnerships preferred.
Pay
$110,000 grant during the first year of the program (the Fellowship training year).
Next Benefits:Benefits
- Healthcare reimbursement of up to $6,000 for an individual healthcare plan or up to $8,000 for a family plan.
- Travel and accommodations for training and during school study travel.
- Reimbursement for up to $5,000 in moving expenses.
- Reimbursements for school design expenses, design team expenses, or professional development (amount dependent on track).
- Opportunity to apply for BES start‑up fund awards and/or those provided exclusively to Fellows by partners.
Additional Information
The BES Fellowship training year runs from January 2027 through December 2027, during which time BES Fellows will receive disbursements from their $110,000 grant. While grant disbursements will end in December 2027 (or typically 12 months after beginning the Fellowship), the authorization process in certain regions can sometimes extend beyond that time. Note that the beginning and end date for the Atlanta Fellowship will depend on the local counties’ authorization timeline AND a candidate’s readiness. BES Fellows will continue to receive coaching and guidance from BES through this phase to help them navigate the entirety of the authorization process. In addition, BES will work with Fellows affected by this timeline to identify additional funding opportunities for Fellows, wherever possible.
We should remove the line about "Please note that Fellows may begin assignments prior to Fellowship orientation." It's somewhat procedural but maybe considered application instruction? It's not exactly applying; it's about timing. Might keep? It's not in the list of headings but could be part of Additional Information. However it's not crucial; we can keep it if we want to preserve all substantive info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that line if it's substantive. It is about timing of assignments. Let's include it in Additional Information paragraph. Add sentence: "Please note that Fellows may