Electrical
B.S. Electrical Engineering. Circuit and device-level design, RF and electromagnetics, signal and power integrity, programmable logic, and the generation and distribution of power itself.
About the practice
I help you build the engineering team, and then I work in it. Research support, prototyping and a straight read on hard decisions, done alongside your engineers rather than handed down to them, plus introductions to specialists I have worked with over twenty years. What gets published here is what I can actually help with and how deep it goes, not a list of logos - client work is confidential. Judge it on the depth, then test it with a call.
Foundations
Degrees in all three, not adjacent skills picked up on a project. It is why I can follow one system from the die to the dashboard without handing it to somebody else halfway.
B.S. Electrical Engineering. Circuit and device-level design, RF and electromagnetics, signal and power integrity, programmable logic, and the generation and distribution of power itself.
M.S. Computer Engineering. Distributed and parallel computing, embedded systems and device drivers, industrial controls and operational technology, and hardware and software co-designed as one system.
Two decades in production. Systems and application engineering, protocol conformance and test automation, platform and cloud architecture, and the delivery practice around all of it.
How I built it
I have never left a job because I was unhappy in it. I left because I had found the edge of what I understood and the next thing was somewhere else. Four times, in this order, and the order is the part that matters.
I could write software against hardware I did not understand, and it bothered me. So I went and ran full ASIC flows through to a fabricated netlist before I touched any platform work. The bottom of the stack stopped being an abstraction, and it is where I met the process, RF and test people I still call.
I knew how to build things and not how they get taken apart, which is a bad asymmetry to carry into a design review. So I spent years on the other side: exploitation, radio, forensics and certification auditing. That is why I design for a motivated attacker instead of a compliant one, and why the assessors and testers I introduce are people I have been measured against.
Everything I had built until then was one system at a time, and I had no feel for what happens when a design choice lands on thousands of estates at once and cannot be walked back quietly. So I went to do platform and portfolio engineering at hyperscale. The SRE and DevSecOps teams in the network come from those years.
Credentials
Engineering degrees at bachelor's and master's level, in electrical and computer engineering respectively. Those do not expire, and I am happy to evidence them.
I also held the security and audit certifications for most of a career - CISSP, CISM, CISA and the rest of that alphabet. I no longer do. They lapsed, I did not renew them, and you will not find them claimed anywhere else on this site.
They are genuinely useful in two situations: a salaried hiring process that needs a filter it can apply at scale, and a room where nobody is placed to judge the work directly. Neither describes this one. You can read what I think about segmentation, secrets, supply chain and the rest, and form a view before we ever speak.
The body of knowledge behind them has also been thoroughly commoditized. It sits in free courseware, in the published standards themselves, and in any model you care to ask. A certification that once stood for access to scarce material stands for less once the material stopped being scarce. What it still evidences is that somebody passed an exam on a particular Tuesday. What I would weigh instead is whether an architecture survives a motivated attacker rather than a compliant one, and whether the person carried a framework all the way to an audit instead of only reading it.
References and named project history are provided directly under engagement, along with any non-disclosure terms your procurement requires. They are not published here, and neither are client names.
If procurement needs to know the shape of the delivery team, ask on the first call. Every specialist who would touch your engagement is named before you sign - there is no bench being allocated behind the scenes, because there is no bench.
Work is delivered in English and Spanish, remotely across the United States and internationally, from San Antonio, Texas.