A complete application in a minute — tailored resume and cover letter, ready to send.
Vatix is seeking a senior backend engineer to steer the architectural direction of a product area and produce production Python weekly. You will own technical specifications, guide a microteam of engineers, and contribute production code in a fully remote or hybrid setup.
The role centers on Django back-end work with a single multi-tenant product, focusing on data models, schemas, and efficient AI-assisted development practices. Strong architectural judgement is essential.
Technical leadership without leaving the code. You'd set the architectural direction for one area of our product, write the specifications your team builds from, and ship production Python every week.
Fully remote in Poland, or hybrid from our Kraków office. Long-term, full-time engagement on a B2B contract, invoiced monthly. 28,000 to 34,000 PLN per month excluding VAT, dependent on experience.
Vatix is a profitable, bootstrapped B2B SaaS company founded in London in 2018, with our engineering team in Kraków from day one. We build a governance, risk and compliance platform covering risk management, audits and inspections, incident management and compliance assurance. Over 800 organisations and more than 75,000 people use it, including Starbucks, British Airways, Dyson, Intel, Siemens, the Co-op, the NHS, Cambridge University and the University of Oxford.
We're not VC-backed and we have no plans to sell. This is a long-term, profitable business growing around 40% year on year, and we're around 30 people. Our customers depend on us for systems they cannot afford to get wrong, which sets the bar for the code we ship.
This is technical leadership rather than management. You wouldn't line manage anyone, run performance reviews or own headcount. What you'd own is the technical direction of an area of the product:
Core application development runs as three microteams. You'd lead one, working with one or two junior engineers, typically high-calibre graduates from top universities. Your peers are the other microteam leads and the senior engineers across the wider group, and you'd be writing production code throughout.
Since we moved to spec-driven development, the constraint on all three teams stopped being how quickly anyone writes code. It's the quality of the specification and the architecture underneath it. That's the honest reason we're hiring.
The depth of the work is in the Django backend. Vatix is a single, fully multi-tenant product: one codebase, one deployment, no per-customer forks. Within that, every account configures itself to an unusual degree, with customers defining their own fields, schemas, layouts and relationships through a no-code builder. The backend has to support all of it generically, which means real work in:
Your microteam's ownership runs through to what the customer sees, so projects will occasionally take you into React. That works because Product delivers a functional frontend prototype alongside every set of requirements, built in Claude Code against our real component library. The question in front of you is rarely "build this from nothing", it's "wire this up properly and make the calls the prototype couldn't". This is a backend role at heart and your Python and Django should be genuinely strong. What's changed is that we no longer hand half-finished features across team boundaries.
We build with AI, and we've thought carefully about how. Our Engineering Manager has written the process up in full on our Medium publication, under the title "AI-First SDLC at Vatix". Worth ten minutes before you apply.
The engineering moved upstream. You'd spend more of your week on design and specification and far less on boilerplate, and edge cases surface in a markdown file rather than when a feature is 70% built. It also raises the stakes on your decisions: a sound architectural call now propagates through ten thousand lines of code in an afternoon, and so does a bad one. That's the entire reason this role is senior. We're not looking for someone to supervise a model, but for someone whose data modelling, choice of patterns and instinct for where a system will break are worth amplifying.
The quality harnesses are human, on purpose:
On the first project we ran this way, 4,400 lines of specification produced 10,000 lines of production code and twelve end-to-end tests, with no code written by hand and every line specified by us first. Scope grew by five tickets rather than doubling.
The process is a few months old and it will change. You'd have a real say in that, and if you've been running your own version and have views on where ours is wrong, that makes for a strong application. Healthy scepticism is welcome. Incuriosity isn't.
The role is available immediately and the process is deliberately short:
For the right person we can move to an offer within a few days. We're hiring one person for this role and the bar is high.
Vatix is an equal opportunity employer. We welcome applicants from all backgrounds.