Volunteer ASL Translator to Help Ashoka Fellows Access and Participate in Bi-monthly Supportive Programming with Ashoka

We need to output HTML fragment with headings

for sections: About the role? Actually we need to follow rules: 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. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: "This is an opportunity to work with an Ashoka Staff This is an unpaid, volunteer opportunity About The Affiliated Organization Ashoka is the world's largest association of leading social entrepreneurs in the world. We call them Ashoka Fellows and they're bringing their systems changing innovations to solve urgent social and environmental issues in 99 countries. We collaborate with our Fellows and numerous other partners to create a world where everyone can learn to access their own power to be changemakers for the good of all. For more information, please visit https://www.ashoka-usa.org/ Job Description As a part of the life-long Fellowship program, the U.S. team hosts bi-monthly, virtual, Fellow-facilitated conversations over Zoom to support them personally, discuss strategy, and build community. We are looking for an ASL translator to ensure our programming is accessible for all members of the network. Topics have included succession planning and leadership transitions, using AI in the workplace, movement building in chaotic times, and democracy. You'll have the chance to be in community with some of the brightest social entrepreneurs of our times and learn interesting things along the way! These virtual sessions are 1hr long, with a combination of presentations and group conversation for 4-8 people. They take place on Thursdays at 12:00PM or 12:30PM EST. Please let us know if you can help! Volunteer Logistics Estimated hours required per week: 1 The estimated duration of the project is: 6-12 months This position is Virtual (Remote) Language Requirements English Desired? Actually "Language Requirements English Desired Skills And Experience ASL & English Fluency with the ability to translate meaning and context in real time.Experience translating using live video software like Zoom Confidentiality & Ethics - These topics are oftentimes vulnerable, with folks sharing real-life challenges and sensitive organizational information. We ask that you have experience with confidentiality." We need to extract sections: About the organization (maybe "About The Affiliated Organization") could be "About the role"? Actually we have "About The Affiliated Organization". Could be considered "About the role"? But we can use "About the organization" as a heading? The allowed headings list includes "About the role". We could map "About The Affiliated Organization" to "About the role"? Not exactly. But we can still use

  for any section heading we want, but they gave examples. Likely we should use headings that match the content: "About the organization", "Job Description", "Volunteer Logistics", "Language Requirements", "Desired Skills And Experience". However they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should stick to those standard headings. But we can also create other headings? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. However we need to include a section ONLY when the posting has real, specific content for it. So we need to decide which sections we have content for. We have: - About the organization (maybe "About the role"? Not exactly but we could treat as "About the role"? Might be okay.) - Job Description (maybe "Responsibilities"? Actually job description includes duties: hosting bi-monthly virtual conversations, ASL translator, topics, etc. Could be under "Responsibilities".) - Volunteer Logistics (estimated hours per week, duration, virtual). Could be under "Schedule"? Actually schedule includes time: Thursdays at 12:00PM or 12:30PM EST. Also hours per week. Could be "Schedule". But they said never create Pay/Schedule/Benefits sections unless posting actually states them. We have schedule info: sessions are 1hr long, Thursdays at 12:00PM or 12:30PM EST. Estimated hours per week: 1. Duration 6-12 months. So we have schedule info. So we could create a "Schedule" section. - Language Requirements: "English". That's a requirement. Could be under "Requirements" or "Qualifications". We have language requirement English. Could be under "Requirements". - Desired Skills And Experience: ASL & English Fluency, ability to translate meaning and context in real time, experience translating using live video software like Zoom, confidentiality & ethics experience. That's skills/experience. Could be under "Skills" or "Qualifications". We have "Skills" heading allowed. - Benefits: none mentioned (unpaid volunteer). So we should not create Benefits section. - Pay: none (unpaid). So we should not create Pay section. Thus we can have sections: About the role (or About the organization), Responsibilities, Requirements, Skills, Schedule. We need to use

  for each section heading. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment. Let's extract content precisely. First, we need to remove duplicated lines, navigation etc. The text seems to have some duplication: "This is an opportunity to work with an Ashoka Staff This is an unpaid, volunteer opportunity". Probably we should combine into a short paragraph. Let's rewrite content in our own words? No, we must preserve ALL substantive information; do NOT invent or summarize away detail. That means we cannot paraphrase? We can rephrase but must keep all info. Usually we can keep the same sentences. It's okay to rephrase slightly as long as we don't lose info. Safer to copy the sentences. We need to avoid repeating the job title as a heading (the page already shows it). There's no explicit job title given; maybe "ASL translator". We'll not repeat that as heading. We need to not put Job ID/requisition numbers as headings; none present. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit boilerplate besides maybe "For more information, please visit https://www.ashoka-usa.org/". That's not boilerplate; it's substantive info about the organization. Keep it. "Please let us know if you can help!" is like a call to action; maybe considered application instruction? It's not exactly instructions to apply, but it's a request to volunteer. Might be considered application instruction? The instruction says remove application instructions. That line is a call to action; maybe we should remove it. However it's part of the volunteer logistics? It's more like a request. Safer to remove it as it's an instruction to respond. We'll remove "Please let us know if you can help!". Also "Volunteer Logistics" heading is not a standard heading but we can treat as part of Schedule or maybe we keep as a heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests using those. However we could embed Volunteer Logistics content under Schedule and maybe Requirements. Let's see. Volunteer Logistics includes: Estimated hours required per week: 1; The estimated duration of the project is: 6-12 months; This position is Virtual (Remote). That's schedule/location info. So we can put under Schedule. Language Requirements English: that's a requirement. Desired Skills And Experience: ASL & English Fluency with ability to translate meaning and context in real time. Experience translating using live video software like Zoom. Confidentiality & Ethics - experience with confidentiality. Thus we can structure:

    About the role

    This is an unpaid, volunteer opportunity to work with Ashoka Staff. Ashoka is the world's largest association of leading social entrepreneurs in the world. We call them Ashoka Fellows and they're bringing their systems changing innovations to solve urgent social and environmental issues in 99 countries. We collaborate with our Fellows and numerous other partners to create a world where everyone can learn to access their own power to be changemakers for the good of all. For more information, please visit https://www.ashoka-usa.org/

    Responsibilities

    • As part of the life-long Fellowship program, the U.S. team hosts bi-monthly, virtual, Fellow-facilitated conversations over Zoom to support them personally, discuss strategy, and build community.
    • We are looking for an ASL translator to ensure our programming is accessible for all members of the network.
    • Topics have included succession planning and leadership transitions, using AI in the workplace, movement building in chaotic times, and democracy.
    • You'll have the chance to be in community with some of the brightest social entrepreneurs of our times and learn interesting things along the way.
    • These virtual sessions are 1hr long, with a combination of presentations and group conversation for 4-8 people.
    • They take place on Thursdays at 12:00PM or 12:30PM EST.
    But note that some of those items are more like schedule info (Thursdays at 12:00PM or 12:30PM EST) and session length. Might be better to put schedule info under Schedule section. However we already have schedule info in Responsibilities list; we could move those to Schedule. Let's decide: We'll have Responsibilities for duties: hosting bi-monthly virtual conversations, ASL translator, topics, chance to be in community, learn interesting things. The session length and timing maybe schedule. Thus: Responsibilities list: - As part of the life-long Fellowship program, the U.S. team hosts bi-monthly, virtual, Fellow-facilitated conversations over Zoom to support them personally, discuss strategy, and build community. - We are looking for an ASL translator to ensure our programming is accessible for all members of the network. - Topics have included succession planning and leadership transitions, using AI in the workplace, movement building in chaotic times, and democracy. - You'll have the chance to be in community with some of the brightest social entrepreneurs of our times and learn interesting things along the way. Schedule section: - These virtual sessions are 1hr long, with a combination of presentations and group conversation for 4-8 people. - They take place on Thursdays at 12:00PM or 12:30PM EST. -