Specialist, Volunteer Selection

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting. Job Title: Specialist, Volunteer Selection Team: Volunteer Team (External Affairs) Location: Remote from one of our current Braven operating states: GA, IL, NY, & NJ Employment Type: Part-time, fixed term until June, 2027 FLSA Classification: Non-Exempt Start Date: ASAP About Braven: description. About The Role: description. What You'll Do: bullet points. Requirements: Minimum Requirements and Preferred Qualifications. Work Demands: remote location, hours, etc. Additional Requirements: Authorized to work in the U.S, no visa sponsorship. Application & Interview Process: description (but we must remove application instructions? The instruction says remove application instructions. The "Application & Interview Process" includes phone screen etc. That's arguably application instructions. Should we remove? Likely yes, as it's part of application process. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the Application & Interview Process section. Benefits Compensation and Benefits: includes compensation description and hourly rate $25 per hour. Also mentions benefits? It says "Braven offers competitive hourly rates...". No explicit benefits like health etc. So we can include Pay section with $25 per hour. Benefits maybe not detailed; we might omit Benefits section if no specific benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated: $25 per hour. Schedule: "Hours vary between 15 and 28 hours per week depending on the recruitment cycle, with lighter weeks during off-peak periods." Also "Weekdays, 11am - 5pm ET Weeknight events, 5-8pm ET Occasional Saturday mornings". So we have schedule info. Benefits: The posting mentions "Compensation and Benefits" but only describes compensation; no explicit benefits like health insurance, retirement, etc. So we should not create a Benefits section unless there is real specific content. Since they only talk about compensation, we can put that under Pay. Benefits section would be empty or filler, so omit. We also have location info: remote from GA, IL, NY, NJ. That's not a heading; we can include in a

maybe under About the role or as a separate section? There's no heading for Location; but we could include it under About the role or as a separate paragraph. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Location is metadata; we can include in a short

. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections with real specific content. Let's map: - About the role: we have "About The Role" paragraph describing purpose. That's substantive. - Responsibilities: "What You'll Do" includes Volunteer Selection (80%) and Administration Duties (20%). That's responsibilities. - Requirements: "Minimum Requirements" (At least 2 years of experience with hiring, interviewing, and/or recruiting). That's requirements. - Qualifications: "Preferred Qualifications" list. That's qualifications. - Skills: Could be derived from preferred qualifications (interpersonal, organizational, communication skills, judgment, etc.) but we already have qualifications. The instruction says we can have Skills section; but we might combine with Qualifications. However we need to decide if we should create a Skills section. The posting does not have a separate "Skills" heading; but we could extract skills from preferred qualifications. However we must not invent sections if not present? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we cannot create a Skills section if we have content that fits under skills. The posting does have skill-related content (Strong interpersonal, organizational, and communication skills; Exceptional judgment; Experience with legal and professional interview note-taking; etc.). So we could create a Skills section with those items. However we also have a Qualifications section for preferred qualifications. Might be overlapping. Better to follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. We can treat: - About the role: the paragraph about role purpose. - Responsibilities: the "What You'll Do" bullet points. - Requirements: Minimum Requirements (at least 2 years experience). - Qualifications: Preferred Qualifications (the list of items). Could be considered qualifications. - Skills: maybe we can extract specific skill items from the preferred qualifications that are skill-oriented: Strong interpersonal, organizational, and communication skills; Exceptional judgment; Experience with legal and professional interview note-taking; Highly organized with strong follow-through; Familiarity with Calendly; Google Suite; Salesforce; Zoom; Ability to work independently; Demonstrated commitment to equity and inclusion; Exemplification of Braven's core values; Experience that has informed belief in Braven's mission. Some of these are more qualifications/experience. But we can still list them under Skills. But to avoid duplication, maybe we put the list under Qualifications and leave Skills empty? But we must not emit empty heading. So we need to decide: either combine Qualifications and Skills into one section (maybe Qualifications) and omit Skills. However the instruction says we should prefer a few substantive sections over many thin ones. So we could omit Skills if it would be thin or duplicate. Let's see if we have enough distinct content for Skills separate from Qualifications. The preferred qualifications list includes skills, experience, qualities. It's ambiguous. Safer to follow the instruction: include a section only when posting has real specific content for it. The posting does not have a explicit "Skills" heading, but it does have skill-related content. However we could argue that the content is already captured under Qualifications. If we create a Skills section, we would be duplicating or splitting the same list, making thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to not create a Skills section; instead put skill-related content under Qualifications (or Requirements). But we already have Requirements for minimum experience. Qualifications can hold the preferred qualifications list (which includes skills, experience, qualities). That seems appropriate. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Benefits omitted. Now we need to format: - Use

