Product engineering
Interfaces, services, and domain workflows designed as one coherent system.
LaravelTypeScriptReactSQL
Mike Vermeer · Software Engineer
I turn complex workflows into reliable software.
I build across product interfaces, backend systems, automation and applied AI—shaping ambiguous problems into tools people can depend on.
System topology / 01
Building internal tooling and automation at Seeders.
Product interfaces, services, APIs, data workflows, and developer tooling.
The Netherlands · Focused on software that solves real operational problems.
01 / Selected work
Engineering, explained through decisions.
Professional systems, native applications and developer tools—presented through the problems, constraints and trade-offs behind them.
01 / Professional · SanitizedIn use
Professional systems work
Selected internal tooling and automation work, presented through an engineering lens without exposing confidential details.
02 / Native macOS productMaintained
EasyHotkeys
A native shortcut utility designed for fast text insertion, thoughtful permission handling, and local-first privacy.
03 / Native macOS utilityMaintained
NoSleep
A small menu-bar utility built around macOS power assertions, session state, and battery-aware safeguards.
02 / Engineering range
Across the layers that make software useful.
Broad enough to connect the system, deliberate enough to go deep where the problem demands it.
Automation & integration
APIs, background processes, and operational tooling that reduce repeated work.
PHPPythonRESTCI/CD
Data & applied AI
Practical data workflows and AI capabilities built around usefulness and clear limits.
Data pipelinesLLMsValidationAutomation
03 / Approach
Engineering beyond the happy path.
Dependable software comes from clear boundaries, recoverable failures, explicit trade-offs, and systems that remain understandable after launch.
- 01Understand the workflow
Make the real problem, constraints, and failure modes explicit before committing to a solution.
- 02Make trade-offs visible
Balance delivery speed, simplicity, reliability, security, and future maintenance deliberately.
- 03Build for real usage
Permissions, recovery, observability, packaging, and deployment are part of the product.
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.