Skip to main content
Matthew BobackBackend & Platform Engineer

Contact

Reach out when the role or project needs someone who can own the messy middle.

The best conversations for me are about backend-heavy products, operator workflows, accessibility and testing discipline, or delivery problems that sit somewhere between platform work and product work.

Best Fit

I am most useful when a team needs backend ownership, practical product judgment, and enough operational care to keep the work understandable after it ships.

Useful Context

A short note about the system, team, users, or delivery pressure is better than a polished pitch. Concrete constraints make the first reply much more useful.

Response Path

Email is the reliable path. The form below opens an email draft unless a form backend is configured, so the message remains visible before it leaves your machine.

Write

Start with a concrete problem, role, or team need.
Short and specific beats polished. If there is a product, team, or system concern behind the conversation, include it.

Include enough context that I can tell whether the work is mostly backend, platform, product-facing, or some combination of the three.

No form backend is configured here, so submit opens your email client instead.

Direct

Email works best.

Click to copy the direct email address.

Open Email Draft

Fit

Good reasons to reach out

Backend and platform roles where shipping discipline matters

Operator-facing tools and internal product workflows

Accessibility, automation, and QA-heavy product surfaces

Systems work that still needs clean product presentation

Elsewhere

Public profiles
GitHubLinkedIn