I build and advise on systems that need to be understandable, reliable, and useful under pressure.
My work sits between product thinking, systems design, and execution. I'm most useful when a team is dealing with complexity that's already affecting trust, speed, or delivery quality.
Systems Architect, Consultant, and Product Builder
14+ years across product systems and platform engineering
years building products, automation, and platforms
clear ways to work with me: hire, consult, or reserve time
experience across leadership, architecture, and hands-on delivery
The work has consistently moved across product, platforms & automation.
Leading a platform that turns large volumes of public information into usable intelligence for operators and decision-makers.
Built automation and orchestration systems for high-volume workflows, runtime control, and operational feedback.
Worked across transaction flows, wallet infrastructure, and product architecture in blockchain-heavy systems.
Explored automation, scraping, and orchestration patterns that later informed product and platform work.
A lot of the value comes from live working sessions — not just polished deliverables after the fact.
The best work happens when product context, technical judgment, and decision-making are in the same conversation: whiteboard sessions, architecture reviews, or pressure-testing a roadmap with the people who need to ship it.
Direct, collaborative, and grounded in the real constraint instead of abstract technical theater.
A clearer decision, a stronger system plan, or a faster path to a useful next step.
Some architecture jokes deserve to stay in the archive.
This Silicon Valley frame sits here as a small culture reference for the kind of technical chaos that makes whiteboard work both funny and useful. A good session is more disciplined than this — but the joke lands because every serious system has one impossible-looking diagram somewhere.
Drop public/silicon-valley-whiteboard.jpg and it appears here automatically.
Systems over tools
Automation over repetition
Evidence over opinion
Scale as a first-class constraint
Clarity over cleverness
Delivery over theater
Contribution history, down to the day, directly from GitHub.
This section is currently showing demo contribution activity so the About page can ship before the live GitHub token is configured.
8,898
Across 4 tracked years for @Menwitz.
Demo contribution data with the same calendar shape as the live GitHub integration.
Last built Sep 30, 2026.
1,652 contributions in 2026
Hover the grid to inspect each day.
2,388 contributions in 2025
Hover the grid to inspect each day.
2,412 contributions in 2024
Hover the grid to inspect each day.
2,446 contributions in 2023
Hover the grid to inspect each day.
Where I explain the tradeoffs behind the systems work.
Metadata Filtering in Vector Search: Pre-Filter, Post-Filter, and the Recall Cliff
How metadata filtering actually behaves in vector search: why post-filtering breaks tenant isolation, when selective filters collapse ANN recall, and what to do.
Embedding Model Selection for Retrieval: How to Choose Without Trusting a Leaderboard
How I pick an embedding model for retrieval: the constraints that decide it before quality does, a bake-off you can run, and the re-index nobody prices.
Worker Fleet Architecture at Scale: Pools, Scaling Signals, and Draining
Scaling a worker fleet isn't adding workers to one queue. Here's how I partition pools, pick the scaling signal, and drain workers without losing jobs.
How to Evaluate RAG Retrieval: Eval Sets, Metrics, and Ship Gates
Retrieval eval is 20% metrics and 80% eval set. How I build one that survives re-indexing, which number to read at which k, and how to gate a change.