ZipRecruiter

Log In

1

Coding Reviewer Jobs in Stoughton, WI (NOW HIRING)

SmartIPlace

Full Stack .NET Developer

Madison, WI · Remote

$50 - $55/hr

Expectations for this position are development of quality code, following coding standards, active participation in code reviews, sharing expertise, respectful communication, transparency, technical ...

Varsity Tutors

Software Tutor

Madison, WI · Remote

$40/hr

Guides students through requirements analysis, architectural planning, code implementation, unit and integration testing, code review practices, and deployment procedures. Emphasizes writing ...

jobr.pro

Software Engineer, Data Migration

Oregon, WI · On-site

Participate actively in code reviews to enforce best practices and patterns * Help troubleshoot and resolve complex technical issues in our distributed systems * Give and solicit feedback on ...

SmartIPlace

.Net Developer [ Hybrid]

Madison, WI · On-site

Expectations for this position are development of quality code, participation in active code reviews, sharing expertise, respectful communication, transparency, and technical documentation. Knowledge ...

SmartIPlace

.NET Developer

Madison, WI · Remote

$45 - $50/hr

Expectations for this position are development of quality code using TDD, participation in active code reviews, sharing expertise, respectful communication, transparency, technical documentation, and ...

Trek Bicycle

ERP Developer lll

Waterloo, WI · On-site

Perform code reviews and enforce development standards, documentation practices, and best practices across the team. * Triage and resolve complex production issues across the ERP ecosystem and ...

previous pagenext page

Showing results 21-40

All JobsCoding Reviewer JobsCoding Reviewer Jobs in Stoughton, WI

Coding Reviewer information

What is a coding reviewer?

Coding Reviewers are professionals responsible for evaluating, analyzing, and verifying code written by other developers to ensure it meets established standards and best practices. They check for errors, maintainability, security vulnerabilities, and adherence to coding guidelines. Their feedback helps improve code quality, reduce bugs, and facilitate team collaboration. Coding Reviewers often participate in code walkthroughs, pull request reviews, and may also mentor junior developers.

How does a coding reviewer typically collaborate with software development teams during the review process?

Coding Reviewers work closely with developers by examining code for quality, consistency, and adherence to best practices before it is merged into the main codebase. They often provide constructive feedback through code review tools or meetings, helping developers understand and resolve issues. Effective collaboration also involves clear communication to ensure that suggested changes are well-understood and implemented, fostering continuous improvement and knowledge sharing within the team.

What are the key skills and qualifications needed to thrive as a coding reviewer, and why are they important?

To thrive as a Coding Reviewer, you need in-depth knowledge of medical coding standards (such as ICD-10, CPT, and HCPCS), healthcare regulations, and relevant clinical terminology, typically supported by a certification like CPC or CCS. Familiarity with electronic health records (EHR) systems, coding audit tools, and healthcare compliance software is essential. Strong attention to detail, analytical thinking, and effective communication skills help Coding Reviewers identify errors and provide clear feedback. These skills ensure accurate billing, regulatory compliance, and optimized revenue cycles in healthcare organizations.

What is the difference between Coding Reviewer vs Medical Coder?

AspectCoding ReviewerMedical Coder
CredentialsCertification in coding (e.g., CPC, CCS)Certification in coding (e.g., CPC, CCS)
Work EnvironmentReviewing medical codes, often in healthcare settingsAssigning medical codes from patient records
Industry UsageUsed in hospitals, clinics, insurance companiesUsed in hospitals, clinics, billing companies
Primary RoleReview and validate coding accuracyAssign and input medical codes

Both Coding Reviewers and Medical Coders require similar certifications and work in healthcare environments. Coding Reviewers focus on verifying the accuracy of codes assigned by others, ensuring compliance and correctness. Medical Coders are responsible for assigning the initial codes based on medical records. While their roles are interconnected, Coding Reviewers primarily audit and validate, whereas Medical Coders handle the coding process itself.

Coding Reviewer jobs near you

AI Agent Trajectory Annotator and Reviewer

Madison, WI

Bespoke Labs
See more jobs at Bespoke Labsexternal

$20 - $30/hr

Full-time

Posted 12 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.

Apply