For years I didn’t have a clean word for what I do. “Full-stack developer” felt too narrow. “Founder” wasn’t right either. Then I found it: product engineer. It’s the most accurate description of how I’ve worked for over a decade — and once it clicked, a lot of things made sense.

What a product engineer actually is

A product engineer is an engineer who owns the outcome, not just the code. Four things set them apart:

1. They think in results, not tickets. Not “what’s the next task?” but “what should we build, and why?”
2. They ship end to end. One person takes an idea from design to backend to frontend to deploy — no handoffs.
3. They have product and business sense. They make the calls a product manager usually makes — what to build, what to cut, what’s good enough — and then they write the code too.
4. They’re pragmatic. “Working and in the user’s hands” beats “perfect but unshipped.”

Put simply: a PM who can ship code, or an engineer with a founder’s brain.

Why I’m one

I didn’t pick the label — I earned it by accident, building the same thing over and over.

My main work is CPA25, the platform that runs a real-estate brokerage in Santiago: leases, billing, settlements, audits, email marketing. I conceived it, built it, deployed it, and I keep it running. It’s the fifth rewrite of a system that started in Google Sheets around 2016 — PHP twice, then Django, now Next.js. Each rewrite taught me the business, not the framework.

I’ve built across very different domains — video streaming sites, e-commerce platforms, content-heavy sites, and CPA25. Same move every time: understand the problem, build it, and put it in front of real users.

Am I the deepest React specialist? No — and that’s the point. The job was never “write a perfect component.” It was “make the brokerage run.” I reach for whatever tool ships the product, AI at my side.

Where I actually live: the terminal

Here’s the part that’s most me: I’m happiest in the console. Bash, ssh, Linux — the command line is where I move fastest, and it’s been that way since Debian in 2004. I run my own hardened infrastructure: a self-hosted VPS serving a ~20,000-property portal, every container sandboxed in gVisor, hardened SSH, automated backups. Plenty of people who call themselves developers have never held a production server. I harden mine from the terminal.

Why this matters more in the AI era

When AI writes more of the code, deep syntax knowledge of one framework matters less. What gets scarce is judgment — knowing what to build, catching when the AI is confidently wrong, and owning the whole thing. I develop CPA25 with six Claude Code agents in parallel; my job isn’t to type, it’s to direct and verify. In that world, the generalist who can run the full span — product, code, infra, security — wins.

That’s a product engineer. That’s what I am.

---

I’m Eduardo, a product engineer from Santiago, Chile. If this resonates, find me on X.