Journey

I'm a software engineer based in Woodland Hills, California. My work sits at the intersection of product code and the systems that keep it from breaking on a Friday afternoon. The short version is on the home page; this is the long one.

I picked up my B.S. in Computer Science from Cal State Monterey Bay in May 2020 and went straight into the deep end at Abbott that November. Over two years there I worked across the engineering side of a platform serving more than half a million users: supporting DevOps with system troubleshooting and release-fix advice, coordinating the team's database maintenance work (schema changes, migrations, data integrity), and converting brittle manual regression suites into automated runs that shortened every release cycle. The work was equal parts software engineering and forensic detective work, and two years of log-diving, telemetry-chasing, and ship-or-don't-ship calls taught me what reliability actually costs and why senior engineers care about boring infrastructure.

In June 2022 I moved to OPTRO as a Software Development Engineer in Test II. The framing flipped: instead of being the engineer who manually tested, I became the engineer who builds the tools other engineers test through. Most weeks I'm writing Playwright + TypeScript suites, building API validation pipelines for backend microservices, and wiring everything into GitHub Actions so each PR earns its merge through continuous validation. Concrete win: 50% reduction in manual testing effort and 40% off regression cycles. Better win: developers ship with real confidence because the safety net is real.

On nights and weekends I'm working through an M.S. in Computer Science at the Georgia Institute of Technology (Georgia Tech), concentrating in Computational Perception & Robotics. It's a long-burn (a few years still in front of me), but the topic pulls at the part of my brain that wants to understand how systems learn to see and reason about the physical world. The OMSCS format works because the work it builds on is the work I'm already doing. Alongside the coursework, I'm also building side projects that showcase both my computer vision and fullstack development work.

The arc I'm chasing: be the kind of engineer who can move between product code, infrastructure, and the harder underlying systems with equal comfort. Specifically I'm looking for fullstack engineering roles where I get to ship features end to end, work on systems with real users, and keep stretching toward the harder problems. If that's the kind of seat you're trying to fill, the contact form is one click away.