Skip to main content
Loading
loadingbar
Loading, Please wait..!!

Senior Software Engineer, Code Review & Quality - FULLY REMOTE

  • Senior Software Engineer, Code Review & Quality - FULLY REMOTE job type Posted on: Nov 17, 2026
  • Senior Software Engineer, Code Review & Quality - FULLY REMOTE experience level Pride Global
  • Senior Software Engineer, Code Review & Quality - FULLY REMOTE employment type San Francisco, California
  • Senior Software Engineer, Code Review & Quality - FULLY REMOTE salary Salary: $120 per hour
  • Senior Software Engineer, Code Review & Quality - FULLY REMOTE employment type Remote
  • Senior Software Engineer, Code Review & Quality - FULLY REMOTE salary Full-time

Point Apply Here APPLY LATER

Curious about compensation?

Explore the historical salary trends, average pay, and estimated compensation for Senior Software Engineer, Code Review & Quality - FULLY REMOTE roles in California.

View Salary Guide →

Job Title :

Senior Software Engineer, Code Review & Quality - FULLY REMOTE

Job Type :

Full-Time

Job Location :

San Francisco California United States

Remote :

Yes

Jobcon Logo Job Description :

Job Description

Job Description

Senior Software Engineer, Code Review & Quality (Contract)

\n\n

\n\n

Employment Type: W2 Contract
\nDuration: 4-6 months to start
\nHours: 40 hours per week on a weekday schedule, with some live collaborative sessions
\nLocation: Fully remote (US-based candidates)
\nCompensation: $120-$177 per hour, depending on experience

\n\n

\n\n

ABOUT THE ROLE

\n\n

Our client, a fast-growing technology company, is building a specialized team of senior engineers to evaluate code produced by automated systems. This is a hands-on quality role: you will examine real work in real repositories and decide what holds up and what doesn’t. Your assessments will feed directly into how these systems get better, and you will collaborate closely with researchers and fellow engineers along the way.

\n\n

\n\n

WHAT YOU’LL DO

\n\n
    \n
  • Evaluate: weigh competing solutions to a difficult engineering problem and give a well-reasoned verdict on which is stronger and by what margin
  • \n
  • Inspect: work through proposed code changes in detail, identify which issues are real, and rate how much each one matters
  • \n
  • Validate: confirm that a claimed fix truly solves the problem, and flag workarounds such as changing a test so it passes
  • \n
  • Communicate: write up every judgment clearly, so a colleague can understand and act on it without a follow-up conversation
  • \n
  • Adapt: move comfortably between repositories and languages, many of which update frequently, with accuracy as the priority
  • \n
  • Collaborate: stay in regular contact with researchers and peer reviewers throughout the engagement
  • \n
\n\n

\n\n

WHAT YOU’LL BRING

\n\n
    \n
  • Engineering depth: roughly 7+ years building production software in environments with rigorous standards, or an established record as an open-source maintainer
  • \n
  • Long-term ownership: sustained responsibility, at least 2 years, for a core service, product area, or shared library, rather than a sequence of short engagements
  • \n
  • Review leadership: experience as the trusted approver on your team, with the judgment to spot subtle problems and send back work that doesn’t meet the bar
  • \n
  • Clear written communication: the ability to lay out your reasoning in concise feedback that others can act on
  • \n
  • Adaptability: you get productive quickly in unfamiliar repositories and across multiple programming languages
  • \n
  • Current hands-on skills: recent, active coding or review work
  • \n
  • Availability: able to commit to a full-time, exclusive engagement for its duration
  • \n
\n\n

\n\n

NICE TO HAVE

\n\n
    \n
  • Senior leadership on engineering teams, such as staff or principal level, or technical lead for platform, infrastructure, or developer tooling
  • \n
  • Proficiency in one or more of Python, TypeScript, Go, or C
  • \n
  • Practical experience with AI coding assistants and a grounded view of their strengths and limits
  • \n
  • Open-source leadership: maintainer or major contributor to an established, actively developed project with a multi-person contributor base and real say over what gets merged
  • \n
\n
\n#RTA
\n#LI-BK1

Jobcon Logo Position Details

Posted:

Nov 17, 2026

Reference Number:

203dd3b2

Employment:

Full-time

Salary:

$120 per hour

City:

San Francisco

Job Origin:

ziprecruiter

Share this job:

  • linkedin

Jobcon Logo
A job sourcing event
In Dallas Fort Worth
Aug 19, 2017 9am-6pm
All job seekers welcome!

Senior Software Engineer, Code Review & Quality - FULLY REMOTE    Apply

Click on the below icons to share this job to Linkedin, Twitter!

Job Description

Job Description

Senior Software Engineer, Code Review & Quality (Contract)

\n\n

\n\n

Employment Type: W2 Contract
\nDuration: 4-6 months to start
\nHours: 40 hours per week on a weekday schedule, with some live collaborative sessions
\nLocation: Fully remote (US-based candidates)
\nCompensation: $120-$177 per hour, depending on experience

\n\n

\n\n

ABOUT THE ROLE

\n\n

Our client, a fast-growing technology company, is building a specialized team of senior engineers to evaluate code produced by automated systems. This is a hands-on quality role: you will examine real work in real repositories and decide what holds up and what doesn’t. Your assessments will feed directly into how these systems get better, and you will collaborate closely with researchers and fellow engineers along the way.

\n\n

\n\n

WHAT YOU’LL DO

\n\n
    \n
  • Evaluate: weigh competing solutions to a difficult engineering problem and give a well-reasoned verdict on which is stronger and by what margin
  • \n
  • Inspect: work through proposed code changes in detail, identify which issues are real, and rate how much each one matters
  • \n
  • Validate: confirm that a claimed fix truly solves the problem, and flag workarounds such as changing a test so it passes
  • \n
  • Communicate: write up every judgment clearly, so a colleague can understand and act on it without a follow-up conversation
  • \n
  • Adapt: move comfortably between repositories and languages, many of which update frequently, with accuracy as the priority
  • \n
  • Collaborate: stay in regular contact with researchers and peer reviewers throughout the engagement
  • \n
\n\n

\n\n

WHAT YOU’LL BRING

\n\n
    \n
  • Engineering depth: roughly 7+ years building production software in environments with rigorous standards, or an established record as an open-source maintainer
  • \n
  • Long-term ownership: sustained responsibility, at least 2 years, for a core service, product area, or shared library, rather than a sequence of short engagements
  • \n
  • Review leadership: experience as the trusted approver on your team, with the judgment to spot subtle problems and send back work that doesn’t meet the bar
  • \n
  • Clear written communication: the ability to lay out your reasoning in concise feedback that others can act on
  • \n
  • Adaptability: you get productive quickly in unfamiliar repositories and across multiple programming languages
  • \n
  • Current hands-on skills: recent, active coding or review work
  • \n
  • Availability: able to commit to a full-time, exclusive engagement for its duration
  • \n
\n\n

\n\n

NICE TO HAVE

\n\n
    \n
  • Senior leadership on engineering teams, such as staff or principal level, or technical lead for platform, infrastructure, or developer tooling
  • \n
  • Proficiency in one or more of Python, TypeScript, Go, or C
  • \n
  • Practical experience with AI coding assistants and a grounded view of their strengths and limits
  • \n
  • Open-source leadership: maintainer or major contributor to an established, actively developed project with a multi-person contributor base and real say over what gets merged
  • \n
\n
\n#RTA
\n#LI-BK1

Loading
Please wait..!!