Policy Enforcement Specialist- Creator and Content
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading
4. Do NOT put Job ID/requisition numbers as headings
5. Preserve ALL substantive information
6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
7. Include a section ONLY when there's real, specific content - never emit heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless posting actually states them
9. Output ONLY HTML fragment - no /, no markdown code fences
Let me analyze the content:
The posting has:
- "Responsibilities" section with "What You'll Do" and "Key Responsibilities" (list of 6 items)
- "Qualifications" section with "Minimum Qualifications" (4 items) and "Preferred Qualifications" (3 items)
- "About USDS" section (prose about the company)
- "Why Join Us" section (prose about mission/values)
- "Diversity & Inclusion" section (prose)
- "USDS Reasonable Accommodation" section (prose with link)
- "Job Information" section with pay transparency details (salary range, benefits details)
I need to structure this into appropriate sections. The rules mention specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Looking at the content:
- "Responsibilities" maps to Responsibilities section
- "Qualifications" maps to Qualifications section (with Minimum and Preferred)
- "About USDS" could be "About the role" or "About the company" - but the rule says "About the role" as a heading option
- "Why Join Us" and "Diversity & Inclusion" are more company culture - could be part of "About the role" or separate
- "USDS Reasonable Accommodation" is legal/boilerplate - should be removed per rules (EEO/equal-opportunity boilerplate)
- "Job Information" has Pay details (salary range) and Benefits details - these should be Pay and Benefits sections since they have real content
The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them" - the posting DOES state pay range and benefits details, so I should include Pay and Benefits sections.
Also: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate" - the Reasonable Accommodation section is EEO-related, so remove.
"Duplicated lines" - none apparent.
"Application instructions" - none in this text.
Now, structure:
1. About the role - could combine "About USDS" and "Why Join Us" and "Diversity & Inclusion" into an "About the role" section? But "About the role" typically describes the role itself, not the company. The posting starts with "Responsibilities E-commerce's Governance and Experience is a global team..." which describes the team/role context. That could be "About the role".
Actually, the first paragraph before "What You'll Do" describes the team and role context. That's "About the role".
Then "What You'll Do" and "Key Responsibilities" -> Responsibilities section.
Then "Qualifications" with Minimum and Preferred -> Qualifications section.
Then "About USDS" -> could be "About the company" but not in the allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Requirements" and "Qualifications" are similar. The posting has "Qualifications" heading. I'll use "Qualifications" for that section.
"Skills" not explicitly separate.
"Benefits" and "Pay" are in Job Information.
"Schedule" - the posting mentions "fully in-person schedule up to 5 days a week" in About USDS. That's schedule info. Should I include a Schedule section? The rule says include only when real specific content. It says "shifting from a hybrid work model to a fully in-person schedule up to 5 days a week." That's specific. So include Schedule section.
But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule (in-person 5 days). So include Schedule.
Now, let's map:
- About the role: first paragraph(s) describing team and role
- Responsibilities: What You'll Do + Key Responsibilities list
- Qualifications: Minimum + Preferred qualifications
- Pay: salary range from Job Information
- Benefits: benefits details from Job Information
- Schedule: in-person 5 days/week from About USDS
I should not include "About USDS" as separate heading if I fold into About the role or Schedule. But "About USDS" is about the joint venture, not the role. However, the first paragraph is about the team. The "About USDS" section is company description. The rules say "About the role" as heading. I'll put the initial team description under "About the role". The "About USDS" company description could be part of "About the role" or omitted? The rule says preserve ALL substantive information. But also "Remove boilerplate". Company description might be considered boilerplate? But it's specific to this joint venture. However, the user said "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include it. But where? Not in allowed headings. Could create a section "About the company" but not in allowed list. The allowed headings are fixed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should only use those. So I need to fit into those.
Maybe "About the role" can include company context. Or I could put "About USDS" under "About the role". The "Why Join Us" and "Diversity & Inclusion" are also company culture. Could be part of "About the role" or omitted as boilerplate? They are not strictly EEO legal boilerplate; they are company mission. But the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". "Why Join Us" and "Diversity & Inclusion" are not legal boilerplate; they are marketing. However, they are generic. The rule says "Preserve ALL substantive information". I think I should include them, but under which heading? Perhaps "About the role" can encompass why join us and diversity. But that's stretching.
Alternatively, the rules might allow only those headings, but if content doesn't fit, maybe omit? The instruction: "Prefer a few substantive sections over many thin ones." So I should only create sections for which there is real content matching the heading names.
Let's list the allowed headings again: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
The posting has:
- Role context (team description) -> About the role
- Responsibilities -> Responsibilities
- Qualifications (Minimum, Preferred) -> Qualifications
- Pay details -> Pay
- Benefits details -> Benefits
- Schedule details (in-person 5 days) -> Schedule
- Skills? Not explicitly separate.
- Requirements? Similar to Qualifications.
I'll use Qualifications for both minimum and preferred.
Now, "About USDS" company description: it's about the joint venture, not the role. But it's substantive. Could be part of "About the role" as context. I'll include it there.
"Why Join Us" and "Diversity & Inclusion": could be part of "About the role" or omitted. Since they are generic, maybe omit as boilerplate? But they are not legal boilerplate. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". These are not that. But they are also not specific to the role. The instruction: "Preserve ALL substantive information". I'll include them in "About the role" as prose.
"USDS Reasonable Accommodation" is EEO boilerplate - remove.
"Job Information" includes pay and benefits - use Pay and Benefits sections.
Also, the posting has "For Los Angeles County (unincorporated) Candidates:" - that's legal compliance, maybe boilerplate. But it's specific to location. Could be part of Benefits or Pay? It's about fair chance hiring. Might be considered legal boilerplate. I'll include in Benefits or Pay? Probably remove as legal boilerplate.
But the salary range is specific. Benefits list is specific.
Now, write HTML.
Structure:
About the role
E-commerce's Governance and Experience is a global team responsible for ensuring our marketplace is safe and trustworthy for not only our users, but also sellers and creators. We value user satisfaction and work on policies, rules and systems to ensure quality. We are looking for an experienced individual contributor to own customer complaint investigations in the U.S. region and drive cross-functional collaboration.
About USDS: TikTok USDS Joint Venture LLC is dedicated to the safety and security of millions of Americans who create, discover, and connect with what they love on the apps we operate. The Joint Venture has been established in compliance with the Executive Order signed by President Trump on September 25, 2025. Our foundation is a comprehensive data privacy and cybersecurity program we operate under defined safeguards to protect national security and secure U.S. user data, apps and the algorithm. We safeguard the U.S. content ecosystem, holding decision-making authority for trust and safety policies and moderation. USDS Joint Venture helps ensure Americans can continue to express their creativity, discover new hobbies and interests, and build thriving communities and businesses on a global scale. On-site presence across teams allows the company to operate with greater speed, alignment, and agility — especially in areas like real-time decision-making, team development, and integrated execution. As such, the company is shifting from a hybrid work model to a fully in-person schedule up to 5 days a week.
Why Join Us: Inspiring creativity is at the core of TikTok's mission. Our innovative product is built to help people authentically express themselves, discover and connect – and our global, diverse teams make that possible. Together, we create value for our communities, inspire creativity and bring joy - a mission we work towards every day. We strive to do great things with great people. We lead with curiosity, humility, and a desire to make impact in a rapidly growing tech company. Every challenge is an opportunity to learn and innovate as one team. We're resilient and embrace challenges as they come. By constantly iterating and fostering an "Always Day 1" mindset, we achieve meaningful breakthroughs for ourselves, our company, and our users. When we create and grow together, the possibilities are limitless.
Diversity & Inclusion: TikTok is committed to creating an inclusive space where employees are valued for their skills, experiences, and unique perspectives. Our platform connects people from across the globe and so does our workplace. At TikTok, our mission is to inspire creativity and bring joy. To achieve that goal, we are committed to celebrating our diverse voices and to creating an environment that reflects the many communities we reach. We are passionate about this and hope you are too.
But that's a lot of prose. Might be okay.
Responsibilities
We are seeking a detail-oriented Policy Enforcement Specialist for our Governance and Experience team. In this role, you will go beyond content moderation to perform strategic audits and trend synthesis across Creator and Content policy domains. You will be responsible for transforming raw operational data into high-fidelity reports that inform policy updates and strategic roadmaps. The ideal candidate possesses
for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when there's real, specific content - never emit heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the content: The posting has: - "Responsibilities" section with "What You'll Do" and "Key Responsibilities" (list of 6 items) - "Qualifications" section with "Minimum Qualifications" (4 items) and "Preferred Qualifications" (3 items) - "About USDS" section (prose about the company) - "Why Join Us" section (prose about mission/values) - "Diversity & Inclusion" section (prose) - "USDS Reasonable Accommodation" section (prose with link) - "Job Information" section with pay transparency details (salary range, benefits details) I need to structure this into appropriate sections. The rules mention specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Looking at the content: - "Responsibilities" maps to Responsibilities section - "Qualifications" maps to Qualifications section (with Minimum and Preferred) - "About USDS" could be "About the role" or "About the company" - but the rule says "About the role" as a heading option - "Why Join Us" and "Diversity & Inclusion" are more company culture - could be part of "About the role" or separate - "USDS Reasonable Accommodation" is legal/boilerplate - should be removed per rules (EEO/equal-opportunity boilerplate) - "Job Information" has Pay details (salary range) and Benefits details - these should be Pay and Benefits sections since they have real content The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them" - the posting DOES state pay range and benefits details, so I should include Pay and Benefits sections. Also: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate" - the Reasonable Accommodation section is EEO-related, so remove. "Duplicated lines" - none apparent. "Application instructions" - none in this text. Now, structure: 1. About the role - could combine "About USDS" and "Why Join Us" and "Diversity & Inclusion" into an "About the role" section? But "About the role" typically describes the role itself, not the company. The posting starts with "Responsibilities E-commerce's Governance and Experience is a global team..." which describes the team/role context. That could be "About the role". Actually, the first paragraph before "What You'll Do" describes the team and role context. That's "About the role". Then "What You'll Do" and "Key Responsibilities" -> Responsibilities section. Then "Qualifications" with Minimum and Preferred -> Qualifications section. Then "About USDS" -> could be "About the company" but not in the allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Requirements" and "Qualifications" are similar. The posting has "Qualifications" heading. I'll use "Qualifications" for that section. "Skills" not explicitly separate. "Benefits" and "Pay" are in Job Information. "Schedule" - the posting mentions "fully in-person schedule up to 5 days a week" in About USDS. That's schedule info. Should I include a Schedule section? The rule says include only when real specific content. It says "shifting from a hybrid work model to a fully in-person schedule up to 5 days a week." That's specific. So include Schedule section. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule (in-person 5 days). So include Schedule. Now, let's map: - About the role: first paragraph(s) describing team and role - Responsibilities: What You'll Do + Key Responsibilities list - Qualifications: Minimum + Preferred qualifications - Pay: salary range from Job Information - Benefits: benefits details from Job Information - Schedule: in-person 5 days/week from About USDS I should not include "About USDS" as separate heading if I fold into About the role or Schedule. But "About USDS" is about the joint venture, not the role. However, the first paragraph is about the team. The "About USDS" section is company description. The rules say "About the role" as heading. I'll put the initial team description under "About the role". The "About USDS" company description could be part of "About the role" or omitted? The rule says preserve ALL substantive information. But also "Remove boilerplate". Company description might be considered boilerplate? But it's specific to this joint venture. However, the user said "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include it. But where? Not in allowed headings. Could create a section "About the company" but not in allowed list. The allowed headings are fixed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should only use those. So I need to fit into those. Maybe "About the role" can include company context. Or I could put "About USDS" under "About the role". The "Why Join Us" and "Diversity & Inclusion" are also company culture. Could be part of "About the role" or omitted as boilerplate? They are not strictly EEO legal boilerplate; they are company mission. But the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". "Why Join Us" and "Diversity & Inclusion" are not legal boilerplate; they are marketing. However, they are generic. The rule says "Preserve ALL substantive information". I think I should include them, but under which heading? Perhaps "About the role" can encompass why join us and diversity. But that's stretching. Alternatively, the rules might allow only those headings, but if content doesn't fit, maybe omit? The instruction: "Prefer a few substantive sections over many thin ones." So I should only create sections for which there is real content matching the heading names. Let's list the allowed headings again: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has: - Role context (team description) -> About the role - Responsibilities -> Responsibilities - Qualifications (Minimum, Preferred) -> Qualifications - Pay details -> Pay - Benefits details -> Benefits - Schedule details (in-person 5 days) -> Schedule - Skills? Not explicitly separate. - Requirements? Similar to Qualifications. I'll use Qualifications for both minimum and preferred. Now, "About USDS" company description: it's about the joint venture, not the role. But it's substantive. Could be part of "About the role" as context. I'll include it there. "Why Join Us" and "Diversity & Inclusion": could be part of "About the role" or omitted. Since they are generic, maybe omit as boilerplate? But they are not legal boilerplate. However, the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". These are not that. But they are also not specific to the role. The instruction: "Preserve ALL substantive information". I'll include them in "About the role" as prose. "USDS Reasonable Accommodation" is EEO boilerplate - remove. "Job Information" includes pay and benefits - use Pay and Benefits sections. Also, the posting has "For Los Angeles County (unincorporated) Candidates:" - that's legal compliance, maybe boilerplate. But it's specific to location. Could be part of Benefits or Pay? It's about fair chance hiring. Might be considered legal boilerplate. I'll include in Benefits or Pay? Probably remove as legal boilerplate. But the salary range is specific. Benefits list is specific. Now, write HTML. Structure:
About the role
E-commerce's Governance and Experience is a global team responsible for ensuring our marketplace is safe and trustworthy for not only our users, but also sellers and creators. We value user satisfaction and work on policies, rules and systems to ensure quality. We are looking for an experienced individual contributor to own customer complaint investigations in the U.S. region and drive cross-functional collaboration.
About USDS: TikTok USDS Joint Venture LLC is dedicated to the safety and security of millions of Americans who create, discover, and connect with what they love on the apps we operate. The Joint Venture has been established in compliance with the Executive Order signed by President Trump on September 25, 2025. Our foundation is a comprehensive data privacy and cybersecurity program we operate under defined safeguards to protect national security and secure U.S. user data, apps and the algorithm. We safeguard the U.S. content ecosystem, holding decision-making authority for trust and safety policies and moderation. USDS Joint Venture helps ensure Americans can continue to express their creativity, discover new hobbies and interests, and build thriving communities and businesses on a global scale. On-site presence across teams allows the company to operate with greater speed, alignment, and agility — especially in areas like real-time decision-making, team development, and integrated execution. As such, the company is shifting from a hybrid work model to a fully in-person schedule up to 5 days a week.
Why Join Us: Inspiring creativity is at the core of TikTok's mission. Our innovative product is built to help people authentically express themselves, discover and connect – and our global, diverse teams make that possible. Together, we create value for our communities, inspire creativity and bring joy - a mission we work towards every day. We strive to do great things with great people. We lead with curiosity, humility, and a desire to make impact in a rapidly growing tech company. Every challenge is an opportunity to learn and innovate as one team. We're resilient and embrace challenges as they come. By constantly iterating and fostering an "Always Day 1" mindset, we achieve meaningful breakthroughs for ourselves, our company, and our users. When we create and grow together, the possibilities are limitless.
Diversity & Inclusion: TikTok is committed to creating an inclusive space where employees are valued for their skills, experiences, and unique perspectives. Our platform connects people from across the globe and so does our workplace. At TikTok, our mission is to inspire creativity and bring joy. To achieve that goal, we are committed to celebrating our diverse voices and to creating an environment that reflects the many communities we reach. We are passionate about this and hope you are too.
But that's a lot of prose. Might be okay.Responsibilities
We are seeking a detail-oriented Policy Enforcement Specialist for our Governance and Experience team. In this role, you will go beyond content moderation to perform strategic audits and trend synthesis across Creator and Content policy domains. You will be responsible for transforming raw operational data into high-fidelity reports that inform policy updates and strategic roadmaps. The ideal candidate possesses