Una candidatura completa en un minuto
Currículum y carta de presentación personalizados, listos para enviar.
fiskaly is seeking a Head of Engineering to lead our engineering organization across Vienna, Warsaw, and remote workers. You will be responsible for the strength of the management layer, planning, capacity, hiring, performance, reliability, and what ships according to regulator dates.
You will report to the Co-CEO and work closely with Engineering Managers, Product, Platform, and the Warsaw team. The stack includes Go within a distributed system in regulated, high-SLA environments across
Join fiskaly! Help Us Simplify Receipts for Millions
Millions of people interact with fiskaly every day, even if they don’t realize it. As a B2B company, we power the retail technology behind digital receipts and secure, legally compliant transactions.
By making receipts tamper-proof through digital signatures, we help fight tax fraud. And with our paperless receipt solution, we offer consumers a modern alternative while helping merchants streamline their operations.
Sure, our solutions sound complex but our mission is simple: make receipts easy for everyone.
You’ll lead our engineering organisation: 5 Engineering Managers and roughly 70 engineers across Vienna, Warsaw and remote, building the products, backend services and platforms behind our fiscalization platform. The Engineering Managers report to you directly. You’re accountable for the strength of that management layer, for how engineering operates as a whole - planning, capacity, hiring, performance, reliability - and for what actually ships, on the dates regulators set.
You report to the Co-CEO
and work day to day with your Engineering Managers, the Product lead, Platform and the team in Warsaw.
The stack is Go, inside a distributed system, running in regulated, high-SLA environments across several European markets, each with its own rules and deadlines. Your Engineering Managers own their teams. You own that they’re good at it - and that the machine works across teams: dependencies don’t fall between them, capacity follows the roadmap, incidents get closed rather than survived, and a regulatory date six months out becomes a plan people can execute against. Problems here arrive as dates, dependencies, and trade-offs, rarely as clean tickets. A real part of the job is turning them into an operating rhythm the whole organisation can plan against.