I'm a computer science junior at UTEP, minoring in math, and I like building software that holds up, not just software that looks good in a screenshot.
Most of the work I enjoy lives in backend systems, distributed pipelines, testing, and the rollout work between "it runs" and "it's ready." At Google I spent a summer on Workspace Policy Infrastructure, parallelizing a policy compilation pipeline and shipping it through a zero-incident gated rollout.
Outside of that I've taught STEAM to 200+ kids, supported TurboTax customers, sold electronics, and worked a pizza counter. Every one of those jobs taught me something about patience, communication, and the people depending on the work.
I'm the first in my family to go to college. Right now I'm looking for Summer 2027 SWE internships and co-ops where I can contribute early, learn from stronger engineers, and keep getting better at shipping careful work.
How I work
Backend and distributed systems
I like the parts of software that have to survive retries, concurrency, and edge cases, and still read cleanly after the first version ships.
Full-stack product work
I still care whether an interface makes sense, whether the copy sounds like a person wrote it, and whether someone would keep using it after the demo.
Testing and rollout discipline
A lot of my best work comes from tightening coverage, watching latency, and making sure a change is safe enough to ship without drama.
Practical AI and ML
The interesting part for me is not just calling a model. It is knowing where automation actually helps and where normal, deterministic software should stay in charge.