Data Partnerships Representative

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. We have sections: About Handshake (company description) – not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. So we need to produce sections based on content. We need to extract: - About the role: description of role (the "About The Role" paragraph). That's substantive. - Responsibilities: list of duties (the bullet points under "Run high-volume outbound..." etc). Those are responsibilities. - Requirements: maybe "Desired Capabilities" list (1-2 years experience etc). That's requirements/qualifications. - Qualifications: maybe "Extra Credit Experience" list? Could be qualifications. - Skills: maybe not explicit; could combine capabilities. - Benefits: "Perks" section with bullet list of benefits. - Pay: Not mentioned explicitly (no salary). So we should NOT include Pay section. - Schedule: Not mentioned explicitly. So omit. We must not include sections with placeholder text. So we include only those with real content. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the text as is, but format into HTML. We need to use

for each section heading. Use

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

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes some boilerplate like "Explore our mission, values, and comprehensive US benefits at joinhandshake.com/careers." That's maybe okay to keep? It's not boilerplate? It's a link. Might be considered navigation? Probably safe to keep as part of benefits? It's a call to action. Might be considered application instruction? It's not exactly application instruction but could be considered promotional. The instruction says remove application instructions. That line is not exactly instruction to apply but a link to explore benefits. Might be considered boilerplate. Safer to drop it. Also need to drop duplicated lines. We need to preserve all substantive info: company description maybe not needed as heading but could be included as a short paragraph before sections? The instruction says we should not repeat job title as heading; we can include a short

  for company overview? It didn't forbid. It says "fold minor metadata into a short

  or drop it." The company description is not minor metadata; it's substantive but not a required section. Could be included as a leading

  before sections. Probably okay. But we need to output only HTML fragment, no /. So we can start with maybe a

  about Handshake, then sections. Let's extract content: About Handshake (company description): "Handshake was founded on a simple belief that everyone deserves a path to a great career, regardless of where they went to school or who they know. Today, we power 25 million job seekers, 1 million+ employers, and 1,600 educational institutions. In 2025, we started Handshake AI and built the fastest-growing AI data business in history. We work directly with frontier AI lab researchers to create evaluations, publish benchmarks, and push the boundary of data. We’ve grown from $0 to ~$1B run rate and pay ~$60M to over 30K individuals every month." Why Join Handshake Now (maybe not needed as heading). Could be considered part of About the role? But it's motivational. Might be considered part of About the role? The instruction says include a section ONLY when the posting has real, specific content for it. The "Why Join Handshake Now" is a section with bullet points? Actually it's a paragraph with bullet-like lines: "Shape how every career evolves..." etc. That's substantive. Could be part of About the role or maybe a separate section like "About the company". But we only have predefined headings; we could put it under About the role? But About the role already has its own content. Might be better to treat "Why Join Handshake Now" as part of the company description, maybe as a

  after the company overview. But we need to avoid duplication. Let's see the text after "Why Join Handshake Now": It's a paragraph with multiple sentences separated by line breaks? Actually it's: "Why Join Handshake Now Shape how every career evolves in the AI economy, at global scale, with impact your friends, family and peers can see and feelPartner hand-in-hand with world-class AI labs, Fortune 500 partners and the world’s top educational institutionsWork together with engineers, scientists, operators, and more from Palantir, Meta, Scale AI, and former YC foundersBuild a massive, fast-growing business with billions in revenue" It seems missing punctuation; it's a run-on. We'll keep as is. Then "About Handshake AI Human data is the core infrastructure to AI advancement...." That's also company description. Then "About The Role" heading. Thus we can produce:

  Handshake was founded on a simple belief that everyone deserves a path to a great career, regardless of where they went to school or who they know. Today, we power 25 million job seekers, 1 million+ employers, and 1,600 educational institutions. In 2025, we started Handshake AI and built the fastest-growing AI data business in history. We work directly with frontier AI lab researchers to create evaluations, publish benchmarks, and push the boundary of data. We’ve grown from $0 to ~$1B run rate and pay ~$60M to over 30K individuals every month. Why Join Handshake Now Shape how every career evolves in the AI economy, at global scale, with impact your friends, family and peers can see and feelPartner hand-in-hand with world-class AI labs, Fortune 500 partners and the world’s top educational institutionsWork together with engineers, scientists, operators, and more from Palantir, Meta, Scale AI, and former YC foundersBuild a massive, fast-growing business with billions in revenueAbout Handshake AI Human data is the core infrastructure to AI advancement. Frontier AI labs currently improve model capabilities with various data-intensive post-training techniques. We believe that data spend for AI training will increase by 3-5x in the next few years and continue for much longer as models take on new domains. Handshake AI supports all of the frontier AI labs, working on their most complex data at the largest scale.

  But that's a huge paragraph; maybe better to split into multiple

  for readability. However instruction: use

  for prose. So we can have multiple

  elements. Now About The Role: we need heading

  About the role

  then

  with the prose. Then Responsibilities: heading

  Responsibilities

  then
  • each bullet. Responsibilities bullet list from the posting: - Run high-volume outbound (calls, email, LinkedIn) against a target account list to find companies with data worth licensing - Get past the gatekeeper and onto a real conversation with an owner, founder, CTO, or Head of Data - Run thorough discovery, not a five-minute qualifier. You need to actually understand what data a company has, how it's structured, who has the authority to sell it, and what would make them comfortable saying yes, before you ever talk price - Handle real hesitation and real objections (competitive fears, security concerns, "why should I trust you with this") with patience, not pressure - Own the deal end to end: scoping, looping in legal/security when needed, negotiating terms, and getting to signature - Hit weekly activity and pipeline targets; this is still a numbers game, just not only a numbers game - Help build the playbook as you go: scripts, target lists, and process will all be actively evolving in your first 90 days We need to keep them as list items. Then Requirements/Qualifications/Skills: The posting has "Desired Capabilities" list and "Extra Credit Experience". We need to map to sections. We have headings: Requirements, Qualifications, Skills. We need to decide what goes where. The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements, Qualifications, Skills sections. We need to include only if there is real specific content. We have Desired Capabilities (1-2 years of prospect or customer facing, high volume outbound sales experience... etc). That's like requirements/qualifications. Extra Credit Experience list: selling into technical buyers, background in data licensing, etc. That could be "Skills" or "Qualifications". We could put Desired Capabilities under Requirements, and Extra Credit under Skills (or Qualifications). But we need to avoid duplication. Better: Requirements: Desired Capabilities list. Qualifications: maybe empty? But we cannot emit heading with filler. So we should not include Qualifications if no specific content distinct from Requirements. However we have Extra Credit Experience which is specific content; we could treat that as Skills. Thus:

    Requirements

    • 1-2 years of prospect or customer facing, high volume outbound sales experience: ideally your second sales role, somewhere with real activity metrics and a track record of quota attainment. A background at a comparable high-velocity outbound sales floor is a strong signal, not a requirement
    • Genuinely comfortable with high-intensity, fast-moving environments. This is an early-stage build inside a fast-growing AI company; the hours and pace reflect that
    • Coachable, not just hard-charging. You can take an "always be closing" instinct and adapt it into "always be understanding" when the moment calls for it
    • A real discovery mindset: you ask more questions than you answer on a first call, and you're comfortable not pitching until you actually understand the situation
    • Composure under a hard or awkward conversation. Asking a company to hand over its data is not a normal sales ask; the reps who win here can sit in that discomfort instead of rushing past it
    • Process discipline: clean notes, real follow-through, nothing goes cold in your pipeline
    • Comfortable with ambiguity: there's no fully-built playbook yet; you're helping write it
    Then Skills:

    Skills

    • Extra Credit Experience selling into technical buyers (CTOs, Heads of Data/Eng)
    • Background in data licensing, ad-tech data, enterprise SaaS, or API/platform sales
    • Familiarity with data privacy or compliance basics (GDPR/CCPA); we'll train this either way
    We could also include any other skills like "comfortable with high-intensity..." but that's already in Requirements. Now Benefits: we have "Perks" section with bullet list. We need to output

    Benefits

    then
    • each. List: - Ownership: Equity in a fast-growing company - Financial Wellness: 401(k) match, competitive compensation, financial coaching - Family Support: Paid parental leave, fertility benefits, parental coaching - Wellbeing: Medical, dental, and vision, mental health support, $500 wellness stipend - Growth: $2,000 learning stipend, ongoing development - In Office Perks: Internet, commuting, and lunch stipend - Time Off: Flexible PTO, 15 holidays + 2 flex days