open to software engineering and security roles
Yogi Makadiya
I build production systems and the pipelines that ship them.
Software engineer with an M.Eng in Cybersecurity from the University of Maryland. I have shipped production features at a startup, hardened CI/CD pipelines, run incident response, and published research on IoT forensics. Most people pick a side between building and securing. I never understood why you would.
scroll to trace the route ↓
hop 02 · build
Where I have shipped
Every role here is both jobs at once: features went out the door, and the door got a lock. The bullets below follow your lens. build reads like a software resume, break reads like a security one. Same jobs, both true.
hop 03 · ship
Things I have built and broken
Each card answers the question that matters in 2026: why does this need a human who understands the system, instead of a prompt? Every project includes a build line and a break line, because every system is both.
hop 04 · link
Toolchain
The ordering below follows your lens. Flip it and watch the priorities change. That is roughly what my brain does too.
hop 05 · sign
Published research
Peer reviewed and shipped to print. The slowest deploy pipeline I have ever worked with.
hop 06 · train
Education
hop 07 · verify
Credentials and leadership
// credentials
// leadership
hop 08 · probe
The career API
Everything on this page is also an endpoint. This sandbox runs entirely in your browser, no network calls, no telemetry. Not every route is in the docs. You know what to do.
# responses appear here. try the chips above, or go off-script.
hop 09 · connect
Destination reached
If you are hiring for software engineering or security, my inbox is open. I answer real emails faster than most APIs answer health checks.
or, if you must: