My career started in the pharmacy, where precision isn't a preference — it's a requirement. Learning to translate dense, high-stakes information into clear instructions for people under pressure taught me something no engineering course does: that technical accuracy and human care are the same discipline.
At
Oracle, I learned that great support isn't reactive — it's architectural.
"Retention Engineering" means tracing a client's silent churn risk back to a malformed header, a missing auth scope, or a 3am latency spike they haven't noticed yet. I stopped closing tickets and started closing gaps.
[1]from my supervisor —
"An absolute problem-solver. Whether it was a complex API bottleneck or a frustrated customer, they found the solution before most people even finished reading the ticket."
Sr. Solutions Engineer, Oracle
I built this site and AgentStat from scratch — the design, the telemetry engine, the open-source library — because I believe the most effective Technical Success partner is also a builder. Someone who reads the stack, feels the friction, and sometimes just fixes it. I'm looking for a team that treats that instinct as an asset, not a curiosity.