Head of Operations - Volunteer Leadership Role
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.
Thus we need to decide which sections to include: About Us (maybe "About the role"? Actually "About Us" is about organization, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can use other headings if appropriate? Probably we should stick to those headings where applicable. We have "About Us" content about organization; maybe we can treat as "About the role"? But that's not exactly. Could we use "About the organization"? Not in list. Might be okay to use "About Us" as heading? The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to use those headings where content matches. We have responsibilities (What You'll Do) -> Responsibilities. We have qualifications (What We're Looking For) -> Requirements or Qualifications. Could split into Requirements and Qualifications? The posting includes experience, skills, etc. Could treat as Requirements. Also we have "About Us" maybe as a brief intro paragraph before sections; we could just put as
without heading. The instruction says 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. So we can have a leading
with the organization description (the first paragraph about Donovan's Venom). Then maybe a
About Us
? Not sure. But we can include an About the Organization
though not in list. Might be okay.
Better: Use About the Organization
for the first two paragraphs (the mission). Then Responsibilities
for What You'll Do. Then Requirements
for What We're Looking For. Then maybe Additional Notes
for the "To ensure alignment" and disclaimer? But those are like conditions; maybe we can incorporate as after sections. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine the alignment and disclaimer into a single
after the Requirements section.
We must not create Pay/Schedule/Benefits sections because not present.
We must use
- for any list of duties/requirements/benefits. So responsibilities list should be
- . Requirements list also
- . The "To ensure alignment" bullet points also list; we could make a
- for those as well, maybe under a heading like "Expectations". But we could just incorporate as
sentences? They are bullet points: "You must be able to start within 10 days", "You must complete the full application", "You must be ready to contribute immediately". Those are specific; we should preserve them. Could make a
- list under a heading like "Expectations". But we don't have a standard heading for that; maybe we can add a
Expectations
. Not in examples but acceptable? The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should try to follow the pattern. However, we could also just put them as a
with sentences separated by commas or semicolons. But that would lose the bullet structure; but still preserve info. The instruction says use
- for any list of duties/requirements/benefits. These are not duties/requirements/benefits but expectations; still a list. Safer to use
- .
Thus we could have sections: About the Organization, Responsibilities, Requirements, Expectations.
But we need to avoid too many thin sections. Expectations is just three bullets; maybe we can incorporate into Requirements as additional bullet points? They are not qualifications but conditions. Could be part of Requirements section as additional bullets. That would keep sections fewer.
Thus final sections: About the Organization (p), Responsibilities (h3 + ul), Requirements (h3 + ul). Within Requirements we include the experience/skills bullets plus the alignment bullets.
Let's extract content.
First paragraph: "The Donovan's Venom, INC. Is a non-profit 501(c)(3) tax exempt organization dedicated to taking music, art, and entertainment to those who need it the most. The Donovan's Venom, INC. Caters to no particular individual(s) yet pledges relief to impaired or deprived individuals who are in need of musical,visual, comedic, and-or any alternative forms of liberation-through fine art & entertainment. The Donovan's Venom INC. Gives its resources to individuals who don't have the means or access."
Second paragraph: "About Us The Donovan’s Venom is a 501(c)(3) nonprofit organization focused on creating universal accessibility to fine arts and music education for all. We are passionately dedicated to ensuring that everyone, regardless of financial circumstances, has access to high-quality music education, performance opportunities, and fine art. We aim to inspire, empower, and uplift communities by fostering a love for music and the arts through our commitment to education, inclusivity, diversity, and social impact, which drives us to continually expand our reach and enrich the lives of those we serve."
We could combine these into a single
about the organization.
Then responsibilities: list each bullet:
- Partner with the Chief Operating Officer to execute the organization’s operational strategy and priorities.
- Lead day-to-day operational initiatives and translate executive priorities into structured, actionable plans.
- Develop, document, implement, and continuously improve organizational processes, workflows, and standard operating procedures.
- Coordinate cross-functional execution across teams and departments.
- Establish systems for tracking operational priorities, deliverables, risks, dependencies, and outcomes.
- Identify operational gaps, inefficiencies, and execution risks and recommend scalable solutions.
- Support resource planning, organizational readiness, and capacity management.
- Partner with functional leaders to improve communication, accountability, and execution across the organization.
- Monitor operational performance and provide regular updates and recommendations to the Chief Operating Officer.
- Escalate key risks, blockers, and decisions requiring executive leadership support.
- Support the implementation and adoption of operational systems and tools.
- Help ensure the organization’s operational infrastructure can effectively scale alongside future growth.
These are all duties.
Then requirements/qualifications: list:
- Experience in operations, business operations, program management, project management, or a related leadership role.
- Demonstrated ability to lead complex, cross-functional initiatives.
- Strong understanding of operational planning, process improvement, and organizational effectiveness.
- Excellent project and program management skills.
- Ability to translate high-level organizational priorities into structured execution plans.
- Strong leadership, communication, and stakeholder-management skills.
- Ability to identify risks, solve problems, and drive initiatives toward completion.
- Ability to operate effectively in a fast-paced and evolving organization.
- Experience in nonprofit, startup, education, technology, or mission-driven organizations is a plus.
- Bachelor’s degree or equivalent professional experience preferred.
Then alignment bullets:
- You must be able to start within 10 days
- You must complete the full application
- You must be ready to contribute immediately
Disclaimer: "Important Disclaimer This is a volunteer role. We are onboarding individuals who are ready to contribute immediately. Please only apply if you are prepared to begin within the next 10 days."
We could incorporate disclaimer as a
after the list.
We must not include application instructions; but the disclaimer includes "Please only apply if you are prepared to begin within the next 10 days." That's application instruction? It's a condition; but it's also similar to alignment bullets. Might be considered boilerplate? It's not EEO etc. It's specific to volunteer role. Probably we should keep it as it's substantive about volunteer nature. However, the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The disclaimer includes "Please only apply if you are prepared to begin within the next 10 days." That's application instruction. Might be considered application instruction. But also it's about volunteer role. The earlier alignment bullets already say must be able to start within 10 days, must complete full application, must be ready to contribute immediately. The disclaimer repeats that. So we could drop the disclaimer as duplicated lines. The alignment bullets already cover that. So we can omit the disclaimer.
Thus final HTML:
[organization description]
Responsibilities
- ...
...
Requirements
- ...
...
- You must be able to start within 10 days
- You must complete the full application
- You must be ready to contribute immediately
We need to ensure we didn't miss any substantive info: The first paragraph about Donovan's Venom includes repeated sentences; we should preserve all. Combine them into a single paragraph maybe with some repetition but that's okay.
Let's craft the organization paragraph: Combine both paragraphs.
"The Donovan's Venom, INC. Is a non-profit 501(c)(3) tax exempt organization dedicated to taking music, art, and entertainment to those who need it the most. The Donovan's Venom, INC. Caters to no particular individual(s) yet pledges relief to impaired or deprived individuals who are in need of musical, visual, comedic, and-or any alternative forms of liberation-through fine art & entertainment. The Donovan's Venom INC. Gives its resources to individuals who don't have the means or access. The Donovan’s Venom is a 501(c)(3) nonprofit organization focused on creating universal accessibility to fine arts and music education for all. We are passionately dedicated to ensuring that everyone, regardless of financial circumstances, has access to high-quality music education, performance opportunities, and fine art. We aim to inspire, empower, and uplift communities by fostering a love for music and the arts through our commitment to education, inclusivity, diversity, and social impact, which drives us to continually expand our reach and enrich the lives of those we serve
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. Thus we need to decide which sections to include: About Us (maybe "About the role"? Actually "About Us" is about organization, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can use other headings if appropriate? Probably we should stick to those headings where applicable. We have "About Us" content about organization; maybe we can treat as "About the role"? But that's not exactly. Could we use "About the organization"? Not in list. Might be okay to use "About Us" as heading? The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to use those headings where content matches. We have responsibilities (What You'll Do) -> Responsibilities. We have qualifications (What We're Looking For) -> Requirements or Qualifications. Could split into Requirements and Qualifications? The posting includes experience, skills, etc. Could treat as Requirements. Also we have "About Us" maybe as a brief intro paragraph before sections; we could just put as
without heading. The instruction says 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. So we can have a leading
with the organization description (the first paragraph about Donovan's Venom). Then maybe a
About Us
? Not sure. But we can include anAbout the Organization
though not in list. Might be okay. Better: UseAbout the Organization
for the first two paragraphs (the mission). ThenResponsibilities
for What You'll Do. ThenRequirements
for What We're Looking For. Then maybeAdditional Notes
for the "To ensure alignment" and disclaimer? But those are like conditions; maybe we can incorporate asafter sections. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine the alignment and disclaimer into a single
after the Requirements section. We must not create Pay/Schedule/Benefits sections because not present. We must use
- for any list of duties/requirements/benefits. So responsibilities list should be
- . Requirements list also
- . The "To ensure alignment" bullet points also list; we could make a
- for those as well, maybe under a heading like "Expectations". But we could just incorporate as
sentences? They are bullet points: "You must be able to start within 10 days", "You must complete the full application", "You must be ready to contribute immediately". Those are specific; we should preserve them. Could make a
- list under a heading like "Expectations". But we don't have a standard heading for that; maybe we can add a
Expectations
. Not in examples but acceptable? The instruction says usefor section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should try to follow the pattern. However, we could also just put them as a
with sentences separated by commas or semicolons. But that would lose the bullet structure; but still preserve info. The instruction says use
- for any list of duties/requirements/benefits. These are not duties/requirements/benefits but expectations; still a list. Safer to use
- .
Thus we could have sections: About the Organization, Responsibilities, Requirements, Expectations.
But we need to avoid too many thin sections. Expectations is just three bullets; maybe we can incorporate into Requirements as additional bullet points? They are not qualifications but conditions. Could be part of Requirements section as additional bullets. That would keep sections fewer.
Thus final sections: About the Organization (p), Responsibilities (h3 + ul), Requirements (h3 + ul). Within Requirements we include the experience/skills bullets plus the alignment bullets.
Let's extract content.
First paragraph: "The Donovan's Venom, INC. Is a non-profit 501(c)(3) tax exempt organization dedicated to taking music, art, and entertainment to those who need it the most. The Donovan's Venom, INC. Caters to no particular individual(s) yet pledges relief to impaired or deprived individuals who are in need of musical,visual, comedic, and-or any alternative forms of liberation-through fine art & entertainment. The Donovan's Venom INC. Gives its resources to individuals who don't have the means or access."
Second paragraph: "About Us The Donovan’s Venom is a 501(c)(3) nonprofit organization focused on creating universal accessibility to fine arts and music education for all. We are passionately dedicated to ensuring that everyone, regardless of financial circumstances, has access to high-quality music education, performance opportunities, and fine art. We aim to inspire, empower, and uplift communities by fostering a love for music and the arts through our commitment to education, inclusivity, diversity, and social impact, which drives us to continually expand our reach and enrich the lives of those we serve."
We could combine these into a single
about the organization. Then responsibilities: list each bullet: - Partner with the Chief Operating Officer to execute the organization’s operational strategy and priorities. - Lead day-to-day operational initiatives and translate executive priorities into structured, actionable plans. - Develop, document, implement, and continuously improve organizational processes, workflows, and standard operating procedures. - Coordinate cross-functional execution across teams and departments. - Establish systems for tracking operational priorities, deliverables, risks, dependencies, and outcomes. - Identify operational gaps, inefficiencies, and execution risks and recommend scalable solutions. - Support resource planning, organizational readiness, and capacity management. - Partner with functional leaders to improve communication, accountability, and execution across the organization. - Monitor operational performance and provide regular updates and recommendations to the Chief Operating Officer. - Escalate key risks, blockers, and decisions requiring executive leadership support. - Support the implementation and adoption of operational systems and tools. - Help ensure the organization’s operational infrastructure can effectively scale alongside future growth. These are all duties. Then requirements/qualifications: list: - Experience in operations, business operations, program management, project management, or a related leadership role. - Demonstrated ability to lead complex, cross-functional initiatives. - Strong understanding of operational planning, process improvement, and organizational effectiveness. - Excellent project and program management skills. - Ability to translate high-level organizational priorities into structured execution plans. - Strong leadership, communication, and stakeholder-management skills. - Ability to identify risks, solve problems, and drive initiatives toward completion. - Ability to operate effectively in a fast-paced and evolving organization. - Experience in nonprofit, startup, education, technology, or mission-driven organizations is a plus. - Bachelor’s degree or equivalent professional experience preferred. Then alignment bullets: - You must be able to start within 10 days - You must complete the full application - You must be ready to contribute immediately Disclaimer: "Important Disclaimer This is a volunteer role. We are onboarding individuals who are ready to contribute immediately. Please only apply if you are prepared to begin within the next 10 days." We could incorporate disclaimer as a
after the list. We must not include application instructions; but the disclaimer includes "Please only apply if you are prepared to begin within the next 10 days." That's application instruction? It's a condition; but it's also similar to alignment bullets. Might be considered boilerplate? It's not EEO etc. It's specific to volunteer role. Probably we should keep it as it's substantive about volunteer nature. However, the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The disclaimer includes "Please only apply if you are prepared to begin within the next 10 days." That's application instruction. Might be considered application instruction. But also it's about volunteer role. The earlier alignment bullets already say must be able to start within 10 days, must complete full application, must be ready to contribute immediately. The disclaimer repeats that. So we could drop the disclaimer as duplicated lines. The alignment bullets already cover that. So we can omit the disclaimer. Thus final HTML:
[organization description]
Responsibilities
- ... ...
Requirements
- ... ...
- You must be able to start within 10 days
- You must complete the full application
- You must be ready to contribute immediately
- .
Thus we could have sections: About the Organization, Responsibilities, Requirements, Expectations.
But we need to avoid too many thin sections. Expectations is just three bullets; maybe we can incorporate into Requirements as additional bullet points? They are not qualifications but conditions. Could be part of Requirements section as additional bullets. That would keep sections fewer.
Thus final sections: About the Organization (p), Responsibilities (h3 + ul), Requirements (h3 + ul). Within Requirements we include the experience/skills bullets plus the alignment bullets.
Let's extract content.
First paragraph: "The Donovan's Venom, INC. Is a non-profit 501(c)(3) tax exempt organization dedicated to taking music, art, and entertainment to those who need it the most. The Donovan's Venom, INC. Caters to no particular individual(s) yet pledges relief to impaired or deprived individuals who are in need of musical,visual, comedic, and-or any alternative forms of liberation-through fine art & entertainment. The Donovan's Venom INC. Gives its resources to individuals who don't have the means or access."
Second paragraph: "About Us The Donovan’s Venom is a 501(c)(3) nonprofit organization focused on creating universal accessibility to fine arts and music education for all. We are passionately dedicated to ensuring that everyone, regardless of financial circumstances, has access to high-quality music education, performance opportunities, and fine art. We aim to inspire, empower, and uplift communities by fostering a love for music and the arts through our commitment to education, inclusivity, diversity, and social impact, which drives us to continually expand our reach and enrich the lives of those we serve."
We could combine these into a single
- for any list of duties/requirements/benefits. These are not duties/requirements/benefits but expectations; still a list. Safer to use
- list under a heading like "Expectations". But we don't have a standard heading for that; maybe we can add a
- for those as well, maybe under a heading like "Expectations". But we could just incorporate as
- . The "To ensure alignment" bullet points also list; we could make a
- . Requirements list also