Gift Planning Advisor

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Department, Reports to, Classification, Hiring pay range, Benefits, Work location, etc. Also "About Seattle Foundation" and "Position Overview". The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to decide which sections to include. The posting includes: - About Seattle Foundation (description of organization). Could map to "About the role"? Actually "About the role" is a typical heading for role overview. The posting includes "Position Overview:" which describes role. So we can use

About the role

and put the Position Overview content there. - Responsibilities: there is a "Responsibilities:" heading with bullet list. So include

Responsibilities

with

• items. - Required Qualifications: there is a "Required Qualifications" heading with bullet list. Could map to

  Qualifications

  or

  Requirements

  . The instruction list includes both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has "Required Qualifications". We could put that under

  Qualifications

  . Also there may be "Skills" but not explicit separate list; qualifications include skills. Could also include a

  Skills

  if we extract skill statements. But better to avoid thin sections. We could combine qualifications and skills into one Qualifications section. The instruction says prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule? Pay is given: "Hiring pay range: $96,000 - $104,000". That's specific, so we should include Pay section. Schedule: not explicitly given; there is "Work location: Flexible work arrangement; can be fully in-person or hybrid (remote and in-person)." Also "Annual remote work, learning, and commuter benefits." No explicit schedule like full-time, but classification says Full-Time, Exempt. That could be considered schedule? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay stated. Schedule? Not explicitly; classification full-time is maybe schedule but not explicit hours. Might be considered schedule but not explicit. Safer to not include Schedule unless explicit. Benefits: clearly stated: "Benefits: Medical, dental, vision, life, AD&D, LTD. 403(b) retirement matched at 5%; increasing to 10% over time, 100% immediate vesting. PTO: 15 days accrued vacation, 10 days accrued sick, 4 wellness days, and 13 holidays annually. Annual remote work, learning, and commuter benefits." So include Benefits. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to preserve all substantive information. Must not invent or summarize away detail. So we need to include all details from each section. Let's extract content. About the role: Should include Position Overview paragraph(s). The Position Overview includes multiple paragraphs. We'll copy them as

  elements. Responsibilities: list after "Responsibilities:" includes many bullet points each starting with a verb. We'll convert each to

