Product engineering
Laravel applications and operational workflows built end to end with Livewire and Filament.
LaravelPHPLivewireFilament
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
Software Engineer at Seeders · Nov 2024 — Present.
Internal Laravel and PHP tooling with Livewire and Filament.
Automation, architecture, product workflows, data processing, and code review.
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 · Confidential clientInternal system
SEO intelligence for a global enterprise client
A custom analytics and automation system that integrated third-party data, processed large datasets, and turned raw metrics into structured insights.
02 / Native macOS productMaintained
EasyHotkeys
A native shortcut utility designed for fast text insertion, thoughtful permission handling, and Keychain-backed 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
External APIs and data workflows that turn repeated work into reviewable processes.
API integrationData workflowsAutomationPython
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.