Software Engineer
Seeders · Full-time
Building internal tooling, automation, and product features for Seeders Studio and operational workflows.
Clarity is part of the engineering.
I enjoy the problems where the difficult part is not only writing code, but turning an unclear workflow into a system that is understandable, dependable, and useful.
01 / Profile
About Mike
I’m Mike, a software engineer based in the Netherlands. I work across layers—from product interfaces and backend services to automation, data workflows, and applied AI.
The problems I like most rarely begin with “build this screen.” They start with an unclear process, competing constraints, or a brittle workflow. My job is to make that problem legible, choose the right trade-offs, and ship something dependable.
Since November 2024, I’ve worked at Seeders on Laravel and PHP product development, internal tooling, and automation for operational workflows. I contribute across implementation, architecture discussions, and code review.
02 / Experience & development
A foundation built through practice.
Professional product work, an accelerated software-development education, and an early competitive milestone.
Experience
Software Engineer Intern
CARD Solutions · Internship
Contributed to the development and maintenance of PHP and Laravel web applications in a professional engineering team.
Education
MBO level 4 · Software Developer
Deltion College
Completed an accelerated Software Developer programme summa cum laude.
Recognition
Skills Heroes · Web Developer
WorldSkills Netherlands
Selected through the preliminary round at Deltion College for the national qualification competition in the Web Developer category.
03 / Working principles
How I approach the work.
Principles are useful when they shape concrete decisions, not when they live in a slide deck.
Find the real problem
Implementation gets easier once the workflow, constraints, ownership, and failure modes are explicit.
Make trade-offs visible
Delivery speed, simplicity, reliability, security, and future maintenance all have a cost.
Build for real usage
Permissions, recovery, observability, packaging, and deployment are part of the product.
Leave systems clearer
Good software should be easier for the next engineer—and future me—to understand and change.
04 / Outside work
Small products, serious engineering.
Outside professional work, I build focused native utilities and developer tools. Small products are excellent places to practise the details—permissions, system APIs, process lifecycle, packaging, and tests—that make software trustworthy.
Let’s talk
Have an engineering problem worth untangling?
I’m always interested in thoughtful software work and conversations with people who care about how things are built.