Performance Engineering
Making the common path fast, and hiding the latency that remains.
evidenced in: 2 case studies · 1 companies
proving documents
Trading a runtime join for a materialized column, then finding the 79% my own migration left behind
A per-request warehouse join was scanning 658.8 MB against a hard 953.7 MiB per-job ceiling, on a table growing with every new customer. I measured it, moved the join into the pipeline that already ran it, deleted the cache that was hiding the problem, then audited my own migration and found 79% of production rows never backfilled, plus 9,299 alerts that had never appeared in the product at all.
Making asset-tree search faster across the API and interface
Browsing a large asset hierarchy meant repeated database queries and slow loading. I contributed a recursive backend traversal that reduced the query pattern from N×3 calls to three, while another engineer completed most of the final search story. The shared feature added contextual search and progressive prefetch; no before-and-after latency was measured.
exercised at