Cloud Infra Engineer

Providing a secure, repeatable platform to allow teams to deploy to the cloud

How do you make our customers happy?

Our focus in Team Hammer is to provide a provisioning product with “batteries included” that lets bol application teams deploy their application to the public cloud (GCP) while simultaneously enforcing bol policies and standards to make sure our applications stay secure and compliant. Our provisioning tool is mission critical for bol, enabling hundreds of engineers to manage their cloud infrastructure.

We make our customers happy by making this experience as friction-free as possible while addressing the needs for data security, customer information privacy, and cost efficiency. We want our teams to focus on their products, not on having to build and maintain a complicated infrastructure for their apps. What you’ll do as a Cloud Infra Engineer

What are our products?

Our primary product is an in-house tool named R2D2. This tool allows application engineers to deploy their infrastructure to the cloud. Under the hood we ensure that we respect various constraints regarding PII (personally identifiable information), financial information, network policies, and other various security considerations. We aim to provide both declarative infrastructure and declarative policies.

Our current mission is to upgrade the internals of this system and move towards a thinner, more lightweight version of our provisioning API. A lot has changed in the realm of platform engineering since we built this version, so we’re actively working on replacing this with more industry-standard tools, frameworks and concepts.

Who is on the team?

You’ll be joining a team of seven people. Five platform engineers, one group product manager and one engineering manager. Our team is a mix of internationals (South Africa, Finland, Netherlands, Bulgaria, United States) that skews more towards the senior end on the spectrum of experience. Many people on the team have been here at bol for many years and have been working in the domain of Platform Engineering and DevOps for quite some time.

What will I do?

• Help us to continue our approach towards modernizing our existing provisioning API. Our goal is to reduce complexity, minimize dependencies and lower the effort to maintain. You'll join us in our current mission to improve this tool
• Help us design the user interface for our provisioning tool. We currently have our own self-developed DSL which application teams currently use. In the coming year we're going to look at how we want to redesign this to make it simpler and easier for other engineers to use
• Lean into bleeding-edge, public cloud infrastructure management. We allow teams to provision their applications in GCP (Google Cloud Platform) and heavily leverage KCC (Kubernetes Config Connector).
• Help support and troubleshoot issues for teams. We are responsible for making sure that errors and bugs with our product get attention and get solved. You'll participate in a regular support rotation that puts you in touch with our customers and their issues

3 reasons why this is (not) for you

Iets

• Kubernetes Expertise
• We're making big investments in the Kubernetes landscape. This is our tool of choice to provision highly available, highly scalable workloads into the public cloud. This is the right role for you if you have hands-on experience working with k8s.
• Configuration Management Tools
• You are familiar with the landscape of configuration and infrastructure management tools. Terraform, Kubernetes Config Connector, Ansible, Puppet, Open Policy Agent - all of these tools ring a bell and mean something to you.
• High standards
• We're on the critical path for many of the teams here at bol which means that we take our jobs and our work very seriously. We invest in brainstorming with our colleagues about solutions, we take merge request reviews seriously, and we test accordingly in multiple environments before we ship to production. If you have high standards for the work you do then this is the right place for you.

Niets:

• Focus on Enabling Others
• This role is centered on providing tools and infrastructure for internal engineering teams, rather than developing end-user-facing features or products. If you’re looking for a position that directly impacts end customers or involves more visible outcomes, you might want to consider if this aligns with your ambitions.
• Commitment to Modernizing Legacy Systems
• While you’ll work on cutting-edge cloud technologies, a significant part of the role involves modernizing and simplifying an existing in-house tool (R2D2). If you prefer working exclusively on greenfield projects or are not keen on improving existing systems, this aspect might require adjustment.
• Collaborative, Process-Oriented Work
• The team emphasizes rigorous processes, including detailed code reviews, extensive testing across environments, and a strong focus on compliance and security. If you thrive in fast-moving, exploratory environments with less structure, this role’s collaborative and methodical approach might feel less dynamic.