Platform engineering / markbovee.com

Senior engineer for teams building systems that need to keep working.

I build platforms that keep working when no one is watching.

I automate the repeatable, make systems explain themselves and stay close to production when the hard parts remain human.

See the work Email Mark GitHub ↗

Platform engineeringArchitecture to production

Automate everythingRepeatable beats heroic

Hands-on deliveryClose to the keyboard

Selected case / B2B commerce

From tightly coupled monolith to a system built for change.

I evolved a large-scale B2B commerce platform into a domain-oriented, API-driven system with asynchronous communication. Architecture, automation and production responsibility in equal measure.

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

shapeDomains

Clear boundaries

connectMessaging

Less coupling

shipDelivery

Frequent releases

seeObservability

Signals before incidents

What I do

Useful in the hard parts.

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

Shape boundaries

Make domain ownership and integration paths understandable.

domains / APIs / messaging

Automate the repeatable

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

CI/CD / Terraform / releases

Make systems observable

Turn production behaviour into signals people can act on.

OTEL / metrics / incidents

Unblock teams

Give technical direction by building alongside the people operating it.

AI / MCP / developer experience

Still building

I automate everything. Even my house.

The same instinct applies everywhere: remove friction, make behaviour observable and let systems handle the repeatable work.

/ coding agentsMaintained

Reusable skill-pack for coding agents.

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

$ od route --intent develop
→ skill: develop / guardrails: active

View GitHub profile ↗

/ home automationIn use

Home Assistant integration, built from the protocol up.

I automate everything, even my house. Reverse-engineered protocol, TCP instead of MQTT, actively maintained with a community that relies on it.

device → connected
transport → TCP / direct
status → operational

View GitHub profile ↗

Mark BoveeSenior Platform Engineer

How I work

Still hands-on. Also useful at system level.

I am not a manager at a distance. I give technical direction by building alongside the people who will operate the result. The principle is simple: automate everything you can, then make the system explain itself.

Trust / autonomy

Responsibility belongs low in the organisation. Results matter more than presence.

Focus / collaboration

Collaborate when it helps. Protect focused time when it does not.

Substance / hierarchy

Content beats hierarchy. Lead by setting the standard and contributing to implementation.

Operating modelless toil / more signal

seeMake it visible

Signals before surprises.

automateRemove the repeatable

Systems handle the routine.

ownLeave it clearer

Teams can operate the result.

startAssess

Understand constraints, system shape and the shortest useful next step.

makeBuild

Systems handle the routine.

leaveTransfer

Leave teams with clearer boundaries and a path they can own.

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

Selected node

.NET / C#

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

Open channel

Have a platform problem that needs an engineer, not a slide deck?

Send the platform problem, the current constraint and the outcome you need. I will tell you what I understand and what I would need to see next.

Start with email LinkedIn ↗