Computer engineer + M.S. CS candidate · May 2027
I’m Joe—a graduate researcher, software builder, and board-level repair technician. Ten years at a repair bench shaped how I approach every system: inspect the evidence, narrow the cause, then make the change.
Begin with what the system actually did.
Reduce the problem until the next test is clear.
Turn the diagnosis into a useful outcome.
Core work
Research at Cal State LA connecting physics-based wildfire simulation with satellite observations, weather inputs, fuel data, Python, and HPC workflows. The work is active, so the emphasis here is the method—not invented results.
WRF-SFIRE · VIIRS · FLAMap · Python · HPC
Cal State LA research teamA decade of board-level diagnostics, microsoldering, repair operations, and customer accountability. The bench taught me to test assumptions before replacing parts—and to own the outcome when the first theory is wrong.
Diagnostics · Microsoldering · Operations · Web
Visit repair site →Develops evaluation rubrics and reviews AI-generated hardware, software, PCB, and circuit outputs for technical quality. The role sits directly between engineering judgment and clear, consistent evaluation.
Rubric design · Technical evaluation · Hardware · Software
AI quality and evaluationSelected builds
Protocol engineering · Python
BuiltA reliable layer with sequence numbers, ACKs, CRC validation, receiver buffering, timeout retransmission, and retry limits.
VerifiedDeterministic tests exercise delay, loss, corruption, and intentional failure cases. Built collaboratively with Alan Lam.
Operational software · Full stack
BuiltA dispatch system for loads, drivers, brokers, payments, documents, maintenance, IFTA, and activity history.
ControlledNext.js and TypeScript over Supabase/Postgres with authentication, row-level security, and private document storage.
Human-in-the-loop AI · Web
BuiltA workflow that turns a schedule image or PDF into structured, editable events and exports them as an ICS calendar.
DesignedGemini Vision and Pydantic handle extraction, while a required review step keeps the user in control before export.
“A clean demo is useful. A system that explains why it works is better.”
Background
Let’s talk