Backend & Platform Engineer

I work on backend systems, deployment infrastructure, and the interfaces that make them operable.

This site is the portfolio. The terminal beside this runs a live StageFlow scan — paste any public URL to try it.

stageflow scan

Enter any public URL above and press Enter to run a live scan

4
Shipped products

StageFlow, AlchemizeCV, Clear11y, and DisplayAnalysis — each with architecture writeups and running code.

280+
Automated checks

Testing spans API behavior, browser flows, and release confidence work.

Solo
End-to-end ownership

Architecture, UI, deployment, and operational cleanup stay in the same feedback loop.

Flagship work

Start with the projects that carry the most proof.

production Solo

StageFlow

Built a self-hosted scan workbench that runs six scanners against live URLs or ZIP builds, streams job state in real time, and merges the results into one evidence-rich triage surface.

6
Built-In Scanners
3
User Phases
3
Durable Streams
3
Audience Modes
Self-HostedJetStreamRootless PodmanSSEUnified ReportCLI
production Solo

AlchemizeCV

Built a job-search workflow platform that turns one master profile into tailored resumes, grounded project bullets, and tracked application runs through a replayable four-phase generation pipeline.

4
Pipeline Phases
3
Job-Hunt Surfaces
<1s
Render Time
2
Provider Paths
Context PruningContent HashingReact + VikePlaywright PoolAST RedactionWebSocket

Working style

What I tend to be responsible for when the work matters.

I am usually strongest where architecture and delivery meet: the parts of a product that need clear system boundaries, understandable UI, and enough operational rigor that the work does not collapse under real usage.

Backend systems that stay inspectable

I like event flows, clear state boundaries, and operational surfaces that explain what the system is doing without needing tribal knowledge.

Product interfaces for technical work

The UI work matters because operators need trust. I spend time on hierarchy, evidence, and interaction clarity, not just endpoint wiring.

Testing that supports shipping

I write tests that catch regressions and give confidence to deploy. Contract tests, integration tests, and threshold-based assertions over snapshot fragility.

Single-host deployment discipline

Rootless Podman, systemd quadlets, Caddy ingress, and compose overlays. Production runs on one machine with clear operational boundaries.

Hiring

Looking for someone who can own both the system and the proof around it?

I am a strong fit for backend, platform, and full-stack roles where the work includes architecture, operator UX, testing discipline, and deployment ownership instead of splitting those concerns apart.

Matthew Boback

Backend-heavy products, cleaner operator workflows, and delivery details that hold up under inspection.

Built with SvelteKit, Tailwind v4, and a light-only editorial system tuned for hiring review.

© 2026 Matthew Boback