← All speakers

Bio, Work & Ideas

Itamar Friedman

Conference affiliation: Co-Founder & CEO · Qodo · 2026

Itamar Friedman is the co-founder and chief executive of Qodo, which builds AI-powered code review, testing, and governance for engineering teams. His premise: generating software faster creates little lasting value unless organizations can verify its quality, preserve architectural understanding, and decide when human judgment remains essential.

From machine vision to code integrity

Friedman studied electrical engineering at the Technion–Israel Institute of Technology and worked at Mellanox before co-founding Visualead, where he served as chief technology officer and developed computer-vision technology for visual QR codes. In 2017, Alibaba moved to acquire Visualead technology and bring members of its engineering team into a Tel Aviv research operation. Friedman subsequently led machine-vision work at Alibaba, including neural-architecture search, model training, and automated machine-learning tools.

In 2022, he and Dedy Kredo founded CodiumAI to help developers understand, test, and review code. The company expanded from automated testing into code integrity across software development and became Qodo in 2024. A $40 million Series A brought its funding to $50 million at the time; Friedman subsequently announced a $70 million Series B in 2026.

  • Flow engineering over prompt engineering. Friedman co-authored AlphaCodium with Tal Ridnik and Kredo, developing a test-driven, multistage approach that iteratively improves generated code. Reliability comes from the surrounding workflow: generating tests, evaluating candidate solutions, and incorporating feedback.
  • Independent code review. Writing code and evaluating it demand different judgments. Qodo’s open-source PR-Agent reflects Friedman’s focus on specialized reviewers that detect consequential defects while considering security, architecture, maintainability, and team standards without inundating developers with irrelevant warnings.
  • Organizational context as infrastructure. Effective review depends on information beyond a codebase: architectural decisions, service contracts, incident investigations, previous pull requests, and engineering conventions. Friedman’s context engine organizes that knowledge so review decisions remain intelligible to humans and usable by coding agents.
  • Adversarial collaboration between coding agents. Friedman uses command-line workflows to connect specialized coding, testing, and review systems, while distinguishing simple pipelines from genuine agent interoperability. His practical escalation rule requires the coding agent and independent reviewer to resolve disagreements; when they cannot, a human decides.
  • Software-graph governance. Friedman wants review systems to evaluate relationships among repositories, services, contracts, and simultaneous changes—not merely individual pull-request diffs. Teams can gradually automate approval and blocking as their standards become explicit and review results earn trust. He calls the translation of accumulated engineering experience into auditable, actionable judgment artificial wisdom.

Read the topics behind these talks

3 conference talks

Key ideas

Scroll to read ↓

Automating review requires more than finding bugs: it requires team standards, architectural contracts, and accumulated experience that both people and agents can inspect.

  • Who verifies the code your agents write?
    0:33 ↗
  • Preserve validation and learning
    1:59 ↗
  • Decide what confidence must mean
    3:38 ↗
  • Context makes a finding relevant
    5:17 ↗
  • Bring scattered knowledge under governance
    6:31 ↗
  • Give humans an inspectable basis for review
    8:53 ↗
  • Turn review findings into an agent handoff
    10:40 ↗
  • Remember contracts and the incidents that exposed them
    12:24 ↗
  • Apply explicit policies across concurrent changes
    13:38 ↗
  • Measure the rules and automate gradually
    15:47 ↗
  • Move experienced judgment into the system
    17:11 ↗

Key ideas

Scroll to read ↓

Faster code generation shifts work into review, testing, and ownership. Itamar Friedman examines the evidence and demonstrates how coding rules can become measurable, adaptive quality workflows.

  • What does a security review leave out?
    0:22 ↗
  • A rule is an instruction, not a guarantee
    2:27 ↗
  • Where generation stops improving the whole system
    4:25 ↗
  • More tools, more output, unresolved quality
    6:09 ↗
  • The work moves into review
    8:04 ↗
  • Quality belongs to code and to the process around it
    9:51 ↗
  • Use testing and review to enforce requirements
    12:23 ↗
  • Context includes the reasons behind the code
    14:11 ↗
  • Give quality agents artifacts, tools, and safe execution
    16:46 ↗
  • Turn a nested-if preference into a learning workflow
    19:03 ↗

Key ideas

Scroll to read ↓

Generating code faster creates a verification problem. Itamar Friedman explores how context, specialized review agents and command-line workflows could make that speed usable across software development.

  • What would make AI coding trustworthy?
    0:15 ↗
  • From completing lines to completing tasks
    2:06 ↗
  • End-to-end depends on the job
    4:56 ↗
  • Give verification an active role
    6:19 ↗
  • Squeezing the development V
    8:20 ↗
  • Context changes what generation can accomplish
    10:00 ↗
  • Feed code understanding and review back into writing
    12:24 ↗
  • Ask the CLI to create a reviewer
    13:57 ↗
  • Compose generation, coverage and review
    16:06 ↗
  • When agents need to discover one another
    17:34 ↗
  • Inspect the definition, then define success
    18:31 ↗
  • Automate the work, choose the interface for the task
    19:48 ↗

References