Chalk
Software Engineer, Developer Productivity
About this role
Chalk seeks the first dedicated Software Engineer for Developer Productivity to own and scale build systems, CI infrastructure, and developer experience across a high-performance ML data platform. You'll work with Bazel, C++, and Rust to optimize builds and tests for a system handling 100k QPS with 5ms latency, serving the entire engineering organization.
What you'll do
- Own Bazel build system including toolchains, dependency management, and remote execution infrastructure
- Build and maintain containerized dev environments with consistent experience across engineering team
- Establish and enforce test and benchmark patterns aligned with system latency requirements
- Maintain CI health by optimizing speed, reliability, and completion rates across GitHub Actions and Buildkite
- Reduce test flakiness and improve build performance through caching, remote execution, and dependency hygiene
- Drive performance improvements in C++ and Rust builds through toolchain optimization and system design
What they're looking for
- Bazel (BUILD files, Starlark, toolchain configuration, workspace migration)
- C++ software engineering
- CI/CD systems and infrastructure
- Build system optimization and remote execution
- Docker and containerization
- Systems performance and benchmarking
- Rust (beneficial)
- Buildkite or GitHub Actions
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.
Chalk
Chalk builds a machine learning data platform that powers ML applications at scale with developer-friendly tools and infrastructure. The company is hiring full-stack engineers, frontend engineers, infrastructure engineers, backend engineers, and a content lead to build and expand their Rust-powered platform across distributed systems, cloud infrastructure, and developer experience.
View all jobs at ChalkLikely interview questions
- Walk us through a Bazel migration or large workspace you've worked on—what were the biggest challenges and how did you solve them?
- How would you approach reducing build times for a C++ project while maintaining hermeticity?