Careers › Engineering
Infrastructure & Cloud Engineer
The terminal runs on dedicated Linux servers in Europe, and it stays up because somebody keeps it up. This role owns that: the machines, the deploys, the database in production, the alerting, and the parts that should move to managed cloud as load grows.
What you would do
- Own the servers. Provisioning, hardening, patching, certificates, and tuning Apache and PHP-FPM for a workload that spikes at the open.
- Make releases boring. Repeatable, reversible, and quick enough that nobody puts one off until the weekend.
- Run Postgres properly: backups that have actually been restored, replication, and version upgrades that do not lose a row.
- Build alerting that catches a dead feed or a full disk before a user emails about it, and keep it quiet enough that people still read it.
- Plan and carry out the move of whatever genuinely belongs in managed cloud, without a weekend of downtime to pay for it.
You would fit if
- You have run production Linux where you were the person who got called.
- You know AWS properly — VPC, IAM, RDS, S3, CloudFront — including what it costs and where the bill goes wrong.
- You have restored a database from a backup under pressure at least once, and it worked.
- You write infrastructure down. Terraform, Ansible, or plain scripts another person can run without you.
- You are sceptical of complexity. We would rather run three things well than fifteen badly.
Skills and stack
Linux, Apache, PHP-FPM, PostgreSQL and TimescaleDB today, on our own servers rather than a cloud estate. AWS and Terraform are on this list because part of the job is deciding what should move there and what should stay exactly where it is.
Working hours and location
Full time, remote and asynchronous. We work across European hours and overlap for a few of them; where you are matters less than whether the overlap is workable. There are no stand-ups and no status meetings, and nothing here is measured in hours logged.
One caveat specific to this role: infrastructure means being reachable when production is not well, and we would agree what that looks like before you start rather than after.
Education and experience
No formal educational credential is required and there is no degree filter. What counts is whether you have run this kind of system in production and can point at it: a repository, a postmortem you wrote, or an hour talking through the last thing that broke on you.
Compensation
Discussed openly on the first call, in numbers, before anyone spends time on a process. It depends on scope and where you are. We are independent and not venture funded, so it is competitive rather than extravagant, and we will not pretend otherwise. A PRO account is included, along with direct access to the founder and a genuine hand in what the product becomes.
How hiring works
Four steps, usually inside two weeks: you write to us with whatever shows your work best, a call of about forty-five minutes where compensation is discussed rather than deferred, a small scoped task from the real backlog that we pay for at the agreed rate, then a decision with a reason. No unpaid take-homes, no algorithm puzzles, and you hear back either way. The careers page sets out each step in full.
How to apply
Email us with the role in the subject line. A CV is fine, so is a repository, a piece you wrote, or a paragraph on something in the terminal you would change. No cover letter and no form. Have a look at the product first — open the terminal; the free account shows most of it.
Apply — careers@qfiterminal.com