Engineering Manager

About Monizze

Monizze is a Belgian HR tech and fintech scale-up of ~150 people, and the challenger in employee benefits and flexible compensation. We issue meal, eco and gift vouchers and help employers build flexible pay packages (cafeteria plan, mobility budget), all on one multi-product platform that handles regulated payments. We move faster than the incumbents, and we're growing fast. 

Our mission: turn complex reward topics into simple, usable solutions, a win-win for workers and employers. 

Your advantages first

💪 Your purchasing power is optimized – the motto is true for clients & employees
🌴 30 days off per year: 20 legal holidays + 6 ADV/RTT + 4 Monidayzz
🚙 A mobility budget / A company car
🏠 Homeworking flexibility with days of remote work and a monthly allowance to make it comfy
🌍 Work from abroad up to 4 weeks a year (after 6 months @ Monizze)
🧇 Belgian roots, mindset & attitude: a cool and informal atmosphere – one of the best things since waffles
🚀 Disrupting and innovative: we digitalized the market and keep pushing innovation in every aspect
🧠 Your growth is our growth: unlimited learning opportunities (languages, personal growth, hard skills,...)
👪 Your health and your family's health is covered by our hospitalization insurance
✨ Internal mobility is regularly an option for anyone looking to evolve or change jobs or departments
🏠 Homeworking opportunities and overall flexibility
🧳 A yearly trip with all your colleagues to celebrate our achievements
➕ We do much more for our employees, but we needed space to describe the job! We'd love to tell you about it though, so ask us!

Engineering at Monizze

Our engineering organisation is built around agentic coding : our engineers don’t just write code, they lead their agents. Skills, agents and context files are versioned and reviewed with the code. Our standards and Architecture Decision Records are written for people and agents alike. Engineers join each initiative at discovery, alongside Product and UX, and them own its design, build, testing and after-care. Two engineering teams are each led by an Engineering Manager, who coaches +/-7 engineers, makes sure the quality holds and drives agentic adoption engineer by engineer. The Delivery Manager makes sure that what we commit to ships on time and as pitched. The Lead Architect owns the architecture direction and the ADRs and sets the framework for agentic coding. Principal Engineers act as the referents for each stack. One quality bar applies to everyone: be proud of what you ship, and AI-generated code meets the same standard as any other code.

The role

This is a people management role for a tech-credible manager who can code. You are the line manager of your team, but you are not on the critical path of delivery. 

Your job in one line: make sure your team is made of engineers who grow, own what they ship, and ship it the right way. 

What You’ll Do

Grow your people

• line-manage the software engineers of your team and run recurrent 1-2-1s: make sure they have what they need, coach their way of working and productivity, spot shortcomings early and act on them 

• develop each engineer, not only their output: training, pairing with more senior profiles, stretch assignments such as leading a first project or a first discovery, exposure to other parts of the stack 

• set objectives and run the mid-year and annual reviews, with no surprise at review time: feedback is given when it happens 

• propose promotions and salary evolution, using the career ladder as the shared reference 

• anticipate people risks (holidays, departures, overload, critical knowledge held by a single person) before they become delivery issues 

Hire and build the team

• define with the CTO the profiles your team needs, run the interviews and take the hiring decision together

• onboard new joiners: our products, standards and ADRs, ways of working, and the agentic way of working from day one, within the framework set by the Lead Architect

• keep a balanced team: seniority mix, no single point of failure on a critical component, capacity to deliver  

Own engineering quality

• challenge and validate tech designs, estimates and POCs before delivery, and bring in the Lead Architect when an initiative goes beyond the agreed ecosystem 

• make sure your team delivers according to the ADRs and quality standards 

• uphold our ways of working: real code reviews (build, test, try to break it), no tests = no merge, AI-generated code under the same quality bar 

• when a problem is architectural, start the reflection with the Lead Architect: you don't run it, you make sure it starts 

• make your team own its after-care: weekly support rotation, runbooks updated after each resolution, a healthy balance between run and delivery 

Make agentic coding real

The Lead Architect sets the direction, the Principal Engineers build the tooling, you make adoption happen engineer by engineer.

• make agentic coding part of each engineer's objectives, reviews and productivity coaching 

• surface your team's real pain points and feed them to the Lead Architect and the Principal Engineers 

• follow the adoption and impact indicators for your team (usage, cycle time, rework, quality) and act on them 

• keep engineers accountable for every line merged, AI-generated or not, with extra caution on critical code (security, payments, card data) 

Take part in engineering steering

• join the recurring engineering steering with the CTO, the Delivery Manager, the Lead Architect and the other Engineering Manager: status, staffing, people risks, tech debt, trade-offs on scope and quality 

• keep both teams consistent with the other Engineering Manager: same practices, same quality bar, engineers able to move from one team to the other 

What this role doesn’t hold

• you're not on the critical path of delivery: delivery planning sits with the Delivery Manager 

• you don't set the architecture direction: the Lead Architect does 

• you don't set product priorities: they sit with Product 

• you don't have the final say on promotions and salaries: you propose, the CTO validates 

What stays yours: whether each engineer grows, whether the team ships to the standard, and whether coding agents become part of everyone's daily toolbox. 

What we’re looking for

• You have managed a software engineering team (~5–10 engineers), ideally after a career as a software engineer or tech lead. 

• You use coding agents daily and have helped a team adopt them: you understand what they change in productivity, code review and quality control. 

• You are tech-credible: you read and challenge a design, a PR or an estimate, and can still code on our stack (PHP/Laravel, Vue/TypeScript, React Native) when it helps: pairing, a POC, unblocking someone. 

• You coach, give direct feedback and handle difficult conversations, including improvement plans. You have hired and onboarded engineers. 

• You care about quality and measure it: code review, test pyramid, CI, ADRs, and indicators you use to ask the right questions, not to replace judgment. 

• Experience in regulated environments (payments, PCI DSS, ISO 27001) is a plus. 

• You are fluent in English and in French or Dutch

Your profile

• credible with engineers first: they trust your tech judgment, even though coding isn’t your core activity

• kind, not soft: you tell uncomfortable truths, give and ask for direct feedback, and don't let things slide to avoid friction 

• a developer of people: you care about how each engineer learns and evolves, not only about what they deliver 

• structured and data-informed: you use indicators to ask the right questions, not to replace judgment 

Why join Monizze ?

Monizze sits at the intersection of purchasing power, payments, mobility and employee benefits. A Belgian challenger with genuine ambition and the pace to match. You'll shape a new role in an engineering organization being redesigned now, and lead a team from developers who write code to engineers who lead their agents. 

Two outcomes are always valid here: change the standard, or follow it. If you want to keep the first possible and the second clear, let's talk.