Skip to main content
matthewboback.comBackend & Platform Engineer
Skills

A focused stack shaped by the kinds of systems I like to own.

Curated for hiring review: not every tool I have touched, but the ones that show up repeatedly in the four systems on this site, from door hardware to LLM agents.

How I read the stack

Backend first

I usually start from contracts, jobs, data flow, and operations, then work outward into the product surface.

Shipped systems

Every highlighted tool links to a system it runs in: the MnB access and video platform, the research agent, StageFlow, or AlchemizeCV.

Operator clarity

I value systems that are easier to debug, easier to explain, and less dependent on hidden process knowledge.

Core languages

The languages I reach for most when the work needs to ship and stay maintainable.

5 tools

Go

core

Site runtimes, agent runtime, orchestrators, CLIs

TypeScript

core

Product UI, device gateway, browser tooling

Python

core

API services, rendering, lab tooling

SQL

Relational modeling, projections, and operational queries

Bash

Deploy scripts, smoke tests, agent shells

Backend systems

Durable jobs, typed contracts, and distributed behavior that stays understandable.

7 tools

NATS JetStream

core

Durable commands and event flow between sites and cloud

Hono

core

Device-facing gateway with signed short-lived tokens

FastAPI

core

Typed API work with generated client types

Chi / net-http

core

Lean Go APIs and internal services

SSE & cursor polling

Progress without a message bus in the web tier

Protobuf & JSON Schema

core

Contracts generated into Go and TypeScript

Pydantic / SQLAlchemy

Validation and persistence

AI agent systems

Model-driven work with the guarantees in code: sandboxes, contracts, evidence checks, and a human decision at the end.

6 tools

Agent runtime (Go)

core

Provider-agnostic loop, persistent shell, resumable sessions

Multi-provider LLM

core

10 providers behind 3 API adapters, fallback on exhaustion

Schema-validated output

core

JSON Schema contracts with bounded in-context repair

Evidence gating

core

Quotes checked against captures, a second model scoring citations

Browser tools for agents

core

Daemon-backed real Chrome with a versioned JSON contract

Evals

Golden tasks in isolated containers, per-model comparison

Hardware & protocols

Physical systems where the software is one part of a safety chain.

4 tools

OSDP / RS-485

core

Card reader framing and poll loops

Modbus TCP

core

Relay and input modules with hardware-timed pulses

RTSP / ONVIF / Frigate

core

Camera commissioning, recording, live relay

Hardware simulation

Protocol-level simulators so the full path runs in CI

Product frontend

Frontend work that makes systems usable and legible for technical users and operators.

4 tools

React / React Router

core

Server-rendered portals and product UIs

Tailwind CSS

core

Design systems and interface implementation

Go html/template

No-JS admin surfaces under a strict CSP

Vite

Fast local and production builds

Infrastructure, security & delivery

I own the release path and the trust boundaries, not only the application code.

8 tools

Podman & Quadlet

core

Rootless workloads as systemd units

PostgreSQL

core

Durable production state and projected read models

SQLite

core

Embedded source of truth, outboxes, job queues

MinIO

Artifacts and archive batch sync

WireGuard

core

Outbound-only site connectivity; brokers bound to the VPN

HPKE & Ed25519

core

Device enrollment bundles, single-use signed grants

Signed releases

Digest-pinned images, hash-verified bundles, rollback images

Testing & automation

Tests and automation protect delivery speed; they are not ceremonial coverage.

6 tools

Playwright

core

Browser automation, e2e, screenshot and axe checks

Go testing

core

Simulated hardware, real-broker integration, golden runs

Pytest

Integration and architecture tests

axe-core

core

Accessibility checks tied to product quality

Conformance gates

Deployed permissions checked against a hashed manifest in CI

Trivy, gitleaks, govulncheck

Image and dependency scanning in the pipeline