Trust and Safety Analyst
Motion Recruitment
- San Francisco, CA
- Contract
- Full-time
- Some security teams have strict requirements about certifications, degrees, years of experience, and things like that. Not us! We’re more interested in the unique perspectives and expertise you’ll bring to the team rather than the acronyms on your resume. However, you’ll be much more likely to be successful in this role if these points seem like a good description of you:
- You’ve been doing data analysis (e.g., SQL, MySQL,) for a while now, probably in the realm of 3+ years
- You are excellent at data visualization, and can bring non-technical parties along for your analysis
- You are quick to learn new technical systems.
- You enjoy finding elegant solutions to tricky problems, the trickier the problem the more fun you have solving it
- You frequently get praise from your peers and coworkers about your communication skills, both written and verbal
- You can translate complex findings and results into a concise and compelling narrative
- You would bring a diverse perspective to the team: for example, maybe you took an unconventional route to get into your current anti-abuse career
- You’ve got a passing familiarity with blockchains and cryptocurrency, or at least a good story about how you thought about investing in Bitcoin in 2014 but decided not to
- You’ve worked on or have thought deeply about Internet-based risk, abuse, fraud, data protection or security
Daily Responsibilities
- You’ll define and evaluate user abuse metrics, and come up with novel ways to investigate what’s driving these metrics
- You’ll build real time rules to respond to attacks and develop features to improve our internal machine learning models
- You’ll devise, build, and maintain tables, dashboards and visualizations to help the business better understand user abuse at the client
- You’ll perform in-depth data analysis and look for patterns and trends to identify potential new security issues, understand attack vectors, and build automated detection systems
- If something happens twice, you’ll write a run-book for it. If it happens three times, you’ll figure out a way to automate that run-book
- The role will focus on combating account takeovers and scams.