Program Officer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when the posting has real, specific content for it. So we need to decide which sections have content.
We have:
- Mission/values description: "SBF attracts folks who care about our mission of building empathetic, resilient communities..." This is about the organization, could be "About the role"? Actually "About the role" is more about the position. The mission statement could be considered "About the organization". But we can put it under "About the role" maybe? The instruction says we can use those headings as examples; we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. We should include sections that have content: Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Also maybe "About the role" could include mission/values and position summary.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: application instructions, "Please check out our benefits page", "Please review our Job Description below, before applying", "Apply Here". Also remove EEO etc (none). Remove duplicated lines.
We need to preserve all substantive information.
Let's extract content:
Mission/values paragraph: "SBF attracts folks who care about our mission of building empathetic, resilient communities. We live our values by building trust, embracing learning, fostering innovation, creating inclusive spaces, and treating one another and our communities with respect and care. We are a consecutive winner of PCBT’s Best Places to Work in the Central Coast. We offer one of the most competitive benefit packages for similar and similarly sized organizations. Please check out our benefits page." The last sentence is application instruction? It's a suggestion to check benefits page; maybe we can keep as part of About the role? It's not boilerplate but it's a reference; we could keep but maybe it's okay. However instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Please check out our benefits page." is not exactly application instruction but could be considered navigation? Might be okay to keep? Safer to remove it as it's not substantive about the role. We'll remove.
Position Summary: "We’re seeking a Program Officer to join the Grantmaking team within our Programs Department. This position reports directly to our Director of Grantmaking and is based in Santa Barbara County."
Then "Position Summary: The Program Officer (PO) supports the Foundation’s mission and strategic priorities by managing and implementing assigned grantmaking programs serving the communities of Santa Barbara County. Reporting to the Director of Grantmaking, this role is responsible for day-to-day portfolio management, community engagement, grantmaking coordination, grantee support, and organizational learning within assigned program areas. The Program Officer manages key aspects of grantmaking for assigned portfolios, including outreach, application and review processes, proposal analysis, grant administration, grantee communication, performance monitoring, and trend tracking. Working closely with nonprofit partners, community members, applicants, grantees, and internal colleagues, the role helps ensure grantmaking practices are transparent, equitable, responsive, and informed by community needs and input. The Program Officer also serves as a primary point of contact for assigned grant programs, helping foster trust-based relationships, support clear and accessible grantmaking processes, and contribute insights that strengthen program implementation and learning across the Foundation."
That's substantive.
Specific Responsibilities: bullet list under headings: Grantmaking Implementation and Portfolio Management, Community Engagement and Grantee Relationships, Learning, Collaboration, and Organizational Support. Each bullet list.
Essential Requirements: list of requirements.
Work Environment: bullet list.
Compensation: "This exempt, full-time role is compensated at $70,000.00 – 80,000.00 annually, depending on skills and work experience."
We need Benefits section: The posting mentions "We offer one of the most competitive benefit packages for similar and similarly sized organizations." That's a statement about benefits but not specific. It's vague; we should not create Benefits section unless posting actually states them. It says "We offer one of the most competitive benefit packages..." but no specifics. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state they offer competitive benefit packages, but not details. Is that enough? It's still a statement about benefits, albeit vague. Might be considered stating benefits exist. However they also said "Please check out our benefits page." which we removed. The statement "We offer one of the most competitive benefit packages for similar and similarly sized organizations." is a claim about benefits. I'd argue we can include a Benefits section with that statement as a
. But the instruction says prefer a few substantive sections over many thin ones. This is thin but still substantive? It's a statement about benefits. I'd include Benefits section with that sentence. Pay section: we have salary range. Schedule: Not mentioned explicitly; hybrid work option may be available and employee must provide their own modem, router and internet connection. That's about work arrangement, could be considered Schedule? Not exactly schedule (hours). There's no explicit schedule like full-time, part-time, hours. The role is exempt, full-time. That's about schedule (full-time). Could include Schedule section with "Full-time, exempt position. Hybrid work option may be available; employee must provide own modem, router, and internet connection." That seems reasonable. Work Environment: we could incorporate into Schedule or maybe a separate section? Not in the list of headings but we could use "Work Environment" as a heading? The instruction only gave examples but didn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; but we could also use other headings if needed? Safer to stick to those. Work environment details could go under Schedule or maybe under About the role? But we have schedule info there. Could put work environment details under Schedule as well.
Let's structure:
About the role
SBF attracts folks who care about our mission of building empathetic, resilient communities. We live our values by building trust, embracing learning, fostering innovation, creating inclusive spaces, and treating one another and our communities with respect and care. We are a consecutive winner of PCBT’s Best Places to Work in the Central Coast.
We’re seeking a Program Officer to join the Grantmaking team within our Programs Department. This position reports directly to our Director of Grantmaking and is based in Santa Barbara County.
The Program Officer (PO) supports the Foundation’s mission and strategic priorities by managing and implementing assigned grantmaking programs serving the communities of Santa Barbara County. Reporting to the Director of Grantmaking, this role is responsible for day-to-day portfolio management, community engagement, grantmaking coordination, grantee support, and organizational learning within assigned program areas. The Program Officer manages key aspects of grantmaking for assigned portfolios, including outreach, application and review processes, proposal analysis, grant administration, grantee communication, performance monitoring, and trend tracking. Working closely with nonprofit partners, community members, applicants, grantees, and internal colleagues, the role helps ensure grantmaking practices are transparent, equitable, responsive, and informed by community needs and input. The Program Officer also serves as a primary point of contact for assigned grant programs, helping foster trust-based relationships, support clear and accessible grantmaking processes, and contribute insights that strengthen program implementation and learning across the Foundation.
Responsibilities
- Grantmaking Implementation and Portfolio Management
- Manage the implementation of assigned grant programs in coordination with the Director of Grantmaking and program staff, ensuring clear communication, responsiveness, and timely execution throughout the grant cycle.
- Coordinate all aspects of assigned grant cycles, including outreach, application support, proposal review processes, grant processing, award distribution, grantee monitoring, and report analysis, with a focus on clarity, accessibility, and timeliness for applicants and grantees.
- Support grant review processes by coordinating committees, preparing materials, and assisting with proposal evaluation and funding recommendations, incorporating community context and partner perspectives where appropriate.
- Monitor grant performance by tracking progress, reviewing reports, and supporting evaluation efforts while maintaining open communication with grantees.
- Develop and maintain working knowledge of assigned issue areas, communities, and relevant organizations to support informed and responsive grantmaking.
- Community Engagement and Grantee Relationships
- Conduct outreach in assigned program areas to understand community needs, engage a broad and diverse range of stakeholders, and incorporate community perspectives into grantmaking implementation.
- Build and maintain respectful, responsive relationships with grantees, applicants, and community partners, serving as a primary point of contact for assigned grant programs.
- Provide clear, timely, and supportive technical assistance to applicants and grantees throughout the grant lifecycle.
- Participate in community meetings, collaborative groups, and partner spaces to stay informed of local and regional developments, emerging needs, and partnership opportunities, and apply this learning to program implementation.
- Plan and coordinate community events, trainings, workshops, and site visits, and support presentations to community groups, partners, committees, and the Board.
- Learning, Collaboration, and Organizational Support
- Support the Foundation’s community engagement priorities by contributing to program activities and integrating insights from community members and partners into grantmaking implementation.
- Contribute to organizational learning by sharing insights and observations from grantmaking and community engagement activities.
- Collaborate with internal teams and departments, including Philanthropic Services and Marketing and Communications, to support alignment, transparency, and information sharing.
- Other duties as assigned.
- with headings inside li. That's okay but maybe better to keep each responsibility heading as
? Not allowed? Only h3 for section headings. Could use inside li. Acceptable. Alternatively we could separate sections: each responsibility heading as
but that would be many sections. The instruction says prefer a few substantive sections over many thin ones. So we keep one Responsibilities section with sub-bullets. Now Requirements: we have Essential Requirements list. Could be Requirements section.
Requirements
- At least 3-5 years of relevant experience in grantmaking, nonprofit programs, community engagement, or a related field
- Strong verbal and written communications skills, with the ability to communicate clearly, respectfully, and effectively with diverse audiences.
- Strong interpersonal skills and emotional intelligence, with the ability to build relationships, listen actively, and navigate complex or sensitive situations.
- Demonstrated ability to manage multiple projects and priorities, with strong organizational skills and attention to detail.
- Ability to work both independently and collaboratively in a fast-paced environment, exercising sound judgment and accountability.
- Experience supporting program implementation, project coordination, or grantmaking processes.
- Ability to assess information and use data to support decision-making, learning, and continuous improvement.
- Proficiency in Microsoft Office Suite and the ability to learn and adapt to new systems and technologies.
- Commitment to working in a collaborative, team-oriented environment, with a willingness to contribute to shared goals and support colleagues.
- Demonstrated openness to feedback, learning, and adapting approaches based on new information and perspectives.
- Knowledge of or experience working with nonprofit organizations, community-based programs, or public sector