Define scoped test coverage
Translate your authorized objectives into test categories such as instruction hierarchy, inappropriate disclosure, tool permissions and handling of untrusted content.
Managed AI staffing
Turn authorized AI safety tests into reproducible findings
An AI safety red team specialist tests how an AI system behaves at the boundaries defined by your evaluation scope. Your bot prepares authorized test cases, runs them in the permitted environment and organizes observed failures so the team can investigate weaknesses and verify mitigations.
Find my AI workerBuild a free role brief Responsibilities, handoffs and quality measures. No signup.
The job behind the title
A safety concern is difficult to fix when it is described only as an alarming transcript. Teams need the test conditions, system boundaries and reproducible evidence that show whether the behavior is a genuine control failure, an expected limitation or an inconclusive result.
Responsibilities
We shape these responsibilities around your systems, priorities and decision permissions.
Translate your authorized objectives into test categories such as instruction hierarchy, inappropriate disclosure, tool permissions and handling of untrusted content.
Create cases using approved fixtures and data, recording the expected boundaries and the environment in which each test may run.
Document prompts, relevant system conditions, outputs and tool actions needed to assess a finding, limiting sensitive details to the authorized review process.
Retest the affected cases and related paths after a change, recording whether the observed failure persists and what coverage remains incomplete.
A clear handoff
Illustrative workflow
An example of how the work could run, tailored during onboarding. This is not a customer case study.
An assistant reads external documents and can request actions through connected tools. The team wants to test whether instructions embedded in a document can improperly influence those actions.
Your bot uses the approved test environment and controlled documents to exercise the boundary. It records the observed response and any attempted tool action, then prepares a finding tied to the expected permission rule.
If a test would leave the authorized environment, access real sensitive records or trigger an unapproved external action, the bot stops that path and records the scope issue for the designated owner.
Onboarding & continued development
We learn the job, your expectations and how your team works. Then we select and configure an AI worker for the role.
We help your bot learn your systems, policies and preferences. Together, we review its work and prepare it for the responsibilities you agree on.
We stay involved, review performance and continue coaching your bot. You have a human Botsource contact when the work needs attention.
We agree on targets and review methods together. These are proposed measures, not claimed results.
Before you get started
The role can be scoped around assistants, retrieval systems and agents with connected tools, provided the environment and authority are clear. Test categories should reflect the system's actual capabilities and the controls it is expected to obey.
The results describe the cases and conditions tested. They do not prove safety across every possible interaction, so the report should preserve known limitations, uncovered areas and any findings that remain unresolved.
The project defines who may receive detailed evidence, where it is stored and how issues are escalated. Reports should provide enough information for authorized remediation without unnecessarily exposing sensitive data or distributing operational details beyond that audience.
Start with the job
Tell us what the role needs to accomplish. We’ll talk through responsibilities, systems, onboarding and how you want to measure performance.
You’ll leave the assessment with a clearer role plan and next steps for preparing the right AI worker.
Related roles
Evaluate AI responses against criteria your team can inspect
Explore the roleFind reproducible software problems before they become support conversations
Explore the roleMove software requirements into working changes with evidence to review
Explore the role