Open roles
None
right now.
We are not hiring at the moment. There is no pipeline, no waiting list, and no role being quietly held open to see who turns up.
A job goes on this page only when it genuinely exists -- when there is more work than the team can do, a budget to pay someone for it, and somebody at the other end reading every application. Until one of those is true, this section stays empty rather than collecting applications for a job nobody is going to get.
That is not the end of the page, though. Below is what we look for when a role does come up, and what to send if you would rather we knew you existed before then.
The shape of the person
Who tends to
do well here.
We are engineers who talk to the people paying for the work. That combination is rarer than it sounds, and it is most of what we are looking for.
- 01You have built something and shipped it
- Finished, live, used by somebody who was not you. Half-built experiments are worth talking about, but the thing that went out into the world tells us far more.
- 02You write in plain English
- Most of this job is understanding a business that is not yours, then explaining a trade-off to someone who does not write code. If that part feels like a chore, this will be a hard place to work.
- 03You ask what the business actually needs
- The useful first question is how the work happens now, not which framework to reach for. Nobody we build for cares what it is written in.
- 04You finish the last ten per cent
- Error states, empty screens, the thing that happens when the upload is 400MB and the signal drops in a lift. That part is the difference between a demo and software.
- 05You say when you do not know
- Nobody here knows everything. Saying so on day one is cheap. Finding out in week six is not.
- 06You are willing to be on the call
- Small team, nobody in between. The person on the other end is a hotel owner or a head teacher, not another engineer, and they need an answer they can act on.
To be straight with you about what this is not: there is no graduate scheme, no internship programme, no recruiter and no careers inbox with a team behind it. Whether a role appears depends on the work coming in, which we cannot promise you and would not pretend to.
What we can promise is that we will not ask you to spend a week on an unpaid exercise, and we will not post a job here that does not exist.
If that is you
Send us something you have built.
Not a CV on its own. One thing you made, and enough of your own words that we get a sense of how you think. That is a better read on somebody than any interview round we could invent.
We read everything that arrives. We are not always quick, and we will not manufacture a role to keep a good conversation going. If something opens up later and yours is the email we remember, we will write to you.
Email hi@azkosoft.comWhat to put in it
- A link to something you built. A repository, a live site, an app in a store -- whatever is closest to real.
- A paragraph on what it does, and a paragraph on the part that was genuinely hard.
- What you would want to spend your time on, and what you would rather never touch again.
- Where in the world you are and what hours you keep. We work across time zones, so this matters more than a postcode.
- Your own words. A cover letter written by a machine tells us nothing about you, and it is obvious.
Worth reading first
- How we workThe way a project actually runs here, from the first call to the weeks after launch.
- What we buildThe six kinds of work that come through the door, and what each one involves.
- Who we build forHotels, schools, clinics, engineering firms, retail and restaurants.
- BlogHow we think about this work, written out properly.