Major Gift Officer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to parse the posting. First, "Who We Are" is about organization. Could be "About the role"? Actually "About the role" is typical heading for description of role. The "Who We Are" could be considered "About the organization". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We have: - Posting Information: Salary Rate: $122,500-$143,500 (Senior Major Gift Officer), $96,250-$123,750 (Major Gift Officer). Also note about placement ranges. Hours per week: 40. Job Classification: Full-time, exempt. Job Type: Hybrid. Location: Massachusetts. Thus Pay: we have salary ranges. Schedule: Hours per week 40, maybe also mention hybrid? But schedule heading is for schedule info; we can include Hours per week: 40, Hybrid? Actually schedule could be "Hours per week: 40". Hybrid is location type maybe not schedule. We'll include schedule as Hours per week: 40. Benefits: we have a list: Sick time, Vacation time, Holiday time, Health insurance, Short-Term and Long-Term Disability Insurance, Massachusetts Paid Family Medical Leave, Life Insurance, 401k with 5% match after 1 year, Employee Assistance Program, Reciprocity (free/discounted admission to museums), Discounts (free entry to Trustees properties, discount event tickets, discounted merchandise), Day of Wonder, Day of Service. Also maybe mention "Equal Opportunity and Diversity" but that's not benefit. We need to output Benefits section with

