2

Remote Surgical Robotics Jobs (NOW HIRING)

... Implant, Surgical Robot, BCI App, Clinical, Full-stack services and infrastructure * Own the software/firmware build tooling at scale. This includes remote caching, remote execution, target ...

Clinic-based position with dedicated surgery days * da Vinci Xi robots * Ancillary services ... Please refer to the to determine whether the position you are interested in is remote or on-site.

... vehicles, surgical robotics, and more all rely on Jama Connect ® requirements management ... Deliver onsite and remote training of the Jama Connect solution to onboard new users * Document and ...

As a global leader in robotic-assisted surgery and minimally invasive care , our technologies--like ... Working Conditions Hybrid; 3 days in office, 2 days remote per week Preferred Skills and Experience

As a global leader in robotic-assisted surgery and minimally invasive care , our technologies-like ... Directly implement and optimize Bazel Remote Caching and Remote Execution (RBE) to enable fast ...

We are looking for talented, motivated and ambitious team members to revolutionize robotic surgery ... Early stage/startup commercial experience #LI-Remote Benefits & Perks (For Full Time Employees)

We are looking for talented, motivated and ambitious team members to revolutionize robotic surgery ... Early stage/startup commercial experience #LI-Remote Benefits & Perks (For Full Time Employees)

We are looking for talented, motivated and ambitious team members to revolutionize robotic surgery ... Early stage/startup commercial experience #LI-Remote Benefits & Perks (For Full Time Employees)

next page

Showing results 1-20

Remote Surgical Robotics information

See salary details

$721

$1.9K

$2.9K

How much do remote surgical robotics jobs pay per week?

As of Jun 16, 2026, the average weekly pay for remote surgical robotics in the United States is $1,882.31, according to ZipRecruiter salary data. Most workers in this role earn between $1,403.85 and $2,307.69 per week, depending on experience, location, and employer.

What is the difference between Remote Surgical Robotics vs Surgical Technologist?

AspectRemote Surgical RoboticsSurgical Technologist
Required CredentialsSpecialized training in robotic systems, certifications in surgical roboticsPost-secondary education, certification as a surgical technologist
Work EnvironmentOperating rooms, remote monitoring centers, healthcare facilitiesHospitals, surgical centers, clinics
Industry UsageHigh-tech surgical procedures, robotic-assisted surgeriesAssisting in surgeries, preparing operating rooms
Common Search/ComparisonYesNo

Remote Surgical Robotics professionals focus on operating and managing robotic surgical systems, often requiring specialized certifications and working in high-tech environments. Surgical Technologists assist in surgeries by preparing equipment and supporting surgical teams. While both roles are vital in surgical settings, Remote Surgical Robotics involves advanced technology management, whereas Surgical Technologists focus on direct surgical support.

More about Remote Surgical Robotics jobs
What cities are hiring for Remote Surgical Robotics jobs? Cities with the most Remote Surgical Robotics job openings:
What are the most commonly searched types of Surgical Robotics jobs? The most popular types of Surgical Robotics jobs are:
What states have the most Remote Surgical Robotics jobs? States with the most job openings for Remote Surgical Robotics jobs include:
Software Engineer, CI/CD

Software Engineer, CI/CD

Neuralink

Austin, TX • Remote

Other

Posted 25 days ago


Job description

Team Description: 

The Infrastructure Team builds the foundation that enables the company to operate safely, robustly, and move at light-speed. We run a mixture of cloud-based and on-prem systems and have a user base spanning from highly technically proficient engineers to non-technical scientists and doctors; but all of them need solid systems, rugged networking, and bullet-proof software to do their jobs. 

Job Responsibilities and Description: 

As a Software Engineer, CICD you will integrate tightly with teams across the company, and span all layers of the work environment stack, from deployment of physical hardware on the manufacturing line, to custom tooling to stream neural recordings from implants. You will: 

  • Design and scale the CI/CD platform that enables engineering teams to ship safely and quickly across verticals including, but not limited to, Brain Implant, Surgical Robot, BCI App, Clinical, Full-stack services and infrastructure
  • Own the software/firmware build tooling at scale. This includes remote caching, remote execution, target identification and selection, etc.
  • Operate and scale a runner fleet spanning on-prem and cloud clusters, cover multiple hardware platforms including Mac, Linux, Embedded devices and Hardware-in-the-loop fixtures
  • Maintain reproducible build and CI environments with Nix
  • Instrument CI health with Prometheus metrics, Grafana dashboards, and automated alerting to maintain high signal-to-noise on pipeline reliability
  • Reduce developer cycle time through pre-commit tooling, caching strategies, test sharding, and build graph optimization

Tech Stack:

  • Rust, Python
  • Terraform
  • Bazel and Nix
  • Kubernetes
  • GitLab CI
  • AWS
  • Darwin, Ubuntu, Fedora

Required Qualifications:

  • Deep experience operating Bazel, or similar hermetic build systems
  • Hands-on experience operating Kubernetes
  • Production experience with GitLab CI (or comparable CI platform), including pipeline architecture, runner fleet management, and custom executor integrations
  • Expertise in operating UNIX systems, including Linux and Mac
  • Familiarity with Nix for reproducible environments, or equivalent experience ensuring hermetic, cacheable builds
  • Bachelor's degree in computer science, a related field, or an equivalent combination of education, training, and/or experience

Preferred Qualifications: 

  • Familiarity with hardware in the loop testing setups
  • Experience working with build system and CI tooling in a monorepo context