Software Engineer
Seeders · Full-time
Building product features, internal tooling, automation, and AI-enabled engineering practices for Seeders Studio and operational workflows.
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.
I’m Mike, a software engineer based in the Netherlands. I work across product engineering, automation, and AI-enabled engineering—connecting the layers needed to turn unclear workflows into dependable systems.
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.
I follow AI progress closely, but novelty is not the goal. I care about which capabilities improve how teams think, build, review, and operate—and how to turn those capabilities into maintainable practice.
At Seeders, I take a leading role in that work by maintaining reusable skills and repository guidance for Claude Code and Codex, supporting AI-assisted code-review and operational workflows, and helping colleagues use these tools effectively without giving up engineering ownership.
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.
Professional product work, an accelerated software-development education, and an early competitive milestone.
Seeders · Full-time
Building product features, internal tooling, automation, and AI-enabled engineering practices for Seeders Studio and operational workflows.
CARD Solutions · Internship
Contributed to the development and maintenance of PHP and Laravel web applications in a professional engineering team.
Deltion College
Completed an accelerated Software Developer programme summa cum laude.
WorldSkills Netherlands
Selected through the preliminary round at Deltion College for the national qualification competition in the Web Developer category.
Principles are useful when they shape concrete decisions, not when they live in a slide deck.
Implementation gets easier once the workflow, constraints, ownership, and failure modes are explicit.
Delivery speed, simplicity, reliability, security, and future maintenance all have a cost.
Permissions, recovery, observability, packaging, and deployment are part of the product.
Good software should be easier for the next engineer—and future me—to understand and change.
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.
I’m always interested in thoughtful software work and conversations with people who care about how things are built.