Hamed BahramiHamed BahramiBerlin, Germany
Senior Product Design Engineer, AI Native

Designer/Builder

I turn complexity and AI Output into clear, state-of-the-art software. For founders and product teams that need senior product judgment, interaction design. I deliver testable pilots or functional product. I work in strategic setups or fully operational. 10+ years experience

I help companies reduce the noise and increase the signal.

I create value through intelligence, creativity, aesthetics and flipping the switch from zero to one.

I have worked in different setups, in different roles. I challenge, I collaborate, ask questions and get things done.

  • Flink
  • sonnen
  • Flexperto
  • Commerzbank
  • NockNock
  • ChefsList
  • Neugelb

A selected list of clients over the years.

From ambiguous idea to working product.

Welcome the new product loop

As building gets faster, the quality of the decision becomes the advantage. Good decisions start with evidence.

DesignBuildLearn
vibe

Framing the problem is crucial to decision making. Evidencing gives us a credible thesis. Always looking for the shortest path from zero to one.

Strategic UX frames the problem

As building gets faster, the quality of the decision becomes the advantage.

FlinkChefsList
UX Project 1 - Flink
Anonymized UX strategy board with journeys, research notes, and test results
Anonymized product interface board with notes and dashboard structure
Anonymized research process board with insights, opportunities, and prioritization
Stakeholder Mapping
Wireframing
Design Roadmapping
Personas
Customer Journey Mapping

Drag to explore

Experimentation Recipes

As building gets faster, the quality of the decision becomes the advantage. Good decisions start with evidence.

Evidence based, conversational, contextual. Intelligent Products need good Context Architecture. Deep technical knowledge into Databases is needed to get the most out of the UX.

Let's design data.

Open Source

I have been building my own tools. AI is only as intelligent as the pipeline. Product outcomes are not guaranteed, when an agent doesn't know what to do, where to look or what the right context is for the task.

I built my own package to code faster, save on tokens and keep most of the workflow deterministic instead of letting the agents handle the fuzzy work.

It doesn't matter where and how the LLM is hosted. The tools stay the same.

Agentic work, is the new normal. Cutting down on the agentic slack too. Too much signal is still noise.

Let's build product,

in a new world.