Contract Technical Sourcer

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. The posting includes description of role, responsibilities, requirements, qualifications, skills, benefits (but note: it's a contractor, not eligible for benefits). The posting says: "A Note About Benefits This is a 90-day, 1099 independent contractor engagement and is not eligible for employee benefits or equity." So there is no benefits for contractor. Should we include Benefits section? The instruction: never create Benefits sections unless posting actually states them. It does state something about benefits (that there are none). But it's not a benefit offering; it's a statement that there are none. Should we include a Benefits section? The rule: 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. The posting does state that it's not eligible for employee benefits or equity. That is specific content about benefits (lack thereof). So we could include a Benefits section with that statement. However, the instruction also says "Prefer a few substantive sections over many thin ones." Might be okay. Pay: The posting does not mention pay/salary. No mention. So we should not include Pay section. Schedule: Not mentioned. So no Schedule. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits (maybe). Let's parse content. About the role: The initial paragraph about Assured mission, claims processing, etc. Could be considered About the role. Also the contract description: "This contract has the potential to extend based on business needs and performance." That's about the role. Responsibilities: The bullet list under "Some of the Problems You'll Solve:" and "How You'll Make an Impact:" and maybe "You'll Probably Thrive Here If You:"? Actually those are more like traits. Responsibilities likely include: identifying and engaging exceptional software engineering talent, partnering with recruiters, building pipelines, designing creative searches, engaging candidates, tracking activity, maintaining candidate info, etc. Requirements/Qualifications/Skills: Overlap. The posting includes "You'll Probably Thrive Here If You:" which lists traits: love the hunt, search creatively, recognize exceptional technical talent, know how to engage engineers, experiment and adapt, use technology thoughtfully, partner well, bring experience with modern recruiting tools. Also earlier: "As a Contract Technical Sourcer, you'll spend time identifying and engaging exceptional software engineering talent. You'll partner with recruiters and hiring leaders to understand what great looks like, translate hiring needs into creative sourcing strategies, and build high-quality pipelines for critical Staff+ engineering roles." That's responsibilities. Qualifications maybe: Experience with LinkedIn Recruiter and Ashby is a plus, but curiosity, resourcefulness, and sourcing craft matter most. Also maybe need to be able to use AI tools. Skills: Could list: sourcing, Boolean search, LinkedIn Recruiter, GitHub, technical blogs, conference speaker lists, talent intelligence, AI tools (Claude, Codex), outreach, tracking in Ashby, etc. We need to avoid repeating job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a scam warning and EEO statement at end; we must remove those. Also remove "Our Commitment: We are an equal opportunity employer..." etc. Also remove the note about falsely posing as recruiters? That's a scam warning; remove. Also remove the line about "If this engagement results in an eligible full-time position, the benefits outlined below would apply..." That's part of benefits note; we might keep the benefits statement but maybe we should keep only the contractor note: "This is a 90-day, 1099 independent contractor engagement and is not eligible for employee benefits or equity." That's specific. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details like "90-day, 1099 independent contractor engagement". Also mention potential to extend. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to output only HTML fragment. Let's structure:

  About the role

  Assured is on a mission to modernize insurance... (the mission paragraph) ... This contract has the potential to extend based on business needs and performance.

  Maybe also include the note about contractor: "This is a 90-day, 1099 independent contractor engagement and is not eligible for employee benefits or equity." Could be part of About the role or Benefits. Better to put that in Benefits section.

  Responsibilities

  • Identify and engage exceptional software engineering talent.
  • Partner with recruiters and hiring leaders to understand what great looks like and translate hiring needs into creative sourcing strategies.
  • Build high-quality pipelines for critical Staff+ engineering roles.
  • Design creative searches using LinkedIn Recruiter, Boolean techniques, GitHub, technical blogs, conference speaker lists, web research, talent intelligence, and unconventional sourcing channels.
  • Engage candidates with thoughtful, personalized outreach that connects their specific systems experience and career motivations with the opportunity.
  • Track sourcing activity, candidate engagement, pipeline progress, and search effectiveness to understand what is working and where to iterate.
  • Maintain accurate, timely candidate information and activity in Ashby or a similar applicant tracking system.

  Requirements

  • Love the hunt – genuine enjoyment of sourcing and finding engineers others might miss.
  • Think beyond job titles and familiar company lists; use adjacent tech stacks, GitHub activity, career patterns, technical communities, conference speaker rosters, and other signals.
  • Recognize exceptional technical talent – able to read a technical background, identify transferable systems experience, and distinguish keyword matches from true Staff+‑level engineers.
  • Know how to engage engineers with concise, personalized, technically credible outreach that earns attention and starts meaningful conversations.
  • Experiment and adapt – treat sourcing as an iterative process, learn from the market, and quickly change direction when a strategy isn’t producing results.
  • Use technology thoughtfully – excited to use AI tools such as Claude, Codex, or similar platforms to make technical research and outreach more creative, efficient, and effective.
  • Partner well with others – communicate clearly, welcome feedback, and build strong working relationships with recruiters, hiring managers, and engineering leaders.
  • Bring experience with modern recruiting tools (LinkedIn Recruiter, Ashby) is a plus, but curiosity, resourcefulness, and sourcing craft matter most.
  We could also have Qualifications and Skills sections, but they'd overlap. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one? But we have to use headings only if there is real specific content. We could have Requirements (covering traits) and Skills (covering tools/techniques). However, the traits could be considered qualifications. The posting also mentions "You'll Probably Thrive Here If You:" which is more about traits/qualifications. The earlier bullet about "As a Contract Technical Sourcer, you'll spend time..." is responsibilities. The "Some of the Problems You'll Solve:" and "How You'll Make an Impact:" are also responsibilities. Thus we could have: - About the role - Responsibilities - Qualifications (or Requirements) - Skills (maybe tools) - Benefits (contractor note) But we need to avoid thin sections. Let's see if we can combine Qualifications and Skills into one section called "Requirements & Skills". However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid combining, but we should follow the headings list if we use them. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests we can use those headings. It doesn't say we must use all; we can pick subset. Thus we could have:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...

  Skills

  ...

  Benefits

  This is a 90-day, 1099 independent contractor engagement and is not eligible for employee benefits or equity. There may be an opportunity to extend the contract or transition into a full-time position based on business needs and performance, but neither is guaranteed.

  But we need to ensure we don't repeat content. The responsibilities list already includes many items; the requirements list includes traits; skills list includes specific tools/techniques. Let's extract skills from posting: "Design creative searches using LinkedIn Recruiter, Boolean techniques, GitHub, technical blogs and conference speaker lists, web research, talent intelligence, and unconventional sourcing channels." Also "Use AI tools such as Claude, Codex, and similar platforms to accelerate technical research, generate new search ideas, personalize outreach, and improve efficiency." Also "Track sourcing activity, candidate engagement, pipeline progress, and search effectiveness" (maybe more responsibility). Also "Maintain accurate, timely candidate information and activity in Ashby or a similar applicant tracking system." Also "Partner closely with recruiters and hiring managers to calibrate profiles, share market insights on the engineering talent landscape, and adjust sourcing strategies as searches evolve." That's responsibility. Skills could be: LinkedIn Recruiter, Boolean search, GitHub, technical blogs, conference speaker lists, web research, talent intelligence, unconventional sourcing channels, AI tools (Claude, Codex), Ashby ATS, sourcing analytics, outreach personalization. We'll list them. Now ensure we don't include any boilerplate: remove the scam warning, EEO, etc. Also remove the line about "We have been made aware of individuals falsely posing as recruiters..." and the EEO commitment. Also remove the line about "Our Commitment: We are an equal opportunity employer..." etc. Also remove the repeated line about "If this engagement results in an eligible full-time position, the benefits outlined below would apply..." We'll keep the contractor note but not the conditional full-time benefits. We need to preserve all substantive information: The note about potential to extend, the 90-day contractor, not eligible for benefits, etc. We'll include that in Benefits. Now check for any duplicated lines: The posting repeats some phrases; we need to ensure we don't duplicate. Let's craft the HTML. We'll start with About the role paragraph: combine mission description and contract note? Actually contract note about potential to extend belongs maybe in About the role. We'll include it there. Paragraph: "Assured is on a mission to modernize insurance. Claims processing (i.e. should we pay this claim?), while often overlooked, is the foundation of the entire industry. It’s currently highly manual, involving phone calls, faxes, and gut instinct, costing tens of billions of dollars a year. We can do better. At Assured, we provide large insurers with the software solutions they need to win in a modern, technology-driven world. From self-service claim-filing software to backend fraud detection, we’re the engine that powers claims processing for some of the largest insurers in the world. The challenges we face are deep and diverse, from creating digital experiences that provide comfort and clarity to claimants at their most stressed and vulnerable to orchest