Luveedu Cloud is a small, technical team running hosting, domains, and business email for customers around the world. We hire people who want to own a problem end to end, and we keep the layers between you and the work as thin as possible.
We build and run the platform ourselves - hosting, DNS, email, CDN, and the tools around them. That changes what a job here looks like.
You own a service, not a ticket queue. The person who builds a system also writes its runbook, documents the failure modes, and decides when it is finished.
We stay small on purpose. Decisions take hours rather than quarters, and there is no layer of coordinators between you and the problem.
Real infrastructure, not a thin wrapper over someone else's API.
NVMe storage, LiteSpeed, anycast DNS, DDoS scrubbing, and 20 data centres. The work is real infrastructure, not a thin wrapper over someone else's API.
Customers reach us from every timezone, through 200+ CDN points of presence, on a platform that has to keep running while you sleep.
Benefits are the same for remote and office-based team members. There is no separate tier for people who work from home.
One package. Remote or in the office.
Nothing here depends on where you sit, and nothing is traded away for working from home.
Medical cover for you and your dependants, with the option to extend to family members at the group rate.
Paid annual leave, public holidays, and separate sick leave. Taking leave is scheduled, not negotiated.
An annual budget you control for courses, books, certifications, and conferences relevant to your work.
Two separate allowances, because a laptop is not a desk.
A hardware allowance for the machine you actually want to work on, refreshed on a fixed cycle.
A one-time allowance for a desk, chair, and the basics of a workspace that does not hurt your back.
Core overlap hours for meetings, and the rest of the day shaped around your timezone and your focus.
A bonus tied to the impact of your work, reviewed twice a year against written goals.
On-call rotation is scheduled in advance and paid. Nobody is expected to be reachable for free.
Most of our work happens in writing, across timezones. That is a deliberate choice, and it shapes how decisions get made and how incidents get handled.
Status updates, design discussions, and handovers happen in writing so nobody has to be online at a specific hour.
Every meaningful decision has a short record: the options considered, the choice, and the reason.
When something breaks, we review the system that allowed it, not the person holding the pager.
Runbooks, architecture notes, and support macros are part of the work, not an afterthought.
Each listing states the location and the engagement type. Apply by email with your CV and a short note about what you would own.
Nothing here fits your skills? Send a speculative application and tell us what you would own.
You will know who you are speaking to at each stage, what is being assessed, and when to expect a decision.
We read every application ourselves. If your experience matches the role, you get a reply with the next step and who you will be speaking to.
A 45-minute call about how you work: systems you have run, problems you have debugged, and the trade-offs you made.
A short task drawn from real work - a troubleshooting scenario, a small script, or a markup component - reviewed with you afterwards.
A written offer with the role, the compensation, and the expectations. Two references, then a start date that suits you.
We are a distributed team with a shared written record, so you can catch up on a project without asking five people what happened. Planning is done in public, priorities are explicit, and the roadmap is short enough to remember.
Support work is respected rather than treated as a stepping stone. Engineers rotate through it because the fastest way to understand a platform is to sit with the people using it at 2am.
We do not expect anyone to be a culture fit in the social sense. We expect you to be reliable, honest about what you do not know, and good at finishing things.
We take a small number of interns each year in support, systems, and frontend development. An internship here has a defined project, a named mentor, and a real deliverable that ships.
Use the subject line "Internship application" so it reaches the right inbox.
What to expect before you send anything in. If your question is not here, write to us and a person replies.
Still have questions? Our security team is available 24/7.
Contact Support