Director of Programs

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we can use those headings. So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That seems okay. We need to avoid duplicating content. Let's extract: About the role: The Position paragraph(s). Let's capture: "Reporting to the Deputy Director and collaborating with the Senior Leadership Team (including the Directors of Development, Finance, Operations & HR, and Policy & Communications), the Director of Programs oversees the strategic design, implementation, management, and evaluation of all GFS programs and initiatives. You will guide strategy and execution for a diverse portfolio, including: - State and federally funded preschools - Full-day toddler daycare center - Family Child Care Home Education Network (FCCHEN) - First 5-Family Resource Center and community programs - School-based programs - Collaborations with the Sí Se Puede Collective As a key thought partner to the Executive and Deputy Directors, this leader will help operationalize GFS’s role as a demonstration site for the City of San José’s Children & Youth Services Master Plan (CYSMP), contributing to systems alignment, equitable access, and a ‘no wrong door’ approach for families. The ideal candidate is an experienced, collaborative leader, with deep knowledge of early childhood education and family engagement. They value co‑creating alongside the families they serve, and are comfortable using design thinking approaches, outcome evaluation, and continuous learning to shape programs. This leader is adept at balancing big‑picture thinking with practical execution and thrives in fast‑moving environments. They are grounded in the community and deeply committed to equity, social justice, and strengthening systems that support children and families." That's a lot; we can keep as prose. Responsibilities: Role Overview bullet points: Program Strategy and Oversight: - Lead the development and implementation of mission-aligned program strategies and initiatives - Collaborate with the Deputy Director and Senior Leadership to identify and pursue strategic program opportunities and partnerships - Ensure programs meet high standards of excellence and comply with relevant regulations and ethical standards - Build shared processes and cross-site workflows so families experience seamless, coordinated care - Develop systems in partnership with our Evaluation Manager for program effectiveness and ensure data-driven decision making, promoting a culture of evaluation amongst the program team - Oversee record-keeping to ensure smooth audits and regulatory compliance - Stay informed of changes to state and federal regulations, especially related to early childhood education - Identify gaps in programming and recommend solutions - Identify and mitigate risks related to program delivery, staffing, and compliance Team Leadership and Supervision: - Supervise and support program managers to foster professional growth, quality assurance, innovation and collaboration - Work with the Director of Operations & HR to recruit and retain qualified program staff - Lead a multi-generational team by providing mentorship, coaching, and clarity around expectations while honoring the organization’s culture, values, and standards. Organizational Leadership: - Collaborate with the Director of Policy and Communications on the implementation of GFS Policy Agenda - Partner with the Director of Finance to oversee program budgets and resource allocation and ensure reporting compliance for contracts - Support the Director of Development in fundraising efforts, including grant and donor reporting and programmatic compliance - Facilitating strong working relationships between program teams and support departments - Participate in collaborative work with the Si Se Puede Collective and other community partners. - Be a visible, trusted presence in the community, representing GFS at events within and outside the organization. We can combine into a single list of responsibilities (maybe with subheadings not needed). We'll just list each bullet as

. Requirements: Required Qualifications list: - Minimum 7 years of progressive program management experience, with at least 5 years in a leadership role - Experience with State of California Department of Education and CDSS contracts - Knowledge of Title V and Title 22 regulations - Demonstrated success in staff supervision, budgeting, program evaluation, and strategic planning - Experience working with diverse populations, including immigrant and Spanish-speaking communities - Strong leadership and collaboration skills - Excellent verbal and written communication skills - Deep commitment to equity, social justice, and community empowerment - Familiarity with professional development, training, and adult learning - Authorization to work in the United States (proof required upon employment) Qualifications: Preferred Qualifications list: - Master’s degree in education, child development, social work, or a related field - Bilingual in English and Spanish - Experience with grants management, fundraising, and systems change initiatives - Problem-solving mindset with a focus on continuous improvement Licenses & Certifications list: - Program Director Permit or valid Teaching Credential (preferred) - CPR/First Aid Certification and Mandated Reporter Training (within 60 days of hire) - Proof of required immunizations (TB, MMR, Tdap, Influenza) - Background check and fingerprint clearance required We could combine Licenses & Certifications into Requirements or Qualifications but better to have a separate section maybe "Qualifications" includes both preferred and licenses? But we already have Qualifications for preferred. Could rename Qualifications to "Preferred Qualifications" but heading must be from list; we can use "Qualifications". We'll put preferred qualifications there. Licenses & Certifications could be part of Requirements? But they are not exactly requirements; they are required certifications. Could include them under Requirements as well. However to avoid many sections, we could merge Licenses & Certifications into Requirements section as additional bullet points. That would keep sections: About the role, Responsibilities, Requirements (including required quals, preferred quals, licenses), Benefits, Pay, Schedule. That's 6 sections. But we need to avoid thin sections; each will have substantive content. Now Benefits: Medical, vision, and dental insurance (valued at over $6,000/year) with no employee contribution; 401(k) retirement plan with 10% employer match contribution; Paid Time Off including: Vacation days, paid holidays, sick leave, and 2 floating holidays annually (upon eligibility). Pay: Salary $130,000 - $150,000. Schedule: Work Environment: This is an in-person role based in the Grail Family Services offices in the Mayfair community of San Jose, CA. Some evening and weekend work is required, with some local travel as needed. We should not include "Core Values" maybe not needed as it's not a section heading; but could be included under About the role? It's extra but maybe we can include as part of About the role? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include core values somewhere. Could be under About the role as a paragraph? But the About the role currently is about the position. Could add a separate section "About the organization"? Not in allowed headings. Could incorporate into About the role as a paragraph after the position description. That would preserve it. Thus About the role will include both the position description and the organization background? Actually the organization background is earlier in the posting (the "Background" and "Organization" sections). That is also substantive. Should we include that? The instruction: Preserve ALL substantive information. The organization description is substantive. Where to put? Could be under About the role? But About the role is supposed to be about the role; but we could treat it as "About the organization" but not a allowed heading. However we could include it in About the role section as a preamble. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding other headings, but says use those for section headings. It might be okay to add other headings but they'd be non-standard. Safer to stick to those headings and place organization info under About the role (makes sense: about the role includes context of organization). We'll include a paragraph about GFS history, mission, etc. Thus About the role will contain: - Organization background (first paragraphs about GFS, Si Se Puede Collective overview maybe? That's also background but could be included). The Si Se Puede Collective overview is also substantive. We'll include that as part of organization description. We must not include duplicated lines. Ensure we don't repeat. Now we need to output only HTML fragment, no markdown fences. We'll produce:

About the role

... organization background ...

... position description ...

Then

Responsibilities

• ... each bullet ...

Then

Requirements

• ... required qualifications ...
• ... preferred qualifications ...
• ... licenses & certifications ...

but we need each item as separate

. Could group but better