How do you make our customers happy?
And what is your biggest challenge?
Well, for your fellow cloud engineer and hopefully future teammate, composing this text was a tougher-than-expected challenge. All joking aside, we really do want to take you on board, because we’re already in the cloud, but we need more people to reach ‘cloud nine’. Want to help us engineer on our cloud infrastructure at GCP? Want to discover what cloud engineering is all about in one of the biggest and most dynamic infrastructures the Netherlands has to offer?
Your responsibilities as a Cloud Engineer
We are heavy users of Kubernetes: we have many thousands of pods running on multiple GKE clusters. At bol.com we believe in agile & autonomy, so our product teams are able to provision GCP projects and Kubernetes namespaces themselves. For provisioning, all cloud teams use an in-house built provisioning system developed on top of Puppet, Terraform and Kubectl. With access to alpha/private GCP features we are able to stay ahead of the curve. We are in the midst of integrating and rolling out Istio in our GKE clusters and datacenters to create one big service mesh. All of this results in some rather stormy clouds, so we balance product engineering with reliability engineering.
It’s up to you and your team to run the cloud and datacenter infrastructure. To engineer new features and to make sure existing features stay available, secure and cost effective. Together with two other teams, we form a group focused on provisioning. That group is, in turn, part of the Space that manages our technical platform. At our scale it makes sense to offer a platform to our ~100 product teams, so they can focus on building awesome software without having to worry (too much) about the infrastructure.
Why you can make a difference
Because you bring the whole package: cloud engineering (preferably GCP), Kubernetes, Terraform, VPC networking, containers, Puppet and Linux experience. If you are also familiar with Redhat/Linux system engineering, even better! Development skills in Python / Bash are a must. As is (basic) knowledge of networking, HTTP and the inner workings of the internet in general. But hey, we take it that’s more or less a given. And you do understand Dutch, at least a bit, so you’re able to ask you colleague to get you a cup of coffee.
3 reasons why this is(n’t) for you
- Because you want to be an active member of a seasoned and skilled engineering team
- Because you love to chat about making things better and welcome different viewpoints
- Because you are a strong writer; documenting engineering feats is your forte
- Because you flat-out refuse to be part of a reserve team, even if we compensate yo
- Because you blindly make changes in production.
- Because you are a lone wolf – sharing knowledge is for sheep
Good! If you have all the skills. Contact us!
If you lack some of the skills but want to learn them all within 1-2 years. Contact us!
How it works
Your applicationCarefully, we take a look at your application. Within 2 weeks you know if we invite you for an interview.
First contactWe call you to set up an interview. And since we’re already talking: feel free to ask any question you may have.
First dateIn this first interview we’ll get to know each other. We want to find out more about you. Work experience is interesting, but we also want to find out more about you as a person. Together, we’ll find out if this job is a match made in heaven.
Your next interviewBefore the next interview we will ask you to take an online assessment. We’ll also discuss the position and your team in depth.
Is this love?2 interviews are usually enough to see if it’s a match. And if you agree… well, it’s the beautiful beginning of your career at bol.com :)