SY 26/27 High School Principal Fellow (Assistant Principal)

We need to output HTML fragment with sections only when content exists. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must not repeat job title as heading. The posting includes "About KIPP Kansas City Public Schools" which is about organization, not necessarily "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if applicable. We have: - About KIPP Kansas City Public Schools: description of organization. Could be "About the role"? Actually "About the role" is about the position. But we have "Position Overview". That could be "About the role". So we can put that under

About the role

with the Position Overview paragraph. - Responsibilities: we have "Key Responsibilities" with subpoints. So

Responsibilities

with

• items. - Requirements: we have "Qualifications" section with bullet list. That could be Requirements. Also there is "Qualifications" heading later. The instruction says we can use Requirements and Qualifications as separate headings. We need to decide what goes where. The posting has "Qualifications" with bullet list of education, experience, license. Then "Skills and Competencies:" with bullet list. So we can map: - Requirements: maybe the qualifications (education, experience, license). Or we could treat "Qualifications" heading as the qualifications, and "Skills" heading as skills. The instruction says we can use both. So we will output:

  Requirements

  with the bullet list under Qualifications (Master’s Degree..., Minimum of 4–6 years..., Possession of a State Building-Level Administrator License).

  Skills

  with the bullet list under Skills and Competencies (Commitment, Leadership, Initiative, Growth Mindset, Communication, Collaboration, Data Analysis). We also have "Additional Information" with Physical Requirements, Work Environment, Travel Requirements, Compensation and Benefits, etc. We need to include Benefits and Pay sections if present. The posting includes "Compensation and Benefits:" with description: Salary based on years..., eligible for benefit plans, comprehensive range of benefits..., professional growth opportunities. So we can create:

  Benefits

  with description of benefits (medical, dental, vision, life insurance, fertility, disability plans, professional growth, advancement opportunities, leadership training). Also maybe mention salary based on experience. Pay: The posting does not give specific salary numbers or range. It says "Salary is based on years of experience, educational background, and level of expertise." That's not a specific number; but it's still some info about pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation info, albeit not a specific number. Should we include Pay? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation info, so we can include Pay section with that statement. However they also said "Prefer a few substantive sections over many thin ones." Might combine Pay and Benefits into one Benefits section? But they gave separate headings possible. We could include Pay with the salary statement, and Benefits with the benefit plans. That seems okay. Schedule: The posting mentions "Work Environment Reports to work Monday-Friday." That's schedule info (Monday-Friday). So we can include Schedule section with that. We must not include boilerplate like EEO, equal opportunity, selection process, application instructions. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can rephrase into HTML? We should preserve the meaning but not necessarily copy verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all details, but we can format them. Likely we should keep the sentences as they are, maybe split into

  or

