Build what you'd want to use
Embedded systems engineer with a passion for product, in Los Angeles.
Case Studies
Self-directed product work. Each one starts from a problem I could go observe in person, and states its assumptions instead of hiding them.
Erick Mercado
I write embedded software for electronic warfare systems at Raytheon out in El Segundo. Before that I was at UC Irvine for computer engineering. I am detailed oriented and diligiant as working with fixed memory, fixed power, and deadlines measured in microseconds suggests. The goal of my work is that the person relying on it never once has to think about whether the system will work or not.
I'm moving into product because the decisions I found most interesting were happening upstream of me: Understanding how a system works and then working backward from there. Who's actually using this, what problem does it solve for them, and does the math work out for the business. I've gotten a real appreciation for how much thought goes into decisions that look small from the outside. Somebody argued about that. There was a tradeoff, and constraints, and probably a meeting nobody enjoyed. Once you start seeing that everywhere it's hard to stop.
What I'm looking for: Products where I get to dig into why people behave the way they do. What they're actually trying to accomplish, what makes an experience feel effortless, and what makes them willing to spend. I think those are the same question. The best products I've used made me happy to hand over money. The worst ones made me feel like I was being worked on. A good PM should be able to grow the business and improve the experience in the same decision, and that's the kind I want to be.
The case studies are the fastest way to see how I think.