Guide to Writing a Trust & Safety Resume
What hiring managers in this field actually look for. And how to show it.
T&S resumes are different. Most resume advice doesn't apply.
Most resume advice was written for software engineers, marketers, and salespeople. It doesn't translate well to Trust & Safety.
T&S work is often confidential. The platforms you've worked on may be under NDA. The scale of your enforcement operations may be sensitive. The policy decisions you've shaped may not be publicly attributable. You can't always say what you did, where you did it, or how many people it affected.
And yet, hiring managers in this field need to understand exactly those things to know whether you're the right person for their team.
This guide covers how to bridge that gap: for candidates who are new to the field and for experienced professionals who know what they've done but struggle to put it on paper.
Understand what T&S hiring managers are actually looking for.
Before you write a single word, understand the lens through which your resume will be read. Every hiring manager in this field is trying to answer three questions.
Keep those three questions in your head as you write every bullet.
Structure and format
Keep it to one page if you have under ten years of experience. Two pages is acceptable for senior professionals with broad scope. More than two pages is almost never necessary in T&S.
Use a clean, readable format. No graphics, no columns, no skill bars. Applicant tracking systems and busy hiring managers both struggle with anything that isn't straightforward text in a logical order. A beautifully designed resume that breaks when copied to plain text is a liability, not an asset.
The summary
A two to three sentence summary at the top of your resume tells the hiring manager immediately what kind of candidate you are. Most people skip it or write something generic. Done well, it's the fastest way to orient a reader who is scanning fifty resumes at once.
A strong T&S summary answers one question: what do you do, at what level, and in what context?
"Trust & Safety operations leader with eight years of experience building and scaling enforcement programs at consumer platforms. Specializes in cross-border policy implementation and vendor operations at high volume. Most recently led a global content moderation function spanning four regions and three outsourced partners."
"Experienced trust and safety professional passionate about keeping online platforms safe for all users. Strong communicator with a track record of cross-functional collaboration."
The first is specific and searchable. The second could describe almost anyone in the field.
Writing your experience section
The most common mistake I see: writing what you were responsible for rather than what you actually changed. Hiring managers don't need a job description. They need evidence of output.
Every bullet should start with a verb and end with something that changed as a result of your work.
"Managed a team of twelve content moderators across two time zones, reducing average case resolution time by 34% over six months through queue restructuring and targeted coaching."
"Responsible for managing a team of content moderators and overseeing daily enforcement operations."
Numbers make vague claims concrete. You don't need a number on every bullet. But aim for at least two or three per role. In T&S, useful numbers include:
You can be specific about scale and scope without revealing sensitive operational details. "Designed the enforcement workflow for a platform with 200 million monthly active users" tells a hiring manager what they need to know without disclosing anything proprietary. "Built a cross-functional task force to address a coordinated inauthentic behavior campaign" communicates real sophistication without identifying the campaign.
If your most significant work is under NDA, you can still describe the nature of the work, the scope of your responsibility, and the outcome. Just not the specific details. When in doubt, describe the shape of the problem rather than the problem itself.
Don't just list what your team did. Show where you operated beyond your immediate function. Examples of cross-functional bullets that consistently land well:
If you work in policy, your resume should look different from someone who works in operations. Hiring managers know the difference and will notice quickly if your experience doesn't reflect the function they're hiring for.
The skills section
Keep it functional, not performative. A skills section that lists "Microsoft Office" and "strong communication" is wasted space. Don't list soft skills. Show them through your bullets instead.
Breaking into T&S from an adjacent field
If you're coming from content moderation, legal, policy, compliance, law enforcement, journalism, or academia, your resume needs to bridge the gap explicitly. Hiring managers won't make the connection for you.
Common mistakes to avoid
These are the issues I see most often across the resumes I review. Most are fixable in an afternoon.
The final test before you send
Read your resume as a hiring manager who has never met you and has thirty seconds to decide whether to keep reading.
If the answer to the question on the right is yes, you're ready. If not, go back to the bullets that are too vague, too generic, or too focused on responsibility rather than impact.
"Does this resume tell me, quickly and specifically, what this person has done, at what scale, and whether it maps to the role I'm hiring for?"
If you're not sure, the answer is no. Go back and fix the bullets that are making the reader work too hard.
Ready to build your profile?
A strong resume is the foundation of a strong Revealed profile. Once your resume is ready, your profile takes less than ten minutes to complete.
Build your profile →Check your profile score.
The AI Profile Coach reviews your profile, scores it, and tells you exactly what to improve before employers start finding you.
Run the AI Profile Coach →