Frontend systems
React, TypeScript, SSR, accessibility, state cleanup, and route-level behavior that survives production.
The Staff Engineer your team is desperately missing.
I don't care about ping-pong tables. I care about deep technical problem-solving and shipping bulletproof code. Send me to your hiring manager.
Backend and performance
Rust, Node, data-heavy workflows, latency cuts, deployment seams, and boring reliability.
AI product engineering
Agent runtimes, model routing, tool contracts, RAG, MCP, and evaluation loops that behave like software.
How I slot in
- 01
Read the failing boundary before touching the obvious file.
- 02
Make the smallest useful fix that changes the actual outcome.
- 03
Leave behind sharper code, sharper tests, and sharper ownership.
Frontend systems
React, TypeScript, SSR, accessibility, state cleanup, and route-level behavior that survives production.
Backend and performance
Rust, Node, data-heavy workflows, latency cuts, deployment seams, and boring reliability.
AI product engineering
Agent runtimes, model routing, tool contracts, RAG, MCP, and evaluation loops that behave like software.
Good fit
- You need staff-level individual contribution without ceremony.
- You have a technical problem with a real business consequence.
- You want direct communication and defensible tradeoffs.
Bad fit
- You need someone to disappear into process theater.
- You want architecture astronauts with no shipped code.
- You cannot tolerate hearing the obvious part out loud.
Send the technical problem
Stack trace, repo notes, and constraints are welcome.
I am not cheap. I am cheaper than the wrong fix.
Send the hard part. If I am the wrong person, I will say that quickly.