On-Prem DevOps Engineer

Job Overview

We are looking for an experienced DevOps Engineer who understands engineering needs and can work with engineers to make their life easier and more productive. Our team is a testament to the ability to unite engineers of different backgrounds over a common vision. We do not shy away from reality and its limitations but we also dream big. You don’t have to fit in a box. We are not looking for a superhero. But we might be looking for you!

About Zendar

Autonomous vehicles need to be able to understand the world around them not only in bright daylight, but also at night, when it is foggy or rainy, or when the sun is shining right in your face. At Zendar, we make this possible by developing the highest-resolution, most information-rich radar in the world. What makes radar powerful - its long wavelength which makes it robust to all sorts of weather and lighting conditions - also makes it really challenging to work with. We have used our deep understanding of radar physics to build radar perception models that bring a rich and complete understanding of the environment around the AV from free space to object detections to road structure.

Zendar has a diverse and dynamic team of hardware, machine learning, signal processing and software engineers with a deep background in sensing technology. We have a global team of 60, distributed across our sites in Berkeley, Lindau (Germany), and Paris. Zendar is backed by Tier-1 VCs, has raised more than $50M in funding and has established strong partnerships with industry leaders.

Your Role

To support our growing team, we’re looking for a DevOps Engineer. DevOps in a small company entails wearing many hats, supporting all the infrastructure, including IT, CI/CD, builds and testing, data uploads and Cloud interactions (Cloud support itself is handled by our MLOps team)! You will be the second engineer on the DevOps team, working with our Senior DevOps Engineer, which means that you will not only have a lot of influence in shaping all of DevOps at Zendar, but also have a lot of learning opportunities and support.

Key Responsibilities

• IT: Handle provisioning, maintenance, and purchasing of workstation and laptop hardware/software. Maintain, monitor, and troubleshoot the office network environment.


• CI/CD and Infrastructure: Maintain and adapt CI runners and CI pipelines using GitHub Actions, ensuring they remain efficient and scalable as we grow.


• Build System and Dependency Management Support: Work alongside the engineering team to manage dependencies and deploy updates to the build system, particularly focusing on CMake and Python dependency management toolchains.

Required Qualifications

• Ability to work from the office in Berkeley, CA, at least from Tuesday to Thursday.


• Engineering mindset and approach to DevOps - you want to design smart solutions, not only follow instructions.


• 2+ years in Infrastructure engineering, DevOps or similar


• Hands-on experience with CI/CD tools like GitHub Actions and a solid understanding of deployment workflows.


• Familiarity with build orchestration technologies and dependency management tools, comfort with containerization (Docker).


• Proficiency with Python and Bash.


• Comfort in managing IT in a small company (device management, user management and maintaining office network).


• A proactive approach to solving problems and willingness to take on new challenges as they arise.


• A fast learner who brings practical, goal-oriented solutions and strong critical thinking to everyday challenges.

Bonus Points For

• Knowledge of Terraform and Ansible.


• Experience with dealing with security topics in a DevOps role.


• Basic familiarity with UI design for building dashboards and internal tools.


• A track record of excelling in ambiguous or evolving roles.

What You Would Work On

Being originally an on-prem company, we have faced infrastructure challenges with the onset of ML trainings requiring Cloud environment and infrastructure. We are now actively supporting workflows both on-prem and in cloud, evaluating pros and cons of any infrastructure change. One example of an on-going project which will help us to have better parity between those two workflows is having an on-prem docker registry (Harbor), which will store local builds of our monorepo for CI. Our monorepo structure brings challenges in the build process and oftentimes pushes the optimization requirements on top of the list. This is especially important for per-PR testing, where developers need to do multiple iterations and the developer experience matters. Looking for ways to optimize our build and test runs, the next possible project could be parallelizing different parts of our testing to different CI runners, reducing the total wait time for devs. We have a new monitoring system with notifications set up for some parts of our infrastructure. We want to have good insight in the health of our infrastructure, meaning we are actively adding to it - most recently we need to report the status of our in-house app for local data synchronization between different offices (US/EU).