Director of Programs, Donor Relations & Stewardship

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Essential duties and responsibilities (list). There's also "Shared Accountabilities" (maybe part of responsibilities). There's "Knowledge And Skills". There's "Experience Required". There's "About Us". There's no explicit Benefits, Pay, Schedule. So we should not include those sections. Also we should not repeat job title. The page already shows it, we don't have title. We'll produce sections: About the role (maybe from About Us? Actually "About the role" could be a summary of role; but we have "Essential Duties and Responsibilities" which is responsibilities. There's no explicit "About the role" paragraph besides maybe the first sentence? The job description starts with "Job Description ESSENTIAL DUTIES AND RESPONSIBILITIES". There's no separate "About the role". However we could treat the introductory paragraph before duties as "About the role"? The text begins: "Job Description ESSENTIAL DUTIES AND RESPONSIBILITIES Lead Stewardship Strategy..." So there is no separate summary. Could we still include an "About the role" section using the first few sentences? Might be considered filler. Better to only include sections with clear content: Responsibilities, Knowledge And Skills (Skills), Experience Required (maybe Qualifications), About Us (maybe About the role? Actually About Us is about the organization, not role). The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - Responsibilities: Essential Duties and Responsibilities + Shared Accountabilities (maybe part of responsibilities). We'll combine. - Skills: Knowledge And Skills. - Qualifications: Experience Required (maybe also Associate's Degree Preferred Bachelor's Degree). Could also include Education. - About the role: Could be the "About Us"? Actually About Us is about the organization, not role. But we could treat "About the role" as a brief summary of the role's purpose; we don't have that. Might be better to omit About the role if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not include About the role if we don't have specific content. Similarly, Requirements maybe same as Qualifications? We could treat Requirements as Experience Required? But we have both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has "Experience Required" and "Associate's Degree Preferred Bachelor's Degree". That's qualifications. There's no separate "Requirements" besides that. So we could put Qualifications heading for that. Requirements could be omitted. - Skills: we have Knowledge And Skills. - Benefits, Pay, Schedule: none. Thus output sections:

Responsibilities

with

