00Career

Join a team small enough to name

AIClouds is run by six people, and every one of them is named on the About page with the role they hold. These roles are not slots in an org chart: you work with the person who decides, on systems that are already carrying somebody else's traffic.

See open positions

2 open rolesremote

01Open positions

Find your next roleat AIClouds

Roles are described as they are. Level, contract type and salary band are not written here because they are not settled yet — ask in the form and the answer will be straight.

DevOps engineer
Build and run client infrastructure across AWS, Azure and GCP: Terraform, Kubernetes, CI/CD pipelines and the monitoring that tells you when they break. You take a system from discovery to the point where the client runs it themselves — the same hands the whole way, no handover to a support tier.
- Remote
- AWS · Azure · GCP
Apply
Content manager
Own what this site says: the blog, the case studies, the copy on the pages. The subject is technical — cloud migrations, cost reduction, incidents — and the raw material comes from the engineer who did the work, so the job is turning real project detail into text, not producing volume around a keyword.
- Remote
Apply

Is your role not on the list?

Tell us what you do and what you want to be doing. There is no HR queue here — the message goes to the person who would work with you.

Drop us a line

02How the work is set up

Three things that aretrue today

01
Fully remote
There is no office to come to and no plan to open one. Hours are yours to arrange around the calls the work actually needs.
02
You talk to the person who decides
The team is small enough that decisions do not travel. You reach the person who makes them, and nothing waits a week for an answer that takes a sentence.
03
Production systems, not sandboxes
The logos above are clients, not aspirations. What you touch carries somebody’s traffic on the day you touch it — which is also why the review is careful.

03Values to work with us

What we expectfrom each other

01Own the outcome, not only the ticket
The task is not finished because a change was merged. It is finished when the system behaves as intended, the people relying on it understand what changed and the next person can operate it without reconstructing the work from chat history.
02Say the difficult thing early
A missed estimate, a risky assumption or a design that is not working gets named while there is still time to act. Quiet agreement is not helpful here. Clear disagreement, backed by what you see and paired with a way forward, is.
03Write for the person who was not in the room
Decisions, runbooks and handovers must make sense without the meeting that produced them. Important context does not stay in private messages or in one person’s memory, and documentation is part of delivery rather than work saved for later.
04Ask before uncertainty becomes production risk
Nobody is rewarded for struggling alone. When the blast radius is unclear, another set of eyes comes in before the change goes out. Seniority here means knowing when to make a decision and when the responsible decision is to ask.
05No status theatre
Progress is shown through working systems, useful notes and specific blockers — not through making activity sound larger than it is. A short honest update is more valuable than a polished report that leaves the real state hard to see.

04Expertise

Our certification pathon the clouds we build on

Multi-cloud is a claim that is easy to make and hard to hold. Here is every exam we take on the three platforms we build on — passed, in progress and scheduled, with nothing dressed up as the other.

Amazon Web Services4
- AWS Certified Solutions ArchitectScheduledAssociateSAA-C03
- AWS Certified SysOps AdministratorScheduledAssociateSOA-C02
- AWS Certified DeveloperScheduledAssociateDVA-C02
- AWS Certified Cloud PractitionerIn progressFoundationalCLF-C02
Microsoft Azure4
- Azure AdministratorScheduledAssociateAZ-104
- Azure Security EngineerScheduledAssociateAZ-500
- Azure DeveloperScheduledAssociateAZ-204
- Azure FundamentalsScheduledFoundationalAZ-900
Google Cloud3
- Associate Cloud EngineerScheduledAssociateACE
- Associate Data PractitionerScheduledAssociateADP
- Cloud Digital LeaderScheduledFoundationalCDL

05Tech stack

What you wouldactually be working with

Not a wish list: this is what is running at clients right now. Nobody is expected to know all of it — the DevOps role touches most of it, the content role writes about it.