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.

stageflow scan

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

Shipped

Products you can use today

StageFlow is open source with a live demo; AlchemizeCV runs in production. Both are inspectable, not just described.

Physical

Systems with real consequences

A commissioned access-control platform keeps doors enforcing access even when the site loses its cloud link.

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.
open sourceSolo
StageFlow
StageFlow is an open-source, self-hostable frontend quality platform. It runs eight scanners — accessibility, performance, SEO, links, security headers, social metadata, content quality, and agent-driven navigation — as one pipeline behind a single report contract, and remembers a baseline per project so every scan can answer the question that matters in CI: did this change make the frontend worse?

8

Built-In Scanners

MIT

Open Source License

3

Clients: Web, CLI, CI

Open SourceGo CLINATS JetStreamRootless Podman
Master Profile projects section with GitHub-imported, grounded proof points.
productionSolo
AlchemizeCV
AlchemizeCV is an AI-powered resume-tailoring and job-application platform. Users maintain a grounded professional profile, discover jobs from multiple boards, generate ATS-optimized resumes through a multi-phase LLM pipeline running on Temporal, render them to PDF, and track applications — with browser-driven job discovery running behind the scenes.

5

Runtimes In One Monorepo

4

LLM Providers (BYOK)

4

Pipeline Phases Per Resume

Temporal WorkflowsFastAPIReact 19Multi-Provider LLM

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.