• . Qualifications: after "Required Qualifications:" includes bullet list. We'll convert each to
• . Benefits: after "Benefits:" includes description. We'll put as

  maybe with

  if list. The text includes multiple items separated by periods. Could keep as

  . But we could also split into list for clarity but not required. The instruction: Use

  • for any list of duties/requirements/benefits. Benefits is a list, so we should use
    • . So we need to parse benefits into list items. Benefits text: "Medical, dental, vision, life, AD&D, LTD. 403(b) retirement matched at 5%; increasing to 10% over time, 100% immediate vesting. PTO: 15 days accrued vacation, 10 days accrued sick, 4 wellness days, and 13 holidays annually. Annual remote work, learning, and commuter benefits." We can split into items: Medical, dental, vision, life, AD&D, LTD; 403(b) retirement matched at 5%; increasing to 10% over time, 100% immediate vesting; PTO: 15 days accrued vacation, 10 days accrued sick, 4 wellness days, and 13 holidays annually; Annual remote work, learning, and commuter benefits. We'll make each as
    • . Pay: "Hiring pay range: $96,000 - $104,000". We'll put as

      . Also there is other metadata: Department, Reports to, Classification, Work location, Must reside in Washington State, visit us online: www.seattlefoundation.org, About Seattle Foundation description. Should we include those? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate, duplicated lines, and application instructions. The metadata like Department, Reports to, Classification, Work location, Must reside in Washington State are substantive. Where to place them? Could be folded into a short

      under About the role or maybe a separate section like "Job Details". But we only allowed headings from list. However we can include a

      without heading? The instruction says output ONLY the HTML fragment; we can include

      elements anywhere. It didn't say we must wrap everything under headings. So we can include a

      for those details after the headings, maybe before or after sections. But we need to avoid creating extra headings not in list. So we can just add a

      containing those details. But we must not repeat the job title as a heading (the page already shows it). Not an issue. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none visible. We also need to remove "visit us online: www.seattlefoundation.org" maybe considered boilerplate? It's not exactly boilerplate but could be considered minor metadata; we can fold into a short

      or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." So we can include a short

      for metadata like Department, Reports to, Classification, Work location, Must reside in Washington State, visit us online. Thus final HTML: maybe start with a

      containing metadata, then

      About the role

      with paragraphs from Position Overview and About Seattle Foundation? Actually About Seattle Foundation is separate description of organization; could be part of About the role or separate. But we have only About the role heading; we could include both Position Overview and About Seattle Foundation under that heading. That would preserve all substantive info. Let's extract Position Overview text: "Seattle Foundation is seeking a proactive, relationship-oriented, and technically skilled Gift Planning Advisor to join our Philanthropic Services team. Reporting to the Director of Gift Planning, this position serves as a trusted charitable planning resource to donors and their professional advisors - including wealth managers, CPAs, trust officers, and estate planning attorneys – and is directly accountable for converting philanthropic intent into completed documented gifts. As a member of the Gift Planning team, the Advisor is often among the first points of contact for prospective donors and referring professional advisors and is accountable for the experience and impression the Foundation makes at that critical first touchpoint. This role combines charitable planning expertise, relationship management, and business development to cultivate philanthropic opportunities and convert them into long-term partnerships that expand the Foundation’s philanthropic capital and community impact. The Advisor owns a portfolio of professional advisors and planned giving donors, is responsible for building and qualifying a pipeline of new referral relationships and serves as an ambassador for the Foundation throughout the community. The ideal candidate for this position has demonstrated business development experience including building a pipeline, qualifying leads, and being voice that brings in, moves and influences transformative capital to create community change in our region. Success in this role requires strong emotional intelligence, sound judgment, attention to detail, and the ability to navigate complex conversations with donors, families, and advisors. The ideal candidate is equally comfortable discussing charitable planning strategies, building trusted relationships, facilitating fund establishment, and representing the Foundation at meetings, events, and community engagements. The Gift Planning Advisor is accountable for measurable results that strengthen Seattle Foundation’s long-term financial sustainability and community impact: growth in new and deferred gifts, expansion of the charitable assets under management, deeper and more productive donor and advisor relationships, and increased philanthropic investment in our region. Success in this role is defined not by activity alone, but by the transformative capital moved and the enduring partnerships built. By connecting generous individuals and families with meaningful opportunities for impact, this position directly advances the Foundation’s mission while strengthening its standing as a leading philanthropic partner in the community." Then About Seattle Foundation paragraph: "Seattle Foundation is a community foundation that works to advance equity, shared prosperity, and belonging throughout the region while strengthening the impact of the philanthropists it serves. Founded in 1946, we continue to evolve to be the organization our community needs. With more than $1.2 billion in assets under management, we work with partners to provide effective advising, education, and experiential learning for our philanthropists interested in making a difference both at home here in Seattle and around the world. Since 2016, our grantmaking, advocacy, and policy work have helped drive over $5 billion in public investments across Greater Seattle for children, housing, transit, and climate justice. Learn more at: www.seattlefoundation.org." We could include that as part of About the role or separate. But we have no heading for About the organization; we could incorporate it under About the role as additional context. That's fine. Now Responsibilities list: Let's extract each bullet. Responsibilities: - Grow the number of philanthropists who partner with Seattle Foundation—and the charitable assets they commit—through the establishment of Donor Advised Funds, endowment funds, charitable trusts, and documented estate gifts, and through active engagement of our services and support of our work in the community. - Own donor and advisor inquiries end to end, delivering a responsive, high-trust experience that reflects the Foundation’s brand and moves interest toward lasting partnership. - Serve as a trusted advisor to donors and their professional advisors by communicating Seattle Foundation's value proposition, service offerings, fee structure, and charitable giving solutions, positioning the Foundation and its philanthropic vehicles as the preferred partner for achieving clients' charitable goals. - Move prospective donors through the full pipeline—from initial inquiry through cultivation, decision-making, and completed fund establishment—accountable for advancing and closing new philanthropic commitments. - Own and steward an assigned portfolio of bequest donors and professional advisors, accountable for retaining these relationships and ensuring the Foundation remains