How to Read a Trust & Safety Job Description: Scope, Workload, and Wellbeing Signals

Two job descriptions can carry the same title, "Trust & Safety Analyst," and describe two completely different jobs. One is a real seat with defined scope and a path to influence policy. The other is a queue you will be plugged into until you leave. The posting almost always tells you which one it is, if you know where to look. Most candidates read for the mission statement and the salary band. Read instead for scope boundaries, escalation authority, staffing ratios, and how the company talks about the content itself.

Scope: is the job bounded or open-ended?

A healthy T&S role names its surface. It says you will handle a specific policy area (harassment, spam and platform manipulation, child safety, regulated goods) or a defined product. That boundary is a promise about what you will and won't be asked to absorb. When a posting lists eight policy verticals under one analyst headcount, that is not breadth, it is under-resourcing. You will be the person everything rolls downhill to.

Watch the verbs. "Own and evolve our harassment policy" is a role with authorship. "Enforce policy per established guidelines" is execution only, which is fine early on if the rest of the posting is honest about it. The problem is the posting that promises strategic influence but describes a review queue. That gap between framing and function is where dissatisfaction lives. Ask in the interview what percentage of time is spent in the queue versus on policy, investigations, or tooling. A specific answer is a green flag; a vague one usually means the queue is most of it.

Escalation authority and decision rights

The single most useful thing to find in a T&S posting is whether the role can escalate and be heard. Look for language about cross-functional work with Legal, Policy, Engineering, or Law Enforcement Response. A role that interfaces with those teams has a channel for the hard cases. If cross-functional escalation is absent from the posting, treat it as a question for the interview rather than proof that no channel exists, but do notice its absence, because without a channel, edge cases tend to get forced into the wrong bucket or silently absorbed by the analyst.

Decision rights matter as much as escalation. Can you overturn an automated decision? Do you feed the appeals process or just process the volume? Roles that mention writing enforcement guidance, calibrating reviewers, or contributing to policy exceptions are roles where your judgment counts. If judgment is nowhere in the description, the job is designed around throughput, and throughput jobs burn out fastest because nothing you notice ever changes the system.

Wellbeing and exposure: read past the boilerplate

For any role touching graphic or abusive material, wellbeing provisions are not a perk; they are safety equipment. Strong postings name them concretely: access to a resiliency or wellness program, on-staff or contracted counseling, muting and grayscale tooling, exposure limits, and rotation off the most severe content. Weak postings say "we care about our team's wellbeing" and stop there, or omit the subject entirely while describing work that clearly involves severe content.

A short field guide to the signals worth weighing:

• Green: named policy vertical, defined queue-versus-project split, cross-functional escalation, concrete wellness and rotation provisions, tenure or growth paths mentioned for the team.
• Red: many verticals under one headcount, throughput or SLA language with no judgment component, severe content implied but no wellbeing mention, "fast-paced" and "wear many hats" doing the heavy lifting, and 24/7 coverage with no mention of how shifts are staffed.

None of these is disqualifying alone. A single red flag in an otherwise specific posting may just be a lazy paragraph. A cluster of them, especially severe-content work with no wellbeing language and unbounded scope, describes a burnout factory regardless of the title on top.

Staffing and permanence

Look for clues about how the function is resourced. Is this a growing team or a backfill for constant attrition? Postings that emphasize speed, "thrive under pressure," and immediate availability, with nothing about mentorship, calibration, or career progression, are often filling a revolving door. Ask how long the last person in the seat stayed and why they left. Ask the ratio of analysts to volume. Teams that resource properly can answer these without discomfort.

What to do with this

Before you apply, mark every posting against four questions: Is scope bounded? Can I escalate and decide? Are wellbeing provisions concrete for the content I will see? Does the team look staffed to last? Bring the gaps to the interview as direct questions. The strength of the answers, not the polish of the mission statement, tells you whether you are joining a real role or feeding a queue.