Assistant Director, Donor Relations
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where there is real specific content. The posting includes: Job Summary (we can treat as About the role). Responsibilities (Specific Responsibilities). Minimum Qualifications (Education, Experience, Certifications, Skills) -> could be Requirements or Qualifications. Preferred Qualifications (Education, Experience, Certifications, Skills) -> could be Skills or Qualifications. Benefits section present. Pay: they gave salary range: target budgeted salary $60,000 - $64,000 annually. So we can include Pay section. Schedule: they mention hybrid work schedule eligible. So we can include Schedule section.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, accommodations, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove "Miscellaneous Performs other duties as assigned." That's generic; we can maybe include under Responsibilities? It's not specific; better to omit if not substantive. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should omit Miscellaneous.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details from each section.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus we need to parse the content.
Let's extract sections:
About the role (Job Summary): The paragraph(s) after "Job Summary Please note: The target budgeted salary for this position is $60,000 - $64,000 annually. Offers will be based on candidate experience and education, as well as equity within Northwestern University. The Assistant Director is a member of Northwestern University's Donor Relations team within Alumni Relations and Development (ARD), helping ensure that major and principal gift donors understand the impact of their philanthropy. This role plays a critical part in stewarding donor relationships through the production and distribution of more than 1,300 customized stewardship reports annually, with a focus on the data, systems, and administrative processes that support this program. Working collaboratively with colleagues across ARD, the Assistant Director collects, analyzes, and maintains stewardship-related data, develops reporting tools and metrics, and serves as a key quality-control partner to ensure the accuracy and integrity of donor and fund information. Through effective project coordination, data management, and cross-functional collaboration, the role helps ensure donors receive accurate, meaningful, and timely information about the impact of their philanthropy. Successful candidates will possess strong technical, analytical, and interpersonal skills; a commitment to data integrity; and the ability to manage multiple priorities while maintaining a high level of accuracy. They will be proactive problem-solvers who enjoy collaborating across teams to support donor stewardship and advance Northwestern's philanthropic mission. This position is eligible for a hybrid work schedule."
We might separate Pay and Schedule later. But the summary includes salary note and hybrid schedule note. However we will create separate Pay and Schedule sections with that info, and maybe keep summary without those details? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary and hybrid schedule info somewhere. If we make separate Pay and Schedule sections, we should still keep the info there, and we could omit from summary or keep but not duplicate? It says preserve all substantive information; duplication is okay? It says remove duplicated lines. So we should avoid duplicating the same info. So we should extract salary and schedule info into their respective sections, and not repeat them in the summary.
Thus About the role section will contain the rest of the summary without salary and schedule lines.
Let's craft About the role paragraph: "The Assistant Director is a member of Northwestern University's Donor Relations team within Alumni Relations and Development (ARD), helping ensure that major and principal gift donors understand the impact of their philanthropy. This role plays a critical part in stewarding donor relationships through the production and distribution of more than 1,300 customized stewardship reports annually, with a focus on the data, systems, and administrative processes that support this program. Working collaboratively with colleagues across ARD, the Assistant Director collects, analyzes, and maintains stewardship-related data, develops reporting tools and metrics, and serves as a key quality-control partner to ensure the accuracy and integrity of donor and fund information. Through effective project coordination, data management, and cross-functional collaboration, the role helps ensure donors receive accurate, meaningful, and timely information about the impact of their philanthropy. Successful candidates will possess strong technical, analytical, and interpersonal skills; a commitment to data integrity; and the ability to manage multiple priorities while maintaining a high level of accuracy. They will be proactive problem-solvers who enjoy collaborating across teams to support donor stewardship and advance Northwestern's philanthropic mission."
That seems good.
Now Responsibilities: list of specific responsibilities bullet points.
We need to extract from "Specific Responsibilities" list:
- Support the production and distribution of more than 1,300 customized stewardship reports annually, contributing to project planning, tracking, and execution.
- Maintain and optimize donor, fund, and stewardship-related data within Salesforce and other platforms to support stewardship activities and ensure data accuracy.
- Develop and maintain reports, dashboards, and metrics used to monitor project activity, workload, and program performance.
- Extract, analyze, and interpret data from multiple systems, including Salesforce, IBM Cognos Analytics, and the Mythos Platform, to support stewardship reporting, project management, and decision-making.
- Serve as a key quality-control and data integrity partner by reviewing stewardship-related data for accuracy and completeness, identifying discrepancies, and collaborating with colleagues to resolve issues.
- Collaborate with colleagues across ARD to gather, review, and organize information used in donor-facing stewardship materials, including websites, PDFs, financial reports, student profiles, and other impact-reporting collateral.
- Provide onboarding, system support, and troubleshooting assistance to contract writers throughout the stewardship reporting cycle.
- Manage a shared team email account and provide responsive customer service to internal and external stakeholders.
- Provide backup support for donor acknowledgment administrative processes, such as assigning acknowledgment letters and preparing correspondence for university leadership.
We should keep these as
- .
Now Requirements/Qualifications: Minimum Qualifications (Education, Experience, Certifications, Skills). We'll treat as Requirements.
List:
- Successful completion of a full 4-year course of study in an accredited college or university leading to a bachelor's or higher degree; OR appropriate combination of education and experience.
- 2 years development, nonprofit operations, analytics, or the equivalent experience is required.
- Demonstrated ability to manage multiple projects simultaneously and meet competing deadlines in a fast-paced environment.
- Strong analytical, problem-solving, and strategic thinking skills, with the ability to identify issues and recommend effective solutions.
- Excellent written, verbal, and interpersonal communication skills, with the ability to collaborate effectively across teams.
We'll put as
- .
Now Preferred Qualifications (Education, Experience, Certifications, Skills) -> could be Skills or Qualifications. We'll treat as Skills maybe. But we already have Skills within Requirements; we could combine? The instruction: Prefer a few substantive sections over many thin ones. Could combine Minimum and Preferred into Qualifications? But we have headings: Requirements, Qualifications, Skills. We need to decide.
We could have Requirements (minimum qualifications) and Skills (preferred qualifications). Or we could have Qualifications (cover both). Since they ask to use headings like Requirements, Qualifications, Skills. We'll use Requirements for minimum, and Skills for preferred. Or we could have Qualifications for both but that might be thin. Let's do Requirements (minimum) and Skills (preferred). That seems reasonable.
Now Benefits: we have a paragraph describing benefits. We'll put as
maybe with list? It's a paragraph describing benefits; we could keep as
. It includes list of benefits but not bullet. We'll keep as
.
Pay: we have salary range: $60,000 - $64,000 annually. Also note offers based on experience etc. We'll put as
maybe.
Schedule: hybrid work schedule eligible. We'll put as
.
Now ensure we don't include boilerplate: EEO, accommodations, etc. Also remove "Note: Not all aspects of the job are covered by this job description." That's generic; we can omit.
Also remove "Miscellaneous Performs other duties as assigned." Omit.
Also remove links? The benefits section includes URLs; we should keep them? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The URLs are part of benefits description; we should keep them. However they might be considered navigation? But they are part of benefits description. We'll keep them as part of the paragraph.
Similarly Professional Growth & Development includes URLs; we should keep? That's also part of benefits? Actually it's separate section about professional growth. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The professional growth section includes URLs but no specific content besides "Visit us at ...". That's maybe boilerplate? It's still specific: they provide a link. However it's similar to benefits. But we already have Benefits section; we could add a Professional Growth section if we want. But the instruction says prefer a few substantive sections over many thin ones. The professional growth section is just a link; maybe we can omit as it's not substantive detail beyond a link. However it's still info about professional growth resources. But we already have benefits; maybe we can combine? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. The professional growth is not a list; it's a sentence with a link. Could be considered boilerplate. I'd lean to omit it to keep sections few.
Similarly Work-Life And Wellness section also just a link; we can omit.
Thus final sections: About the role (
About the role
), Responsibilities (Responsibilities
), Requirements (Requirements
), Skills (Skills
), Benefits (Benefits
), Pay (Pay
), Schedule (Schedule
).
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
Check for any duplicated lines: Ensure we didn't repeat salary/hybrid schedule in About the role.
Now write.
About the role: ...
Responsibilities: Responsibilities
- ...
...
Requirements: Requirements
- ...
...
Skills: Skills
- ...
...
Benefits: Benefits
...
Pay: Pay
...
Schedule: Schedule
...
Now ensure we preserve all substantive info from benefits paragraph: "At Northwestern, we are proud to provide meaningful and competitive benefits. The available benefits package for this position will include health, dental, vision, disability, and life insurance; paid vacation and holidays; paid medical/sick and parental leave; tuition benefits for the employee and dependents; pre-tax and flex spending accounts for commuting and dependent care; generous retirement savings options; and wellness programs. For a comprehensive overview of available benefits, including eligibility details, visit us at https://www.northwestern.edu/hr/benefits/index.html to learn more."
We'll keep that as .
Pay: "The target budgeted salary for this position is $60,000 - $64,000 annually. Off
for prose. Thus we need to parse the content. Let's extract sections: About the role (Job Summary): The paragraph(s) after "Job Summary Please note: The target budgeted salary for this position is $60,000 - $64,000 annually. Offers will be based on candidate experience and education, as well as equity within Northwestern University. The Assistant Director is a member of Northwestern University's Donor Relations team within Alumni Relations and Development (ARD), helping ensure that major and principal gift donors understand the impact of their philanthropy. This role plays a critical part in stewarding donor relationships through the production and distribution of more than 1,300 customized stewardship reports annually, with a focus on the data, systems, and administrative processes that support this program. Working collaboratively with colleagues across ARD, the Assistant Director collects, analyzes, and maintains stewardship-related data, develops reporting tools and metrics, and serves as a key quality-control partner to ensure the accuracy and integrity of donor and fund information. Through effective project coordination, data management, and cross-functional collaboration, the role helps ensure donors receive accurate, meaningful, and timely information about the impact of their philanthropy. Successful candidates will possess strong technical, analytical, and interpersonal skills; a commitment to data integrity; and the ability to manage multiple priorities while maintaining a high level of accuracy. They will be proactive problem-solvers who enjoy collaborating across teams to support donor stewardship and advance Northwestern's philanthropic mission. This position is eligible for a hybrid work schedule." We might separate Pay and Schedule later. But the summary includes salary note and hybrid schedule note. However we will create separate Pay and Schedule sections with that info, and maybe keep summary without those details? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary and hybrid schedule info somewhere. If we make separate Pay and Schedule sections, we should still keep the info there, and we could omit from summary or keep but not duplicate? It says preserve all substantive information; duplication is okay? It says remove duplicated lines. So we should avoid duplicating the same info. So we should extract salary and schedule info into their respective sections, and not repeat them in the summary. Thus About the role section will contain the rest of the summary without salary and schedule lines. Let's craft About the role paragraph: "The Assistant Director is a member of Northwestern University's Donor Relations team within Alumni Relations and Development (ARD), helping ensure that major and principal gift donors understand the impact of their philanthropy. This role plays a critical part in stewarding donor relationships through the production and distribution of more than 1,300 customized stewardship reports annually, with a focus on the data, systems, and administrative processes that support this program. Working collaboratively with colleagues across ARD, the Assistant Director collects, analyzes, and maintains stewardship-related data, develops reporting tools and metrics, and serves as a key quality-control partner to ensure the accuracy and integrity of donor and fund information. Through effective project coordination, data management, and cross-functional collaboration, the role helps ensure donors receive accurate, meaningful, and timely information about the impact of their philanthropy. Successful candidates will possess strong technical, analytical, and interpersonal skills; a commitment to data integrity; and the ability to manage multiple priorities while maintaining a high level of accuracy. They will be proactive problem-solvers who enjoy collaborating across teams to support donor stewardship and advance Northwestern's philanthropic mission." That seems good. Now Responsibilities: list of specific responsibilities bullet points. We need to extract from "Specific Responsibilities" list: - Support the production and distribution of more than 1,300 customized stewardship reports annually, contributing to project planning, tracking, and execution. - Maintain and optimize donor, fund, and stewardship-related data within Salesforce and other platforms to support stewardship activities and ensure data accuracy. - Develop and maintain reports, dashboards, and metrics used to monitor project activity, workload, and program performance. - Extract, analyze, and interpret data from multiple systems, including Salesforce, IBM Cognos Analytics, and the Mythos Platform, to support stewardship reporting, project management, and decision-making. - Serve as a key quality-control and data integrity partner by reviewing stewardship-related data for accuracy and completeness, identifying discrepancies, and collaborating with colleagues to resolve issues. - Collaborate with colleagues across ARD to gather, review, and organize information used in donor-facing stewardship materials, including websites, PDFs, financial reports, student profiles, and other impact-reporting collateral. - Provide onboarding, system support, and troubleshooting assistance to contract writers throughout the stewardship reporting cycle. - Manage a shared team email account and provide responsive customer service to internal and external stakeholders. - Provide backup support for donor acknowledgment administrative processes, such as assigning acknowledgment letters and preparing correspondence for university leadership. We should keep these as
- .
Now Requirements/Qualifications: Minimum Qualifications (Education, Experience, Certifications, Skills). We'll treat as Requirements.
List:
- Successful completion of a full 4-year course of study in an accredited college or university leading to a bachelor's or higher degree; OR appropriate combination of education and experience.
- 2 years development, nonprofit operations, analytics, or the equivalent experience is required.
- Demonstrated ability to manage multiple projects simultaneously and meet competing deadlines in a fast-paced environment.
- Strong analytical, problem-solving, and strategic thinking skills, with the ability to identify issues and recommend effective solutions.
- Excellent written, verbal, and interpersonal communication skills, with the ability to collaborate effectively across teams.
We'll put as
- .
Now Preferred Qualifications (Education, Experience, Certifications, Skills) -> could be Skills or Qualifications. We'll treat as Skills maybe. But we already have Skills within Requirements; we could combine? The instruction: Prefer a few substantive sections over many thin ones. Could combine Minimum and Preferred into Qualifications? But we have headings: Requirements, Qualifications, Skills. We need to decide.
We could have Requirements (minimum qualifications) and Skills (preferred qualifications). Or we could have Qualifications (cover both). Since they ask to use headings like Requirements, Qualifications, Skills. We'll use Requirements for minimum, and Skills for preferred. Or we could have Qualifications for both but that might be thin. Let's do Requirements (minimum) and Skills (preferred). That seems reasonable.
Now Benefits: we have a paragraph describing benefits. We'll put as
maybe with list? It's a paragraph describing benefits; we could keep as
. It includes list of benefits but not bullet. We'll keep as
. Pay: we have salary range: $60,000 - $64,000 annually. Also note offers based on experience etc. We'll put as
maybe. Schedule: hybrid work schedule eligible. We'll put as
. Now ensure we don't include boilerplate: EEO, accommodations, etc. Also remove "Note: Not all aspects of the job are covered by this job description." That's generic; we can omit. Also remove "Miscellaneous Performs other duties as assigned." Omit. Also remove links? The benefits section includes URLs; we should keep them? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The URLs are part of benefits description; we should keep them. However they might be considered navigation? But they are part of benefits description. We'll keep them as part of the paragraph. Similarly Professional Growth & Development includes URLs; we should keep? That's also part of benefits? Actually it's separate section about professional growth. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The professional growth section includes URLs but no specific content besides "Visit us at ...". That's maybe boilerplate? It's still specific: they provide a link. However it's similar to benefits. But we already have Benefits section; we could add a Professional Growth section if we want. But the instruction says prefer a few substantive sections over many thin ones. The professional growth section is just a link; maybe we can omit as it's not substantive detail beyond a link. However it's still info about professional growth resources. But we already have benefits; maybe we can combine? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. The professional growth is not a list; it's a sentence with a link. Could be considered boilerplate. I'd lean to omit it to keep sections few. Similarly Work-Life And Wellness section also just a link; we can omit. Thus final sections: About the role (
About the role
), Responsibilities (Responsibilities
), Requirements (Requirements
), Skills (Skills
), Benefits (Benefits
), Pay (Pay
), Schedule (Schedule
). Now we need to output only HTML fragment, no /, no markdown. Let's craft. Check for any duplicated lines: Ensure we didn't repeat salary/hybrid schedule in About the role. Now write. About the role:...
Responsibilities:Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
...
Pay:Pay
...
Schedule:Schedule
...
Now ensure we preserve all substantive info from benefits paragraph: "At Northwestern, we are proud to provide meaningful and competitive benefits. The available benefits package for this position will include health, dental, vision, disability, and life insurance; paid vacation and holidays; paid medical/sick and parental leave; tuition benefits for the employee and dependents; pre-tax and flex spending accounts for commuting and dependent care; generous retirement savings options; and wellness programs. For a comprehensive overview of available benefits, including eligibility details, visit us at https://www.northwestern.edu/hr/benefits/index.html to learn more." We'll keep that as. Pay: "The target budgeted salary for this position is $60,000 - $64,000 annually. Off
- for any list of duties/requirements/benefits, and
- .
Now Preferred Qualifications (Education, Experience, Certifications, Skills) -> could be Skills or Qualifications. We'll treat as Skills maybe. But we already have Skills within Requirements; we could combine? The instruction: Prefer a few substantive sections over many thin ones. Could combine Minimum and Preferred into Qualifications? But we have headings: Requirements, Qualifications, Skills. We need to decide.
We could have Requirements (minimum qualifications) and Skills (preferred qualifications). Or we could have Qualifications (cover both). Since they ask to use headings like Requirements, Qualifications, Skills. We'll use Requirements for minimum, and Skills for preferred. Or we could have Qualifications for both but that might be thin. Let's do Requirements (minimum) and Skills (preferred). That seems reasonable.
Now Benefits: we have a paragraph describing benefits. We'll put as