Partnerships Associate

We need to output HTML fragment with sections: About the role, Responsibilities (You Will), Requirements (You Have), Benefits (Perks), Pay (salary ranges). Also maybe About Us and About The Team? The instructions: 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. 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. We need to decide which sections to include. The posting includes About Us, About The Team, About The Role, You Will (responsibilities), You Have (requirements), Perks (benefits), Pay (salary ranges). Also location info (You can work from ...). That could be part of About The Role or maybe a separate section? The instructions say we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some. We should not include About Us or About The Team as separate sections unless they have real specific content? They do have content, but the instruction list didn't mention About Us or About The Team as headings to use. However we could still include them if we want, but the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. It says "include a section ONLY when the posting has real, specific content for it". So we could include About Us and About The Team as sections if we want, but they might be considered boilerplate? They are substantive but not required. The instruction says "Prefer a few substantive sections over many thin ones." So maybe we should combine About Us and About The Team into a brief intro paragraph? But we must preserve ALL substantive information; we cannot drop details. However we could embed them in a

under a heading like "About Twitch" or something. But the instruction didn't forbid adding other headings; it just gave examples. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings where applicable. It doesn't forbid other headings, but to be safe we stick to those. Thus we need to extract: - About the role: The paragraph starting "About The Role Twitch is looking for a knowledgeable Partnerships Associate..." plus maybe the location line? Actually location line is "You can work from San Francisco, CA; Irvine, CA; Los Angeles, CA; Seattle, CA; New York, NY." That's part of the role description. Could be included in About the role. - Responsibilities: The bullet list under "You Will:" (the list of duties). We'll put in

• . - Requirements: The bullet list under "You Have:" (the list of qualifications). We'll put in
  • . - Benefits: The "Perks" list: Medical, Dental, Vision & Disability Insurance, 401(k), Maternity & Parental Leave, Flexible PTO, Amazon Employee Discount. Also later mentions Amazon package includes sign-on payments and RSUs, and comprehensive benefits including health insurance etc. But we should not duplicate. We'll capture the Perks list and maybe also mention sign-on payments and RSUs as part of Pay? Actually Pay section includes salary ranges and mention of sign-on payments and RSUs. We'll include Pay section with salary ranges and note about sign-on payments and RSUs. - Pay: The base salary range table for each location. Also note: "Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location." Also "Amazon also offers comprehensive benefits including health insurance ..." but that's benefits. We'll keep Pay as salary ranges and mention sign-on payments and RSUs. - Schedule: Not mentioned, so we omit. We must not include boilerplate like "Pursuant to the San Francisco Fair Chance Ordinance..." etc. That's legal boilerplate; remove. Also remove EEO statement, privacy notice, etc. Also remove duplicated lines: The Perks list appears earlier and later benefits description; we should keep only one instance, but preserve all substantive info. We'll combine: we can list the Perks as given, and also note that Amazon offers comprehensive benefits including health insurance etc. But that may be redundant. To avoid duplication, we can mention the Perks list and then note that Amazon also offers comprehensive benefits (health insurance etc.) as part of benefits. But we need to preserve all substantive info; we can combine them into a single benefits section that includes both the Perks list and the comprehensive benefits description. Thus Benefits section will include: - Medical, Dental, Vision & Disability Insurance - 401(k) - Maternity & Parental Leave - Flexible PTO - Amazon Employee Discount - Sign-on payments and restricted stock units (RSUs) (maybe under Pay though) - Comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. But note 401(k) appears both in Perks and later; we can deduplicate. We'll produce a Benefits
    • list that includes unique items. Let's list unique benefits: - Medical insurance - Dental insurance - Vision insurance - Disability Insurance - 401(k) (matching mentioned later) - Maternity & Parental Leave - Flexible PTO - Amazon Employee Discount - Sign-on payments - Restricted stock units (RSUs) - Basic Life & AD&D insurance - Option for Supplemental life plans - EAP (Employee Assistance Program) - Mental Health Support - Medical Advice Line - Flexible Spending Accounts - Adoption and Surrogacy Reimbursement coverage - Paid time off (already covered by Flexible PTO? but we can keep) - Parental leave (already covered) We might combine some. But we must not invent details; we must only include what's in the posting. The posting says: "Perks Medical, Dental, Vision & Disability Insurance 401(k) Maternity & Parental Leave Flexible PTO Amazon Employee Discount". Then later: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Then: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." Thus we should include all those items. We'll create a Benefits section with a list. Now Pay section: We'll include the base salary ranges per location, and note that final compensation based on experience, qualifications, location, and that Amazon package includes sign-on payments and RSUs. We'll format Pay as maybe a

      with the ranges, or a

      • for each location. Since it's a list, we can use
        • . Now About the role: We'll include the paragraph about the role and location line. Now Responsibilities: We'll list each "You Will:" item. Now Requirements: We'll list each "You Have:" item. We must not include the "Bonus Points" section? It says "Bonus Points Personal experience as a live streamer..." That's substantive; could be part of Requirements or Skills. We could include it under Requirements or maybe a Skills section. The instruction list includes Skills as a possible heading. We could treat Bonus Points as Skills. But we must not create thin sections; we could incorporate Bonus Points into Requirements or Skills. Since we already have Requirements, we could add a Skills section for Bonus Points. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we should merge Bonus Points into Requirements (as additional qualifications) or into a Skills section. Let's create a Skills section for Bonus Points. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We must not include About Us or About The Team as separate headings; we could incorporate them into a brief intro paragraph before About the role? But the instruction says 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. It doesn't forbid having an introductory paragraph about the company. However we must preserve ALL substantive information; the About Us and About The Team paragraphs are substantive. If we drop them, we lose info. So we need to include them somewhere. We could include them as a

          before the first heading, or under a heading like "About Twitch". But the instruction didn't list About Twitch as an example heading, but it didn't forbid. To be safe, we could include a heading "About Twitch" (h3) and put the About Us and About The Team content there. That seems reasonable. Thus we will have:

          About Twitch

          About Us Twitch is the world’s biggest live streaming service, with global communities built around gaming, entertainment, music, sports, cooking, and more. It is where thousands of communities come together for whatever, every day. We’re about community, inside and out. You’ll find coworkers who are eager to team up, collaborate, and smash (or elegantly solve) problems together. We’re on a quest to empower live communities, so if this sounds good to you, see what we’re up to on LinkedIn and X, and discover the projects we’re solving on our Blog. Be sure to explore our Interviewing Guide to learn how to ace our interview process. About The Team The Global Partnerships team lies at the heart of Twitch. Our team is dedicated to serving streamers in our Twitch Partner Program from around the world. Our partner managers are custodians of meaningful and enduring relationships with our Partners. Our operations managers lead the execution and efficiency of critical processes used to support the Partner experience. Our program managers design and implement initiatives that acknowledge and enable Partner success. Collectively, we shape and evolve the Partner Program with meticulous care. Every decision is guided by the diverse needs of our streamers, who are the essence of Twitch’s success.

          Then

          About the role

          with the role paragraph and location line. Then

          Responsibilities

          with ul. Then

          Requirements

          with ul (You Have). Then

          Skills

          with ul (Bonus Points). Then

          Benefits

          with ul (combined benefits). Then

          Pay

          with ul (salary ranges) and maybe a p about sign-on payments and RSUs. We must not include any boilerplate like EEO, privacy, etc. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now we need to output only HTML fragment, no