Mike Vermeer · Software Engineer

I turn complex workflows into reliable software.

I build reliable products, automation, and AI-enabled engineering workflows—turning ambiguous problems and fast-moving capabilities into dependable systems and better ways of working.

The NetherlandsCurrently at SeedersOpen to good conversations
System topology / 01
INTERFACESERVICESAUTOMATIONDATAAI WORKFLOWS
Currently

Software Engineer at Seeders · Nov 2024 — Present.

Building

Internal Laravel and PHP tooling with Livewire and Filament.

AI enablement

Reusable agent skills, repository guidance, code-review workflows, and practical team adoption.

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.

01 — PRODUCT

Product engineering

Laravel products and operational workflows built across interface, backend, and delivery concerns.

LaravelPHPLivewireFilament
02 — SYSTEMS

Automation & integration

APIs, data processing, and operational workflows that turn repeated work into dependable, reviewable processes.

API integrationData workflowsAutomationPython
03 — AI

AI-enabled engineering

Reusable agent skills, repository guidance, AI-assisted review, and human-owned validation that turn new capabilities into repeatable practice.

Claude CodeCodexAgent skillsHuman review
03 / AI-enabled engineering

From new capability to dependable practice.

At Seeders, I take a leading role in evaluating new AI capabilities and turning the useful ones into repeatable engineering and operational workflows. The goal is better work, more efficiently—while people retain ownership of decisions, validation, and approval.

  1. Track progress

    Follow meaningful advances in models, coding agents, tools, and workflow capabilities while separating durable improvements from novelty.

  2. Assess the opportunity

    Define the engineering or business problem, expected value, constraints, and which decisions must remain human-owned.

  3. Encode context

    Maintain reusable Claude Code and Codex skills, repository guidance, and engineering standards so agents work with relevant context.

  4. Apply and validate

    Use AI across software delivery, code review, research, and selected operational workflows. Validate output through tests, static analysis, runtime checks, and human review.

  5. Standardize and enable

    Turn useful lessons into repeatable practices, improve skills and instructions, and help colleagues adopt the workflows effectively.

04 / Approach

Engineering beyond the happy path.

Dependable software comes from clear boundaries, recoverable failures, explicit trade-offs, and systems that remain understandable after launch.

  • Clear boundaries
  • Recoverable failures
  • Explicit trade-offs
  • Maintainable systems
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.