TECHNOLOGY LEADER · ENGINEER · OPERATOR
20+ years across design, growth, engineering, product and technical leadership — from hands-on building to CTO-level responsibility, and still close to the work today.
THE THROUGH-LINE
Design raised questions about adoption. Growth pulled the work into data and engineering. Engineering expanded into architecture. Technical leadership connected product, teams, economics and responsibility for the outcome.
WHERE IT STARTED
Make it clear. Make it useful. Make people care enough to use it.
The first problems were visual. Design became web development because shaping the experience meant understanding how it actually worked — not just how it looked.
Then the questions moved underneath the interface. Why did people use one thing and ignore another? Where did they leave? What brought them back? What could the business learn from the behavior?
The interface was only the surface. Performance was underneath it.
TERAPEAK · LATER ACQUIRED BY EBAY
Building the experience wasn’t enough. The next question was whether it moved the business.
At Terapeak, design, engineering, experimentation, data and revenue converged around outcomes. The boundaries mattered less than whether the work changed what users did and what the business achieved.
AI prototypes had to prove ROI. Retention work had to move churn. Product decisions had to connect to ARPU and adoption. That operating range continued through Terapeak’s acquisition by eBay.
Tie the work to outcomes and the boundaries disappear.
CTO-LEVEL OPERATING SCOPE
Eventually, the responsibility stopped ending with the technology.
Architecture still mattered. So did product direction, hiring, operating cost, reliability, delivery speed and whether the technology could support the business it was meant to become.
Across mobility and financial technology, the work moved from early ambiguity into real operating scale. At that scope, engineering decisions were business decisions.
See the whole system. Find the constraint. Move it.
SUKOW VENTURES · SENIOR SOFTWARE ENGINEER / GROWTH & TECHNICAL STRATEGY
The code still matters. So does everything it sets in motion.
Hands-on engineering keeps the constraints real. Broader operating experience keeps the consequences visible — product, infrastructure, economics, adoption and what happens after launch.
The question isn’t only whether something can be built. It’s what deserves to be built, what is actually blocking scale, where AI changes the operating model and which technical choices create leverage.
Build the system, not just the ticket.
Use new capability where it changes the operating model.
Connect technical choices to adoption, revenue and user value.
Make decisions with downstream consequences in view.
Depth matters. Range makes the depth more useful.
See the full trajectory →STILL BUILDING
New technology gets interesting when it survives contact with a real problem.
AI is changing what software can do, how products are designed and where the economics of a system live. The useful understanding comes from building with it — turning possibility into working products and testing the assumptions against real constraints.
How persistent agents coordinate work across tools, infrastructure and business processes — and where human judgment should stay in the loop.
What changes when generation, memory, identity, multimodal interaction and model choice become first-class parts of a product system.
Usage, infrastructure cost, pricing and monetization are increasingly technical design constraints — especially in AI-native products.
Exploration keeps judgment current. Building keeps it honest.
WORKING NOTES
Ideas on engineering, AI, product, systems and the decisions that connect them.
All notes →The strongest architecture decision is often the one that correctly identifies the business, product or operating constraint first.
As AI moves from assistant to actor, usage, authorization, cost and monetization become part of the product architecture.
Knowing the ideal architecture is useful. Knowing what the system needs next is what moves the company.
OPEN CHANNEL
Hard problem. Ambitious product. System that needs to become something more. Those are usually the conversations worth having.
