Skip to main content
Matthew BobackBackend & Platform Engineer

Backend & Platform Engineer

I build backend systems and the interfaces that make them possible to operate.

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

View Case StudiesContact Me
stageflow scan

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

2

Flagship products

StageFlow and AlchemizeCV are the best starting points if you want to see shipped systems.

280+

Automated checks

The projects use API tests, browser checks, contract tests, and release gates where they matter.

Solo

End-to-end ownership

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

Flagship Work

Start with the systems that carry the most evidence.

These are the two case studies I would read first. They show the mix I care about: backend architecture, operator-facing product work, and deployment decisions that survive real use.

Live StageFlow playground for configuring URL or ZIP scans and scanner options.
productionSolo
StageFlow
StageFlow unifies multi-scanner website audits, replacing the need to manage eight different tools that don't agree on shape, severity, or remediation details. It runs up to eight scanners in parallel inside a rootless Podman pod, watches container execution in real-time, and aggregates the findings into a single, deduplicated report with concrete code evidence.

8

Built-In Scanners

6

Durable Consumers

10 min

ACK Timeout

NATS JetStreamRootless PodmanSvelte 5 RunesSSE Streaming
Read Case StudyLive Product
Authenticated AlchemizeCV profile builder with completion progress and section ordering.
productionSolo
AlchemizeCV
AlchemizeCV is a multi-runtime resume/application workflow system. It takes a master profile, pulls real code facts from GitHub repositories, and uses a feedforward pruner to tailor them to a job description—ensuring the same accomplishment is not repeated across different roles.

4

Pipeline Phases

SKIP LOCKED

Lease Engine

<1s

Render Time

Feedforward PruningRow-Level LockingReact + VikePlaywright Pool
Read Case StudyLive Product

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, explicit state boundaries, and operational surfaces that explain what the system is doing without tribal knowledge.

Product interfaces for technical work

The UI work matters because operators need trust. I care about hierarchy, evidence, and interaction clarity as much as endpoint wiring.

Testing that supports shipping

Accessibility checks, browser automation, and integration coverage are part of delivery, not cleanup after the fact.

Single-host deployment discipline

I work comfortably close to the machine: containers, reverse proxying, systemd, and release workflows that make rollback and debugging sane.

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.

Get in TouchBrowse the Work