Own and improve the development experience by designing and maintaining build systems and developer tooling at Eka Robotics.
Posted by employer 1 week ago
First seen on Joblaze 53 minutes ago
Last verified on the company career page 53 minutes ago
Skills & Technologies
What you'll build
Must have
Nice to have
Not disclosed in this posting: compensation, years of experience, work arrangement, visa sponsorship.
Joblaze summary
In this role, the Developer Productivity Engineer at Eka Robotics focuses on enhancing the development experience by designing and maintaining the build system and tooling used by engineers and researchers. Key skills include expertise in build systems, proficiency in Python and Linux, and a strong understanding of dependency management and reproducibility. This position is ideal for someone with a background in software engineering or systems tooling, particularly those who thrive in ambiguous environments and can drive solutions from concept to implementation. The team is dedicated to improving workflows and reducing friction, ultimately enabling faster and more reliable robotics developme
Joblaze insights
Quick facts
From the original posting
Making progress towards the above requires tools that let researchers and engineers move quickly from an idea to a working experiment and, ultimately, to a real robot.
Role Overview
We're looking for an engineer to own and improve that development experience. You'll design, implement, and maintain our build system and developer tooling, working directly with the people who use them. Your impact will show up in faster feedback, reliable builds, easier onboarding, and fewer interruptions across the team.
Responsibilities
Own & Evolve Build Infrastructure: Own and evolve our Bazel build system, including build rules, toolchains, dependency management, and remote caching.
Optimize Velocity & Reliability: Make builds and tests faster and more reliable across local development and CI.
Streamline Engineering Workflows: Improve everyday workflows, from setting up a development environment to debugging a failed test or packaging a training job.
Build Internal Tooling as a Product: Build tools that make common tasks straightforward and failures easy to understand.
Collaborate & Measure Impact: Work with researchers and robotics engineers to identify recurring friction, prioritize improvements, and measure whether they help.
Ensure Multi-Platform Reproducibility: Keep development environments and build outputs reproducible across Linux, macOS, and GPU-enabled containers.
Minimum Qualifications
Build Systems & DevEx Experience: Track record of building and maintaining build systems, developer tools, or CI infrastructure used by other engineers.
Product Mindset for Internal Tools: Ability to write clear, maintainable software and treat internal tools as products with users.
Systems & Build Theory Expertise: Deep understanding of dependency graphs, caching, reproducibility, and the tradeoffs involved in speeding up builds and tests.
Polyglot & Systems Tooling: Proficiency with Python, Linux, shell tooling, and debugging problems across language and system boundaries.
Autonomy & Ownership: Ability to take an ambiguous problem, work with its users, and carry a solution through implementation and adoption..
Preferred Qualifications
Hands-on experience with Bazel
Experience managing C++ toolchains, Python packaging, GPU software dependencies, or machine learning training infrastructure.
Prior robotics or reinforcement learning experience
Build & CI/CD: Bazel, Bzlmod, Gazelle, GitHub Actions
Languages: Python, C++
Infrastructure & Containerization: Docker, Google Cloud Platform (GCP), Terraform
Compute & ML Frameworks: JAX, CUDA, MuJoCo/MJX, NVIDIA Warp
Note: You do not need experience in every tool listed above to be successful in this role.
Success means engineers spend less time waiting for builds, repairing environments, and diagnosing infrastructure failures, and more time developing and testing ideas. You'll build the tools that multiply the team's output.
Standard company text repeated across Eka Robotics's postings is omitted here.