Mads Tinko Madsen

I've been building frontend software since 2016 — starting with six months of hand-writing HTML and CSS, eight hours a day, with no framework. That foundation is why my CSS and layout work is automatic rather than looked-up: it's the one part of the stack I never have to check documentation for.

My formal education came after the fundamentals, not instead of them: a 1.5-year web-integrator program (2017) — the exam project was a full webshop I built solo — followed by a six-year apprenticeship — Datatekniker med speciale i programmering — completed inside real companies (IT Klyngen, then Hartvig Consult) and finished in 2024. The program itself was backend- and systems-design-focused, but I stayed full-stack in practice throughout it — doing both frontend and backend at IT Klyngen, plus shipping production websites for small local businesses on the side (including a licensed healthcare clinic) — until I was put in charge of frontend development at Hartvig Consult, where it became my dedicated, full-time focus. The apprenticeship itself is where I picked up backend, systems design, and full-stack thinking on top of that foundation.

For the past two years I've been the frontend lead at Engii-Soft, leading the frontend team. My day-to-day covers more than "frontend engineer" — architecture, code review and mentoring, CI/CD and repository administration, and translating leadership's requirements into structured, sequenced work across frontend and backend.

I'm full-stack capable — C#/.NET, Node, gRPC, SQL — but I specialize in frontend and design systems by choice. I relax by playing Factorio and Satisfactory, which tells you most of what you need to know about how I think about architecture: as systems with clean boundaries, not one-off pages.

The clearest single piece of evidence for how I work is the platform rebuild described below.