Cloud Engineer

Elevate our cloud to the next level

In the current digital age defined by the power of cloud technology, delivering seamless SaaS products to businesses worldwide is at the heart of what we strive. Our cloud operations are the foundation of our cutting-edge SaaS offerings, ensuring they are secure, scalable, and impeccably reliable, both on our own private Gomibo Cloud and other public clouds.

Cloud Engineering at Gomibo

Our digital ecosystem relies on the seamless operation of cloud infrastructure, and this is where you come in. As a Cloud Engineer at Gomibo, you'll take center stage in managing and enhancing our cloud systems. From configuring cloud resources and optimizing deployment processes to crafting the cloud infrastructure that underpins our innovative solutions. All while navigating the ever-evolving landscape of cloud technologies and making sure we stay ahead of the curve.

As a Cloud engineer, you will contribute to the design and optimization of our cloud-based systems for our very own Gomibo Cloud, from architecting database clusters to orchestrating applications in our private cloud. You will tackle challenges that span from fine-tuning the heartbeat of key components to harnessing the full potential of cloud resources.

Our stack

We continuously look at the newest solutions and technologies. Below is a limited list that could be considered as the backbone of our Cloud stack to help us deliver top-notch services to our customers:

• Kubernetes: For orchestrating our containers
• Flux: Automating our Continuous Delivery (CD)
• Vault: For secure secrets management
• Prometheus: Powering our monitoring solutions
• HAProxy & NGINX: Optimizing load balancing and realizing High availability
• Ansible: For Automation in infrastructure management
• Helm: Simplifying and acceleration application deployment

What do you do as a Cloud Engineer?

Your responsibilities will encompass:

• Cloud Infrastructure Management: Maintain and optimize our cloud infrastructure, ensuring efficient resource allocation, scalability, and responsiveness.
• Continuous Innovation: Identify opportunities to enhance our cloud ecosystem by adopting emerging technologies and building innovative solutions.
• Security and Compliance: Implement and enforce security best practices, ensuring the integrity and confidentiality of our cloud-based systems.
• Performance Optimization: Regularly assess cloud system performance, identify bottlenecks, and optimize configurations for optimal operation.
• Collaborative problem solving: Collaborate closely with application, network and DevOps engineers to ensure the seamless operation of our cloud infrastructure and development operations.
• Automation: Develop and maintain automation scripts and tools to streamline cloud deployment and management processes.

You work at the office in Groningen during your entire onboarding period. After that, we have a remote working policy of a maximum of 2 days per week. More days are possible in consultation.

Method of working

• Gomibo maintains a flat organisational structure, which means that there isn’t a layered hierarchy, despite different degrees of work experience. Decisions are not imposed from the top down, but rather made in dialogue with the team.
• You are the technical expert. So no non-technical colleagues who sit in your technical chair. Cobbler, stick to your last.
• We replace the legacy proactively. Every system has a legacy, of course, but you don't have to keep legacy systems going forever.
• Informal working atmosphere. Everyone can be themselves with us.

Also nice to know

This is what your day could look like:

• You grab a cup of coffee from the pantry and start your day by. You have a look at your to-do for today and have a quick look at the agenda for today’s meeting with Arthur
• During the daily stand-up with the DevOps team. A colleague addresses a slight increase in resource utilization. You discuss it briefly and decide further investigate it today
• You start your day by working on researching the newest update for a Prometheus: There are some new features introduced that might be beneficial for other application developers.
• Time to wrap up your findings. You write down the new benefits and ask other teammates to give their 2 cents on the matter.
• Lunch break! Today is “Subway-day”, where all DevOps & Gomibo cloud team members grab lunch together and enjoy it on our roof terrace. The conversation moves between the latest tech trends, the most recent vulnerability threat, weekend plans, and that upcoming team-building event.
• Post-lunch, you dive deep into logs, metrics, and traces to pinpoint the root cause of the resource issue. After some investigation, you discover a misconfiguration in one of the cloud resources.
• Coffee break and a quick meeting with Mathijs – Network Engineer from your team – about optimizing network routes to improve data flow between servers. Together, you find a few next steps that are logical to work next on.
• Next up, you look into a request from a developer that reached out to discuss the deployment of a new service in the cloud and its potential impact on performance. You collaborate to share ideas and set up a plan for a smooth deployment.
• Before winding up, you check the system dashboards again. Everything looks stable, no big issues detected. You schedule some cloud infrastructure updates for off-peak hours.