Skip to main content

Avride

Software Engineer – Simulation Backend

Texas, USmidAdded 1 month ago

About this role

Build scalable backend infrastructure for distributed simulation systems that power autonomous vehicle development. Design and optimize data pipelines, job orchestration, and cloud-based services enabling research teams to run large-scale experiments efficiently.

What you'll do

  • Design and implement backend services for managing and orchestrating simulation jobs at scale
  • Develop efficient data storage and retrieval pipelines using S3, Postgres, and Redis
  • Build and maintain distributed messaging systems with Kafka for event-driven workflows
  • Define and automate infrastructure as code using Terraform on AWS clusters
  • Collaborate with simulation engineers and infrastructure teams on integration and performance

What they're looking for

  • Backend service development (3+ years production experience)
  • Python, Java, or Go
  • Cloud-native architecture and distributed systems design
  • AWS (S3, EKS), Kafka, Postgres, and Redis
  • Terraform and infrastructure as code
  • Docker and Kubernetes containerization
  • Data pipeline design
  • Event-driven architecture
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

  • Tell us about a time you designed and deployed a distributed backend service in production. What challenges did you face with scaling and reliability?
  • Describe your experience with Kafka or similar messaging systems. How have you used event-driven architecture to solve a complex problem?