for section headings. - Use

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

  for prose. We must not repeat job title as heading. We need to include location info maybe as a short

  after About the role? Or incorporate into About the role? The location is metadata; we can add a short

  after About the role: "Location: Remote from one of our current Braven operating states: GA, IL, NY, & NJ." But we must not repeat job title. That's fine. Also employment type: Part-time, fixed term until June, 2027. FLSA Classification: Non-Exempt. Start Date: ASAP. Could be included as metadata paragraph. We need to preserve all substantive information. So we should include those details somewhere. We could create a

  after About the role that includes: "Employment Type: Part-time, fixed term until June, 2027. FLSA Classification: Non-Exempt. Start Date: ASAP. Location: Remote from one of our current Braven operating states: GA, IL, NY, & NJ." That seems okay. Now let's draft. Section About the role: combine the "About Braven" and "About The Role"? Actually "About Braven" is organization description; could be part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put Braven description under About the role? Might be better to have About the role include both Braven description and role description. But we have separate "About Braven" paragraph. We'll include it in About the role section as prose. Thus About the role section:

  About the role

  then

  containing Braven description and role description. But we must not repeat job title as heading; fine. Now Responsibilities:

  Responsibilities

  then
  with items from "What You'll Do". Need to capture both Volunteer Selection (80%) and Administration Duties (20%). We'll break into list items. Volunteer Selection - 80%: we can split into sub-items? Could keep as one list item with semicolons. Better to keep as one item: "Develop a strong understanding of Braven's Leadership Coach and Professional Mentor programs, including requirements, rubrics, and volunteer profiles, to assess and select high-quality volunteers; Conduct and assess Leadership Coach volunteer interviews using Braven's Interview Guide, including both live Zoom interviews and asynchronous review of recorded video submissions; Review Professional Mentor volunteer applications using Braven's rubric and resources; Make selection recommendations (accept, reject, waitlist, etc) for Leadership Coaches and Professional Mentors, grounded in evidence and aligned with established rubrics; Update Salesforce records and ensure data accuracy." Administration Duties - 20%: "Respond to selection recommendation-related inquiries from staff; Assist Volunteer Coordinators with volunteer selection audit resolution as needed; Other duties as assigned." We'll put each as separate
  • . Now Requirements:

    Requirements

    then
    with Minimum Requirements: "At least 2 years of experience with hiring, interviewing, and/or recruiting." Now Qualifications:

    Qualifications

    then
    with Preferred Qualifications list items. List them: - Strong interpersonal, organizational, and communication skills - Exceptional judgment, with the ability to make detailed, rubric-based selection recommendations - Experience with legal and professional interview note-taking; handles confidential, sensitive information with absolute discretion - Highly organized with strong follow-through; comfortable managing multiple tasks and deadlines across a fast-moving recruitment cycle - Familiarity of and comfort with Calendly - Familiarity of and comfort with Google Suite (Gmail, Sheets, Docs, Slides) - Familiarity of and comfort with Salesforce - Familiarity of and comfort with Zoom virtual meetings - Ability to work independently and exercise good judgment about when to escalate or ask for guidance - Demonstrated commitment to equity and inclusion - Exemplification of Braven's core values - Experience that has informed your belief in Braven's mission and has prepared you to work with, or for, Braven's student Fellow population Also note: "Please know that no one ever meets 100% of the preferred qualifications. If much of this describes you, we encourage you to apply." That's more encouragement; we could include as a

    after the list, but it's not a list; it's prose. We'll add a

    after the list. Now Pay:

    Pay

    then

    with compensation info: "The hourly rate for this role is set at $25 per hour." Also maybe mention that it's competitive hourly rates based on midpoint of market among not-for-profit organizations of similar size. We'll include that. Now Schedule:

    Schedule

    then

    with schedule info: "Hours vary between 15 and 28 hours per week depending on the recruitment cycle, with lighter weeks during off-peak periods. Expected availability: Weekdays, 11