Skip to main content

Avride

DevOps Engineer – Developer Tools

Texas, USmidAdded 1 month ago

About this role

Join our developer tools team supporting autonomous driving technology by optimizing CI/CD pipelines, build systems, and developer infrastructure for a large-scale monorepo. You'll enhance build performance, maintain deployment reliability, and embed security practices across our development ecosystem.

What you'll do

  • Design and maintain CI/CD pipelines for fast, reliable software delivery
  • Debug complex build and deployment issues in large monorepo environments
  • Optimize build and deployment performance to accelerate development cycles
  • Implement observability and monitoring for CI/CD infrastructure and code quality metrics
  • Manage third-party software package integration and updates
  • Embed DevSecOps practices including vulnerability scanning and security policy enforcement

What they're looking for

  • Python or Go programming (middle-level proficiency)
  • CI/CD processes and GitHub workflows
  • Software build systems (Bazel preferred)
  • DevOps and infrastructure practices
  • Dynamic linking and software packaging
  • Linux package management
  • C++ (nice to have)
  • Kubernetes (nice to have)
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Avride

Avride develops autonomous vehicle and delivery robot technology, building the computational infrastructure, data systems, and localization platforms that enable autonomous driving development. The company is hiring backend engineers, ML infrastructure specialists, data platform engineers, robotics software engineers, and site infrastructure engineers to scale its simulation, training, logging, and operational systems.

View all jobs at Avride

Likely interview questions

  • Walk us through your experience with CI/CD pipeline design and implementation. What tools and platforms have you worked with, particularly GitHub?
  • Describe a time you debugged a complex build issue in a large codebase. How did you approach it and what was the outcome?