Part-Time Center Manager
Code Ninjas (Tampa-Carrollwood) · San Diego, California, United States · 1 mo ago
OTHR$17.75–$20/hrFull-time
We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "Position Overview", "Key Responsibilities", "Qualifications", "The Person We Are Looking For", "Compensation". Also maybe "About Us". We must not repeat job title as heading. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Remove boilerplate: EEO, equal-opportunity, application instructions? The instruction says remove application instructions. So we should drop "To Apply Please submit your résumé..." Also drop "Code Ninjas Rancho Bernardo is an equal-opportunity employer." Also drop "About Us" maybe? It's not a required heading but could be included if substantive. It's about the company; we can keep as a section maybe "About Us". But we need to include a section only when posting has real specific content. The "About Us" paragraph is substantive. So we can include a heading "About Us". However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not limited to those. We can use any appropriate heading. Likely we should use headings like "About the role", "Responsibilities", "Qualifications", "Benefits", "Pay", "Schedule". But we have content: "Who We Are" could be "About the role"? Actually "Who We Are" is about the company, not role. Could be "About Us". But they gave example headings; we can still use others if appropriate. Safer to follow examples: Use headings: About the role, Responsibilities, Qualifications, Pay, Schedule? Also maybe "Benefits" if present. There's no explicit benefits besides compensation. There's schedule info: "approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays." That's schedule. Pay: "$17.75 - $20.00 per hour". So we can have Pay and Schedule sections.
We also have "Key Responsibilities" which is a list. Use Responsibilities
then - ... each responsibility.
Qualifications: list.
"The Person We Are Looking For" maybe could be part of Qualifications or separate "Skills"? Could be "Skills". But we can treat as "Skills" heading.
We also have "Who We Are" maybe as "About the role"? Actually "About the role" would be position overview. We have "Position Overview". So we can use "About the role" heading for that.
Thus sections:
- About the role (position overview paragraph)
- Responsibilities (list)
- Qualifications (list)
- Skills (maybe "The Person We Are Looking For")
- Pay (compensation)
- Schedule (hours)
We must not include filler like "commensurate with experience". Not present.
We must not include application instructions, EEO, etc.
We must preserve all substantive information. So we need to include all details from sections we keep.
Let's extract content.
Who We Are: paragraph about Code Ninjas, kids ages 5-14, etc. This is substantive. Could be part of "About the role"? Actually "About the role" is position overview. But we could also have a separate "About Us" heading. However instruction says prefer few substantive sections over many thin ones. Could combine Who We Are and Position Overview into About the role? But they are distinct: Who We Are is about company; Position Overview is about role. Might be okay to have two sections: About the company and About the role. But they said use headings like About the role, Responsibilities, etc. Not strictly limited. I'd include "About the role" for position overview, and maybe "About the company" for Who We Are. But to keep few sections, maybe we merge Who We Are into About the role? However that would mix company description with role overview; still substantive. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe we can have sections: About the role (includes company description and position overview), Responsibilities, Qualifications, Skills, Pay, Schedule. That's 6 sections.
Let's craft About the role paragraph: combine Who We Are and Position Overview.
Who We Are: "Code Ninjas is a leading children’s coding and STEM education franchise where kids ages 5–14 learn to code by creating video games, developing projects, and solving exciting challenges. Our students—called Ninjas—progress from White Belt to Black Belt while developing valuable skills in coding, mathematics, logic, creativity, and problem-solving. Our promise is simple: Kids have fun. Parents see results. Code Ninjas Rancho Bernardo is an established, award-winning center with a strong reputation in the community. We are looking for a motivated and dependable Center Manager who can maintain our high standards while helping the center continue to grow."
Position Overview: "We are seeking a dynamic and results-driven Part-Time Center Manager to oversee daily operations, support and supervise our instructional team, communicate with families, and drive student enrollment and retention. The ideal candidate is organized, proactive, professional, and comfortable balancing customer service, sales, staff leadership, and student engagement. Coding experience is helpful but not required; however, the candidate must be enthusiastic about technology and willing to learn our programs and curriculum. This position requires approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays."
We need to avoid repeating schedule info in About the role if we will have Schedule section later. But we can keep schedule mention in About the role? Might duplicate. Better to keep schedule only in Schedule section. So we should remove schedule sentence from About the role. Also we should remove the "approximately 20–25 hours per week..." from About the role. Also we might keep the part about coding experience helpful but not required etc. That's qualifications.
Thus About the role will combine Who We Are and Position Overview minus schedule line.
Let's craft:
"Code Ninjas is a leading children’s coding and STEM education franchise where kids ages 5–14 learn to code by creating video games, developing projects, and solving exciting challenges. Our students—called Ninjas—progress from White Belt to Black Belt while developing valuable skills in coding, mathematics, logic, creativity, and problem-solving. Our promise is simple: Kids have fun. Parents see results. Code Ninjas Rancho Bernardo is an established, award-winning center with a strong reputation in the community. We are looking for a motivated and dependable Center Manager who can maintain our high standards while helping the center continue to grow. We are seeking a dynamic and results-driven Part-Time Center Manager to oversee daily operations, support and supervise our instructional team, communicate with families, and drive student enrollment and retention. The ideal candidate is organized, proactive, professional, and comfortable balancing customer service, sales, staff leadership, and student engagement. Coding experience is helpful but not required; however, the candidate must be enthusiastic about technology and willing to learn our programs and curriculum."
Now Responsibilities: list from Key Responsibilities bullet points.
We need to extract each bullet:
- Oversee the center’s daily operations and ensure all classes and programs run smoothly
- Complete opening and closing responsibilities
- Maintain a clean, organized, safe, and welcoming learning environment
- Manage student attendance, scheduling, makeup sessions, and other administrative tasks
- Ensure center policies, safety procedures, and brand standards are consistently followed
- Provide the owner with regular updates regarding center activities, staffing, enrollment, and performance
- Supervise, schedule, train, and support instructors
- Assign staff responsibilities based on enrollment and student needs
- Monitor instructor performance and provide ongoing coaching and feedback
- Arrange coverage for employee absences and resolve scheduling issues
- Build a positive, accountable, and collaborative team culture
- Create a fun, encouraging, and safe environment where students can learn and grow
- Build strong relationships with students and families
- Communicate professionally with parents regarding student progress, scheduling, and center programs
- Address parent questions or concerns calmly, promptly, and effectively
- Ensure every family receives a consistently positive experience
- Respond promptly to inquiries from prospective families
- Conduct center tours and explain Code Ninjas programs clearly and enthusiastically
- Follow up with leads, trial families, and former members
- Convert tours and trial sessions into enrollments
- Support student retention by maintaining strong communication with current families
- Assist with marketing, community outreach, camps, events, and promotional activities
- Track leads, tours, enrollments, cancellations, and follow-up activities
We need to put each as
- .
Qualifications: list from Qualifications section.
Extract:
- Previous experience in management, education, childcare, tutoring, enrichment programs, customer service, or sales
- Experience supervising employees or coordinating a team is strongly preferred
- Experience working with children ages five and older
- Strong verbal and written communication skills
- Excellent organization, time-management, and problem-solving abilities
- Professional, dependable, and comfortable taking initiative
- Able to handle multiple responsibilities in a fast-paced environment
- Confident communicating with parents and following up with prospective customers
- Comfortable using computers, scheduling systems, email, and basic business software
- Knowledge of coding or technology is helpful, but the ability and willingness to learn are essential
- Must enjoy working with children and contributing to a positive team environment
- Must be available during weekday afternoons and Saturdays
- Must successfully complete all required background and child-safety checks
Note: availability duplicates schedule; we will have schedule section, but we can keep it in qualifications? Might duplicate. Better to move availability to Schedule section and remove from Qualifications. However the instruction says preserve ALL substantive information; we can't remove it. But we can keep it in both places? That would be duplication. Better to keep it in Schedule section and not duplicate in Qualifications. But then we lose that piece from Qualifications. However we could keep it in Qualifications and also have Schedule section referencing it; but that duplicates. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. However they said remove duplicated lines. So we should avoid duplicate lines. So we should place availability only once, likely in Schedule section. So we remove from Qualifications.
Thus Qualifications list without availability line.
Now Skills: "The Person We Are Looking For" paragraph.
Extract:
"Our ideal Center Manager is warm with children, professional with parents, supportive but accountable with employees, and confident with sales. This person notices what needs to be done, takes ownership, communicates clearly, and follows through without requiring constant supervision. If you are passionate about working with children, developing a strong team, delivering excellent customer service, and helping a growing education business succeed, we would love to hear from you."
We can put as
under Skills heading.
Now Pay: "$17.75 - $20.00 per hour"
Now Schedule: "approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays."
We should also mention that it's part-time. Already implied.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce:
About the role
...
Responsibilities
- ...
...
Qualifications
...
Skills
...
Pay
$17.75 - $20.00 per hour
Schedule
approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays.
Check for any leftover boilerplate: We removed EEO, application instructions, "About Us" duplicate? We kept company description in About the role. Good.
Check that we didn't include "To Apply" etc.
Now ensure we didn't miss any substantive info: The "Who We Are" includes "Code Ninjas Rancho Bernardo is an established, award-winning center with a
for prose. Remove boilerplate: EEO, equal-opportunity, application instructions? The instruction says remove application instructions. So we should drop "To Apply Please submit your résumé..." Also drop "Code Ninjas Rancho Bernardo is an equal-opportunity employer." Also drop "About Us" maybe? It's not a required heading but could be included if substantive. It's about the company; we can keep as a section maybe "About Us". But we need to include a section only when posting has real specific content. The "About Us" paragraph is substantive. So we can include a heading "About Us". However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not limited to those. We can use any appropriate heading. Likely we should use headings like "About the role", "Responsibilities", "Qualifications", "Benefits", "Pay", "Schedule". But we have content: "Who We Are" could be "About the role"? Actually "Who We Are" is about the company, not role. Could be "About Us". But they gave example headings; we can still use others if appropriate. Safer to follow examples: Use headings: About the role, Responsibilities, Qualifications, Pay, Schedule? Also maybe "Benefits" if present. There's no explicit benefits besides compensation. There's schedule info: "approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays." That's schedule. Pay: "$17.75 - $20.00 per hour". So we can have Pay and Schedule sections.
We also have "Key Responsibilities" which is a list. Use Responsibilities
then - ... each responsibility.
Qualifications: list.
"The Person We Are Looking For" maybe could be part of Qualifications or separate "Skills"? Could be "Skills". But we can treat as "Skills" heading.
We also have "Who We Are" maybe as "About the role"? Actually "About the role" would be position overview. We have "Position Overview". So we can use "About the role" heading for that.
Thus sections:
- About the role (position overview paragraph)
- Responsibilities (list)
- Qualifications (list)
- Skills (maybe "The Person We Are Looking For")
- Pay (compensation)
- Schedule (hours)
We must not include filler like "commensurate with experience". Not present.
We must not include application instructions, EEO, etc.
We must preserve all substantive information. So we need to include all details from sections we keep.
Let's extract content.
Who We Are: paragraph about Code Ninjas, kids ages 5-14, etc. This is substantive. Could be part of "About the role"? Actually "About the role" is position overview. But we could also have a separate "About Us" heading. However instruction says prefer few substantive sections over many thin ones. Could combine Who We Are and Position Overview into About the role? But they are distinct: Who We Are is about company; Position Overview is about role. Might be okay to have two sections: About the company and About the role. But they said use headings like About the role, Responsibilities, etc. Not strictly limited. I'd include "About the role" for position overview, and maybe "About the company" for Who We Are. But to keep few sections, maybe we merge Who We Are into About the role? However that would mix company description with role overview; still substantive. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe we can have sections: About the role (includes company description and position overview), Responsibilities, Qualifications, Skills, Pay, Schedule. That's 6 sections.
Let's craft About the role paragraph: combine Who We Are and Position Overview.
Who We Are: "Code Ninjas is a leading children’s coding and STEM education franchise where kids ages 5–14 learn to code by creating video games, developing projects, and solving exciting challenges. Our students—called Ninjas—progress from White Belt to Black Belt while developing valuable skills in coding, mathematics, logic, creativity, and problem-solving. Our promise is simple: Kids have fun. Parents see results. Code Ninjas Rancho Bernardo is an established, award-winning center with a strong reputation in the community. We are looking for a motivated and dependable Center Manager who can maintain our high standards while helping the center continue to grow."
Position Overview: "We are seeking a dynamic and results-driven Part-Time Center Manager to oversee daily operations, support and supervise our instructional team, communicate with families, and drive student enrollment and retention. The ideal candidate is organized, proactive, professional, and comfortable balancing customer service, sales, staff leadership, and student engagement. Coding experience is helpful but not required; however, the candidate must be enthusiastic about technology and willing to learn our programs and curriculum. This position requires approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays."
We need to avoid repeating schedule info in About the role if we will have Schedule section later. But we can keep schedule mention in About the role? Might duplicate. Better to keep schedule only in Schedule section. So we should remove schedule sentence from About the role. Also we should remove the "approximately 20–25 hours per week..." from About the role. Also we might keep the part about coding experience helpful but not required etc. That's qualifications.
Thus About the role will combine Who We Are and Position Overview minus schedule line.
Let's craft:
"Code Ninjas is a leading children’s coding and STEM education franchise where kids ages 5–14 learn to code by creating video games, developing projects, and solving exciting challenges. Our students—called Ninjas—progress from White Belt to Black Belt while developing valuable skills in coding, mathematics, logic, creativity, and problem-solving. Our promise is simple: Kids have fun. Parents see results. Code Ninjas Rancho Bernardo is an established, award-winning center with a strong reputation in the community. We are looking for a motivated and dependable Center Manager who can maintain our high standards while helping the center continue to grow. We are seeking a dynamic and results-driven Part-Time Center Manager to oversee daily operations, support and supervise our instructional team, communicate with families, and drive student enrollment and retention. The ideal candidate is organized, proactive, professional, and comfortable balancing customer service, sales, staff leadership, and student engagement. Coding experience is helpful but not required; however, the candidate must be enthusiastic about technology and willing to learn our programs and curriculum."
Now Responsibilities: list from Key Responsibilities bullet points.
We need to extract each bullet:
- Oversee the center’s daily operations and ensure all classes and programs run smoothly
- Complete opening and closing responsibilities
- Maintain a clean, organized, safe, and welcoming learning environment
- Manage student attendance, scheduling, makeup sessions, and other administrative tasks
- Ensure center policies, safety procedures, and brand standards are consistently followed
- Provide the owner with regular updates regarding center activities, staffing, enrollment, and performance
- Supervise, schedule, train, and support instructors
- Assign staff responsibilities based on enrollment and student needs
- Monitor instructor performance and provide ongoing coaching and feedback
- Arrange coverage for employee absences and resolve scheduling issues
- Build a positive, accountable, and collaborative team culture
- Create a fun, encouraging, and safe environment where students can learn and grow
- Build strong relationships with students and families
- Communicate professionally with parents regarding student progress, scheduling, and center programs
- Address parent questions or concerns calmly, promptly, and effectively
- Ensure every family receives a consistently positive experience
- Respond promptly to inquiries from prospective families
- Conduct center tours and explain Code Ninjas programs clearly and enthusiastically
- Follow up with leads, trial families, and former members
- Convert tours and trial sessions into enrollments
- Support student retention by maintaining strong communication with current families
- Assist with marketing, community outreach, camps, events, and promotional activities
- Track leads, tours, enrollments, cancellations, and follow-up activities
We need to put each as
- .
Qualifications: list from Qualifications section.
Extract:
- Previous experience in management, education, childcare, tutoring, enrichment programs, customer service, or sales
- Experience supervising employees or coordinating a team is strongly preferred
- Experience working with children ages five and older
- Strong verbal and written communication skills
- Excellent organization, time-management, and problem-solving abilities
- Professional, dependable, and comfortable taking initiative
- Able to handle multiple responsibilities in a fast-paced environment
- Confident communicating with parents and following up with prospective customers
- Comfortable using computers, scheduling systems, email, and basic business software
- Knowledge of coding or technology is helpful, but the ability and willingness to learn are essential
- Must enjoy working with children and contributing to a positive team environment
- Must be available during weekday afternoons and Saturdays
- Must successfully complete all required background and child-safety checks
Note: availability duplicates schedule; we will have schedule section, but we can keep it in qualifications? Might duplicate. Better to move availability to Schedule section and remove from Qualifications. However the instruction says preserve ALL substantive information; we can't remove it. But we can keep it in both places? That would be duplication. Better to keep it in Schedule section and not duplicate in Qualifications. But then we lose that piece from Qualifications. However we could keep it in Qualifications and also have Schedule section referencing it; but that duplicates. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. However they said remove duplicated lines. So we should avoid duplicate lines. So we should place availability only once, likely in Schedule section. So we remove from Qualifications.
Thus Qualifications list without availability line.
Now Skills: "The Person We Are Looking For" paragraph.
Extract:
"Our ideal Center Manager is warm with children, professional with parents, supportive but accountable with employees, and confident with sales. This person notices what needs to be done, takes ownership, communicates clearly, and follows through without requiring constant supervision. If you are passionate about working with children, developing a strong team, delivering excellent customer service, and helping a growing education business succeed, we would love to hear from you."
We can put as
under Skills heading.
Now Pay: "$17.75 - $20.00 per hour"
Now Schedule: "approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays."
We should also mention that it's part-time. Already implied.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce:
About the role
...
Responsibilities
- ...
...
Qualifications
...
Skills
...
Pay
$17.75 - $20.00 per hour
Schedule
approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays.
Check for any leftover boilerplate: We removed EEO, application instructions, "About Us" duplicate? We kept company description in About the role. Good.
Check that we didn't include "To Apply" etc.
Now ensure we didn't miss any substantive info: The "Who We Are" includes "Code Ninjas Rancho Bernardo is an established, award-winning center with a
under Skills heading. Now Pay: "$17.75 - $20.00 per hour" Now Schedule: "approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays." We should also mention that it's part-time. Already implied. Now we need to output HTML fragment only, no /, no markdown. We'll produce:
About the role
...
Responsibilities
- ... ...
Qualifications
-
...
Skills
...
Pay
$17.75 - $20.00 per hour
Schedule
approximately 20–25 hours per week, primarily during weekday afternoons and Saturdays.
Check for any leftover boilerplate: We removed EEO, application instructions, "About Us" duplicate? We kept company description in About the role. Good. Check that we didn't include "To Apply" etc. Now ensure we didn't miss any substantive info: The "Who We Are" includes "Code Ninjas Rancho Bernardo is an established, award-winning center with a