1

File Reviewer Jobs in Arizona (NOW HIRING)

Paralegal

Phoenix, AZ · On-site

$25 - $30/hr

The paralegal will handle state fair hearing projects, including file review and updating hearing databases. Triage incoming mail, such as state fair hearing requests, motions, orders, and other mail ...

Audit foreclosure and bankruptcy files using system applications and manual checklists to ensure compliance and accuracy. * Review and process a high volume of invoices, prepare audit packages, and ...

Showing results 41-60

File Reviewer information

What is a file reviewer?

A File Reviewer is responsible for evaluating documents, records, or applications to ensure accuracy, compliance, and completeness. They typically work in industries like finance, insurance, legal, or healthcare, where document verification is crucial. Their duties may include identifying errors, verifying data against established criteria, and providing feedback on necessary corrections. Strong attention to detail and knowledge of relevant regulations are essential for this role.

What skills and qualifications are needed to thrive as a file reviewer?

To thrive as a File Reviewer, you need a strong attention to detail, analytical thinking, and an understanding of regulatory or compliance standards typically gained through relevant education or experience. Familiarity with document management software, databases, and sometimes industry-specific tools like mortgage or insurance platforms is often required. Excellent organizational abilities, time management, and effective written communication skills help individuals excel in this role. These competencies are critical to accurately evaluating files, ensuring compliance, and supporting business operations efficiently.

What are common challenges faced by file reviewers, and how can they be managed?

File Reviewers often face challenges such as managing large volumes of documents within tight deadlines and ensuring each file meets strict compliance standards. Staying updated on changing regulations or internal policies can also require continuous learning and adaptability. To manage these challenges, strong organizational skills and effective prioritization are essential, along with utilizing digital tools that streamline review processes. Many teams support collaboration and provide ongoing training to help File Reviewers stay efficient and maintain high accuracy. As you gain experience, you'll become skilled at identifying discrepancies quickly and contributing to quality assurance within your team.

Infographic showing various File Reviewer job openings in Arizona as of August 2026, with employment types broken down into 81% Full Time, 15% Part Time, 1% Temporary, 2% Contract, and 1% Nights. Highlights an 88% Physical, 4% Hybrid, and 8% Remote job distribution.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Phoenix, AZ

$20 - $30/hr

Full-time

Posted 6 days ago


Job description

Type: Contract, hourly

Location: Remote

Hours: 20–30 per week

Pay: $20–30/hour, based on experience and language coverage

Start: Immediate

ABOUT THE ROLE

We evaluate how well advanced AI coding agents solve real engineering problems. An agent is given a real open source codebase inside a container and a hard task, then works on its own for 80 to 250 steps. A trajectory is the full record of that run — every command, result, and decision.

You will do two jobs, and you should expect either on any given day.

•Annotate — Read a trajectory nobody has looked at yet and judge it step by step.

• Review — Take an existing annotation, written by our AI tooling or another person, and confirm, correct, or reject it.

TASKS YOU'LL SEE

• Feature build — Add a working feature to a live library without breaking anything that already worked.

• Rebuild — Work out what a compiled tool does by running it, then rebuild it to match its output, exit codes, and file effects.

• Bug hunt — Find and fix twenty undocumented bugs across a dozen files with no test suite, then record what caused them.

Mostly Python and Go, with some Rust, C, and Ct+. A trajectory runs about 100 steps.

WHAT YOU JUDGE IN A TRAJECTORY

• Was the command right for the state the environment was actually in?

• Did the agent read the previous output correctly?

• Was the step wrong, or only inefficient — these are scored differently.

• Where did the run first go off course — usually earlier than where it visibly broke.

• Did the agent notice its own mistake and recover, or keep building on a false assumption?

• Did it game the grader instead of solving the task (e.g., weakening a test or hardcoding an expected value)?

WHAT WE NEED FROM YOU

• Experience — 2+ years in software engineering, DevOps, or site reliability, with real debugging in real codebases.

• Languages — Strong in Python or Go, and able to read a language you've never used.

• Linux — Comfortable with logs, running processes, build failures, and containers.

• Workflow — Everyday Git, diffs, pull requests, and issue tracking.

• Debugging — Able to work with no test suite and no error message pointing at the cause.

• Focus — Able to hold context across a long run, because step 74 can depend on step 12.

• Writing — Clear English, since every judgement needs an explanation another engineer can check.