DevOps Engineer
We are hiring a remote DevOps Engineer with 2 or more years running production systems to keep our builds fast, our deploys boring and our backups proven, for our own products and for clients.
- Location
- Remote, worldwide
- Type
- Full-time
- Openings
- 2
- Experience
- 2 years or more
- Stack
- Linux, Docker, Dokploy, CI runners, Cloudflare
- Posted
- 30 October 2026
What you will do
- Run our apps in Docker on Linux servers, ARM and x86, deployed through Dokploy.
- Keep our self-hosted CI runners fast and reliable: image builds, caching, test jobs and deploy gates.
- Look after DNS, TLS, caching and protection in Cloudflare, and the reverse proxies behind it.
- Own backups for PostgreSQL and SQLite: schedules, offsite copies and restore tests that prove they work.
- Set up monitoring, error tracking and alerts that point at real problems.
- Do the security basics properly: least-privilege access, secrets out of code, patched hosts and private networking.
- Help on client work: cloud cost and security audits, AWS setup and migrations, pipelines and disaster recovery.
- Write runbooks that someone else can follow at 2 a.m.
What we look for
- 2 or more years running production systems on Linux.
- Deep Docker: multi-stage and multi-architecture builds, networking and volumes.
- CI/CD pipelines you built or kept running.
- DNS, TLS and HTTP: you can trace a 502 from the browser to the container.
- Database operations: backup, restore and upgrades.
- Scripting in Bash and Python.
- Hands-on AWS, for client work.
Good to have
- Cloudflare
- Dokploy, Coolify or Docker Swarm
- Tailscale or WireGuard
- Terraform
- Go
- Cloud cost optimisation
How we work
Clear scope, visible progress.
Written scope first
Every piece of work starts with a short written scope: what ships and when.
Weekly demos
We show progress on a live link every week, to each other and to clients.
A direct line
You talk to clients and to our founder directly. There is no account layer in between.
Remote and written
We work remotely and write things down: decisions, handovers and runbooks. Expect a few hours a week of overlap with India time (UTC+5:30) for demos and reviews.
How to apply
Email [email protected] with “DevOps Engineer” in the subject line, and send:
- A system you ran: what it was, what it served, and what you changed.
- An incident you handled, and what you changed afterwards so it would not happen again.
- Your CV or LinkedIn profile, your time zone, and when you could start.
What happens next
- We read and reply. We read every application and reply to each one, including when the answer is no.
- A conversation. If there is a fit, a call of about 30 minutes about work you have done.
- A clear answer. We decide and tell you either way. We never charge applicants anything.
Apply for DevOps Engineer.
We read every application and reply to each one.