Head of Engineering

- Role: Head of Engineering

- Location: Hybrid set up in Vienna

- Language: Full professional English. Any other European language spoken in our markets (e.g. Spanish, German, Italian, French, Polish) is a plus

- Experience: At least 5 years leading software engineers, plus at least 3 managing engineering managers or team leads.

🚀 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.

This is an operational leadership role. The technical direction of individual services sits with your Engineering Managers and their dev leads; you own the system that turns a roadmap into shipped, compliant software. Product is part of the same organisation, not a counterpart across a wall: product managers sit with the teams, and you and the Product lead share one roadmap, one planning cadence, and one definition of shipped. 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.

• People: hiring, developing, and holding accountable your Engineering Managers - 1:1s, feedback that lands, calibration across their teams so "good" means the same in Vienna and Warsaw, performance issues addressed early at the manager level too. You own the headcount plan and the hiring bar for the whole organisation. We expect you to build a management layer people want to work for, where delivery pressure never costs trust or psychological safety in any team.
• Technology: you don't set the direction of individual services -you enable your teams to do so with their EM and teach leads. You own that it gets set deliberately and coherently across teams: one platform across markets rather than a stack per country, tech debt managed as a portfolio, engineering health measured and trending the right way organisation-wide. Plus agentic engineering as an enabler for faster delivery, higher quality and innovative solutions.
• Process: the operating system of engineering - how the organisation plans, allocates capacity, delivers, and reflects. One planning cadence every team runs on, flow and capacity signals every EM reads the same way, and room for teams to differ where it helps. Throughput per engineer is yours too: AI-assisted development is part of how we work, and where it earns its place is your call.
• Delivery: the roadmap and the regulatory calendar across all teams, together with the Product lead inside the same organisation. You turn dates set by legislators into multi-quarter plans the organisation can execute against, make capacity follow the roadmap, and surface risk to the Co-CEO and the management team while there is still time to act. You make technical reality legible at organisation level - to Product, Compliance, Customer Support, Sales, and leadership.
• Quality and reliability: the reliability posture of the whole platform. Prevention with SRE and QE, incident management as a system rather than a heroics roster - sustainable on-call, consistent severity handling, postmortem actions that close across teams - and the reliability numbers customers, auditors, and certification bodies ask about.
• Engineering leadership: you run the Engineering Leadership Team - your EMs, and tech leads - and you own what happens between teams: dependencies that would otherwise fall through, practices that should spread, decisions that need one owner. The new Warsaw Office is in that forum from day one, and you represent engineering to the rest of fiskaly.

• An engineering background. You came up as a software engineer and have stayed close enough to the craft to make sound calls, spot a weak technical argument, and earn the trust of the senior engineers and managers who report to you.
• At least 5 years leading software engineers, plus at least 3 managing engineering managers or team leads. You have built a management layer, not just a team - hired managers, developed them, and dealt with it when one wasn't working.
• A track record of delivering outcomes through an organisation of several teams, over multiple quarters, against deadlines you didn't set - regulatory, contractual, or otherwise fixed.
• Experience running services in a distributed system under real reliability constraints. You have owned an SLA, and the incident and on-call process behind it, for more than one team at a time.
• An operating cadence you have built yourself: how several teams plan, allocate capacity, deliver, and reflect, with flow and reliability signals everyone reads the same way. You know which parts to standardise and which to leave to the teams.
• Credible technical challenge. You don't need to write the code, but you can question an architecture direction across teams, weigh trade-offs, and tell a real constraint from a preference.
• Strong written and verbal communication, including making engineering legible to people who don't share your background - Product, Sales, Customer Support, leadership, and the occasional auditor.
• Comfort setting direction with incomplete information, and holding it across teams once it's set.
• Calm and direct under pressure - in incidents, in difficult performance conversations with managers, and in trade-off conversations with Product.
• Experience leading across locations. You have run teams that don't sit in the same office, and you know what it takes to make a second site a real part of the organisation rather than an annex.
• Fluent English (company language)
• Experience in regulated or compliance-sensitive domains: fiscalisation, e-invoicing, payments, fintech, healthtech or similar.
• Go, distributed systems, observability.
• Having led an engineering organisation - not just a team - through a significant phase shift: a re-org, a platform migration, a reliability turnaround, or a step change in size.
• Scale-up experience where the org changed shape underneath you, ideally as the one who reshaped it.
• Having built up a second engineering site, or integrated one into an existing organisation.
• Having been through technical due diligence, from either side.
• Hands-on experience with agentic workflows or LLM-assisted development, and a view on how they change the way an engineering organisation should be run.
• German, Polish, or other European languages. English is our working language, and we're on our way to becoming the leading compliance suite across all 27 EU member states - and every additional language gets you closer to a team, a regulator, or a customer somewhere.

• A company in an unusual position for a scale-up: growing fast, cash-flow positive, and in a market where growth is written into law - you build, you don't rescue
• A leadership role with real scope: the engineering organisation, its people, and its standard are yours to shape
• Short decision paths: you are part of the Company Leadership Team
• An amazing office in the heart of Vienna plus hybrid setup and flexible working hours
• Budget for personal and professional development, plus monthly time set aside to use it
• Hardware of your choice: Windows, Linux, or Mac
• 25 vacation days - and Christmas to New Year's fully off on top, no vacation days needed
• Sabbatical option for personal projects or learning, and one paid volunteering day per year
• fiskalversary bonuses at 3, 5, and 7 years
• Pension fund contributions of up to 10%, or €25/month into Zukunftssicherung
• Annual Wiener Linien ticket or part of your Klimaticket
• Up to €100/month in meal vouchers, and bike leasing via salary conversion
• Free on-site occupational health services and OpenUp - professional mental health support, anytime
• Monthly fiskaly Breakfast in every office, CorpLife discounts, and an international team of more than 30 nationalities
• Relocation allowance for your move to Vienna for you and your family

We work on real problems that have impact, not vanity projects. Our team is pragmatic, direct, and focused on building solid tech for an industry that needs it. We care about how things work, not how they look on paper. If that resonates, you’ll probably enjoy working here.