System Engineer | Email Team

About the role

JOIN THE TEAM BUILDING AN AI-FIRST COMPANY.

Hostinger serves more than 5.5 million clients across 150 countries, but we're still excited about what we're creating next.

AI is changing how we build products, support customers, work together, and solve problems. It helps us move faster, spend less time on repetitive work, and focus on bigger ideas.

If you want your work to influence both what we build and how we build it, we'd like to meet you.

Our culture: Guided by 10 company principles https://www.hostinger.com/principles

YOUR ROLE AT HOSTINGER

As System Engineer, you'll join one of the few places left where a single team owns the whole stack end to end - compute, storage, networking, and the services running on top of it. Email is what makes that infrastructure hard: it's stateful, latency-sensitive, adversarial, and it never stops. You'll join at a point where large parts of the platform are being modernized, so there's genuine architectural work ahead, not just maintenance of someone else's decisions. This isn't a role where you follow playbooks - you'll write them.

Curious to learn more? Connect with your team: Edgaras Lukoševičius, Engineering Manager, Email Hosting. https://www.linkedin.com/in/edgaras-lukosevicius/

YOUR DAY-TO-DAY

- Build and scale the infrastructure behind the service. Design and operate the systems that carry millions of messages a day — compute, networking, routing, and throughput — at a volume where a fraction of a percent is thousands of clients.

- Run storage at scale. Petabytes of customer data across a distributed storage fleet: capacity planning, performance tuning, backups, and data integrity.

- Automate everything you touch. Our infrastructure lives in code. If you did it manually twice, the third time should be a pull request.

- Engineer how we ship. Build the testing and deployment pipeline that lets a platform this large change safely — infrastructure tests, preflight checks, progressive rollouts. Confident releases are an engineering achievement, not an accident.

- Own monitoring and observability. Metrics, logs, SLOs, and alerting — build the systems that surface a problem while it's still small, so it's solved before anyone notices it.

- Fight spam and abuse. Tune the filtering engines, rate limits, and authentication that stand between millions of mailboxes and everyone trying to get into them.

- Solve problems at the root. When something surfaces, the interesting question isn't how to close the ticket — it's what change makes that entire class of problem stop happening.

- Share what you learn. Review code, write the runbook, explain the failure mode. The team gets stronger, or it doesn't scale.

WHAT WILL HELP YOU SUCCEED

- Strong Linux experience (5+ years) — deep and hands-on, not just comfortable at a shell.

- On-prem and cloud. We run most of our systems on our own hardware, with parts in the cloud (GCP, AWS, Cloudflare). We're looking for either a strong on-prem and virtualization background (Proxmox, KVM, bare metal) with cloud exposure, or a strong cloud background with real hands-on on-prem experience.