Partnerships & Ecosystem Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content.
We have:
- Responsibilities: "What you’ll do:" and "What success looks like in this role:" maybe combine.
- Requirements: language fluency, work authorization, location preference, etc.
- Qualifications: "What you bring:" list.
- Skills: maybe subset of qualifications? Could combine.
- Benefits: health coverage, retirement benefits, paid sick leave, vacation, holidays.
- Pay: salary range $115,000-$125,000.
- Schedule: "Flexible hours possible with core hours as a base. 40 hours per week, exempt."
Also we have "Work Capacity: Full-time" and location info.
We must not create sections with filler like "not specified". So include only those with real content.
We must not repeat job title as heading. So no heading for Partnerships & Ecosystem Manager.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove boilerplate: EEO statements, equal opportunity, etc. Also remove "We understand that strong candidates may not meet every qualification listed." That's maybe not boilerplate but it's encouraging to apply; could be considered filler? It's not a substantive requirement; but it's part of the posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The line "We understand that strong candidates may not meet every qualification listed. If you believe your experience and perspective would make you a good fit for this role, we encourage you apply." That's basically an encouragement to apply, maybe considered application instruction? It's not exactly instruction but it's encouraging to apply. Might be considered boilerplate? Safer to remove it as it's not substantive detail about role. Also "The ARLA team is small, collaborative, and relational..." that's culture description; could be considered substantive? It's about team environment. Might be kept under About the role or maybe a separate section? Not listed as a standard heading; we could include under About the role as prose.
We need to decide sections:
- About the role: Could include description of ARLA and role purpose. The "About ARLA" paragraph plus maybe the mission. Also the "What success looks like" maybe part of responsibilities.
Better to follow typical job posting sections: About the role (overview), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for:
About the role: Could combine "About ARLA" and maybe the role purpose: "We are seeking a highly organized, strategic, and relationship-oriented Partnerships & Ecosystem Manager to serve as the primary steward of ARLA’s partner ecosystem and the Living Infrastructure Field Kit in collaboration with Spherical LLC." That's about role.
Responsibilities: The bullet list under "What you’ll do:" plus maybe the success metrics? But success metrics could be separate but we can include under Responsibilities as they describe expected outcomes.
Requirements: Language fluency (English and Spanish), work authorization (US authorized, no visa sponsorship), location preference (LA County-based, familiarity), maybe also "Work from home; frequent travel within Los Angeles County expected". Also "Full-time". Also "Reports to: Interim Executive Director". Also "Additional requirements:" maybe.
Qualifications: The "What you bring:" list: 7+ years experience in partnership and ecosystem stewardship, passion for climate and community resilience, environmental justice, equity, highly organized, detail-oriented, project management, knowledge about LA region, exceptional interpersonal skills, written/verbal communication, collaborative, experience setting up and managing CRM systems, understanding privacy/data protection, experience developing and implementing growth and partnership strategies, experience with document management systems, video conferencing, project management systems, other online platforms (Google Workspace and Zoom preferred), comfort working independently in mostly remote environment, ability to take initiative and direction, ability to uphold strict confidentiality.
Skills: Could be overlapping with qualifications; maybe we can treat some as skills: CRM, project management, communication, etc. But we might just put them under Qualifications and not create a separate Skills section if it would be thin. However instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section? But headings are predefined; we can omit Skills if not enough distinct content. However we have many skill-like items; maybe we can create Skills section for technical skills: CRM systems, document management, video conferencing, project management, Google Workspace, Zoom. But that would split the qualifications list. Might be okay.
But we need to preserve all substantive info; we can split but ensure not to duplicate.
Better: Have Qualifications section for experience and attributes, Skills section for technical/tools skills.
Let's extract:
Qualifications (experience/attributes):
- 7+ years of experience in partnership and ecosystem stewardship
- Passion for climate and community resilience, environmental justice, and equity
- Highly organized, detail-oriented, and great at project management
- Knowledge about the Los Angeles region and passion for the people and places of Los Angeles
- Exceptional interpersonal skills, with strong written and verbal communication skills, and a collaborative and team-oriented perspective; you resonate with our engagement principles and uphold ARLA’s relationship-based approach to philanthropy and partnerships
- Experience setting up and managing CRM systems, with an understanding of privacy and data protection and stewardship issues
- Experience developing and implementing growth and partnership strategies
- Comfort working independently in a mostly remote environment, with the ability to both take initiative and take direction
- Ability to uphold a strict level of confidentiality
Skills (tools/platforms):
- Experience with document management systems, video conferencing services, project management systems, and other online platforms used by the ARLA team (experience with Google Workspace and Zoom preferred)
We could also include "Experience setting up and managing CRM systems" already in qualifications; but we could move to skills. To avoid duplication, maybe keep CRM experience in qualifications and skills separate for other tools.
But we need to ensure we don't lose any info. Let's decide:
Qualifications: experience, passion, organized, knowledge LA, interpersonal skills, CRM experience, growth strategy experience, remote work comfort, confidentiality.
Skills: document management, video conferencing, project management systems, Google Workspace, Zoom.
Now Benefits: health coverage, retirement benefits, paid sick leave, vacation, holidays.
Pay: salary range $115,000-$125,000 annually, depending on skills and experience.
Schedule: Flexible hours possible with core hours as a base. 40 hours per week, exempt.
Also we have location and work arrangement: "Location:Los Angeles County-basedWork from home; frequent travel within Los Angeles County expectedARLA has a preference for candidates who are already based in and familiar with the Los Angeles area." This could be part of Requirements or About the role. We'll put under Requirements.
Also "Reports to: Interim Executive Director" and "Work Capacity: Full-time" and "Compensation: $115,000-$125,000, depending on skills and experience" (but we already have Pay). We'll include Reports to maybe under About the role? Could be a metadata; but instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include Reports to and Work Capacity in a short paragraph under About the role or maybe a separate meta paragraph. But we have a section for About the role; we can include that info there.
We must not repeat job title as heading.
Now we need to output HTML fragment with headings
and content.
We must not include any markdown fences.
Let's craft:
About the role
Reports to: Interim Executive Director. Work capacity: Full-time. ARLA Accelerate Resilience L.A. (ARLA), a sponsored project of Rockefeller Philanthropy Advisors, is a small nonprofit project dedicated to regenerating living systems in service of community resilience in the Los Angeles region and its source watersheds. We are seeking a highly organized, strategic, and relationship-oriented Partnerships & Ecosystem Manager to serve as the primary steward of ARLA’s partner ecosystem and the Living Infrastructure Field Kit in collaboration with Spherical LLC.
Responsibilities
- Nurture and steward relationships with partners across the ARLA ecosystem through partner events, site visits, community meetings, and public forums – in person and virtually – to identify opportunities for collaboration and strengthen connections across ARLA’s network.
- Set up and maintain a clear system (CRM) for understanding partner relationships across ARLA’s ecosystem, documenting partner engagement, collaboration opportunities, Living Infrastructure Field Kit use and other touchpoints that help ARLA see how its network is evolving.
- Synthesize and communicate insights from partner engagement, user experiences, and field work to ensure that on-the-ground learnings inform overall ARLA program integration, strategy, and cross-team alignment.
- Contribute to ARLA’s strategy development for enabling partners and their beneficiaries to advance a living infrastructure approach across LA County and its source watersheds.
- Help develop and enact a Field Kit audience and participation growth strategy that is nested within ARLA’s broader ecosystem growth and partnership strategy.
- Use insights from partner engagement to understand who is using the Living Infrastructure Field Kit, identify gaps and opportunities across audiences and sectors, and inform efforts to grow and support the Field Kit community.
- Together with the Senior Manager of Planning &
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO statements, equal opportunity, etc. Also remove "We understand that strong candidates may not meet every qualification listed." That's maybe not boilerplate but it's encouraging to apply; could be considered filler? It's not a substantive requirement; but it's part of the posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The line "We understand that strong candidates may not meet every qualification listed. If you believe your experience and perspective would make you a good fit for this role, we encourage you apply." That's basically an encouragement to apply, maybe considered application instruction? It's not exactly instruction but it's encouraging to apply. Might be considered boilerplate? Safer to remove it as it's not substantive detail about role. Also "The ARLA team is small, collaborative, and relational..." that's culture description; could be considered substantive? It's about team environment. Might be kept under About the role or maybe a separate section? Not listed as a standard heading; we could include under About the role as prose. We need to decide sections: - About the role: Could include description of ARLA and role purpose. The "About ARLA" paragraph plus maybe the mission. Also the "What success looks like" maybe part of responsibilities. Better to follow typical job posting sections: About the role (overview), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: About the role: Could combine "About ARLA" and maybe the role purpose: "We are seeking a highly organized, strategic, and relationship-oriented Partnerships & Ecosystem Manager to serve as the primary steward of ARLA’s partner ecosystem and the Living Infrastructure Field Kit in collaboration with Spherical LLC." That's about role. Responsibilities: The bullet list under "What you’ll do:" plus maybe the success metrics? But success metrics could be separate but we can include under Responsibilities as they describe expected outcomes. Requirements: Language fluency (English and Spanish), work authorization (US authorized, no visa sponsorship), location preference (LA County-based, familiarity), maybe also "Work from home; frequent travel within Los Angeles County expected". Also "Full-time". Also "Reports to: Interim Executive Director". Also "Additional requirements:" maybe. Qualifications: The "What you bring:" list: 7+ years experience in partnership and ecosystem stewardship, passion for climate and community resilience, environmental justice, equity, highly organized, detail-oriented, project management, knowledge about LA region, exceptional interpersonal skills, written/verbal communication, collaborative, experience setting up and managing CRM systems, understanding privacy/data protection, experience developing and implementing growth and partnership strategies, experience with document management systems, video conferencing, project management systems, other online platforms (Google Workspace and Zoom preferred), comfort working independently in mostly remote environment, ability to take initiative and direction, ability to uphold strict confidentiality. Skills: Could be overlapping with qualifications; maybe we can treat some as skills: CRM, project management, communication, etc. But we might just put them under Qualifications and not create a separate Skills section if it would be thin. However instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section? But headings are predefined; we can omit Skills if not enough distinct content. However we have many skill-like items; maybe we can create Skills section for technical skills: CRM systems, document management, video conferencing, project management, Google Workspace, Zoom. But that would split the qualifications list. Might be okay. But we need to preserve all substantive info; we can split but ensure not to duplicate. Better: Have Qualifications section for experience and attributes, Skills section for technical/tools skills. Let's extract: Qualifications (experience/attributes): - 7+ years of experience in partnership and ecosystem stewardship - Passion for climate and community resilience, environmental justice, and equity - Highly organized, detail-oriented, and great at project management - Knowledge about the Los Angeles region and passion for the people and places of Los Angeles - Exceptional interpersonal skills, with strong written and verbal communication skills, and a collaborative and team-oriented perspective; you resonate with our engagement principles and uphold ARLA’s relationship-based approach to philanthropy and partnerships - Experience setting up and managing CRM systems, with an understanding of privacy and data protection and stewardship issues - Experience developing and implementing growth and partnership strategies - Comfort working independently in a mostly remote environment, with the ability to both take initiative and take direction - Ability to uphold a strict level of confidentiality Skills (tools/platforms): - Experience with document management systems, video conferencing services, project management systems, and other online platforms used by the ARLA team (experience with Google Workspace and Zoom preferred) We could also include "Experience setting up and managing CRM systems" already in qualifications; but we could move to skills. To avoid duplication, maybe keep CRM experience in qualifications and skills separate for other tools. But we need to ensure we don't lose any info. Let's decide: Qualifications: experience, passion, organized, knowledge LA, interpersonal skills, CRM experience, growth strategy experience, remote work comfort, confidentiality. Skills: document management, video conferencing, project management systems, Google Workspace, Zoom. Now Benefits: health coverage, retirement benefits, paid sick leave, vacation, holidays. Pay: salary range $115,000-$125,000 annually, depending on skills and experience. Schedule: Flexible hours possible with core hours as a base. 40 hours per week, exempt. Also we have location and work arrangement: "Location:Los Angeles County-basedWork from home; frequent travel within Los Angeles County expectedARLA has a preference for candidates who are already based in and familiar with the Los Angeles area." This could be part of Requirements or About the role. We'll put under Requirements. Also "Reports to: Interim Executive Director" and "Work Capacity: Full-time" and "Compensation: $115,000-$125,000, depending on skills and experience" (but we already have Pay). We'll include Reports to maybe under About the role? Could be a metadata; but instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include Reports to and Work Capacity in a short paragraph under About the role or maybe a separate meta paragraph. But we have a section for About the role; we can include that info there. We must not repeat job title as heading. Now we need to output HTML fragment with headings
and content.
We must not include any markdown fences.
Let's craft:
About the role
Reports to: Interim Executive Director. Work capacity: Full-time. ARLA Accelerate Resilience L.A. (ARLA), a sponsored project of Rockefeller Philanthropy Advisors, is a small nonprofit project dedicated to regenerating living systems in service of community resilience in the Los Angeles region and its source watersheds. We are seeking a highly organized, strategic, and relationship-oriented Partnerships & Ecosystem Manager to serve as the primary steward of ARLA’s partner ecosystem and the Living Infrastructure Field Kit in collaboration with Spherical LLC.
Responsibilities
- Nurture and steward relationships with partners across the ARLA ecosystem through partner events, site visits, community meetings, and public forums – in person and virtually – to identify opportunities for collaboration and strengthen connections across ARLA’s network.
- Set up and maintain a clear system (CRM) for understanding partner relationships across ARLA’s ecosystem, documenting partner engagement, collaboration opportunities, Living Infrastructure Field Kit use and other touchpoints that help ARLA see how its network is evolving.
- Synthesize and communicate insights from partner engagement, user experiences, and field work to ensure that on-the-ground learnings inform overall ARLA program integration, strategy, and cross-team alignment.
- Contribute to ARLA’s strategy development for enabling partners and their beneficiaries to advance a living infrastructure approach across LA County and its source watersheds.
- Help develop and enact a Field Kit audience and participation growth strategy that is nested within ARLA’s broader ecosystem growth and partnership strategy.
- Use insights from partner engagement to understand who is using the Living Infrastructure Field Kit, identify gaps and opportunities across audiences and sectors, and inform efforts to grow and support the Field Kit community.
- Together with the Senior Manager of Planning &