Sales Development Representative (US/Tech Sales)

We need to output HTML fragment with sections: About the Company, About the Role, Responsibilities, Qualifications, Benefits, Pay (if present). Also maybe "Skills"? The posting includes Required Skills and Preferred Skills; we could combine into a Skills section. But we need to follow rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and extract sections. Let's extract content: - About the Company: paragraph describing Stream powers real-time Chat, Video, Activity Feeds, AI Moderation for billions of end-users across thousands of apps, from Strava and Bumble to eBay and Patreon. Our platform processes billions of API requests per month and supports applications with millions of concurrent users, while delivering highly reliable, low-latency services and a great developer experience. - About the Role: The role We're looking for a Sales Development Representative . It's a fast way to learn technical sales and own real revenue impact. Expect to craft thoughtful outbound messaging, run crisp qualification through cold calls, and personalise your outreach daily. This is a full-time role based in our Boulder office, three days a week in the office. We could combine "About the Role" as a section heading

  About the Role

  with paragraph(s). The "The role" phrase is part of the content. - Responsibilities: The section "Responsibilities What will you work on You'll partner with our Account Executives on moderation outbound, and work with managers to test new outbound ideas. Day to day, you'll write outbound messaging that's worth reading, run sharp qualification on cold calls, and personalize your outreach rather than blasting templates. Identify, research, and qualify new business through targeted outbound prospectingRun strong discovery to understand a prospect's needs and connect them to StreamBook qualified meetings with ICP prospects across phone, email, LinkedIn, and creative outreachWork closely with AEs: join intro calls and make the handoff cleanHit your activity and pipeline goals by keeping the top of funnel healthyKeep CRM data accurate in SalesforceKnow Stream's AI moderation product, value, ICP, and competitors well enough to speak to them naturally" We need to break into list items for duties. The text is a bit run-on; we can split by sentences. Let's extract bullet points: - Partner with our Account Executives on moderation outbound, and work with managers to test new outbound ideas. - Write outbound messaging that's worth reading, run sharp qualification on cold calls, and personalize your outreach rather than blasting templates. - Identify, research, and qualify new business through targeted outbound prospecting. - Run strong discovery to understand a prospect's needs and connect them to StreamBook qualified meetings with ICP prospects across phone, email, LinkedIn, and creative outreach. - Work closely with AEs: join intro calls and make the handoff clean. - Hit your activity and pipeline goals by keeping the top of funnel healthy. - Keep CRM data accurate in Salesforce. - Know Stream's AI moderation product, value, ICP, and competitors well enough to speak to them naturally. We'll put these in
  • . - Qualifications: The section "Qualifications About You You're motivated, curious, and comfortable with a "no" on the way to a "yes." You think about outbound strategically, you like running experiments, and a fast-changing environment suits you. You're a self-starter who wants to learn the fundamentals of technical sales and contribute to revenue from the start. Required Skills You have: Cold calling and emailing skills you can point to results forExperience with CRMs and sales engagement toolsStrong business sense and the ability to think on your feetClear, persuasive written and verbal communicationResilience: you handle rejection and stay motivatedExperience in a fast-paced, goal-oriented environment Preferred Skills 6+ months of SDR or outbound lead-gen experience at a tech companyExperience at a SaaS startupExposure to API-driven or developer-focused productsExposure to Trust & Safety, content moderation, or risk/fraud" We need to separate Qualifications (maybe about you) and Skills. The instruction says we can have sections like Qualifications, Skills. We could combine Required Skills and Preferred Skills under a Skills section. But we also have a Qualifications section about personal traits. Let's decide: We'll have

    Qualifications

    with paragraph about personal traits (motivated, curious, etc.) and maybe also include Required Skills? But they said use
    • for any list of duties/requirements/benefits. So Required Skills and Preferred Skills are lists; we should put them under a Skills section as
      . The Qualifications section could be about personal traits (About You). Let's do that. Thus:

      Qualifications

      You're motivated, curious, and comfortable with a "no" on the way to a "yes." You think about outbound strategically, you like running experiments, and a fast-changing environment suits you. You're a self-starter who wants to learn the fundamentals of technical sales and contribute to revenue from the start.

      Then

      Skills

      with two lists: Required Skills and Preferred Skills. Could we separate into two subheadings? The instruction only mentions using

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings, but we should avoid extra headings unless needed. Could combine Required and Preferred into one list? Might lose distinction. Better to have two

      with preceding

      indicating Required Skills and Preferred Skills. Or we could have

      but not allowed? The instruction only says use

      for section headings; doesn't forbid other headings but says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use h3 for those sections; we could still use other headings for sub-sections but maybe not needed. Safer to just have one Skills section with two paragraphs: one for Required Skills (list) and one for Preferred Skills (list). We'll put each list preceded by a short

      like "Required Skills:" then

      . That should be fine. - Benefits: The posting includes "Pay range and compensation package Stream employees enjoy some of the best job benefits in the industry: 19+ days of paid time off plus 10 paid holidaysHybrid work flexibility (3 days a week from the office)Free health insurance for the employee and partial coverage for dependents (80% contribution coverage for health and 100% for dental and vision)401k contribution plan with 4% matchFitness stipendCompany equityDog-friendly office!A Macbook Pro providedA Learning and Development budgetTeam lunches and plenty of snacksRTD pass + free parking pass on Pearl StreetAn office on Pearl Street in downtown Boulder12 weeks paid parental leave for primary parentsThe opportunity to attend or present to global conferences and meetupsThe possibility to visit our office in Amsterdam Note: this list of benefits applies to Colorado-based employees and is adjusted per your location of residence." We need to extract benefits as list items. Let's parse: - 19+ days of paid time off plus 10 paid holidays - Hybrid work flexibility (3 days a week from the office) - Free health insurance for the employee and partial coverage for dependents (80ents (80% contribution coverage for health and 100% for dental and vision) - 401k contribution plan with 4% match - Fitness stipend - Company equity - Dog-friendly office - A Macbook Pro provided - A Learning and Development budget - Team lunches and plenty of snacks - RTD pass + free parking pass on Pearl Street - An office on Pearl Street in downtown Boulder - 12 weeks paid parental leave for primary parents - The opportunity to attend or present to global conferences and meetups - The possibility to visit our office in Amsterdam Also note: "Note: this list of benefits applies to Colorado-based employees and is adjusted per your location of residence." That's a note; we could include as a paragraph after the list. - Pay: The posting includes "Salary (for Colorado only) Our salary ranges are based on national averages. We have wide ranges so we can be flexible and determine compensation based on a number of factors including the candidate's skills, level of experience, and location. For Colorado-based candidates we offer a salary $55,000 to $75,000 (OTE). Compensation at all other locations will be based on the factors as stated above." Thus we have Pay section with specific salary range for Colorado. We should include that. The instruction says include Pay section only if posting actually states them. Yes, it does. So we will have

      Pay

      with paragraph(s). We should not include filler like "commensurate with experience". The text includes specifics: $55,000 to $75,000 (OTE). We'll include that. - Schedule: The posting mentions "This is a full-time role based in our Boulder office, three days a week in the office." That's schedule info (hybrid). Could be considered Schedule section. The instruction says include Schedule section only if posting actually states them. It does mention three days a week in the office. However, we already have hybrid work flexibility in Benefits. But we could still include Schedule section with that detail. However, we should avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we incorporate schedule info into About the Role or Benefits. But we have a Benefits section already includes hybrid work flexibility. So we could omit a separate Schedule section to avoid thin section. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule (three days a week). But we already have that in Benefits. However, we could still include Schedule but it might be thin. Better to incorporate schedule into About the Role or Benefits. Since Benefits already includes hybrid work flexibility, we can keep Benefits and not add Schedule. Thus sections: About the Company, About the Role, Responsibilities, Qualifications, Skills, Benefits, Pay. Check for any other sections like Requirements? Not needed. Now we need to ensure we remove boilerplate: Equal Opportunity Statement, Additional Information (Why This Role Matters, What Makes Stream Exciting) - those are boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why This Role Matters" and "What Makes Stream Exciting" might be considered substantive? They are more marketing but could be considered part of the posting. However, they are not explicitly listed as sections to keep; but they are not boilerplate. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep them if they are substantive. However