I build software. Then I try to break it before someone else does.
Software engineer with an M.Eng in Cybersecurity from the University of Maryland.
I ship production features and harden the pipelines that ship them.
Most people pick a side between building and securing. I never understood why you would.
π Resume? It lives on my portfolio, in two editions: one for software roles, one for security. Flip the lens and grab whichever fits.
π΅ Build Β Ship full stack features end to end. React and Node on top, Python and REST APIs in the middle, real databases underneath, and CI/CD on AWS that delivers it all without a human babysitting the release.
π’ Break Β Threat model before the first line of code. Run security reviews and pentests, wire scanning gates that catch bugs before they reach production, and handle incident response when production decides to page at the worst possible hour.
The interesting work is the seam between the two, and that is where I like to live.
- π οΈ Software Engineer (DevSecOps) at CuraJoy, owning features from design to deploy and keeping the platform secure as it grows
- π€ Building AI agents that make security review faster without drowning people in false alarms
- π Two published papers on IoT security and forensics (IEEE and Springer)
- π Phi Kappa Phi inductee, ISC2 Graduate Scholarship recipient
Languages
Frameworks
Cloud and DevOps
Security and Tooling
- IoT Forensics System based on Blockchain Β· IEEE INDIACom 2023
- Exploring Cyber Security Issues in the Internet of Healthcare Things (IoHT) Β· Springer ICTCS 2022
Curious how a resume can run like an API? Open the portfolio and send a request.