• items. Responsibilities: The "What You'll Do" and "The Role" and bullet list starting with "Specifically, you'll:" includes many duties. So we can put Responsibilities section with those bullet points. Requirements: The "Requirements What You'll Need: Skills and Experience:" includes required and preferred. Could split into Requirements and Qualifications? The instructions list both Requirements and Qualifications as possible headings. We need to decide what goes where. Typically Requirements = mandatory, Qualifications = preferred or education etc. We'll put required items under Requirements, preferred under Qualifications. Skills: maybe separate Skills section for skills like "Articulate, strategic..." but those are also under requirements. Could combine. But we have separate Skills heading possible. We could put skills under Skills section. However we already have Requirements and Qualifications; maybe we can put required experience under Requirements, and skills under Skills, and preferred under Qualifications. Let's parse. Required: - 8-10+ years of fundraising experience with demonstrated success in major gifts, annual fund, and/or planned giving solicitations - Proven front-line fundraiser with experience building and managing a donor portfolio and a track record of securing five- and six-figure gifts - Articulate, strategic, solution-oriented and entrepreneurial with a strong ability to listen, write, and speak effectively - Highly motivated self-starter who thrives in a fast-paced environment and takes pride in exceptional preparation for every donor interaction - Strong collaboration skills with the ability to work seamlessly across teams and communicate effectively at multiple levels of an organization - Excellent strategic thinking and analytical skills - Proficiency with Salesforce or a comparable CRM system - Bachelor's degree or equivalent experience Preferred: - Experience in conservation, land stewardship, environmental, or cultural preservation organizations - Familiarity with planned giving and legacy gift solicitation - An understanding of philanthropic communities in specific regions of Massachusetts - Strong creative event planning skills and experience building host committees or donor engagement programming Eligibility Criteria: - Current authorization to work in the United States - A satisfactory criminal background (CORI) check. - Encouragement to apply even if missing some skills. We could put eligibility under Requirements maybe as separate bullet. But we need to avoid boilerplate like EEO etc. We'll remove Equal Opportunity and Diversity section. Now "About the role": maybe we can include a brief paragraph summarizing the role from "Who We Are"? Actually "Who We Are" is about organization, not role. The role description is in "What You'll Do:" and "The Role:" etc. So we could put a short paragraph under About the role summarizing the purpose: The Trustees is ... As a Major Gift Officer, you will be on front lines building donor relationships... That content is present in "Your Impact:" and "The Role:" paragraphs. We could extract a summary for About the role. But we must not repeat job title as heading. Already we have heading

  About the role

  . Then we can put a

  with that summary. We need to preserve all substantive information; do not invent or summarize away detail. However we can condense but must preserve details. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we need to keep all details. So we cannot summarize away details; we need to include all details. That means we need to include the bullet points etc. So we need to include all details in appropriate sections. Thus we need to include all details from the posting, organized under headings. We can have multiple sections: About the role (maybe a brief paragraph summarizing the role but we must keep details; maybe we can put the "Your Impact:" and "The Role:" paragraphs there as prose, and then Responsibilities as bullet list of specific duties. However that would duplicate content. Better to follow typical pattern: About the role = overview paragraph; Responsibilities = bullet list of duties; Requirements = mandatory; Qualifications = preferred; Skills maybe not needed if we covered; Benefits; Pay; Schedule. We must ensure we don't lose any detail. Let's map: Overview paragraphs: - "Who We Are:" (organization description) could be part of About the role? Actually it's about the organization, not role. But we could include it under About the role as context. It's substantive. - "Your Impact:" paragraph: describes transformational chapter, campaign, etc. - "The Role:" paragraph: describes managing portfolio, etc. We could combine these into About the role section as multiple paragraphs. Then Responsibilities: the bullet list starting with "Specifically, you'll:" includes many duties. We'll put each as

• . Requirements: required items (8-10+ years experience, proven front-line fundraiser, articulate..., highly motivated..., strong collaboration..., excellent strategic thinking..., proficiency with Salesforce, bachelor's degree). Also eligibility criteria (work authorization, CORI check). Could also include "Current authorization to work in the United States - a candidate must have such authorization by his or her first day of employment." and "A satisfactory criminal background (CORI) check." We'll include those. Qualifications: preferred items (experience in conservation..., familiarity with planned giving..., understanding of philanthropic communities..., strong creative event planning skills...). Also maybe "Don't quite have all the skills..." but that's encouragement, not a qualification. Skills: maybe we could separate skills like "Articulate, strategic..." but those are already in requirements. Could omit Skills section to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we can combine skills into Requirements. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to format. Pay: we have salary ranges and placement note. We'll include both ranges and note about placement for new employees. Schedule: Hours per week: 40, Hybrid? Actually schedule heading maybe just hours. We'll include "Hours per week: 40" and maybe note "Hybrid" as work arrangement but that's location type. Could include under Schedule: "Hybrid work arrangement (some remote, some on-site)". But the posting says Job Type: Hybrid Location: Massachusetts. So we could put under Schedule: "Hybrid (remote and on-site) – 40 hours per week". That's substantive. Now Benefits: list all benefits. Let's extract benefits list exactly: - Sick time: 120 hours per year - Vacation time: 20 days per year (prorated) - Holiday time: 12 set holidays, 3 floating - Health insurance: You are eligible to participate in the Trustees health insurance benefit via Blue Cross Blue Shield (BCBS). BCBS also offers additional benefits, such as fitness reimbursement and rewards for healthy habits. - Short-Term and Long-Term Disability Insurance - Massachusetts Paid Family Medical Leave - Life Insurance - 401k with 5% match after 1 year of employment - Employee Assistance Program: Free access to a confidential service that helps employees and their communities with personal and work-related issues, such as mental health support, counseling, and financial advice. - Reciprocity: Employees have access to free and discounted admission and membership to more than 50 nearby museums and cultural institutions. - Discounts: Enjoy free entry to all Trustees properties, discount event tickets, and discounted merchandise at our stores and on stays at our inns. - Day of Wonder: Spend one workday per year to exploring a Trustees property - Day of Service: Spend one workday per year to helping with a project at a Trustees property We'll put each as
• . Now we need to ensure we don't include boilerplate like EEO, diversity statement, application instructions, contact email (people@thetrustees.org) maybe we can keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The contact email appears in "Questions? Contact our People team at people@thetrustees.org" and also later in accommodation request. That's arguably application instruction/contact. Should we remove? It's not exactly application instruction but it's a contact for questions. Might be considered application instruction. Safer to remove. Also "Don't quite have all the skills and experience listed above? We still want to hear from you! Research shows that historically marginalized groups are less likely to apply if they do not meet every single requirement. We are committed to building a diverse team and encourage you to apply even if you are missing some of the skills and experience above." That's encouragement but maybe considered boilerplate? It's not EEO but it's encouraging to apply. Might be considered part of the posting but not essential? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That encouragement is substantive? It's more about encouraging applications; could be considered boilerplate but it's specific to the posting. I'd keep it maybe under Requirements or Qualifications as a note. However it's not a requirement. Could be placed under Requirements as a note. But it's not a requirement; it's a statement. Might be considered part of the posting but not a requirement. I'd keep it as a paragraph under Requirements maybe as a note. But the instruction says remove duplicated lines and application instructions. This is not exactly application instruction but encouraging to apply. Might be considered part of the posting but not a requirement. I'd keep it. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

  About the role

  Who We Are: ... (the paragraph).

  Your Impact: ... (the paragraph).

  The Role: ... (the paragraph).

  Then

  Responsibilities

  • ... each bullet from "Specifically, you'll:"
  Then

  Requirements

  • ... required items

  Note: Don't quite have all the skills and experience listed above? We still want to hear from you