Global

I build AI products that inspire real users.

Technical Product Manager. Developer Infrastructure. AI Systems.

Available for remote roles.

Philosophy

How I Think About AI Products

AI products fail when teams treat models like features instead of systems. A feature ships and works. A system ships and degrades, hallucinates, and surprises you at 3am. The product discipline for AI isn't just roadmap management — it's building the evaluation infrastructure that tells you when your system is lying.

My method: Discovery → System design → Experimentation → Evaluation → Iteration. I focus on products where model capability is core, not cosmetic — where the intelligence layer is the product, not a chatbot bolted onto a CRUD app.

My background in Human-Computer Interaction means I design for the human failure modes, not just the model ones. Five years of shipping across distributed systems, crypto infrastructure, and developer tooling taught me that the messy parts — edge cases, error states, confused users — are where product quality actually lives.

Career

Where I've Built

2025

Technical Product Manager

Block Labs · Lisbon, PT

Developer infrastructure platform — APIs, SDKs, platform services

2024

Technical Product Manager

SSV Labs · Remote

$400M+ infrastructure migration, API design, partner integrations

2022

Product Manager

KNOW Foundation · Remote

Distributed compute platform, cloud-native architecture

2021

MA, Human-Computer Interaction

Reichman University · Israel

Interaction design research for complex technical systems

2020

UX Researcher

Wix / DeviantArt · Israel

User research, interaction design, design systems

Operating System

Working Principles

01

AI is stochastic. Product must be deterministic.

Build evaluation layers, fallback paths, and human override systems before you build features.

02

Intelligence is cheap. Trust is expensive.

Users don't leave because the model is wrong. They leave because they can't tell when it's wrong.

03

Shipping beats theorizing.

A deployed system with instrumentation teaches you more than six months of architecture documents.

04

Interfaces are contracts.

Backward compatibility, versioning discipline, and abstraction integrity are how you earn the trust of downstream consumers.

05

Design for the confused user, not the happy path.

Edge cases, error states, and recovery flows are where product quality lives.

Methodology

How I Build

User InputResearchOrchestrationProduct LayerModel CallAPIEvaluationLayerOutputShipped FeatureFeedbackLoop

Contact

Let's Build Something

I'm interested in roles where AI capability is core to the product — not a feature checkbox. If you're building something that matters, let's talk.