2

Remote Code Review Jobs in New York (NOW HIRING)

Remote Apply Our mission is to automate coding. The first step in our journey is to build the best ... Bugbot reviews pull requests, catches bugs, suggests improvements, and is becoming a critical part ...

Certified Medical Coder | Remote | Temp to Hire | $21.42/Hour Put Your Medical Coding Expertise to ... Review complex medical claims and reimbursement determinations * Analyze payment discrepancies ...

New

Certified Medical Coder | Remote | Temp to Hire | $21.42/Hour Put Your Medical Coding Expertise to ... Review complex medical claims and reimbursement determinations * Analyze payment discrepancies ...

New

Director, Engineering

New York, NY · On-site +1

$261K - $320K/yr

... code reviews and design reviews; and 2 years of experience using Kafka or Kinesis to review system design. Must live within regular commuting distance from the Blockgraph office in NYC. Remote work ...

Be Seen First

Certified Medical Coder | Remote | Temp to Hire | $21.42/Hour Work From Home Opportunity ... Provided by Client Weekly Pay What you'll do Review complex medical claims and reimbursement ...

New

Lead secure design reviews, threat modeling, code review, and penetration testing for high-risk ... Employees who do not live near one of our hubs are part of our remote workforce. At Gemini, we ...

UI React Developer - Remote

Somerset, NJ · On-site +1

$50.25 - $65.25/hr

Remote Duration: 6-12 months What You Will Do: * Knowledge of end-to-end systems development life ... Participate in code reviews. * Write unit, functional, acceptance, and/or user tests. * Challenge ...

They will focus on reviewing inpatient clinical documentation and assigning accurate diagnosis and procedure codes for complex cases. This position is 100% remote and part of the clients centralized ...

New

... review to support coded diagnoses. This is a fully remote position. Candidates must be available to work Eastern Standard Time (EST) business hours. Salary: $85,000-$90,000 annually, commensurate ...

New

next page

Showing results 1-20

Remote Code Review information

What is the difference between Remote Code Review vs Remote Software Developer?

AspectRemote Code ReviewRemote Software Developer
Required CredentialsKnowledge of coding standards, version control, and code analysis toolsProgramming skills, relevant certifications, and development experience
Work EnvironmentPrimarily reviewing code remotely, often as part of a team or projectDesigning, coding, testing, and deploying software remotely
Employer & Industry UsageTech companies, software firms, open-source projectsTech companies, startups, enterprise software firms
Search & Comparison IntentUnderstanding roles related to code quality and review processesRoles involving software development and programming tasks

Remote Code Review focuses on evaluating and improving code written by developers, requiring knowledge of coding standards and review tools. Remote Software Developers actively create and implement software solutions, requiring programming expertise. Both roles are common in tech industries and often collaborate, but they differ in responsibilities and skill sets.

What are the main challenges faced by professionals in remote code review roles, and how can they be addressed?

One of the main challenges in remote code review roles is effective communication—conveying feedback clearly and constructively without face-to-face interaction. Additionally, understanding the context of code changes and ensuring consistency with team standards can be harder when working remotely. These challenges can be addressed by establishing clear review guidelines, utilizing collaborative tools like code review platforms, and maintaining regular virtual check-ins with the development team. Building strong documentation and participating in team discussions also help remote code reviewers stay aligned with project goals.

What is a remote code review?

A remote code review is the process of examining and evaluating someone’s code from a different location, often using online tools or platforms. This allows software developers to review code changes, suggest improvements, and detect bugs without being physically present with the author. Remote code reviews help ensure code quality, maintain consistency, and foster collaboration within distributed teams. Tools like GitHub, GitLab, and Bitbucket are commonly used to facilitate remote code reviews through features like pull requests and inline comments.

What are the key skills and qualifications needed to thrive as a Remote Code Reviewer, and why are they important?

To thrive as a Remote Code Reviewer, you need expert knowledge of programming languages, software development best practices, and extensive experience with code review processes. Familiarity with version control systems like Git and code review tools such as GitHub, GitLab, or Bitbucket is typically required. Strong attention to detail, effective written communication, and the ability to provide constructive feedback are crucial soft skills in this role. These skills ensure code quality, foster team collaboration, and help maintain reliable and maintainable software in distributed work environments.
What cities in New York are hiring for Remote Code Review jobs? Cities in New York with the most Remote Code Review job openings:
Infographic showing various Remote Code Review job openings in New York as of July 2026, with employment types broken down into 35% Full Time, 44% Part Time, and 21% Contract. Highlights an 100% Remote job distribution.

Software Engineer, Bugbot

Anysphere, Inc

New York, NY • On-site, Remote

Full-time

Re-posted 2 days ago


Job description

Engineering • Full-time • San Francisco; New York; Remote
Apply
Our mission is to automate coding. The first step in our journey is to build the best tool for professional programmers, using a combination of inventive research, design, and engineering. Our organization is very flat, and our team is small and talent dense. We particularly like people who are truth-seeking, passionate, and creative. We enjoy spirited debate, crazy ideas, and shipping code.
About the role
We're hiring a Software Engineer to work on Bugbot. Bugbot reviews pull requests, catches bugs, suggests improvements, and is becoming a critical part of how engineering teams ship software. As LLMs rapidly mature, the surface area of what Bugbot can do is expanding just as fast.
From the model integration and agent harness improvement to the product UI, integrations, and onboarding experience, you'll maintain Bugbot being the industry's best AI code reviewer. This is a full-stack IC role where you'll ship features end-to-end and directly shape how millions of engineers interact with AI during code review.
What you'll do
  • Launch new Bugbot features end-to-end from defining the feature and building the UI to wiring up the backend and iterating on model behavior so that each release meaningfully improves code review quality. You can check out Bugbot blog post for some examples of how Bugbot was improved in the past: https://cursor.com/blog/building-bugbot .
  • Evolve the review pipeline adapting prompting strategies, model routing, context selection, and agent orchestration to take advantage of new capabilities while managing cost and latency.
  • Build integrations that embed Bugbot into every engineer's workflow making AI-assisted review a seamless, default part of the development loop.
  • Own product quality and reliability monitor precision and recall, triage false positives, improve observability across the review pipeline, and ensure Bugbot earns trust with every review it posts.
  • Design onboarding and adoption flows that help teams go from first install to daily active usage.
  • Partner with ML, infrastructure, and product teams to inform model improvements with real-world review data, shape the Bugbot roadmap, and scale the system as adoption grows.
  • You will own Bugbot's product surface end-to-end: features, integrations, review pipeline, onboarding, configuration, and the user experience of AI code review.
  • You will not own foundation model training or core infrastructure services - but you will be a key consumer and collaborator, driving requirements based on what Bugbot needs.
  • You will not be a backend-only engineer or an ML researcher who doesn't ship product. This role requires you to move fluidly between the model layer and the product layer.
  • Quality is the product. A code review assistant that posts noisy or unhelpful comments is worse than no assistant at all. You'll be obsessive about making Bugbot's output genuinely useful. You obsess about your evals.

You may be a fit if
  • You've built or worked on agents that integrate into the code review or CI/CD workflow.
  • You've shipped full-stack product features end-to-end and enjoy moving between frontend, backend, and model integration.
  • You care deeply about developer experience and collecting new evals from customers and internal team members.
  • You can hold the tension between "ship fast to learn" and "don't erode trust with bad suggestions."
  • You've launched a product or feature to external users and owned the full loop: onboarding, documentation, feedback, and iteration.

#LI-DNI