PHP Developer | Email Team

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

Your role at Hostinger

As a Software Engineer on the Email Team, you’ll build and run high-performance, high-scale public and private APIs and the internal services behind them, in Go and PHP: authentication, provisioning, webhooks, and websockets; webmail, contacts, calendar, email migration/import system; routing, policy, and spam filtering systems. None of it stops at deployment - you’ll be watching it in production and making it faster as it grows.

The stack is mostly PHP (Laravel), with the highest-throughput services built in Go, backed by MySQL, Redis/Valkey, Memcached, and ClickHouse, with Kafka/Redpanda moving events between them, and Grafana and Sentry watching it all in production. You don’t need Go coming in - just the willingness to learn it. Large parts of the platform are still being shaped, so you won’t just be shipping into an existing pattern - you’ll help set it.

Curious to learn more? Connect with your team: Edgaras Lukoševičius, Engineering Manager

Your day-to-day

• Build across the platform. Provisioning, authentication, webhooks and websockets, email apps, policy, routing, and spam filtering, and the public APIs and SDKs built on top.

• Own features end to end. Discovery to deployment, and the follow-up after - not just the pull request.

• Work mostly in PHP, and in Go for the high-scale, high-availability pieces.

• Make it fast. A slow query here isn’t a minor bug - it’s felt by millions of mailboxes at once.

• Harden the product. Authentication, sessions, and the edge cases that become security issues if nobody catches them.

• Watch it in production. Grafana, Sentry, and the alert that catches it before a client does.

• Raise how the team builds. Tooling, automation, and docs that make the next feature faster to ship.

• Review, and be reviewed. Raise the bar on both sides of a pull request.