Lead Architect

h3bAbout Monizze /b /h3pbMonizze /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. /ppOur mission: turn complex reward topics into simple, usable solutions, a win-win for workers and employers. /ph3bYour advantages first /b /h3pYour purchasing power is optimized – the motto is true for clients employeesbr/30 days off per year: 20 legal holidays + 6 ADV/RTT + 4 Monidayzzbr/A mobility budget / A company carbr/Homeworking flexibility with days of remote work and a monthly allowance to make it comfybr/Work from abroad up to 4 weeks a year (after 6 months @ Monizze)br/Belgian roots, mindset attitude: a cool and informal atmosphere – one of the best things since wafflesbr/Disrupting and innovative: we digitalized the market and keep pushing innovation in every aspectbr/Your growth is our growth: unlimited learning opportunities (languages, personal growth, hard skills,...)br/Your health and your family's health is covered by our hospitalization insurancebr/Internal mobility is regularly an option for anyone looking to evolve or change jobs or departmentsbr/Homeworking opportunities and overall flexibilitybr/A yearly trip with all your colleagues to celebrate our achievementsbr/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 /ph3Engineering at Monizze /h3pOur 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. /ph3The role /h3pYou make sure Monizze's software evolves in one coherent direction, written down and usable by humans and agents alike. /ppYou lead through influence: you stay hands-on, close to the code and the engineers, and your authority comes from the quality of your decisions, the clarity of the standards and the trust you earn. /ph3What You’ll Do /h3pKeep the architecture coherent across products /pullipcarry the target architecture (multi-product, shared foundations) and make it understandable to everyone, not only to the people who drew it /p /li /ulullipown the cross-cutting topics: API contracts, gateway and partner API versioning, orchestration vs. choreography, new service vs. new domain /p /li /ulullipjoin discovery when an initiative goes beyond our agreed ecosystem or spans several stacks, so structural choices are known before the pitch /p /li /ulullipsurface structural projects early, and bring done is done discipline to migrations: frozen scope, explicit go, a closing criterion /p /li /ululliptake on critical pieces yourself when complexity or urgency calls for it, including during incidents /p /li /ulpDrive architecture decisions /ppYou turn structural choices into Architecture Decision Records (ADRs), keep that base current with the help of Principal Engineers, and make sure every team and agent follows it. You design how each decision is enforced; Engineering Managers check conformity in their teams. /pullipspot early where a structural choice is needed and propose the decision /p /li /ulullipmaintain two sets of ADRs: a short, curated Target that every new component must follow, and a Baseline for existing code that grows one agreed decision at a time /p /li /ululliprun the ADR lifecycle, from proposal and review with the relevant engineers to decision and publication , and superseding with a new ADR when a decision changes /p /li /ulullipattach an enforcement mechanism to every ADR (CI, agent skill or PR review) and have every repo declare which rules apply, so CI and agents load the right ones /p /li /ulullipbuild consensus among engineers and, when they can't agree, frame the options for the CTO to decide /p /li /ulpTurn tech watch into decisions /ppTech watch means turning what’s relevant into concrete proposals. /pullipkeep a living tech radar (Adopt / Trial / Assess / Hold), the entry point for