%20--%3e%3cstyle%20type='text/css'%3e.cls-0%20{fill:%23FF9900;}%3c/style%3e%3cpath%20class='cls-0'%20d='m117.3%2084h-14.1l39.2-79h-24.8l-20.3%2041.7-20.5-41.7h-3.8l-20.3%2041.7-20.8-41.7h-24.3l41%2083.3h8.2l18.2-37.7%2018.3%2037.8h23.7v2.8h10.7v-10.5h-10.6v3.3h0.2zm3.3-74.7h15.2l-28.9%2057.1-7.2-14.9%2020.6-42.2h0.3zm-69.3%2074.9-37-75h15.1l20.8%2042.4-5.8%2011%204.1%201.6%2016.9-33.9%207.2%2015.7-18.4%2038.1-2.9%200.1zm44.5-0.1-28.2-58.9%207.4-14.8%2029.6%2060.8-6.1%2012.9c0%200.1-2.7%200-2.7%200zm27.9%200.6v2.8h-3.1v-2.8h3.1z'/%3e%3c/svg%3e)
Working here
No open roles right now. If you are the kind of engineer described below, write anyway — we would rather know who you are before we are hiring than after.
There are no open roles today
This page has no vacancies on it and no pipeline behind it. Warqline is a small team and hires rarely; when that changes, the roles will be listed here with what they actually involve. Until then a speculative note is genuinely read — it is just read by someone who cannot offer you a job this month.
Who tends to fit
Not a requirements list. Four things that describe the work honestly enough for you to rule us out.
You operate what you build
The work here does not stop at handover. If your instinct on being handed a design is to ask who gets paged when it fails, this is the right shape of job.
You can write
There are 153 technical articles on this site and every one was written by an engineer. Explaining a system in prose is part of the work, not an adjacent skill.
You are deep in something
AWS or Google Cloud, Kubernetes, platform engineering, security, FinOps, or AI systems in production. Depth in a few areas is what we sell; breadth alone is not.
You will say what you do not know
Half this site is a statement about what we have not measured, do not hold, or cannot see. Working here means being comfortable putting that in writing in front of a client.
What the job is
Client engineering on AWS and Google Cloud: migrations, landing zones, Kubernetes platforms, delivery pipelines, security and cost work, and AI systems that have to survive production. Small team, so the range is wide and nobody is only ever doing one thing.
Remote. The company is registered in the Netherlands and the team is distributed; the systems are in someone else's cloud account, so location is mostly a time zone question. How an engagement actually runs — the call, the assessment, the build, operating it, handing it over — is set out on the company page, and it is an accurate description of the days.
What we are not offering: a bench, a rotation through unrelated accounts, or a role where you specify something and somebody else runs it.
How to write to us
Send something to partner@warqline.com. What helps: one system you built or operated and what went wrong with it, anything you have written publicly, and what you would want to be doing. What does not help: a covering letter about our mission.
We reply to speculative notes, though not always quickly, and we will tell you plainly if there is nothing. Anything you send is kept only while it is relevant and is never passed on — the same handling as any other enquiry, set out in the privacy policy.
Here about a project instead?
If you were looking for the other kind of conversation, the first call is free and forty-five minutes with an engineer.
Talk to an engineer