Engineering Manager

h3bAbout Monizze /b /h3 pbMonizze /b 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. /p pOur mission: turn complex reward topics into simple, usable solutions, a win-win for workers and employers. /p h3bYour advantages first /b /h3 ul liYour purchasing power is optimized – the motto is true for clients employees /li li30 days off per year: 20 legal holidays + 6 ADV/RTT + 4 Monidayzz /li liA mobility budget / A company car /li liHomeworking flexibility with days of remote work and a monthly allowance to make it comfy /li liWork from abroad up to 4 weeks a year (after 6 months @ Monizze) /li liBelgian roots, mindset attitude: a cool and informal atmosphere – one of the best things since waffles /li liDisrupting and innovative: we digitalized the market and keep pushing innovation in every aspect /li liYour growth is our growth: unlimited learning opportunities (languages, personal growth, hard skills,...) /li liYour health and your family's health is covered by our hospitalization insurance /li liInternal mobility is regularly an option for anyone looking to evolve or change jobs or departments /li liHomeworking opportunities and overall flexibility /li liA yearly trip with all your colleagues to celebrate our achievements /li liWe 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 /li /ul h3Engineering at Monizze /h3 pOur 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. /p h3The role /h3 pThis 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. /p pYour job in one line: make sure your team is made of engineers who grow, own what they ship, and ship it the right way. /p h3What You’ll Do /h3 h3Grow your people /h3 ul liline-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 /li lidevelop 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 /li liset objectives and run the mid-year and annual reviews, with no surprise at review time: feedback is given when it happens /li lipropose promotions and salary evolution, using the career ladder as the shared reference /li lianticipate people risks (holidays, departures, overload, critical knowledge held by a single person) before they become delivery issues /li /ul h3Hire and build the team /h3 ul lidefine with the CTO the profiles your team needs, run the interviews and take the hiring decision together /li lionboard 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 /li likeep a balanced team: seniority mix, no single point of failure on a critical component, capacity to deliver /li /ul h3Own engineering quality /h3 ul lichallenge and validate tech designs, estimates and POCs before delivery, and bring in the Lead Architect when an initiative goes beyond the agreed ecosystem /li limake sure your team delivers according to the ADRs and quality standards /li liuphold 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 /li liwhen a problem is architectural, start the reflection with the Lead Architect: you don't run it, you make sure it starts /li limake your team own its after-care: weekly support rotation, runbooks updated after each resolution, a healthy balance between run and delivery /li /ul h3Make agentic coding r