Jobs · Project Management · California

Alameda Creek Watershed Center Programs and Operations Manager (0922) – Natural Resources and Lands Management Division (Sunol, CA) – SFPUC (167137)

Project ManagementFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About the Natural Resources and Lands Management Division", "About The Position", "Work Schedule", "Working Relationship", "Nature of Work", "Essential duties and responsibilities include but are not limited to:" with subcategories: Strategic Operations and Facility Management, Interpretation, Education, and Program Leadership, Community Engagement and Partnership Development, Staff and Volunteer Leadership, Administration and Strategic Planning. Also "Ideal Candidate And Competencies", "How To Qualify Minimum Qualifications", "Desirable Qualifications". Also "Work Schedule" is given: Tuesday through Saturday with occasional work on evenings and Sundays for special events, subject to change if necessary. Also "Pay" and "Benefits" not present, so we should not include those sections. Also "Schedule" we have a Work Schedule line; we can include a Schedule section with that content. Also "Benefits" not present, so omit. "Pay" not present, omit. We need headings using

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We can map content to these headings: "About the role" could be the description about the position (About The Position). "Responsibilities" could be the essential duties and responsibilities (the bullet lists). "Requirements" could be Minimum Qualifications. "Qualifications" maybe Desirable Qualifications? Or "Skills" could be Ideal Candidate And Competencies. But we need to follow instruction: use those headings exactly? It says: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings, but not required to use all; we should include a section only when posting has real specific content. So we can choose appropriate headings that match content. We have content: About the Natural Resources and Lands Management Division (maybe "About the role"? Actually that's about division). About The Position (role description). Work Schedule (Schedule). Essential duties and responsibilities (Responsibilities). Minimum Qualifications (Requirements). Desirable Qualifications (Qualifications or Skills). Ideal Candidate And Competencies (Skills). Also maybe "Working Relationship" and "Nature of Work" could be part of Responsibilities or separate? Could be included under Responsibilities as prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the details exactly as given, but we can format as

or

  • . For lists, we need to use
    • . For prose,

      . For headings,

      . We must not repeat the job title as a heading (the page already shows it). The job title is "Programs and Operations Manager". Not to repeat. We must not put Job ID/requisition numbers as headings; fold minor metadata into a short

      or drop it. So we can include a short paragraph with the metadata like Application Opening Date, Filing Deadline, Location, Recruitment ID, maybe the amendment notes. But we should remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes amendment notes about closing date extensions; those are procedural but maybe considered boilerplate? It's about application dates; could be considered metadata. We could include them in a short paragraph at top. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the amendment notes? They are about application dates; they are substantive for applicants. Likely we should keep them but maybe as a short paragraph. We must remove duplicated lines. There are duplicated amendment lines (two similar paragraphs). We should deduplicate. Let's extract key info: - Amendment notes: Two notes about extending closing date: 9/11/2026: extended to Sep 25, 2026. 8/31/2026: extended to Sep 9, 2026. Both say similar encouragement. We can combine into one note: "This Job Ad has been amended to extend the closing date of application submissions to September 25, 2026 (originally September 9, 2026 after an earlier amendment). If you qualify, you are encouraged to file an application as soon as possible. If you have already applied to this specific recruitment, you do not need to apply again." That's summarizing but might be considered summarizing away detail? The instruction says do NOT invent or summarize away detail. Summarizing could be considered summarizing away detail. Better to keep both notes but remove duplication? They are not identical; they have different dates and different closing dates. We could keep both as separate paragraphs. That's fine. - Application Opening Date: August 25, 2026 - Application Filing Deadline: Application filing will be open at least through September 25, 2026 at 11:59PM (PDT), and will close any time thereafter - Location: 505 Paloma Way, Sunol, CA 94586 - Recruitment ID: PBT-0922-167137/ RTF0167136-01122585 - This is a Position-Based Test conducted in accordance with CSC Rule 111A. We can include those in a short paragraph. Now sections:

      About the role

      maybe combine division description and position description? Could split: "About the Natural Resources and Lands Management Division" and "About The Position". But we only have heading "About the role". Could we use two headings? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid multiple headings; we can use those exact headings. So we could have:

      About the role

      with content about division and position.

      Responsibilities

      with essential duties and responsibilities (including subheadings maybe as

      or

      • ?). The subheadings like "Strategic Operations and Facility Management" etc are not headings per instruction; we could treat them as

        bold? But we cannot add arbitrary headings not listed? It didn't forbid other headings, but said use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those for major sections; subheadings could be

        or . Safer to keep them as

        with maybe to emphasize. But we need to use

        • for any list of duties/requirements/benefits. So we need to turn the duties into list items. The duties are grouped under categories; we could make a flat list of all duties, but that would lose grouping. However instruction: use
          • for any list of duties/requirements/benefits. It doesn't say we cannot have headings inside list? Probably we should make a list where each item is a duty; we could include subheadings as part of the item text. Thus for Responsibilities, we can create a
              with
            • items each being a duty sentence. We'll need to extract each duty bullet from the text. Let's list duties from the posting: Under "Essential duties and responsibilities include but are not limited to:" then categories: Strategic Operations and Facility Management: - Provide daily oversight of facility operations to ensure a safe, welcoming, and mission aligned visitor experience. - Lead the development and implementation of operational policies and procedures that guide facility use, visitor services, safety practices, and daily operations. - Oversee the aquarium, exhibits, grounds, and community spaces to ensure safe, high quality and consistent standards. - Direct the care, protection, and organization of collections and interpretive materials. - Oversee safety, security, and emergency preparedness efforts in alignment with SFPUC policies and regulatory requirements. - Coordinate maintenance and repairs with the facilities team and contractors, proactively identifying operational needs and improvements. Interpretation, Education, and Program Leadership: - Provide leadership for the development and delivery of interpretive, educational, and public programs that support SFPUC goals and community needs. - Establish interpretive themes related to watershed ecology, cultural and tribal history, and the Hetch Hetchy Regional Water System. - Develop program guidelines, procedures, and quality standards to ensure consistency and excellence across offerings. - Evaluate program effectiveness and develop summary reports using data and community feedback, supporting continuous improvement. - Maintain subject matter expertise in regional natural and cultural history and SFPUC systems. Community Engagement and Partnership Development: - Lead outreach, community engagement, and communications strategies that increase visibility and participation in ACWC programs. - Build and sustain partnerships with public agencies, schools, community based organizations, tribal representatives and local governments. - Represent the ACWC, the Division, and the SFPUC at public meetings, professional conferences, and community events. - Support initiatives that strengthen community relationships, advance equity, and expand access to programs and services. Staff and Volunteer Leadership: - Build and maintain staff capacity to ensure the ACWC is fully and reliably staffed for public operating hours, programs, and special events - Develop staff guidelines, volunteer protocols, and workflow procedures to support consistent operations. - Lead staff development, performance management, scheduling, and training. - Oversee volunteer recruitment, onboarding, training, and engagement programs. - Provide coaching, and support to staff and volunteers, promoting a collaborative, inclusive, and service oriented culture. Administration and Strategic Planning: - Manage budgets, contracts, procurement, and HR related processes in alignment with SFPUC policies. - Develop and maintain administrative policies and procedures that support efficient, compliant, and transparent operations. - Contribute to strategic planning and the development of long term goals, policies, and operational plans for the Division and SFPUC. - Prepare reports and performance metrics that support accountability and continuous improvement. We need to preserve all these exactly. Now Requirements: Minimum Qualifications: Education: Possession of a baccalaureate degree from an accredited college or university Experience: Five (5) years of professional work experience coordinating or directing environmental stewardship, education or related community programs in visitor services, educational programming, interpretive center operations, or community engagement; Experience managing budgets, contracts, or administrative processes and collaborating with community partners, public agencies, educators, or local governments. License: Possession of a valid and current California driver’s license. Substitution: Additional qualifying professional experience may substitute for the education requirement on a year for year basis for up to 2 years. One (1) year is equivalent to thirty (30) semester units/forty-five (45) quarter units. Note: One year of full-time employment is equivalent to 2000 hours. (2000 hours of qualifying work experience is based on a 40-hour work week.) Applicants must meet the minimum qualification requirement by the final filing date unless otherwise noted. Applicants who meet the minimum qualifications are not guaranteed to advance through all of the steps in the selection process. We need to put these as list items (
              • ) for any list of duties/requirements/benefits. So we can make a list of each requirement item. Qualifications: Desirable Qualifications (list). Let's extract: Desirable Qualifications The stated desirable qualifications may be used to identify job finalists at the end of the selection process when candidates are referred for hiring. - Supervisory experience with staff and volunteers interacting with the public. - Experience developing or implementing policies, procedures, or standard operating guidelines for community, non-profit or public facilities, such as visitor centers or education centers. - Experience supporting operations for a community facility (opening/closing, safety procedures, coordinating maintenance and repairs). - Experience representing and working within a public agency or large governmental or nonprofit organization, such as a park agency, public utility or municipal government. - Leadership experience

Similar jobs