• ... items. Need to preserve all substantive information; do not invent or summarize away detail. We need to convert the paragraphs into list items. The duties are many sentences; we could break each sentence into a list item. Must preserve all info. Let's extract duties: From "Essential DutIES AND RESPONSIBILITIES": - Lead Stewardship Strategy to Build a Best-in-Class Program - Develop and execute a comprehensive donor relations and stewardship strategy focused on strengthening donor trust, retention, and future giving to support overall fundraising performance and pipeline sustainability. - Serve as a clear voice of the donor in shaping stewardship priorities, communications, and experiences. - Ensure stewardship programs are proactive, consistent, and tailored to donor intent and level of engagement to deepen relationships and drive sustained philanthropic investment. - Lead the design and execution of a comprehensive donor stewardship communications program, establishing a structured annual cadence of donor touchpoints. - Engage volunteers, physicians, and hospital leaders in delivering meaningful, relationship-driven donor experiences that deepen connections and support retention and future giving. - Establish clear standards, policies, and protocols that reinforce excellence, compliance, and timeliness in donor reporting. - Oversee donor recognition programs, including walls, plaques, and signage, ensuring alignment with donor intent and an exceptional donor experience. - Track and evaluate program performance through dashboards and key metrics to continuously improve donor engagement and retention, including ensuring every $1M+ donor receives a high-quality written report. Then "Lead and Develop a High-Performing Team": - Set clear expectations, goals, and accountability measures aligned with team performance and donor engagement outcomes. - Model and reinforce HEART values—Humility, Excellence, Accountability, Respect, and Trust—through leadership expectations and team performance. - Foster a culture of transparent performance management and accountability, using metrics and a regular cadence to assess progress. - Empower team members to take ownership, execute with precision, and continuously improve. - Ensure the team balances high-quality execution with strong relationship management to deliver a consistent and meaningful donor experience. Then "Partner Across Teams to Align Donor Strategy and Enhance the Donor Experience": - Collaborate across Finance, clinical leadership, and Philanthropy teams to ensure accurate and timely delivery of donor reports that reinforce trust and transparency. - Integrate stewardship into broader communication and fundraising strategies to strengthen donor connection to impact and outcomes. - Partner closely with gift officers to align stewardship strategies with donor goals, expectations, and future giving potential. - Contribute to donor strategy discussions by identifying opportunities to deepen engagement and increase philanthropic investment. Then "Leverage Data and Systems to Drive Stewardship Performance and Accountability": - Maintain accurate donor data and ensure stewardship activity is appropriately documented to support strong relationship management and continuity. - Identify trends and evolving best practices to continuously strengthen the stewardship program and improve donor retention and satisfaction. - Lead the development of unified systems and processes that provide visibility into stewardship activity, progress, and donor engagement outcomes. - Implement tools and workflows that enhance operational efficiency and elevate the overall donor experience. Then "The statements listed above are intended to describe the essential responsibilities performed by individuals assigned to this position. They are not intended to be an exhaustive list of all responsibilities." This is a disclaimer; we should preserve? It's substantive but maybe boilerplate? It's not a list of duties; it's a note. Might be considered boilerplate but it's part of description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is not exactly legal; it's about responsibilities. Might keep? It's not a duty but a note. I'd keep it as a paragraph after list maybe. Then "Shared Accountabilities": list: - Complete timely performance appraisals for direct reports. - Conduct appropriate investigations and follow-up on individual and patient complaints. - Develop and modify job descriptions as necessary. - Ensure new staff attend hospital and department orientation within 30 days of employment. - Prepare and submit annual capital and operating budgets. - Report performance and outcomes on a monthly basis. - Submit performance planning documents, ongoing planning materials, action plans, and department goals. We should include these as part of responsibilities (maybe separate subsection). We'll just add them as list items under responsibilities. Now Knowledge And Skills: - Demonstrated ability to manage multiple projects simultaneously, work effectively with diverse stakeholders and personalities, establish goals, execute strategies, and drive results. - Strong and positive communicator with a creative, relationship-focused approach and demonstrated ability to collaborate effectively across teams. - Strategic thinker who can translate organizational and fundraising priorities into actionable donor relations and stewardship strategies. - Thorough understanding of donor relations and stewardship programs, practices, and emerging best practices. - Strong interpersonal and written communication skills, with the ability to develop high-level plans and strategies in collaboration with leadership and key stakeholders. - Demonstrated ability to build trusted relationships and work effectively with donors, organizational leaders, physicians, volunteers, and fundraising professionals. - Poised and professional presence with sound judgment and discretion when working with donors and senior-level stakeholders. Experience Required: - Seven (7) years of fundraising, donor relations, project management, grants, reporting, and/or related experience. - One (1) year of formal supervisory experience. - Associate's Degree Preferred Bachelor's Degree We could phrase as list items. About Us: we could include as a section maybe "About the organization"? But headings list does not include About Us. Could we put it under About the role? Not really. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings if needed, but better to stick to those. About Us content is about the organization, not role. Could we treat it as "About the role"? Not accurate. Perhaps we omit About Us because no matching heading. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit About Us, we lose substantive info about the organization. But maybe it's considered boilerplate? It's descriptive of the organization, not strictly boilerplate like EEO. It's substantive. We need to include it somewhere. Could we put it under a heading like "About the role"? That would be misleading. Perhaps we can add a heading "About Texas Children's" but not in the list. The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't say we cannot use other headings, but suggests we should use those. Safer to include About Us as a paragraph without a heading? The instruction: Use

  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. It doesn't forbid other headings, but says use h3 for section headings (e.g., those). So we could still use h3 for other headings if needed, but better to follow the pattern. Perhaps we can treat About Us as "About the role" by rephrasing? But we cannot invent content. We could include a short paragraph under "About the role" that describes the organization? That would be inaccurate. Better to include a heading "About Texas Children's" as h3, even if not in the example list. The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies examples, not exclusive. So we can use other headings. Thus we will include:

    About Texas Children's

    with paragraph(s) from About Us. Now we need to ensure we don't include boilerplate like EEO statement at end. Remove that. Now produce HTML fragment. We'll structure:

    Responsibilities

    • ...
    ...
    Then maybe

    Shared Accountabilities

    but we could incorporate under Responsibilities. To avoid too many sections, we could keep Shared Accountabilities as part of Responsibilities list. But the instruction: Prefer a few substantive sections over many thin ones. So we could merge Shared Accountabilities into Responsibilities as list items. Thus Responsibilities list includes all duties and shared accountabilities. Then

    Knowledge and Skills

    with list. Then

    Qualifications

    with list (Experience Required + Education). Then

    About Texas Children's

    with paragraph(s). We should not include Requirements, Benefits, Pay, Schedule. Now craft list items preserving exact wording. Let's copy duties exactly as sentences. I'll produce list items: - Lead Stewardship Strategy to Build a Best-in-Class Program - Develop and execute a comprehensive donor relations and stewardship strategy focused on strengthening donor trust, retention, and