We are not hiring yet. That will change.
If you want to be told when it does, leave your details at the bottom of this page.
That is the entire purpose of this page, and we would rather say so than dress an empty roster up as an opportunity. If you have ever applied to a role that did not exist, you know why.
A young firm, with everything that implies
We are early. There are no client logos on this site because there are no client logos to put on it. AInops is live and we run our own operation on it, and that is the extent of what we can currently show anyone.
Joining now means the upside and the exposure of that, in the same measure. You would be shaping how the work is done rather than following how it has always been done. You would also be somewhere with a shorter track record than the firm down the road, and if that is the wrong trade for where you are in your life, it is a completely reasonable conclusion to reach.
What you would actually spend your days doing
Building things that go into production and stay there. Not prototypes handed over at the demo. The five lines on our homepage about what we will not do are the ones you would be held to.
Writing the finding. Every engagement starts with a written document that says what the problem is and whether we should take it. Sometimes it says do not build this. You would be the person writing that sentence, and then defending it on a call to someone who arrived wanting to spend money.
Operating what you ship. We monitor and retrain the retrofits we build. Nothing gets thrown over a wall and forgotten, which means you find out whether your own work was any good.
Being in the room. Small firm, so you talk to the client directly. There is no account manager between you and the person whose process is broken.
Three things, and a fourth we do not care about
You can say no with a reason. The hardest skill in this work is telling someone that AI will not fix their problem, in writing, with the argument attached. Technical ability is easier to find than that.
You have shipped something and watched it break. Not a course, not a certificate. Something that had real users and a bad day, and taught you what production feels like when it goes wrong at four in the afternoon.
You know when AI is the wrong tool. Plenty of people can wire up a model. We want the person who spots that a database query would have been cheaper, faster and easier to hand over, and who says so before the invoice rather than after.
What we do not care about: where you studied, or whether you did. Show us a repository, a product, or something you wrote.
How it will work
Roles will be posted on this page. Each one will say what the work is.
People who have left details here hear first, before anything is posted anywhere else.
For when we open something
No CV upload and no account to create. A link to something you have built tells us more than a formatted document does.