Development Manager

We need to output HTML fragment with sections: Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must include sections only when posting has real specific content. We must preserve all substantive info, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove EEO policy lines. Also remove "Why Blue Star Families?" maybe that's benefits? It includes mission-driven work, flexible work options, competitive salary, comprehensive benefits, 403(b) etc. That's benefits info. So we can include Benefits section with those bullet points. We need to include Pay section: posting says "Anticipated Pay Range at Commencement of Employment: $56,000 - $71,000". So include Pay section. Schedule: Not explicitly given; but there is mention of travel, nights, weekends, holidays as necessary. No explicit schedule like full-time. Could we infer? The posting says Position Type: Full-Time Employee. That's schedule info. So we could include Schedule section with "Full-Time". However rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Position Type: Full-Time Employee. So we can include Schedule with Full-Time. But we must avoid filler like "commensurate with experience" etc. In Required Experience they have "Bachelor's degree ... or commensurate experience." That's a phrase we must preserve? The rule says: Do NOT invent or summarize away detail. Preserve ALL substantive information; do NOT invent or summarize away detail. However we must not 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 posting actually states them. The phrase "commensurate experience" appears in the Required Experience bullet. That is not a heading; it's within a list item. The rule about not emitting a heading followed by filler/placeholder text refers to sections; we can still include that phrase inside content. It's okay. We need to remove duplicated lines. Also remove "EEO Policy" and maybe "Why Blue Star Families?" but we can keep benefits from that. We need to structure: Likely sections: About the role (maybe from General Description), Responsibilities (Key Job Functions), Requirements (Required Experience, Skills, Background), Qualifications (maybe Desired Experience?), Skills (maybe combine?), Benefits, Pay, Schedule. But we must prefer a few substantive sections over many thin ones. Could combine some. Let's extract substantive content: - About the role: The mission description of Blue Star Families, maybe not needed? The "General Description" is about Development Manager role. Could be "About the role". We'll include a paragraph summarizing the role: The Development Manager provides administrative support to the Development Department while learning and performing core fundraising processes and tasks. Detail-oriented, deadline-driven, well-organized, able to stay flexible in fast-paced environment. Understands importance of clean donor database, works closely with staff to maintain data integrity. Strong writer, can learn and apply tone/style through editing/revision, will support grant writing efforts. Brings genuine enthusiasm for learning all aspects of fundraising within a growing organization serving military-connected families. As fully remote organization, rely on regular in-person gatherings; role requires ability to travel overnight several times per year to attend team offsites, leadership sessions, company-wide events. Attendance and participation in these gatherings is a non-negotiable component. That's substantive. - Responsibilities: Key Job Functions bullet list. We need to convert each bullet into

. The bullet list includes: Administrative Tasks - Accurately create and update Salesforce records to capture all donor interactions and opportunities, ensuring the accuracy and integrity of BSF's donor data. - Use AI or other tools to take comprehensive meeting notes, and proactively initiate and manage follow-up actions so all tasks and commitments are addressed in a timely manner. - Efficiently manage appointments and schedules using Google Calendar. - Assist the Senior Manager of Operations & Stewardship and the Lead Vice President in tracking and creating stewardship reports for corporate and foundation donors. - Backstop the Senior Manager of Operations & Stewardship on the Development Team's interactions with the Finance Department. Technical Proficiency - Use Google Suite (email, calendar, chat) and Google Drive to create, edit, and save Docs, Sheets, and Slides. - Utilize Hive to streamline tasks and collaborate efficiently with BSF colleagues and teams. - Design engaging, impactful donor reports using Canva. Fundraising Skills Development - Apply key fundraising techniques, including research/prospecting, grant writing, and donor cultivation and stewardship. - Support the planning and execution of special events, particularly maintaining invitation lists. Communication and Research - Craft clear, effective written communications, including emails, memos, flyers, letters of intent, proposals, and reports. - Conduct donor research to identify new, appropriate funding prospects (private and public) for BSF's programs and priorities. Department Coordination - Maintain the department meeting calendar and agenda. - Provide updates at department meetings. - Perform other duties as assigned. We could group under headings? But rule: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have subheadings inside sections; but we should likely just have a Responsibilities section with a

