Director of Development Operations (Full Time, Remote)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting and produce sections.
We have:
- Position: Director of Development Operations (Full Time, Remote)
- Organization: Accelerate Change
- Reports to: VP of Development & Executive Operations, Frank Morris Lopez
- Direct Reports: Grants Manager | Development & Communications Manager
- Location: Full-time, 100% remote position in the United States (from home or co-working space) with occasional travel once every 2-3 months
- COVID-19: We take Covid-19 safety very seriously. Employees must follow our Covid safety protocols and be fully vaccinated and boosted. Accommodations are provided to the extent required by law. For employees based in the state of Florida and Texas, the COVID-19 vaccine is encouraged but not required due to Florida and Texas state laws.
- About Accelerate Change (description)
- About the Position (description)
- Here’s what you could expect to do as the Director of Development Operations (key responsibilities): list of responsibilities (bulleted)
- We’ll also look for the Director of Development Operations to: TBD. (This is placeholder; we should not include a section with TBD)
- As part of a rapidly growing organization, you’ll need to embrace change... (some prose)
- Help advance our goal of becoming an anti-racist organization... (prose)
- Serve as a resource to our networks of partners... (prose)
- Take an entrepreneurial approach... (prose)
- What We’re Looking For (section)
- Commitment to social change... (prose)
- 5+ years experience with key responsibilities: ... (list)
- Salesforce & NPSP Experience: ... (list)
- Nonprofit Financial Compliance: ... (list)
- Detail-Oriented & Results-Driven Mindset: ... (list)
- People Management Experience: ... (list)
- Solutions-Oriented Process Improvement: ... (list)
- Benefits: list of benefits (salary range, flexibility, health care, vacation, holidays, sick days, professional development funds, cell phone/internet reimbursement, need-based educational loan assistance, 401K contributions and matching, annual office closure)
- Apply To apply... (application instructions) -> remove.
- Accelerate Change is an equal opportunity employer... (EEO boilerplate) -> remove.
We need to produce sections: maybe "About the Organization", "About the Position", "Responsibilities", "Qualifications" (or "Requirements"), "Benefits". Pay is part of Benefits (salary range). Schedule maybe not explicitly stated; they mention flexibility for work and life: 40 hours each week, occasional sprints, trust schedule. That could be considered Schedule. But we should only include Schedule if posting actually states them. It does mention flexibility and schedule, so we could include a Schedule section. However they said "Prefer a few substantive sections over many thin ones." Might combine Schedule into Benefits? But Benefits section is for benefits like health care, vacation, etc. Schedule could be separate. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated (salary range). Schedule is stated (flexibility, 40 hours, occasional sprints). Benefits is stated (list). So we could have three sections: Pay, Schedule, Benefits. But they also said "Prefer a few substantive sections over many thin ones." Might be better to combine Pay and Benefits into a "Compensation & Benefits" section? But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use those headings if content exists.
We need to decide which sections to include.
We have:
- About the Organization: description of Accelerate Change.
- About the Position: description of role.
- Responsibilities: list of duties.
- Requirements/Qualifications: list of what we're looking for (experience, skills, etc.)
- Benefits: list of benefits (including salary range? Actually salary range is Pay.)
- Pay: salary range.
- Schedule: flexibility description.
We need to avoid duplication. The "What We’re Looking For" includes commitment to social change (maybe a qualification), then 5+ years experience, Salesforce & NPSP, Nonprofit Financial Compliance, Detail-Oriented & Results-Driven Mindset, People Management Experience, Solutions-Oriented Process Improvement. That's qualifications/requirements.
We also have some additional prose after "We’ll also look for the Director of Development Operations to: TBD." and then some paragraphs about embracing change, anti-racist organization, partner resource, entrepreneurial approach. Those are more like expectations or cultural fit; could be part of Responsibilities or Qualifications? They are not exactly responsibilities but more like expectations. Could be included under "Responsibilities" as additional duties? But they are not specific duties; they are more about attitude. Might be better to include them under "About the Position" or as a separate section like "Expectations". But we only have allowed headings list; we could add a custom heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those.
We could incorporate those paragraphs into "About the Position" or "Responsibilities". For simplicity, we can add them to "About the Position" as extra prose.
Thus sections:
- About the Organization (maybe heading "About the Organization" but not in list; we could use "About the role"? Actually "About the role" is for role description. "About the Organization" could be okay but not in examples. Might be safer to use "About the Organization" as a heading; they didn't forbid. But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not exhaustive. So we can use other headings like "About the Organization". However to be safe, we could use "About the Organization" as .
- About the Position (or "About the role") - we can use "About the role" heading.
- Responsibilities
- Requirements (or Qualifications) - we can use "Requirements" heading.
- Benefits
- Pay
- Schedule
We need to ensure we don't create empty sections.
Now we need to extract content.
About the Organization: The paragraph starting "Founded in 2012, Accelerate Change is a nonprofit (c3/c4) digital media lab. We work to increase civic engagement with BIPOC and low-income communities through digital media. Our programs include: Scaling emerging cultural media propertiesInvesting in established cultural media propertiesBuilding influencer networksLeading a digital media labDriving civic engagement campaigns Learn more about our theory of change, approach, and impact at https://acceleratechange.org/about/ Our team is made up of digital media innovators and operators who bring a mix of tech, business, civic engagement, and media backgrounds. Meet our team and learn more about our culture at https://acceleratechange.org/values-team/"
We need to preserve all substantive information; we can keep the URLs as plain text.
About the Position: The paragraph after "About the Position": "Accelerate Change is seeking an experienced Director of Development Operations to lead and execute on the strategic vision for the Development Operations Department, overseeing all aspects of grant management and managing and optimizing donor data and operational responsibilities. This role supports high-level fundraising and external funder communications, provides leadership to the Development Operations Department team and collaborates cross-functionally, and ensures all grant activities are compliant with rigorous audits."
Then after that, there is "Here’s what you could expect to do as the Director of Development Operations (key responsibilities):" which we will treat as Responsibilities.
But we also have additional paragraphs after the TBD section: "As part of a rapidly growing organization, you’ll need to embrace change and that your responsibilities will shift over time. Pitching in to help with the needs of your department and the overall Central Team is an important part of your role.Help advance our goal of becoming an anti-racist organization. Within your role, apply equitable work practices, challenge white supremacy, and help make our programs more inclusive. Center our understanding that multiple systems of oppression intersect with racism and be an active part of our values work.Serve as a resource to our networks of partners. Help amplify partner successes, make connections between partners and facilitate learning sharing, and offer your expertise to partners in our networks wherever it makes sense.Take an entrepreneurial approach to their work and learning new skills. In our fast-paced, unstructured environment, we love it when staff first try to figure things out on their own and then ask for help if they’re stuck.Seek out opportunities to deepen their skills on current/emerging platforms and with lean startup methodology. We take an individualized approach to growth where staff have the chance to explore and propose development opportunities that align with their interests and the team’s priorities."
We could incorporate these into About the Position or Responsibilities. Probably better to add to About the Position as extra description.
Now Responsibilities: list of bullet points after "Here’s what you could expect to do as the Director of Development Operations (key responsibilities):" Each line starts with a verb. We need to capture all.
Let's extract them:
- Lead the strategic vision for the Development Operations Department, ensuring alignment with organizational goals, strategy, and priorities.
- Oversee all aspects of grant management, including grant writing, proposal development, and grant reporting for Accelerate and incubated projects.
- Oversee and optimize all development operations, including processing donations, tracking data in Salesforce, donor and donation reporting, acknowledgment letters, fulfillment of stakeholder information requests, and other key operational responsibilities.
- Lead and execute external funder communications strategies, including email campaigns, LinkedIn presence, funder events, webinars, and production of annual reports and other donor-facing materials and communications activities.
- Support fundraising solicitation and funder relationship management led by the Executive Director and President alongside the Head of Partnerships.
- Ensure that every donor and prospect has an elevated and meaningful stewardship experience, overseeing and directly answering questions, addressing issues, and providing information to current and prospective funders.
- Provide leadership, coaching, and performance management to the Development Operations Department team to foster professional growth and accountability.
- Collaborate cross-functionally with program and finance teams to ensure all grant activities are compliant with approved budgets and project objectives.
- Provide regular updates to leadership on grant performance, compliance issues, and opportunities for improvement to the President and Executive Director as needed.
- Conduct quarterly audits of grant compliance and expenditures, ensuring strict adherence to funder guidelines and organizational policies.
- Systematically review and audit grant agreement terms to ensure organizational adherence and proactively identify and flag potential risks
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and produce sections. We have: - Position: Director of Development Operations (Full Time, Remote) - Organization: Accelerate Change - Reports to: VP of Development & Executive Operations, Frank Morris Lopez - Direct Reports: Grants Manager | Development & Communications Manager - Location: Full-time, 100% remote position in the United States (from home or co-working space) with occasional travel once every 2-3 months - COVID-19: We take Covid-19 safety very seriously. Employees must follow our Covid safety protocols and be fully vaccinated and boosted. Accommodations are provided to the extent required by law. For employees based in the state of Florida and Texas, the COVID-19 vaccine is encouraged but not required due to Florida and Texas state laws. - About Accelerate Change (description) - About the Position (description) - Here’s what you could expect to do as the Director of Development Operations (key responsibilities): list of responsibilities (bulleted) - We’ll also look for the Director of Development Operations to: TBD. (This is placeholder; we should not include a section with TBD) - As part of a rapidly growing organization, you’ll need to embrace change... (some prose) - Help advance our goal of becoming an anti-racist organization... (prose) - Serve as a resource to our networks of partners... (prose) - Take an entrepreneurial approach... (prose) - What We’re Looking For (section) - Commitment to social change... (prose) - 5+ years experience with key responsibilities: ... (list) - Salesforce & NPSP Experience: ... (list) - Nonprofit Financial Compliance: ... (list) - Detail-Oriented & Results-Driven Mindset: ... (list) - People Management Experience: ... (list) - Solutions-Oriented Process Improvement: ... (list) - Benefits: list of benefits (salary range, flexibility, health care, vacation, holidays, sick days, professional development funds, cell phone/internet reimbursement, need-based educational loan assistance, 401K contributions and matching, annual office closure) - Apply To apply... (application instructions) -> remove. - Accelerate Change is an equal opportunity employer... (EEO boilerplate) -> remove. We need to produce sections: maybe "About the Organization", "About the Position", "Responsibilities", "Qualifications" (or "Requirements"), "Benefits". Pay is part of Benefits (salary range). Schedule maybe not explicitly stated; they mention flexibility for work and life: 40 hours each week, occasional sprints, trust schedule. That could be considered Schedule. But we should only include Schedule if posting actually states them. It does mention flexibility and schedule, so we could include a Schedule section. However they said "Prefer a few substantive sections over many thin ones." Might combine Schedule into Benefits? But Benefits section is for benefits like health care, vacation, etc. Schedule could be separate. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated (salary range). Schedule is stated (flexibility, 40 hours, occasional sprints). Benefits is stated (list). So we could have three sections: Pay, Schedule, Benefits. But they also said "Prefer a few substantive sections over many thin ones." Might be better to combine Pay and Benefits into a "Compensation & Benefits" section? But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use those headings if content exists. We need to decide which sections to include. We have: - About the Organization: description of Accelerate Change. - About the Position: description of role. - Responsibilities: list of duties. - Requirements/Qualifications: list of what we're looking for (experience, skills, etc.) - Benefits: list of benefits (including salary range? Actually salary range is Pay.) - Pay: salary range. - Schedule: flexibility description. We need to avoid duplication. The "What We’re Looking For" includes commitment to social change (maybe a qualification), then 5+ years experience, Salesforce & NPSP, Nonprofit Financial Compliance, Detail-Oriented & Results-Driven Mindset, People Management Experience, Solutions-Oriented Process Improvement. That's qualifications/requirements. We also have some additional prose after "We’ll also look for the Director of Development Operations to: TBD." and then some paragraphs about embracing change, anti-racist organization, partner resource, entrepreneurial approach. Those are more like expectations or cultural fit; could be part of Responsibilities or Qualifications? They are not exactly responsibilities but more like expectations. Could be included under "Responsibilities" as additional duties? But they are not specific duties; they are more about attitude. Might be better to include them under "About the Position" or as a separate section like "Expectations". But we only have allowed headings list; we could add a custom heading? The instruction says use