Test automation & frameworks
Building and scaling test frameworks that actually get used — readable test plans, maintainable suites, and the tooling that keeps engineers and testers on the same page.
Belgian software engineer with 14+ years of experience across test automation, Python systems, and embedded products. Now freelancing as Unfoxxed — available for teams that value craft, scale, and a calm head.
I'm a freelance software engineer based in Belgium, working under Unfoxxed. Master in Industrial Engineering (Electronics-ICT) and over a decade in the field — from embedded healthcare systems to large-scale test automation.
Right now I'm working on an EGSE system that supports the testing of space instruments. Before that, I led a small team at a global HVAC manufacturer, building the test framework that tied their product lineup together — a codebase that scaled from a handful of setups to dozens of products without losing its footing. And further back, I built mobile and Python systems for hospital and elderly-care alarms, where reliability isn't optional.
I'm at my best on problems that need a senior who can both code and lead — designing for scale, untangling inherited complexity, and helping teams ship without burning out.
What energises me is work that makes someone's life tangibly better — smoother teams, cleaner workflows, features people actually use. The more concrete the impact, the better.
The best technical solution isn't always the right one. The end user wins, not the architecture diagram.
Good products come from good teams. I'd rather sharpen a team than be the lone hero.
I want to know what we're building and why before diving in. Solving the right problem beats solving any problem well.
Building and scaling test frameworks that actually get used — readable test plans, maintainable suites, and the tooling that keeps engineers and testers on the same page.
Backends, APIs, automation, and device glue. Eight-plus years of Python in production, on Linux, in containers, and on small hardware where it matters.
Guiding small teams (3–5 people) through scale-up phases — turning patches into architecture, unblocking the day-to-day, and growing engineers while shipping.
Day-to-day for the last 8+ years.