• list of all duties. Could keep the subheadings as plain text inside
• ? Might be okay but better to keep as plain text within
• . However the bullet list includes headings like "Administrative Tasks". Those are not duties but categories. We could keep them as
• Administrative Tasks: then sublist? But rule says use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists. But to keep simple, we could flatten: each duty as a
  • . The category headings could be omitted or turned into plain text within
  • . But we must preserve ALL substantive information; removing the category headings might lose some structure but not substantive info? The headings themselves are not substantive info; they are just grouping. Probably okay to drop them. But we could keep them as part of the
  • text: e.g., "
  • Administrative Tasks: Accurately create and update Salesforce records...
  " That preserves the heading. We'll do that. - Requirements: Required Experience, Skills, Background bullet list. List: - 2-4 years of related sales or fundraising experience. - Bachelor's degree in a discipline such as marketing, social work, English, communications, management, or public relations, or commensurate experience. - Demonstrated experience effectively managing administrative tasks, including record management, note-taking, and scheduling. - Proficiency in Google Suite, Canva, Salesforce, and Hive, or a proven ability to quickly learn and master these tools. - Strong research skills, ideally in contexts relevant to fundraising, business, or similar fields. - Excellent written and verbal communication skills. - Excellent attention to detail. - Quick learner, adaptable to a variety of tasks and challenges in a fast-paced environment. - Works and communicates effectively with people from different backgrounds, and fosters collegial teamwork. - Experience working in a virtual environment. - Ability to travel out of town overnight several times per year for staff offsites, planning retreats, and company-wide events; these gatherings are essential for connection, brainstorming, and staying strategically aligned across teams, and participation is required as a core part of the role. - May be required to work nights, weekends, and holidays as necessary to carry out key job functions. We'll put each as
  • . - Qualifications: Desired Experience, Skills & Background bullet list. List: - Familiarity with the military community. - Familiarity with membership-driven organizations. We'll include as
  • . - Skills: Could be derived from Required Experience but maybe we can combine? The rule says prefer few substantive sections. Could merge Requirements and Qualifications into one "Requirements" section, and maybe have a "Skills" section for technical proficiencies? But we already have technical proficiency in Responsibilities. Might be okay to have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We'll omit Qualifications separate. - Benefits: From "Why Blue Star Families?" plus maybe other benefits mentioned earlier: "Competitive salary", "Comprehensive benefits, including health, dental, and vision insurance", "403(b) retirement plan with employer match", "Flexible Spending Accounts, life insurance, and disability insurance", "Communications allowance", "Professional development and career growth opportunities", "PCS leave for Active Duty military spouses", "Flexible work options (remote, or hybrid depending on the role)". Also "Mission-driven work supporting military service members and their families". We'll include those as bullet list. - Pay: Anticipated Pay Range at Commencement of Employment: $56,000 - $71,000. - Schedule: Position Type: Full-Time Employee. Also mention travel requirement etc but that's in Responsibilities. We'll just put Full-Time. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce:

    About the role

    ...

    Responsibilities

    • Administrative Tasks: Accurately create and update Salesforce records to capture all donor interactions and opportunities, ensuring the accuracy and integrity of BSF's donor data.
    ...
    Similarly for Requirements. We need to ensure we don't include any boilerplate like EEO Policy, etc. Check for duplicated lines: The posting had repeated "Blue Star Families is the largest nonprofit..." etc. We'll include only once in About the role maybe. We need to preserve all substantive info: The mission description etc. We'll include that in About the role. Let's craft About the role paragraph(s). Could be multiple

    tags. We'll include:

    Blue Star Families is the largest nonprofit dedicated to making military life better for families. Each year, we support over 1.5 million military- and veteran-connected family members through a national network of 300,000+ members and local chapters in communities across the country. Our mission is simple and bold: We make military life awesome for families. We listen, share, partner, and act to deliver evidence-based, data-driven solutions that work for real people. We’re a lifestyle organization, a friend and neighbor, and a trusted partner. Our approach is collaborative, human-centered, and designed with the whole family in mind. A Blue Star Family is one with an immediate family member — a spouse, parent, or child — actively serving in the U.S. Armed Forces, including the Guard and Reserves. These families face unique challenges: frequent relocations, deployments, career disruption, and isolation. We respond with research-informed programs that create connection, build resilience, and foster a true sense of belonging. We serve with urgency but build trust over time — because change happens at the speed of trust. Whether we’re driving spouse employment, supporting caregivers, or helping communities welcome military families, we strive for upstream solutions.

    Then a second paragraph about the role:

    The Development Manager provides administrative support to the Development Department while learning and performing core fundraising processes and tasks. The Manager is detail-oriented, deadline-driven, well-organized, and able to stay flexible in a fast-paced environment. They understand the critical importance of a clean donor database and work closely with staff to maintain data integrity. A strong writer, the Manager can learn and apply Blue Star Families' tone and style through editing and revision, and will support the organization's grant writing efforts. The Manager brings genuine enthusiasm for learning all aspects of fundraising within a growing organization serving military-connected families. As a fully remote organization, we rely on regular in-person gatherings to fulfill core business functions, including strategic