Work with me
Most of my work is writing, building, and shipping inside Airbnb. A handful of times a year I work with engineering teams on the platform layer underneath their AI tools, when there's real fit on both sides.
By Matthew Fontana · Staff Engineer at Airbnb · ex-Spotify, ex-UPS · 13 yrs in enterprise software
What I tend to help with
Every team's situation is different, so I don't sell fixed packages. These are the kinds of problems I'm useful on:
- Agentic platform strategy: turning a pile of AI tool licenses into a platform your teams actually use.
- MCP architecture: exposing your codebase, data, and internal services to agents under existing auth.
- Evaluations: codebase-specific harnesses so you can tell when an agent is helping and when it's drifting.
- Developer productivity: measuring the platform in terms leadership can defend to the business.
How I tend to work
No two engagements look the same, so this isn't a fixed process. It's the handful of principles that shape every piece of platform work I take on.
Outcomes over outputs
The deliverable isn't a deck or a Notion page. It's measurable adoption and a velocity number that moves. We agree on the metric early and instrument for it.
Vendor-agnostic by design
Codex, Copilot, Claude Code, Cursor, Windsurf are tactical. The platform layer is strategic. I build to the meta-layer so the system survives the next tool launch.
Evaluations are the missing layer
Most rollouts skip evals because they're hard. That's why adoption stalls. Codebase-specific evaluation harnesses are non-negotiable in the work I do.
Your codebase is the context
Generic agents are weak. The moat is org-specific context: internal MCP servers, packaged skills, and subagent patterns shaped to how your teams actually ship.
What's different
A few things that show up whenever I work with a team, and are easy to miss when comparing on a website.
Hands on keyboard
I write the configs, ship the MCP servers, and run the evals. No subcontractors, no junior associates billing my rate.
Single senior point of contact
You work directly with me. No account team layer, no handoffs between phases.
Production codebases, not pilots
The work lands in your real repos with real teams. Pilots that never ship don't move metrics.
Get in touch
No pitch deck, no qualification form. Email me what you're wrestling with: where adoption stalled, what shipping faster would unlock. We'll figure out together whether there's a fit.