Compensation: TBD, based on education, experience, role fit, startup needs, and interview process.
Job summary
As a Risk Operations Analyst, you will support one or more startups connected to Metasoft Capital by helping founders turn early ambition into practical execution. This role is built for remote startup environments where priorities can change quickly, information may be incomplete, and useful work depends on clear writing, steady ownership, and good judgment.
The role focuses on operational risk signals, suspicious behavior, process controls, and risk reporting. You may work with founders, product teams, technical teams, operations, customers, partners, or investors depending on the startup assignment. The goal is to help the company protect users, improve quality, reduce operational risk, and help startups build trust as products scale, while building habits that make the team more reliable as it grows.
Core responsibilities
- Own the day-to-day work connected to operational risk signals, suspicious behavior, process controls, and risk reporting, keeping priorities clear and progress visible.
- Work closely with founders, managers, product, technology, operations, and customer-facing teams as needed.
- Create clear notes, decisions, requirements, checklists, or reports so work does not depend on memory or guesswork.
- Review risks, quality issues, user reports, incidents, or policy questions using clear standards and documentation.
- Use practical judgment to balance speed, quality, cost, risk, and learning in a startup environment.
- Monitor quality, safety, privacy, fraud, abuse, accessibility, or policy issues and turn findings into clear action for the team.
- Create review workflows, checklists, escalation paths, incident notes, QA reports, or policy documentation that can be repeated reliably.
- Work with product, engineering, operations, legal, support, and leadership teams to prevent small issues from becoming public or user-impacting problems.
- Balance user protection, fairness, speed, and practical startup constraints when recommending improvements.
- Turn messy information into clear analysis, written findings, dashboards, recommendations, or experiments that help the startup make better decisions.
- Question assumptions, check data quality, and explain uncertainty honestly instead of presenting weak evidence as certainty.
Education and experience requirements
- Education or experience in QA, risk, policy, privacy, trust and safety, compliance, operations, accessibility, fraud, cybersecurity, or equivalent practical work is helpful.
- Strong judgment, documentation, attention to detail, discretion, and calm decision-making are important.
- Experience with moderation tools, QA systems, incident response, risk reviews, policy enforcement, audit trails, or accessibility testing is valuable.
- Ability to spot patterns, investigate root causes, and communicate sensitive findings carefully.
- Respect for user safety, fairness, privacy, and the long-term trust a startup must earn.
- Candidates should be ready to share examples of relevant work, projects, portfolios, case studies, writing samples, code samples, dashboards, campaigns, processes, or other evidence of ability when applicable.
Helpful skills and tools
- QA platforms, ticketing systems, risk logs, moderation tools, policy documents, privacy tools, accessibility checkers, incident trackers, dashboards, and audit evidence repositories.
- Experience in trust and safety, QA, fraud, risk, content moderation, privacy operations, compliance, or support operations.
- Strong judgment, documentation discipline, emotional steadiness, and ability to handle sensitive cases responsibly.
- Strong ownership mindset, reliability in remote work, and comfort working with incomplete information.
- Ability to communicate progress, blockers, and tradeoffs in a simple way for both technical and non-technical teammates.
- Curiosity, humility, and willingness to keep learning as the startup changes direction or grows.
- Clear written communication, organized files, practical documentation, and reliable follow-through are important because most teams operate remotely.
Remote startup working style
- Work asynchronously when possible, document decisions, and keep teammates updated on progress, blockers, risks, and next steps.
- Be comfortable with early-stage ambiguity, changing priorities, limited resources, and the need to learn quickly from customers and teammates.
- Use sound judgment to decide when to move fast, when to ask for help, when to slow down, and when to protect quality or trust.
- Respect confidentiality, founder context, customer information, and the trust required to support early-stage companies.
Success in this role looks like
- Reduced platform risk, better issue resolution, stronger policy consistency, fewer repeat defects, and higher user trust.
- Users experience fewer preventable problems, and the team learns from incidents instead of only reacting.
- Quality and safety risks become visible earlier.
- The startup earns trust through systems, not only promises.
- The startup team can point to clearer execution, better documentation, stronger collaboration, and practical improvements connected to this role.
How to apply
- Email your resume/CV to Jobs@MetasoftCapital.com and include JID: 1839728 in the email subject line and at the beginning of your message.
- Use a subject line similar to: JID: 1839728 - Risk Operations Analyst - Resume/CV.
- Briefly explain why this role, a remote startup environment, and the relevant industry or function fit your experience, interests, and learning goals.
- If useful for the role, include links to your portfolio, GitHub, LinkedIn, website, writing samples, case studies, dashboards, design files, campaigns, or other work examples.