Platform Engineer & Senior .NET Developer

Hi, I'm Mark.

I build things...

From platforms to pretty much everything else.

Software, infrastructure, automation, hardware, home projects — I like figuring out how things work, then making them work better. Professionally, that means engineering reliable, observable platforms that teams can deliver through repeatable pipelines — from architecture and code to infrastructure and production.

Portrait of Mark Bovee
Platform engineeringArchitecture to production
Automate everythingRepeatable beats heroic
Hands-on deliveryClose to the keyboard
Selected case / B2B commerce

From monolith to microservices, built for change.

I shaped a large-scale B2B commerce platform into domain-oriented, API-driven architecture with asynchronous communication. I owned the architecture, the pipelines that shipped it, and the alerts that told us if it broke.

Architecture / delivery / observabilityProof over promises

What I owned

System boundaries, integration patterns and the operating path from code to customer.

  • Designed domain boundaries and integration patterns
  • Introduced messaging and caching to reduce coupling
  • Standardised pipelines and zero-downtime delivery
  • Implemented OpenTelemetry observability
  • Applied AI and MCP tooling to speed diagnosis
~1,800concurrent users, designed for higher peaks
~125/snormal requests
10M+API calls per day
100–300containerized workloads
~5 mindeployment time
~€100Mannual revenue supported
~22,000dealers supported across Europe
shapeDomains

Clear boundaries

connectMessaging

Less coupling

shipDelivery

Frequent releases

seeObservability

Signals before incidents

What I do

Where architecture meets production.

No strategy decks without implementation. I work where architecture meets the repository, the pipeline and the production incident.

Shape boundaries

Give each domain a clear boundary and each integration a path people can follow.

domains / APIs / messaging

Automate the repeatable

Remove manual work until the safe path becomes the obvious path.

CI/CD / Terraform / releases

Make systems observable

Make production behaviour visible before an incident turns into guesswork.

OTEL / metrics / incidents

Build what teams need

Don't just document the path. Build it. Create the tooling, automation and workflows that turn good engineering practices into something teams can actually use.

platform tooling / AI / MCP / developer experience
Still building

I automate everything. Even my house.

I bring the same habit home: remove the tedious steps, expose what the system is doing and let it handle the work that keeps repeating.

/ coding agentsMaintained

Reusable skill-pack for coding agents.

Cross-platform integration patterns with YAML-based routing. Capable tooling made repeatable instead of mysterious.

$ claude
Loading skills from .claude/skills/ ...
→ 12 skills discovered / 3 platforms

> refactor the auth middleware to use the new token guard

Reading skill: develop
→ guardrails: active
→ router: matched intent "develop"

Applying pattern: token-guard-v2
Running tests ... 14/14 passed

Dispatching subagent: code-reviewer
→ skill: review / guardrails: active
→ diff verified against style guide
→ no guardrail violations

✓ Done. 3 files changed, 42 insertions(+), 18 deletions(-)
View repository ↗
/ home automationIn use
Home Assistant energy dashboard showing controls, energy usage, water heating and electricity prices
live system / home energy overview

Home Assistant integration, built from the protocol up.

The same habit that runs the platform runs at home. I reverse-engineered the protocol, use TCP instead of MQTT, and maintain it for a community that relies on it.

device → connected
transport → TCP / direct
hems → operational
- heating water (58°C) [12:00 - 13:00]
- charging battery [12:00 and 17:30]
- car charger not connected
View repository ↗
Mark BoveePlatform Engineer & Senior .NET Developer
How I work

Own the code.

AI can help build it. I still need to understand exactly what happens, and own what I ship.

Keep it simple

KISS over cleverness. I solve the problem and skip unnecessary complexity.

Start small

POCs, small steps, testable increments: prove progress and make change safer.

Automate the path

DTAP, repeatable deployments and automation by default. Manual work disappears first.

Observe and iterate

Logs, metrics and traces show what the system needs next. I improve from evidence, not guesswork.

How a project runsin code, not in decks
01, lookRead the system first

Logs, deploys, on-call history. I want to see how it actually behaves before I propose anything.

02, buildShip in small pieces

No big-bang rewrites. Every change is small enough to roll back and prove itself in production.

03, hand over clearlyBuild for the next change

Documented, automated and clear enough to operate, debug and change without guesswork.

Career / 20+ years of building

From application code to the platform beneath it.

A hands-on engineering path from C# and .NET application code to the Azure and Kubernetes platform beneath it. I modernised legacy systems, built Terraform and CI/CD delivery, and made the cloud operational. Today the platform serves more than 10 million API calls per day across 100–300 containerised workloads.

2025 — now

Accell Global

Platform Engineer

Working hands-on on the evolution of a large-scale B2B commerce platform into a domain-oriented, API-driven distributed system. I work across architecture, messaging, caching and the delivery path, using Terraform, CI/CD and AI-driven engineering workflows; the current platform runs on .NET 10 and .NET Aspire.

2024 - 2025

Accell IT

Technical Operations Manager

A short transition role working with the development team, product and architecture. It kept me close to the technical decisions and led back to hands-on platform engineering.

2014 — 2024

Accell IT

Senior .NET Developer

Owned the technical evolution from classic ASP to cloud-native .NET microservices on AKS, while building the accompanying DevOps practice from the ground up.

2009 — 2014

Branch Solutions

Application Developer

Continued building business applications after the acquisition of ACF Software, including consultancy work and the first years embedded at Accell.

2004 — 2009

ACF Software

Application Developer

Part-time development of custom applications for small and medium-sized businesses alongside a degree in Computer Science.

Read the full CV ↗
Working stack

Tools are a means. The system is the work.

Choose a node to see where I spend time. This is not a badge wall. It is the vocabulary of systems I build and operate.

Build
Operate
Improve

.NET / C#

Application platforms, APIs and services that stay understandable under load.

AI / MCP

Agents that read logs and diffs so I find the bug faster, not tools that write the fix for me.

SQL

Relational data models and queries that support transactional business systems.

Elasticsearch

Search and indexing for fast access to operational and domain data.

Kubernetes

Container orchestration, workload boundaries and operational clarity.

Azure

Cloud infrastructure shaped around reliability, cost and repeatable delivery.

Linux

The operating-system layer where useful work still happens.

Terraform

Infrastructure as code that makes environments reviewable and reproducible.

CI/CD

Pipelines, release automation and deployments that do not need babysitting.

Contact

Looking for hands-on engineering, not another slide deck?

Share what you are building, changing or trying to improve. We can use that as a starting point for a focused conversation.

Open the contact formLinkedIn ↗