Software Engineer II - Build Tools

Role overview

This Software Engineer II role strengthens the build and release foundation used by teams developing safety-critical autonomous systems. You will build and operate production infrastructure, improve CI/CD pipelines, and write scalable automation that increases release velocity while protecting reliability and software quality. The role is available remotely in the United States or in a hybrid arrangement in Ann Arbor, Michigan, and includes participation in an on-call rotation.

Responsibilities

- Translate requirements into automation and infrastructure solutions, seeking input from peers and managers on scope and objectives. - Participate in design discussions, proposing implementation approaches and producing diagrams and technical documentation. - Develop, test, debug, and maintain code using unit and integration testing practices. - Collaborate through code reviews and integration work, contributing to shared quality standards and continuous learning. - Support production operations by investigating incidents, reviewing logs, participating in root-cause analysis, and taking part in on-call coverage. - Improve runbooks, tutorials, API documentation, and user guidance while coordinating with teams across the broader product organization.

Requirements

- A bachelor’s degree with at least four years of experience, or a master’s degree with up to three years of experience. - Ability to handle critical technical challenges with limited supervision and exercise strong independent judgment. - Experience with AWS services such as IAM, EC2, and S3, plus Docker and container orchestration platforms including Kubernetes, EKS, or ECS. - Fluency in an object-oriented language, preferably Python, along with scripting or templating using Bash or Go. - Hands-on experience with build systems such as Bazel, CMake, Maven, or Gradle and code-quality or coverage tools. - Working knowledge of CI/CD, workflow orchestration, logging, and monitoring platforms.

Nice to have

- Experience with artifact or package registries such as JFrog Artifactory. - Familiarity with safety-critical or embedded software practices and testing tools. - Exposure to C or C++ in addition to Python.