Build the infrastructure behind intelligent business.
Our software runs payroll, stock, and invoices for businesses that stop working when it does. That is the appeal and it is also the standard: the work is closer to civil engineering than to a growth team, and the people who enjoy it here tend to be the ones who like that.
Distributed across Europe·10:00–16:00 UTC overlap·Four-stage process
What is genuinely different about this one.
Four things that are true here and are not true at most places hiring for the same titles.
How hiring runs.
Four stages, roughly two to three weeks end to end. You are told where you stand after each one, including when the answer is no.
- 01
Application
A person reads it. Tell us one thing you built and what you would change about it now — that paragraph does more than a covering letter ever has.
- 02
Conversation
Forty-five minutes on what you have done and what you want to do next. Not a quiz. You should leave knowing what the job actually is.
- 03
Practical
A real problem from our domain, timeboxed, paid if it runs long. No take-home that quietly costs you a weekend, and no algorithm theatre.
- 04
Team and terms
Meet the people you would work with, ask them the awkward questions, then the offer with the numbers in it. We do not negotiate against another candidate.
What we are looking for, in every discipline.
These come up in every hire we make, whether the role is engineering, delivery, design, or support.
- You write clearly
- Proposals here are documents. If you cannot make an argument in a page, most of the job will be closed to you regardless of discipline.
- You have shipped something people depend on
- Scale is not the point. Consequence is. Something that broke and mattered, and what you changed afterwards.
- You go and look
- You would rather watch the process than read the requirements document about it, and you have a story that proves that instinct paid off.
- You can say 'I do not know'
- In an interview, in a review, and in front of a customer. Under-claiming is a feature in a company that runs other people's payroll.
Terms, stated plainly.
The things candidates ask on the last call. They are here instead so you can ask better questions on the first one.
- Where
- Distributed across European time zones, with 10:00–16:00 UTC held in common. Occasional travel to customer sites.
- Pay
- A band per role, published in the posting. The same band applies wherever you live, and we do not adjust it downwards by geography.
- Equity
- Offered with the role. The structure is explained in full before you accept, not after.
- Hours
- Meetings cluster; the rest of the day is left whole. On-call is rota'd, compensated, and includes the people who wrote the code.
- Kit and setup
- Machine of your choice within reason, plus a budget for the desk you actually work at.
- Learning
- A conference or a course each year, and time to do it in. Open-source contribution during work hours is expected, not tolerated.
Open roles.
Posted as they open, each with the band and the team named in it.
Nothing open right now.
We post roles when we have a seat and a budget, not to collect applications. If you would be a fit for one of the disciplines on the team page, write anyway — speculative approaches are read by a person and answered, and a few of them have turned into roles that did not exist that morning.
Next step
Write to us before there is a posting.
careers@veyqon.com. One paragraph on something you built and what you would change about it now.