DevOps engineer

Webosa runs on its own dedicated hardware with Proxmox as the virtualisation layer. On it live the shared hosting, the VPS machines and the business email of our clients: hundreds of websites, mailboxes and domains that simply have to work, at three in the morning too. We do not buy in a managed platform, we build and run it ourselves. That means full control over the stack, and the responsibility that comes with it. We are growing, and we are looking for someone who not only keeps that platform up but also makes it steadily more boring: less manual work, fewer surprises, more that takes care of itself.

What you will do

• You manage the virtualisation layer: you set up nodes, allocate resources and keep capacity planning up to date, so a full server is never a surprise.
• You automate recurring work. Provisioning new clients and environments, backups, updates and recovery actions should be scripts, not actions.
• You watch over uptime and performance, and when something breaks you tackle the cause instead of the symptom. What went wrong once shouldn't quietly come back.
• You keep security in order: patch policy, hardening, access management and separating customer environments.
• You run the back-up and recovery process and actually test it. A back-up you have never restored is an assumption.
• You set up monitoring and alerting so that we see a problem before a customer calls, without burying everyone under notifications.
• You think along about the next step in the infrastructure: extra hardware, network layout, redundancy and what that may cost per customer.
• You write down how things work, so knowledge doesn't stay in one person's head.

What you'll work with

• Proxmox on our own dedicated servers
• Linux, NVMe storage, Plesk as the hosting panel
• PHP 8.5 with OPcache, MariaDB, Redis
• Cloudflare at the edge, UptimeRobot for monitoring
• Laravel for our own applications and customer portal

What you bring

• You're at home on Linux and feel more comfortable on the command line than in an interface.
• You have experience with virtualisation, for example Proxmox, KVM or VMware, and you understand what happens under the bonnet.
• You automate work away in Bash, Python or something similar, and make deliberate choices about what you do and don't automate.
• You understand networking, DNS, TLS and mail flow well enough to unravel an outage yourself instead of passing it on.
• You can prioritise when several things are beeping at once, and you keep a cool head during an incident.
• You work carefully with production systems: you know when to do something at night and when to check in first.
• Experience with Plesk, hosting environments or email infrastructure is a big plus, not a requirement.

What you get

• Full ownership of the infrastructure, not a slice of someone else's platform.
• Fully remote work, you decide where and largely when. 24 to 40 hours, by arrangement.
• Short lines: no layers of management between you and a decision about the stack.
• Room to solve things structurally instead of working through tickets.
• A platform that is growing, so you help build what it looks like two years from now.