Major Gifts Officer
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 decide which sections to include based on content.
We have:
- About Wildlife Conservation Society (WCS) (organization description). Could be "About the role"? Not exactly. Could be "About the organization". But the allowed headings list includes "About the role". However we could still use "About the role" heading for the description of the role? The posting includes "Job Summary" and "About Wildlife Conservation Society". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings where appropriate.
We have:
- Job Summary: could be part of About the role? Or maybe we treat "About the role" as a short prose summary.
- Major Responsibilities: corresponds to Responsibilities.
- Qualification Requirements: includes Job Qualifications (experience, etc.) and also Physical Demands and Workplace Conditions. Those could be under Requirements or Qualifications? The list includes Requirements and Qualifications separate. Usually Requirements are mandatory, Qualifications are preferred. But we can combine.
We have "Job Qualifications:" bullet list: 4+ years frontline fundraising experience..., ability to work independently..., excellent communication..., advanced understanding..., commitment..., passion..., BS/BA degree, valid driver's license preferred.
Also Physical Demands and Workplace Conditions: could be under Requirements? Might be considered "Requirements". But they are detailed physical demands; we could include them under a "Requirements" section as a list.
We also have "The MGO is a hybrid role..." about location/hybrid schedule. That could go under Schedule? Actually schedule is about work hours; location/hybrid could be under Schedule or maybe we could create a "Schedule" section if we have specifics: "The MGO is a hybrid role, with time spent both working at home and at WCS's New York City office at the Bronx Zoo. The MGO must be able to flexibly schedule and attend donor and prospect meetings in the greater NYC/Tri-State area with regular frequency. This role will occasionally include national or international travel. The MGO will occasionally work evenings, weekends, and/ or holidays based on donor and event schedules." That's schedule/location info. So we could create a Schedule section.
We also have Salary Range: "Salary Range 110,000-150,000". That's Pay. So we should include a Pay section.
Benefits: Not mentioned explicitly. No benefits listed. So we should not create Benefits section.
Skills: Not explicitly listed separate from qualifications; but we could include under Qualifications or Skills. The instruction says we can have Skills section if there is real specific content. There's no explicit skills list besides communication, writing, attention to detail, interpersonal skills, etc. Those could go under Skills. But we already have Qualifications covering many. To avoid thin sections, we could combine Qualifications and Skills into one section, maybe "Qualifications". But the instruction says prefer a few substantive sections over many thin ones. So we could have sections: About the role (or About Wildlife Conservation Society?), Responsibilities, Qualifications (including requirements), Pay, Schedule. Possibly also "About the organization" but not in allowed headings. Could we use "About the role" to include the organization description? The heading "About the role" is expected to contain description of the role, not the organization. But we could put the organization description under About the role? Might be okay but could be considered not accurate. However we need to preserve all substantive information; we could include a paragraph about WCS under About the role or maybe we could create a separate section not in allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. It doesn't forbid other headings, but to be safe we should stick to those. So we need to map content to those headings.
Thus we need sections:
- About the role: could include Job Summary and maybe description of role.
- Responsibilities: Major Responsibilities list.
- Qualifications: includes Job Qualifications, Physical Demands, Workplace Conditions, maybe also education.
- Pay: Salary Range.
- Schedule: Hybrid location, travel, evenings/weekends.
We could also include Requirements separate but we can combine into Qualifications.
We must not repeat job title as heading.
We must not include boilerplate like EEO etc. Remove that.
We must not include application instructions.
We must preserve all substantive information.
Let's extract substantive content:
About WCS: description of organization, mission, parks, visitors, achievements, etc. This is substantive. Where to put? Could be under About the role? Might be okay as context. But maybe better to put under About the role? The role is Major Gifts Officer; the description of WCS is not about the role but about employer. However the instruction's example headings are just examples; we could also use "About the organization" but not listed. But we could still use for any heading; they just gave examples. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but they gave examples. To be safe, we could use "About the role" for the job summary and maybe include a brief note about WCS within that paragraph. But we need to preserve all substantive info; we could include a paragraph about WCS inside About the role section.
Alternatively, we could create a section "About the organization" using About the organization. Since they didn't forbid, it's probably okay. 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 typical but not exhaustive. I'd assume it's okay to use other headings as long as they are meaningful. However to avoid risk, maybe we stick to the given headings and embed WCS description in About the role.
Let's craft:
About the role
[Job Summary] plus maybe a sentence about WCS.
But we need to include the WCS description fully. Could be multiple paragraphs.
Let's write:
About the role
As a Major Gifts Officer (MGO), you will join a team of development professionals responsible for cultivating and securing significant major gifts to support the organization's fundraising goals, contributing to and growing $160M+ in annual department revenue. Reporting to the Director, Individual Giving, you will steward gifts beginning at $25,000, with the goal of growing a portfolio focused on gifts at the $100,000+ level. This includes identifying, cultivating, and soliciting individuals, family foundations, and other philanthropic entities in support of WCS's mission, leading the entire donor relationship cycle. You will manage a high-value portfolio of donors with capacity to give at the five-, six-, and seven-figure+ levels, working directly with WCS Trustees and leadership around the world.
Wildlife Conservation Society (WCS) saves wildlife and wild places worldwide. We are the only organization that combines on‑the‑ground field conservation programs in more than 55 countries with the world's largest network of urban wildlife parks, based in New York City. WCS's five wildlife parks, led by our flagship Bronx Zoo, have educated and inspired over 425 million visitors since 1899. Each year, WCS welcomes about 3.5 million visitors to the Bronx Zoo, Central Park Zoo, Prospect Park Zoo, Queens Zoo, and New York Aquarium—opening people's eyes to the wonders of the natural world, while setting the gold standard for animal care and well being. WCS has a long track record of achieving innovative, impactful results at scale. Our scientists, veterinarians, and conservation experts have helped recover bison, tigers, gorillas, whales, coral reefs, and more. In the past century, we have helped governments create more than 430 protected areas around the world on land and sea, and we currently work with national governments and local communities to manage and monitor several hundred protected areas.
That preserves all.
Now Responsibilities:
Responsibilities
- Manage a portfolio of 150-250 high-net worth individuals, including current donors and prospects.
- Develop bespoke cultivation, solicitation, and stewardship plans for each.
- Create and execute personalized strategies to successfully cultivate, solicit, and steward each prospect to support the WCS mission at their maximum capacity.
- Demonstrate exceptional stewardship of new and established donors, including developing personalized outreach plans for individuals.
- Continually assess portfolio health and make recommendations for donor moves to the Director, Individual Giving.
- Regularly meet with donors and prospects, including introducing them to WCS, briefing them on WCS and their impact, providing tours of WCS facilities, and making funding requests.
- Develop and maintain familiarity with programmatic needs, budgets, and priorities.
- Represent WCS's mission and persuasively articulate WCS's impact and strategies.
- Strategically activate and coordinate efforts with WCS Trustees, leadership, program staff, and other colleagues to create donor cultivation and stewardship strategies. For example, actively participate in donor strategy sessions with WCS leadership and program staff.
- Help develop inspiring proposals, reports, letters, and other correspondence, working with our fundraising communications team and program experts around the world.
- Attend WCS events to support donors and prospects, such as Gala events, lectures, salons and dinners, and similar convenings. These events occasionally include evenings, weekends, and holidays.
- Propose and implement strategies to engage new prospects.
- Work with the WCS Development Research Team to develop materials required for cultivation and solicitation of prospects.
- Actively participate in team meetings and collaborate with colleagues by providing feedback and suggestions to help advance donor strategies.
- With support from Development colleagues, effectively use Salesforce to track and evaluate key performance metrics and activities.
- Maintain an up-to-date record in Salesforce for each donor and prospect and follow best practices for data hygiene.
Now Qualifications (including
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 decide which sections to include based on content. We have: - About Wildlife Conservation Society (WCS) (organization description). Could be "About the role"? Not exactly. Could be "About the organization". But the allowed headings list includes "About the role". However we could still use "About the role" heading for the description of the role? The posting includes "Job Summary" and "About Wildlife Conservation Society". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings where appropriate. We have: - Job Summary: could be part of About the role? Or maybe we treat "About the role" as a short prose summary. - Major Responsibilities: corresponds to Responsibilities. - Qualification Requirements: includes Job Qualifications (experience, etc.) and also Physical Demands and Workplace Conditions. Those could be under Requirements or Qualifications? The list includes Requirements and Qualifications separate. Usually Requirements are mandatory, Qualifications are preferred. But we can combine. We have "Job Qualifications:" bullet list: 4+ years frontline fundraising experience..., ability to work independently..., excellent communication..., advanced understanding..., commitment..., passion..., BS/BA degree, valid driver's license preferred. Also Physical Demands and Workplace Conditions: could be under Requirements? Might be considered "Requirements". But they are detailed physical demands; we could include them under a "Requirements" section as a list. We also have "The MGO is a hybrid role..." about location/hybrid schedule. That could go under Schedule? Actually schedule is about work hours; location/hybrid could be under Schedule or maybe we could create a "Schedule" section if we have specifics: "The MGO is a hybrid role, with time spent both working at home and at WCS's New York City office at the Bronx Zoo. The MGO must be able to flexibly schedule and attend donor and prospect meetings in the greater NYC/Tri-State area with regular frequency. This role will occasionally include national or international travel. The MGO will occasionally work evenings, weekends, and/ or holidays based on donor and event schedules." That's schedule/location info. So we could create a Schedule section. We also have Salary Range: "Salary Range 110,000-150,000". That's Pay. So we should include a Pay section. Benefits: Not mentioned explicitly. No benefits listed. So we should not create Benefits section. Skills: Not explicitly listed separate from qualifications; but we could include under Qualifications or Skills. The instruction says we can have Skills section if there is real specific content. There's no explicit skills list besides communication, writing, attention to detail, interpersonal skills, etc. Those could go under Skills. But we already have Qualifications covering many. To avoid thin sections, we could combine Qualifications and Skills into one section, maybe "Qualifications". But the instruction says prefer a few substantive sections over many thin ones. So we could have sections: About the role (or About Wildlife Conservation Society?), Responsibilities, Qualifications (including requirements), Pay, Schedule. Possibly also "About the organization" but not in allowed headings. Could we use "About the role" to include the organization description? The heading "About the role" is expected to contain description of the role, not the organization. But we could put the organization description under About the role? Might be okay but could be considered not accurate. However we need to preserve all substantive information; we could include a paragraph about WCS under About the role or maybe we could create a separate section not in allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. It doesn't forbid other headings, but to be safe we should stick to those. So we need to map content to those headings.
Thus we need sections:
- About the role: could include Job Summary and maybe description of role.
- Responsibilities: Major Responsibilities list.
- Qualifications: includes Job Qualifications, Physical Demands, Workplace Conditions, maybe also education.
- Pay: Salary Range.
- Schedule: Hybrid location, travel, evenings/weekends.
We could also include Requirements separate but we can combine into Qualifications.
We must not repeat job title as heading.
We must not include boilerplate like EEO etc. Remove that.
We must not include application instructions.
We must preserve all substantive information.
Let's extract substantive content:
About WCS: description of organization, mission, parks, visitors, achievements, etc. This is substantive. Where to put? Could be under About the role? Might be okay as context. But maybe better to put under About the role? The role is Major Gifts Officer; the description of WCS is not about the role but about employer. However the instruction's example headings are just examples; we could also use "About the organization" but not listed. But we could still use for any heading; they just gave examples. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but they gave examples. To be safe, we could use "About the role" for the job summary and maybe include a brief note about WCS within that paragraph. But we need to preserve all substantive info; we could include a paragraph about WCS inside About the role section.
Alternatively, we could create a section "About the organization" using About the organization. Since they didn't forbid, it's probably okay. 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 typical but not exhaustive. I'd assume it's okay to use other headings as long as they are meaningful. However to avoid risk, maybe we stick to the given headings and embed WCS description in About the role.
Let's craft:
About the role
for any heading; they just gave examples. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but they gave examples. To be safe, we could use "About the role" for the job summary and maybe include a brief note about WCS within that paragraph. But we need to preserve all substantive info; we could include a paragraph about WCS inside About the role section.
Alternatively, we could create a section "About the organization" using About the organization. Since they didn't forbid, it's probably okay. 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 typical but not exhaustive. I'd assume it's okay to use other headings as long as they are meaningful. However to avoid risk, maybe we stick to the given headings and embed WCS description in About the role.
Let's craft:
About the role
About the organization. Since they didn't forbid, it's probably okay. 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 typical but not exhaustive. I'd assume it's okay to use other headings as long as they are meaningful. However to avoid risk, maybe we stick to the given headings and embed WCS description in About the role.
Let's craft:
About the role
About the role
[Job Summary] plus maybe a sentence about WCS.
But we need to include the WCS description fully. Could be multiple paragraphs. Let's write:About the role
As a Major Gifts Officer (MGO), you will join a team of development professionals responsible for cultivating and securing significant major gifts to support the organization's fundraising goals, contributing to and growing $160M+ in annual department revenue. Reporting to the Director, Individual Giving, you will steward gifts beginning at $25,000, with the goal of growing a portfolio focused on gifts at the $100,000+ level. This includes identifying, cultivating, and soliciting individuals, family foundations, and other philanthropic entities in support of WCS's mission, leading the entire donor relationship cycle. You will manage a high-value portfolio of donors with capacity to give at the five-, six-, and seven-figure+ levels, working directly with WCS Trustees and leadership around the world.
Wildlife Conservation Society (WCS) saves wildlife and wild places worldwide. We are the only organization that combines on‑the‑ground field conservation programs in more than 55 countries with the world's largest network of urban wildlife parks, based in New York City. WCS's five wildlife parks, led by our flagship Bronx Zoo, have educated and inspired over 425 million visitors since 1899. Each year, WCS welcomes about 3.5 million visitors to the Bronx Zoo, Central Park Zoo, Prospect Park Zoo, Queens Zoo, and New York Aquarium—opening people's eyes to the wonders of the natural world, while setting the gold standard for animal care and well being. WCS has a long track record of achieving innovative, impactful results at scale. Our scientists, veterinarians, and conservation experts have helped recover bison, tigers, gorillas, whales, coral reefs, and more. In the past century, we have helped governments create more than 430 protected areas around the world on land and sea, and we currently work with national governments and local communities to manage and monitor several hundred protected areas.
That preserves all. Now Responsibilities:Responsibilities
- Manage a portfolio of 150-250 high-net worth individuals, including current donors and prospects.
- Develop bespoke cultivation, solicitation, and stewardship plans for each.
- Create and execute personalized strategies to successfully cultivate, solicit, and steward each prospect to support the WCS mission at their maximum capacity.
- Demonstrate exceptional stewardship of new and established donors, including developing personalized outreach plans for individuals.
- Continually assess portfolio health and make recommendations for donor moves to the Director, Individual Giving.
- Regularly meet with donors and prospects, including introducing them to WCS, briefing them on WCS and their impact, providing tours of WCS facilities, and making funding requests.
- Develop and maintain familiarity with programmatic needs, budgets, and priorities.
- Represent WCS's mission and persuasively articulate WCS's impact and strategies.
- Strategically activate and coordinate efforts with WCS Trustees, leadership, program staff, and other colleagues to create donor cultivation and stewardship strategies. For example, actively participate in donor strategy sessions with WCS leadership and program staff.
- Help develop inspiring proposals, reports, letters, and other correspondence, working with our fundraising communications team and program experts around the world.
- Attend WCS events to support donors and prospects, such as Gala events, lectures, salons and dinners, and similar convenings. These events occasionally include evenings, weekends, and holidays.
- Propose and implement strategies to engage new prospects.
- Work with the WCS Development Research Team to develop materials required for cultivation and solicitation of prospects.
- Actively participate in team meetings and collaborate with colleagues by providing feedback and suggestions to help advance donor strategies.
- With support from Development colleagues, effectively use Salesforce to track and evaluate key performance metrics and activities.
- Maintain an up-to-date record in Salesforce for each donor and prospect and follow best practices for data hygiene.