Technical Sourcer | Engineering (Contract)

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: 1. About Ramp (company description) - this is prose, not a list 2. About The Role - prose description 3. What You'll Do - list of responsibilities 4. What You'll Need - list of requirements 5. Nice to Haves - list 6. Benefits Available To All Full-time Ramp Employees (Global) - list of benefits, with sub-sections for US, Canada, UK 7. Referral Instructions - prose 8. Other Notices - legal boilerplate (should be removed per rules) Rules: - Use

for section headings - Use

• for lists - Use

  for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Now, let me structure this: The posting has: - "About Ramp" - company description, prose - "About The Role" - role description, prose - "What You'll Do" - list of duties - "What You'll Need" - list of requirements - "Nice to Haves" - list - "Benefits Available To All Full-time Ramp Employees (Global)" - this is a benefits section with sub-sections for different countries. The heading says "Benefits Available To All Full-time Ramp Employees (Global)" then lists "Flexible PTO", "Centralized home-office equipment ordering", etc. Then "United States", "Canada", "United Kingdom" with specific benefits. This is a benefits section with real content, so I should include it. - "Referral Instructions" - prose, but this seems like application instruction boilerplate? The rule says remove application instructions. But "Referral Instructions" might be considered part of the process. However, the rule says "remove ... application instructions". I think this is an application instruction, so I should remove it. - "Other Notices" - legal boilerplate (San Francisco Fair Chance Ordinance, scam warning, privacy notice) - remove per rules. Also note: "This is a full-time, 6 month contract position" - this is schedule info. The rule says never create Schedule section unless posting actually states them. It does state "full-time, 6 month contract position". But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule (full-time, 6 month contract). However, the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is specific: full-time, 6 month contract. So I could include a Schedule section. But the rule says "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". The schedule is mentioned in the "About The Role" section. I could either fold it into a paragraph or create a Schedule section. Since it's a specific detail, I'll include it as a short paragraph maybe under "About The Role" or as a separate section. The rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Schedule might be considered metadata. I'll fold it into the role description. Similarly, "Benefits" section is substantial, so I'll include it. Now, for the benefits section: The heading is "Benefits Available To All Full-time Ramp Employees (Global)". Then a list of global benefits, then country-specific benefits. I'll structure as a main benefits section with sub-lists. Since we can only use

  for headings, I'll use

  for "Benefits" and then maybe use

  ? But the rule says use

  for section headings. It doesn't forbid

  , but says "use

  for section headings". I'll use

  for main sections, and for sub-sections like United States, Canada, UK, I could use

  or just include them as list items with bold? But the rule says use

  • for any list. The country-specific benefits are lists. I could make them nested lists. For example:

    Benefits

    • Flexible PTO
    • Centralized home-office equipment ordering
    ...
    • United States
      • 100% medical, dental & vision insurance coverage for you, with partial coverage for dependents
      ...
    ...
    But that might be messy. Alternatively, I could have separate

    for each country? But the rule says use

    for section headings like "Benefits". The countries are sub-sections of benefits. I think nested lists are fine. However, the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those are suggested. I'll keep Benefits as one section with nested lists. Now, let's write the HTML. I'll start with "About Ramp" as a section? The rule says use

    for section headings like "About the role". "About Ramp" is company description. I'll include it as a section with heading "About Ramp". But the rule says "do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the input, but the page already shows it. The input starts with "About Ramp". That's not the job title. The job title might be "Technical Sourcer" or something. But we don't have it. So I'll include "About Ramp" as a section. But the rule says "include a section ONLY when the posting has real, specific content for it". "About Ramp" has content. So I'll include. Similarly, "About The Role" has content. Now, "What You'll Do" -> Responsibilities "What You'll Need" -> Requirements "Nice to Haves" -> Qualifications or Nice to Haves "Benefits Available To All Full-time Ramp Employees (Global)" -> Benefits I'll map headings to the suggested ones: "About the role", "Responsibilities", "Requirements", "Qualifications", "Benefits". But the rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should use those exact headings? It says "e.g." so they are examples. I can use similar but not necessarily identical. However, to be safe, I'll use the standard ones: "About the role", "Responsibilities", "Requirements", "Qualifications", "Benefits". But the posting has "About Ramp" which is company description, not "About the role". I'll keep "About Ramp" as a heading? The rule doesn't forbid it. It says "use

    for section headings (e.g. ...)". So I can use other headings. I'll use "About Ramp" and "About the Role" as headings. But the rule says "do NOT repeat the job title as a heading". That's fine. Now, let's write. I'll output only the HTML fragment. Let's structure:

    About Ramp

    Ramp is building the smart infrastructure for finance teams, embedded in the transaction flow of every dollar a business spends. We automate how over $200B in annualized spend flows in and out of 70,000+ companies: authorizing payments, flagging risk, categorizing spend, and closing books. The problems are high-stakes, data-dense, and unforgiving. We hire people with high agency and high urgency. We look for slope over intercept. We care less about where you trained and more about what you’ve built. At Ramp, everyone is a builder who owns problems end to end and makes consequential decisions that shape the outcome. The median Ramp customer saves 5% and grows revenue 16% in their first year – far in excess of businesses operating without Ramp. We believe every ambitious company deserves the same. If you want to build systems that directly shape how companies move and manage billions, Ramp is the place to do it.

    About the Role

    As a critical member of our growing talent team, you will own building our sourcing engine to engage and hire world-class talent. This is an opportunity to partner directly with our talent dense Engineering teams. You will be the first point of contact for countless industry professionals, fully responsible for delivering an excellent candidate experience right from the start. This is a full-time, 6 month contract position.

    Responsibilities

    • Innovate and operationalize creative sourcing strategies to deliver top technical talent to Ramp
    • Own talent mapping research, referral generation, and sourcing campaigns
    • Effectively align candidates’ motivations with Ramp's value proposition, roles, and expectations
    • Lead intake meetings with stakeholders to qualify and deeply understand requirements/qualifications for tech job profiles
    • Manage pipeline activity reports and analyze historical data to optimize hiring impact
    • Drive Ramp’s engagement across external conferences, networking events, and professional association partnerships
    • Partner closely with recruiting leadership to anticipate upcoming headcount and proactively understand how new hires will fit into the organization
    • Build networks and long-term relationship for potential candidates and communities

    Requirements

    • 2+ years of technical sourcing experience in a similar role at a high-growth technology company or startup preferred
    • Familiarity with traditional and modern (AI) sourcing and search techniques
    • Excellent written and verbal storytelling communication skills
    • Ability to influence at various levels in an organization, anchoring on data-driven decision-making

    Qualifications

    • Demonstrated knowledge of Software Engineering job profiles
    • Experience with our suite of recruiting tools (Ashby, Claude Code, etc.)
    • Bachelor's degree from an accredited university

    Benefits

    • Flexible PTO
    • Centralized home-office equipment ordering
    • Health and wellness stipend
    • Budget for intra-office travel
    • Weekly coffee stipend
    • United States
      • 100% medical, dental & vision insurance coverage for you, with partial coverage for dependents
      • One Medical annual membership
      • 401(k), including employer match on contributions made while employed by Ramp
      • Fertility HRA (up to $10,000 per year)