// Engineering Consultancy · Belgium
Stqn Technology provides end-to-end engineering consulting — delivered by someone who has written the code, shipped it to production, and lived through the consequences.
fr_BE
en_GB
Working languages
// What I do
Engineering & Architecture
10+ years of Ruby in production, along with the scars to prove it. Architecture, development, testing, DevOps/SRE — with strong opinions about what good software looks like and why your test suite should never fail on a Thursday afternoon.
Technical Leadership
People first, then product, then technology — in that order. Building and leading engineering teams through servant leadership and radical candor: creating the conditions for autonomy, not dependency.
Audits & Due Diligence
Technical assessment of codebases, teams, and processes — for companies preparing to scale or investors doing their homework. I read the code. I talk to the engineers. I don't produce a report from a questionnaire.
Product Thinking & Delivery
Stepping back from the code to ask whether you're building the right thing. Strategic product thinking, roadmap ownership, and the discipline to prioritise what actually moves the needle — before writing a single line.
Writing, Training & Speaking
Conference talks, podcast episodes, and workshops on engineering leadership, communication, and technical craft. Also a blog at stan.boyet.me, and eight years running Ruby Belgium — because community matters.
Software & R&D
From idea to production. Conception, development, and iteration on software products and digital services — with the pragmatism to ship before it's perfect and the discipline to make it better afterwards.
// Behind the company
Engineer by training, generalist by choice. I've spent 10+ years building software, leading teams, reviewing architectures, and turning ambiguous requirements into things that actually work in production.
I work across the full spectrum — from hands-on code to strategic technical leadership — adapting to what the situation actually needs rather than what my title suggests I should be doing.
* Equal parts engineer, architect, and occasional team therapist.
Not necessarily in that order.