• . Avoid omitting any detail. Let's extract substantive content: About KIPP Kansas City Public Schools: paragraph about mission, network, founded 2007, serves 1,000 students Pre-K-12, etc. Position Overview: The Principal Fellow is a pivotal leadership position designed for high-potential assistant principals preparing to transition into the role of principal/school leader The role of the Fellow will focus on academic excellence, character development, and a positive school culture. . This position functions as an intensive residency, requiring the Fellow to shadow a mentor principal while taking on significant leadership responsibilities to ensure a school’s operational and academic success. Under the guidance of a Mentor Principal and District Leadership, the Fellow will develop the competencies required to lead a high-performing K-12 school, focusing on instructional leadership, school culture, and organizational management. This Principal Fellow will collaborate with the principal/school leader, Instructional Coach, Dean of Culture, ISS Coordinator, and teachers. We need to keep that exactly, maybe fix double period. Key Responsibilities: list with subheadings: Instructional Leadership, Teacher Leadership & Development, School Culture and Operations, Data Analysis & Decision-Making, Communication & Collaboration. Each has bullet points (some are sentences). We need to preserve each bullet. We'll create
  • for each duty. Might need to keep subheadings inside
  • ? Could do
  • Instructional Leadership: ...
  . That preserves. Qualifications (Requirements): bullet list: - Master’s Degree in Educational Leadership or currently enrolled in a recognized Principal Prep program - Minimum of 4–6 years of exemplary K-12 teaching experience; including at least 2 years of leadership or teacher-leader experience (e.g., Grade Level Lead, Instructional Coach, Content Lead) - Possession of a State Building-Level Administrator License We need to keep exactly. Skills and Competencies: bullet list: - Commitment: Upholds KIPP Kansas City’s mission and values, including a deep belief in the potential of all students. - Leadership: Strong leadership and team management skills, with the ability to inspire and develop educators. - Initiative: Exemplifies proactive problem solving and willingness to move from “me to we.” - Growth Mindset: Able to receive and handle feedback while assisting with setting the school’s professional culture. - Communication: Excellent interpersonal and communication skills exemplified among the school leadership team and school staff conveying clear, concise, and timely information among all stakeholders. - Collaboration: Ability to collaborate with multiple stakeholders beyond the school staff such as regional and CSuite teams. - Data Analysis: Ability to analyze data, identify trends, and implement strategic interventions based on findings. Additional Information: Physical Requirements, Work Environment, Travel Requirements, Compensation and Benefits, etc. We need to extract Benefits: "As a full-time KIPP Kansas City employee, you are eligible to participate in all KIPP Kansas City benefit plans. We offer a comprehensive range of benefits with competitive rates, including medical, dental, and vision options, as well as life insurance, fertility, and disability plans. KIPP Kansas City is committed to the professional growth and development of our staff. We provide numerous opportunities for advancement, ongoing professional development, and leadership training to help you achieve your career goals." Pay: "Salary is based on years of experience, educational background, and level of expertise." Schedule: "Reports to work Monday-Friday. Typical school or office environment with frequent interruptions. Travel Requirements: Ability to travel to work location." We also have Physical Requirements: "The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this position. Reasonable accommodations may be made to enable individuals with disabilities to perform the functions. The person in this position needs to be able to move about inside and outside the school or office throughout the workday. The candidate is expected to attend conferences, meetings and training sessions both virtually and in person within the Region." Work Environment: Already covered? Actually we have "Work Environment Reports to work Monday-Friday. Typical school or office environment with frequent interruptions." That's schedule and environment. Travel Requirements: "Ability to travel to work location." We need to decide where to put Physical Requirements, Work Environment, Travel Requirements. The instruction only mentions sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fold other info into those sections if relevant, or maybe drop if not fitting? But we must preserve ALL substantive information. So we need to include them somewhere. Could add them under appropriate sections: Physical Requirements could go under Requirements? Or maybe under About the role? But better to create a section? Not allowed headings other than those listed. So we must embed them into existing sections, maybe as

  under appropriate heading. We could add a

  under About the role for the organization description, and then another

  for Position Overview. Then Responsibilities as list. Then Requirements (qualifications) as list. Then Skills as list. Then Benefits as list? Actually benefits description is prose; we can put in

  . Pay as

  . Schedule as

  . Physical Requirements, Work Environment, Travel Requirements could be placed under Schedule or Benefits? Perhaps under Schedule we can include work schedule and travel requirements. Physical Requirements could be under Requirements? But Requirements is about qualifications; maybe we can add a

  under Requirements for physical demands. However the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It doesn't say we cannot have other headings, but we should follow the pattern. Safer to stick to those headings only. So we need to fit all info under those headings. Let's map: - About the role: includes organization description and position overview. - Responsibilities: list of duties. - Requirements: includes qualifications (education, experience, license) and maybe physical requirements? But physical requirements are not qualifications; they are job demands. Could be considered part of Requirements? Might be okay. - Qualifications: maybe we treat as separate from Requirements? Actually we have both headings; we could put education/experience/license under Requirements, and skills under Qualifications? But they gave Skills separate. Hmm. Better: Use Requirements for the mandatory qualifications (education, experience, license). Use Qualifications for the skills/competencies? But they also have Skills heading. The example list includes both Qualifications and Skills. So we need three sections: Requirements, Qualifications, Skills. We can assign: - Requirements: the bullet list of education, experience, license. - Qualifications: maybe the bullet list of commitment, leadership, etc? But those are skills/competencies. Actually they labeled "Skills and Competencies:" So Skills heading fits that. Thus Qualifications could be something else? The posting also has "Qualifications" heading with bullet list of education/experience/license. So we could map that to Qualifications. Then Requirements could be something else like "Minimum of 4–6 years..."? But that's also part of qualifications. Hmm. We need to decide. The instruction says use those headings as examples; not mandatory to use all. We can choose which sections to include based on content. So we could have: - About the role - Responsibilities - Qualifications (education/experience/license) - Skills (commitment, leadership, etc.) - Benefits - Pay - Schedule We can omit Requirements if we don't have distinct content besides qualifications. But we have physical requirements etc. Could we put physical requirements under Schedule? Not ideal. Maybe we can include a Requirements section for physical demands and work environment, and keep Qualifications for education/experience/license, Skills for skills/competencies. That would use all three. Thus: - Requirements: Physical Requirements, Work Environment, Travel Requirements (maybe combine). - Qualifications: Education, experience, license. - Skills: Commitment, Leadership, Initiative, Growth Mindset, Communication, Collaboration, Data Analysis. That seems