About / San Jose
I’m a computer science student at San José State. I’m available immediately for part-time technical work, on-site, hybrid, or remote, with an interest in software, cybersecurity, and solutions engineering.
01 / Direction
I keep gravitating toward work where the code is only half the problem. The other half is understanding what the system is doing and making that answer useful to a teammate, customer, or operator.
So far, that has meant production scoring software at Virtius, a Wazuh lab built around Windows account events, an Airtable CRM at HeartBeam, and a Selenium tool for the tennis desk at AVAC. Different systems, same question: what is actually happening here?
02 / Learning
When I want to understand a system, I stop reading once I know enough to make a useful attempt. I retrieve the commands without notes, build something real, and pay attention to where my mental model falls apart.
That last part matters. Recognition is cheap; debugging without the tutorial open is where I find out what I actually know. Then I write down the result clearly enough that someone else can reproduce it.
I also keep security news in my routine. As of September 2026, I’ve listened to more than 75 episodes of CyberWire Daily. NetworkChuck, Darknet Diaries, and other technical creators give me new systems and security questions to explore. How I stay current →
03 / Piano
I’ve played piano since sixth grade and still practice and perform. It rewards careful preparation, but it also teaches a less glamorous skill: recovering from a mistake without advertising it to the whole room.
That habit carries into technical work. Listen closely, notice the pattern that changed, and keep working the problem instead of getting attached to the first explanation.
04 / Work
The work page includes production code I contributed to, a staff tool I built, a kiosk I run, and controlled security labs. Each case study explains my contribution and what the evidence supports.