Do you love being in the flow as a developer and want to enable that for everyone else as well? Do you believe that the key to personal flow is in making the developer build experience fast, well-integrated, automated and with meaningful insights?

We are seeking a collaborative and curious Engineer to help drive and develop the next generation of developer infrastructure and tooling as we establish a unified, robust and scalable monorepo ecosystem for all engineers at our client.

Intro

Our client's Product Area, Platinum, has historically owned and operated both their VCS and CI systems in addition to the Fleet Management product for helping developers manage large scale software changes. In the last year, they have invested a huge amount of time and effort into the next steps of that and their migration towards monorepos. Our client's main objective is to enable developers to innovate swiftly and efficiently across software components and team boundaries while they as the Platform mission take more ownership of the nuts and bolts and amplify the developer experience.

The role is located in the Platform Developer Experience (PDX) R&D Studio within the Platform Mission. The PDX R&D Studio oversees and owns cross discipline infrastructure that cuts across all engineering, including their VCS, CI systems and beyond.

What you’ll do

• Bring your experience and knowledge of working with Bazel and scaling monorepos to millions of lines of code to help our client rethink the future of backend engineering.
• Help the team migrate to, in addition to own and maintain Bazel and any related abstractions built to improve the developer experience.
• Collaborate with adjacent infrastructure teams across the company to develop what a best in class monorepo experience means.

Who you are

• Strong passion for making developers highly productive
• Experience developing and maintaining tools for large monorepo-based codebases
• Excellent problem solving skills
• Experience working with the Bazel build system and its ecosystem (e.g: rulesets such as rules_jvm_external, IntelliJ Bazel plugin, etc.)
• Fluency in Java, Python, Starlark and TypeScript