Recruiter II (GTM)

We need to output HTML fragment with sections: headings

for each section that has content. Use

• for lists. Use

  for prose. No job title heading. No Job ID. Remove boilerplate: EEO, legal, etc. Also remove navigation, cookie, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. Let's extract sections: - The Role: description paragraph(s). It includes: "As Everlaw's first recruiter on the ground in Midtown Manhattan office in New York City, you'll help execute our go-to-market talent (GTM) acquisition strategy across NYC, Washington D.C., and the UK. You'll partner closely with sales and GTM leadership to build a high-performing, diverse pipeline that fuels our rapid expansion across key growth regions. There will be a large amount of independence to develop region-specific top of funnel strategies and refine the candidate experience in these very important offices. This is a full-time, exempt position based in our New York City office with a hybrid work schedule: in office M/W/Th with the option to work from home on Tu/Fr." We need to decide sections: maybe "About the role" heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these headings. We have responsibilities (what you'll do). We have requirements/qualifications (About you). We have benefits (Total Rewards & Benefits). We have Pay (salary range). We have Schedule (hybrid work schedule). Also maybe "About Everlaw" could be a section? Not in list but could be "About the company"? Not required. We can include if substantive but not required headings. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include sections for which we have content. Thus sections: - About the role (intro paragraph) - Responsibilities (what you'll do) - Requirements (or Qualifications) (About you) - Benefits (Total Rewards & Benefits) - Pay (salary range) - Schedule (hybrid work schedule) We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract each. About the role paragraph: The first paragraph(s) before "What you'll do...". It includes two sentences: "As Everlaw's first recruiter on the ground in Midtown Manhattan office in New York City, you'll help execute our go-to-market talent (GTM) acquisition strategy across NYC, Washington D.C., and the UK. You'll partner closely with sales and GTM leadership to build a high-performing, diverse pipeline that fuels our rapid expansion across key growth regions. There will be a large amount of independence to develop region-specific top of funnel strategies and refine the candidate experience in these very important offices. This is a full-time, exempt position based in our New York City office with a hybrid work schedule: in office M/W/Th with the option to work from home on Tu/Fr." But note schedule is also mentioned there; we might separate schedule into its own section. However the schedule info appears in that paragraph. We could still keep it in About the role or move to Schedule section. Since we have a Schedule section, we should extract schedule details there and maybe remove from About the role to avoid duplication. But instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move schedule to its own section, we still preserve it. It's okay to not duplicate. We'll need to ensure we don't lose any info. Thus About the role paragraph could be: "As Everlaw's first recruiter on the ground in Midtown Manhattan office in New York City, you'll help execute our go-to-market talent (GTM) acquisition strategy across NYC, Washington D.C., and the UK. You'll partner closely with sales and GTM leadership to build a high-performing, diverse pipeline that fuels our rapid expansion across key growth regions. There will be a large amount of independence to develop region-specific top of funnel strategies and refine the candidate experience in these very important offices. This is a full-time, exempt position based in our New York City office." Then Schedule section: "Hybrid work schedule: in office M/W/Th with the option to work from home on Tu/Fr." Now Responsibilities: bullet list under "What you'll do...". Let's extract each bullet: - Manage full-cycle recruiting for 6 to 10 active GTM requisitions across sales, business development, and customer success roles as we grow our footprint outside of HQ. - Partner directly with executives and hiring managers to design tailored talent strategies, align on role profiles, and sequence sourcing plans for critical growth hires. - Build and maintain robust, diverse candidate pipelines through targeted passive candidate outreach, referral programs, and strategic sourcing initiatives. - Design compelling closing strategies and compensation recommendations to land in-demand sales and GTM talent. - Leverage recruiting metrics and pipeline data to identify bottlenecks, refine interview processes, and present actionable insights to hiring partners. - Help evolve our regional recruiting footprint, establishing operational best practices and delivering an exceptional, candidate-first interview experience. These are list items. Now Requirements/Qualifications: "About you" paragraph with bullet-like sentences. Let's extract each: - You have at least 3 years of full-cycle recruiting experience, with a proven track record of sourcing and closing GTM talent in-house or in an agency setting. - You've built and executed proactive sourcing strategies for passive candidates across competitive GTM functions and regional markets. - You partner consultatively with hiring managers and business leaders to drive structured, equitable, and inclusive hiring decisions. - You're analytical and comfortable using recruiting data to tell stories, solve hiring challenges, and optimize pipeline health. - You excel at managing multiple hiring priorities independently with exceptional organization, attention to detail, and process control. - You have hands-on experience with Greenhouse applicant tracking system (ATS) and have found ways to leverage AI to help you be more effective in your role. - You are authorized to work in the United States. Please note that at this time, Everlaw is not sponsoring U.S. employment visas for this role. - Think you're missing some of the skills and are hesitant to apply? We do not believe in the 'perfect' candidate and encourage you to apply if you feel you can bring value to our team. We often revisit candidates who may have applied for a different role if something comes up that's a better fit. The last two sentences are more encouragement; still substantive. We'll keep them as part of Requirements. Now Benefits: Under "Total Rewards & Benefits". There's a list: Health & wellness - Comprehensive medical, dental, and vision coverage - Flexible Spending Accounts for health and dependent care expenses - Membership to Modern Health to support mental health and wellness - Paid parental leave - Company-sponsored life and disability insurance Financial rewards - Competitive equity grants, so you share in Everlaw's long-term growth - 401(k) plan with company matching of up to 4% of eligible annual compensation Growth & everyday perks - An accrual of 17 paid vacation days, 11 federal holidays, and paid sick leave - Hybrid work with regular work-from-home days and flexibility for life's logistics - Monthly home internet reimbursement, plus a stipend for your desk setup - Catered lunch each workday, plus snacks and company-wide events in our offices Note: Hybrid work appears again; but we already have schedule section. Might be duplicate; we can keep but maybe we should not duplicate. However we need to preserve all substantive info; duplication is okay but we could avoid duplication by not repeating. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but we should avoid unnecessary repetition? Not explicitly forbidden. However we already have schedule section; we could keep hybrid work mention in benefits as part of perks. It's okay. Now Pay: "The expected salary range for this role is $123,000 - $156,000. Final salary depends on factors including the candidate's experience and skills, and the base pay range is subject to change. This role is also eligible for equity and the benefits below." We already have benefits separate; we can keep pay section with salary range and note about equity eligibility. Now Schedule: we already extracted. Now we also have "About Everlaw" paragraph describing the company. Could be a section but not in list; we could include as "About the company" but not required. The instruction: use headings from the list; but we could also add other headings if needed? It 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 those as examples. Safer to stick to those. The About Everlaw paragraph is substantive; we could put it under "About the role"? Not exactly. Could be "About the company" but not in list. Might be better to omit? But we must preserve ALL substantive information. If we omit, we lose info. So we need to include it somewhere. Perhaps we can include it under "About the role" as a paragraph? But that would misrepresent. However we could add a heading "About Everlaw" even though not in the example list; the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not exclusive. So we can add other headings as needed. We'll add

  About Everlaw

  . Now we need to remove boilerplate: EEO, legal, etc. At the end there is a long EEO statement, privacy notice, Gem usage, etc. Remove all that. Also remove "The Team - Recruiting" paragraph? That's substantive about the team; we could include maybe under "About the team"? Not in list but we could add. However we already have "About Everlaw" covering company; the team paragraph is also substantive. We could include under "About the team" heading. But we need to decide if we want to add many sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we can incorporate team description into About Everlaw or About the role? The team paragraph: "The Recruiting team builds the teams that advance Everlaw's mission by connecting exceptional, diverse talent with meaningful work. It partners across the company to define what success looks like, attract strong candidates, and support fair, evidence-based hiring decisions. This work strengthens a scalable, quality-focused hiring engine that raises talent density while delivering a candidate experience worthy of Everlaw's award-winning culture." That's substantive about the team. Could be included under "About the role" as context, but maybe better to have a separate "Team" section. However to keep few sections, we could merge into About Everlaw or About the role. I'd lean to add a "Team" heading (though not in list) but it's still a section. The instruction says prefer few sections; adding another section increases count. But we already have many sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule, About Everlaw. That's 7. Adding Team makes 8. Might be okay. But we could incorporate team description into About Everlaw (makes sense). Let's do that: About Everlaw section includes both company description and team description. Thus About Everlaw paragraph: combine the company description and the team paragraph. Now we need to ensure we didn't miss any substantive info: The line "Think you're missing some of the skills and are hesitant to apply? We do not believe in the 'perfect' candidate and encourage you to apply if you feel you can bring value to our team. We often revisit candidates who may have applied for a different role if something comes up that's a better fit." This is encouragement; we kept it in Requirements.