Rohlik is the leading Central European e-grocer. More than a million customers buy their groceries from us through Rohlik.cz, Knuspr.de, Kifli.hu, Gurkerl.at and Sezamo.ro, choosing from over 17,000 items, delivered within a couple of hours in 15-minute windows.
Behind that promise, real software meets the physical world: warehouse automation, ML forecasting, and a shopping experience that has to be right when the vans leave at dawn. It is built by Group Tech — one technology team whose work lands in the daily operations of every business in the group.
Rohlik Tech is organised into cells: teams of three to five engineers, each owning a single business metric together with a Business Lead who answers for the commercial side. Work arrives through that number rather than through a ticket queue, and because the team is small, what each engineer contributes is visible to everyone. Product engineers carry their features from design through deployment to production monitoring — trunk-based, behind feature flags, with automated canary rollouts, shipping to production dozens of times a day.
Every cell here owns one business number, and yours will move because of what you ship.
AI is woven into how the work gets done: most of our code contributions are agentic, engineers use Claude Code and Devin daily, and some merge requests already merge on AI review alone. Everything we use is public, with live numbers pulled straight from our repositories, on our tech stack page.
All of this serves something worth doing: a better food system — more sustainable, more inclusive, healthier — with the freshest local produce moving from farmers to a customer’s door in hours through our Farm-to-Door program.
What you will own and deliverYour cell’s metric. You will be the senior engineer in a cell of three to five, carrying the hardest technical work behind its North Star metric while respecting the guardrails the cell has promised the business not to break.
Your features in production. You design, build, ship and monitor what you own, and you are on call for it — deploying often enough that releasing stays routine.
Technical Guild initiatives. Guilds are how craft travels between cells, and we expect a senior engineer to take at least two initiatives a year from idea to adoption beyond their own team.
Multiplying the team. Mentoring, code reviews that teach, and technical guidance that makes the engineers around you measurably better.
Architecture. A real voice in system design and cross-cell technical reviews, arguing for solutions that stay scalable, maintainable and robust as five markets lean on them.
Technical debt. You notice it early and pay it down before it slows the whole cell.
This is a senior individual-contributor role in our group technology team, reporting to an Engineering Manager who still designs, codes and shares the on-call. Your cell also has a Business Lead who owns the commercial metric, which keeps the distance between your work and the business as short as we can make it. Beyond the cell, you bring your expertise to architectural review boards and cross-cell technical discussions, and your work ships to all five markets.
Leadership at this level runs through technical initiatives and influence rather than people management. If you want the full picture of how the organisation works — why cells stay at three to five people, how the metrics are chosen, and what sits in the thin layer on top — we wrote it up in How We Structure Rohlik Tech.
What we are looking for5+ years of professional software development with a proven record of delivering complex projects, with a degree in computer science, software engineering or a related field behind it.
You have led technical work from concept to launch and stayed with it long enough to learn what production thought of it.
Deep expertise in system design, data modeling and application architecture. You can defend the design you chose and the two you rejected.
AI is how work gets done here. Our engineers use Claude Code and Devin daily, and prototypes are vibe-coded during requirements analysis. We are looking for engineers who are comfortable directing agents while keeping the quality bar exactly where it was.
You make others better. Mentoring, constructive review, and communication that lands with technical and non-technical audiences alike.
Particularly relevant. Presenting technical concepts to mixed audiences; active participation in technical communities or open source; a master’s degree in a relevant field.
You should not have to take our word for any of this. Our engineers write up how we actually work on the Rohlik Tech Blog:
Tiny Refactor a Day — an agent that proposes one small code improvement daily, the Boy Scout Rule with safeguards.
How AI Runs Our War Rooms — incident detection, log analysis and war-room prep done before humans arrive.
The Overnight Feedback Loop — customer conversations turned into merge requests overnight, with human approval gates.
The stack itself lives on our tech stack page.
What success looks like in 90 daysYou know your cell’s North Star metric and its guardrails as well as anyone on the business side, and you have shipped changes that moved it. You have taken your first on-call rotation for the things you built, and you have found the first practice worth improving beyond your own cell and started turning it into a guild initiative.
Are we a good fit?Take this role if you want your code to reach a million households by tomorrow morning, if you like your impact to be readable in a single number, and if you would rather lead through the quality of your thinking than through an org chart. Read our culture code and are we a good fit? — we mean them.
What we offerA senior role with real ownership — a cell metric your work visibly moves, guild leadership, and an architectural voice across the group
An AI-native engineering environment — the tools, and the mandate to use them
Five markets, more than a million customers, and your work in production the same day
Benefits — see what we offer
Instead of a cover letter, tell us about one system you built and ran in production — what it changed, what broke, and what you would do differently. Then find this role on our career pages.