Administrative Support & Community Outreach (Hybrid)
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. Do NOT repeat the job title as a heading. 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:
- Position Overview (prose)
- Key Responsibilities (with subcategories: Administration & Operations, Programs & Events, Community Outreach & Communications). Could be a single Responsibilities section with sublists? The rule says use
for section headings like Responsibilities. So we can have Responsibilities
and then maybe subheadings? Not required but we can keep subheadings as
maybe? But we should not create extra headings unless needed. Could keep subheadings as
... but that adds formatting not requested. Simpler: list all responsibilities in a with items. However we have categories; we could embed categories as part of list items.
- Qualifications (list)
- Schedule (specific: 8–16 flexible hours/week, Hybrid, occasional events in-person, approx one team meeting per month, ability to commit to 1 year preferred, opportunity for growth). This is substantive, so we include Schedule section.
- Compensation & Benefits: includes $20/hour, up to 16 hours/week or more pending funding, performance, and needs; also "Connections with AAPI community leaders..." etc. That seems like benefits. So we can have a Benefits section (maybe also Pay). The rule says use Pay and Benefits headings if stated. The posting states compensation: $20/hour. Benefits: connections, hands-on experience, letter of recommendation, etc. So we could have Pay
with $20/hour, up to 16 hours/week or more pending funding...
and Benefits
with list.
But the rule says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Compensation & Benefits section. However they gave examples of headings: Pay, Benefits. But we can decide to have a single section "Compensation & Benefits". The rule says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using a combined heading. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples of possible headings. We can use any of those. Using "Compensation & Benefits" is not in the list but could be okay? Might be safer to use separate Pay and Benefits sections as they are explicit examples. However the rule also says "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits might be thin if each only has a short paragraph. But we have substantive content for both: Pay has rate and hours; Benefits has list of connections, experience, letter of recommendation. That's enough.
We also need to include About the role? The Position Overview could be About the role. So we could have About the role
with prose.
Thus sections: About the role, Responsibilities, Qualifications, Schedule, Pay, Benefits.
We must not include headings with filler. All have content.
Now we need to strip boilerplate: The posting includes lines like "Posted: Sep 11, 2026 Administrative Support & Community Outreach (Hybrid) SPEAK (a Supportive Place for Empowering Asian Americans and Kin), Inc business_center Part-time Salary: $20.00 - $20.00 Hourly Application Deadline: Oct 30, 2026". That's metadata; we can fold into a short
or drop. 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 paragraph at top with that info, maybe as a
but we shouldn't add classes? Not prohibited. But we can just include a
with the posted date and location etc. However they said "Preserve ALL substantive information". The posted date, location, hybrid, part-time, salary, deadline are substantive? Possibly yes. But they also said "fold minor metadata into a short
or drop it." So we can include a short paragraph with that info.
We also need to remove duplicated lines, cookie/navigation/legal/EEO etc. At the end there is "************ SPEAK is an equal opportunity employer..." that's EEO boilerplate; remove.
Also "Share Share Share Share email Share" etc; remove.
Also "Applications accepted on a rolling basis. Position will be available until filled, even if before the deadline indicated." That's application instructions; remove.
Now we need to preserve all substantive info: Position Overview, responsibilities, qualifications, schedule, compensation, benefits.
Let's extract:
Position Overview paragraph:
"SPEAK seeks a reliable, detail-oriented Administrative Assistant to support the day-to-day operations of our growing nonprofit. This position will provide administrative and logistical support across programs, trainings, events, communications, and organizational operations."
That's it.
Responsibilities:
Administration & Operations:
- Monitor general email and assist with routine correspondence and scheduling.
- Maintain calendars, Google Drive, spreadsheets, and organizational records.
- Assist with minor website updates (Squarespace).
- Help improve administrative systems and workflows, including appropriate use of AI and technology.
- Provide administrative support to the Executive Director and team on special projects.
Programs & Events:
- Coordinate logistics for administrative needs for trainings and community events.
- Prepare and organize participant licensing and training materials.
- Attend and support in-person events throughout Westchester County.
Community Outreach & Communications:
- Maintain community, partner, volunteer, and stakeholder contact lists.
- Assist with outreach emails, event promotion, and partner communications.
- Provide basic support for social media, website content, flyers, and other communications.
- Assist with fundraising, sponsorship, grant, and donor-related administrative tasks as needed.
Qualifications (list):
- Must be able to travel in-person within Westchester and occasionally carry event materials (e.g., box of tabling materials).
- Excellent attention to detail, organization, and follow-through.
- Reliable, responsive, and able to work independently.
- Strong written and verbal communication skills.
- Comfortable with Google Workspace and learning new technology.
- Ability to manage multiple priorities in a small, growing organization.
- Passion for AANHPI mental health and health equity strongly preferred.
Schedule:
- 8–16 flexible hours/week
- Hybrid, with occasional events in-person in Westchester (some daytime, predominantly evening/weekend).
- Approximately one team meeting per month.
- Ability to commit to 1 year preferred.
- Opportunity for the position to grow based on organizational needs, performance, and funding.
Pay:
- $20/hour, up to 16 hours/week or more pending funding, performance, and needs of a growing organization
Benefits:
- Connections with AAPI community leaders, mental health professionals, and nonprofit organizations in the greater New York area
- Hands-on nonprofit administration, communications, and community outreach experience
- If appropriate, a letter of recommendation available upon completion of a successful tenure
We could also include "Part-time" etc but that's covered in schedule/hours.
Now produce HTML:
We'll start with a
for metadata: maybe "Posted: Sep 11, 2026 | Administrative Support & Community Outreach (Hybrid) | SPEAK, Inc | Part-time | Application Deadline: Oct 30, 2026". But we need to avoid duplication; we already have schedule/hours etc. The posted date maybe not needed but it's substantive? Could include short
.
Let's include:
Posted: Sep 11, 2026 | Administrative Support & Community Outreach (Hybrid) | SPEAK, Inc | Part-time | Application Deadline: Oct 30, 2026
Then sections.
We must not use markdown code fences. Just raw HTML.
Let's craft:
About the role
SPEAK seeks a reliable, detail-oriented Administrative Assistant to support the day-to-day operations of our growing nonprofit. This position will provide administrative and logistical support across programs, trainings, events, communications, and organizational operations.
Responsibilities
- Administration & Operations: Monitor general email and assist with routine correspondence and scheduling; maintain calendars, Google Drive, spreadsheets, and organizational records; assist with minor website updates (Squarespace); help improve administrative systems and workflows, including appropriate use of AI and technology; provide administrative support to the Executive Director and team on special projects.
- Programs & Events: Coordinate logistics for administrative needs for trainings and community events; prepare and organize participant licensing and training materials; attend and support in-person events throughout Westchester County.
- Community Outreach & Communications: Maintain community, partner, volunteer, and stakeholder contact lists; assist with outreach emails, event promotion, and partner communications; provide basic support for social media, website content, flyers, and other communications; assist with fundraising, sponsorship, grant, and donor-related administrative tasks as needed.
But note: The rule says use - for any list of duties/requirements/benefits. Using inside li is okay. However we might want to separate each duty as separate li items rather than grouping. Could produce many li items. That's fine.
Better to list each duty as separate li. Let's do that.
Thus:
- Monitor general email and assist with routine correspondence and scheduling.
- Maintain calendars, Google Drive, spreadsheets, and organizational records.
- Assist with minor website updates (Squarespace).
- Help improve administrative systems and workflows, including appropriate use of AI and technology.
- Provide administrative support to the Executive Director and team on special projects.
- Coordinate logistics for administrative needs for trainings and community events.
- Prepare and organize participant licensing and training materials.
- Attend and support in-person events throughout Westchester County.
- Maintain community, partner, volunteer, and stakeholder contact lists.
- Assist with outreach emails, event promotion, and partner communications.
- Provide basic support for social media, website content, flyers, and other communications.
- Assist with fundraising, sponsorship, grant, and donor-related administrative tasks as needed.
That preserves all.
Now Qualifications:
- Must be able to travel
for prose. Do NOT repeat the job title as a heading. 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: - Position Overview (prose) - Key Responsibilities (with subcategories: Administration & Operations, Programs & Events, Community Outreach & Communications). Could be a single Responsibilities section with sublists? The rule says use
for section headings like Responsibilities. So we can have Responsibilities
and then maybe subheadings? Not required but we can keep subheadings as
maybe? But we should not create extra headings unless needed. Could keep subheadings as
... but that adds formatting not requested. Simpler: list all responsibilities in a $20/hour, up to 16 hours/week or more pending funding... or drop. 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 paragraph at top with that info, maybe as a but we shouldn't add classes? Not prohibited. But we can just include a with the posted date and location etc. However they said "Preserve ALL substantive information". The posted date, location, hybrid, part-time, salary, deadline are substantive? Possibly yes. But they also said "fold minor metadata into a short or drop it." So we can include a short paragraph with that info.
We also need to remove duplicated lines, cookie/navigation/legal/EEO etc. At the end there is "************ SPEAK is an equal opportunity employer..." that's EEO boilerplate; remove.
Also "Share Share Share Share email Share" etc; remove.
Also "Applications accepted on a rolling basis. Position will be available until filled, even if before the deadline indicated." That's application instructions; remove.
Now we need to preserve all substantive info: Position Overview, responsibilities, qualifications, schedule, compensation, benefits.
Let's extract:
Position Overview paragraph:
"SPEAK seeks a reliable, detail-oriented Administrative Assistant to support the day-to-day operations of our growing nonprofit. This position will provide administrative and logistical support across programs, trainings, events, communications, and organizational operations."
That's it.
Responsibilities:
Administration & Operations:
- Monitor general email and assist with routine correspondence and scheduling.
- Maintain calendars, Google Drive, spreadsheets, and organizational records.
- Assist with minor website updates (Squarespace).
- Help improve administrative systems and workflows, including appropriate use of AI and technology.
- Provide administrative support to the Executive Director and team on special projects.
Programs & Events:
- Coordinate logistics for administrative needs for trainings and community events.
- Prepare and organize participant licensing and training materials.
- Attend and support in-person events throughout Westchester County.
Community Outreach & Communications:
- Maintain community, partner, volunteer, and stakeholder contact lists.
- Assist with outreach emails, event promotion, and partner communications.
- Provide basic support for social media, website content, flyers, and other communications.
- Assist with fundraising, sponsorship, grant, and donor-related administrative tasks as needed.
Qualifications (list):
- Must be able to travel in-person within Westchester and occasionally carry event materials (e.g., box of tabling materials).
- Excellent attention to detail, organization, and follow-through.
- Reliable, responsive, and able to work independently.
- Strong written and verbal communication skills.
- Comfortable with Google Workspace and learning new technology.
- Ability to manage multiple priorities in a small, growing organization.
- Passion for AANHPI mental health and health equity strongly preferred.
Schedule:
- 8–16 flexible hours/week
- Hybrid, with occasional events in-person in Westchester (some daytime, predominantly evening/weekend).
- Approximately one team meeting per month.
- Ability to commit to 1 year preferred.
- Opportunity for the position to grow based on organizational needs, performance, and funding.
Pay:
- $20/hour, up to 16 hours/week or more pending funding, performance, and needs of a growing organization
Benefits:
- Connections with AAPI community leaders, mental health professionals, and nonprofit organizations in the greater New York area
- Hands-on nonprofit administration, communications, and community outreach experience
- If appropriate, a letter of recommendation available upon completion of a successful tenure
We could also include "Part-time" etc but that's covered in schedule/hours.
Now produce HTML:
We'll start with a for metadata: maybe "Posted: Sep 11, 2026 | Administrative Support & Community Outreach (Hybrid) | SPEAK, Inc | Part-time | Application Deadline: Oct 30, 2026". But we need to avoid duplication; we already have schedule/hours etc. The posted date maybe not needed but it's substantive? Could include short .
Let's include:
Posted: Sep 11, 2026 | Administrative Support & Community Outreach (Hybrid) | SPEAK, Inc | Part-time | Application Deadline: Oct 30, 2026 SPEAK seeks a reliable, detail-oriented Administrative Assistant to support the day-to-day operations of our growing nonprofit. This position will provide administrative and logistical support across programs, trainings, events, communications, and organizational operations. with items. However we have categories; we could embed categories as part of list items.
- Qualifications (list)
- Schedule (specific: 8–16 flexible hours/week, Hybrid, occasional events in-person, approx one team meeting per month, ability to commit to 1 year preferred, opportunity for growth). This is substantive, so we include Schedule section.
- Compensation & Benefits: includes $20/hour, up to 16 hours/week or more pending funding, performance, and needs; also "Connections with AAPI community leaders..." etc. That seems like benefits. So we can have a Benefits section (maybe also Pay). The rule says use Pay and Benefits headings if stated. The posting states compensation: $20/hour. Benefits: connections, hands-on experience, letter of recommendation, etc. So we could have
Pay
with Benefits
with list.
But the rule says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Compensation & Benefits section. However they gave examples of headings: Pay, Benefits. But we can decide to have a single section "Compensation & Benefits". The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using a combined heading. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples of possible headings. We can use any of those. Using "Compensation & Benefits" is not in the list but could be okay? Might be safer to use separate Pay and Benefits sections as they are explicit examples. However the rule also says "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits might be thin if each only has a short paragraph. But we have substantive content for both: Pay has rate and hours; Benefits has list of connections, experience, letter of recommendation. That's enough.
We also need to include About the role? The Position Overview could be About the role. So we could have
About the role
with prose.
Thus sections: About the role, Responsibilities, Qualifications, Schedule, Pay, Benefits.
We must not include headings with filler. All have content.
Now we need to strip boilerplate: The posting includes lines like "Posted: Sep 11, 2026 Administrative Support & Community Outreach (Hybrid) SPEAK (a Supportive Place for Empowering Asian Americans and Kin), Inc business_center Part-time Salary: $20.00 - $20.00 Hourly Application Deadline: Oct 30, 2026". That's metadata; we can fold into a short About the role
Responsibilities
But note: The rule says use
That preserves all.
Now Qualifications: