Felipe Barreiros 🔥

Felipe Barreiros 🔥

Senior Product Engineer at AWS

Austin, Texas, United States

Actions

Felipe Barreiros is a Senior Product Engineer at AWS, where he leads a tech product from idea til impact. He has coached 12,000 tech graduates, hired 600+ engineers, and built and scaled edtech companies that trained 40,000+ students. His work focuses on Product Engineering: helping senior engineers and leaders own the full loop from problem definition to production impact. Before AWS, Felipe was a two-time founder, named #1 Most Attractive Edtech Startup by 100 Open Startups, and recognized by the World Economic Forum as a Global Shaper for impact in tech education.

Area of Expertise

  • Business & Management
  • Information & Communications Technology

Topics

  • Product Engineering
  • Technical Product Leadership
  • AI
  • Product Engineer
  • Software Development Engineer
  • Technical Product Management
  • Product Management
  • Developer Experience (DX)
  • SDLC (Software Development Lifecycle)
  • Product
  • Leadership & Strategic Planning
  • Engineering Leadership & Management
  • Product Innovation
  • Product Development
  • Developer Productivity
  • Harness Engineering
  • Agent Memory
  • Agentic
  • Agentic AI architecture
  • AI Agentic Workflows
  • Agentic automation
  • Agentic Systems
  • Agentic rags
  • LLMs & Agentic AI
  • Agentic AI Orchestrator
  • agentic software engineering
  • Agentic Engineering
  • Generative & Agentic AI
  • Agentic AI
  • AI & Agentic Systems
  • Agentic Workflow
  • Workflow
  • Workflow Automation
  • Workflows
  • Multi-Modal & Agentic AI
  • api
  • API First
  • aws
  • Kiro
  • Claude Code
  • Claude
  • Anthropic Claude
  • Anthropic
  • OpenAI
  • z.ai
  • glm
  • LLMs
  • LLMOps
  • LLM Inference at Scale
  • Code LLM
  • AI/LLMs
  • Retrieval Augmented Generation (RAG) and LLM Applications
  • RAG
  • Retrieval-Augmented Generation (RAG)

The Post-Engineer Org: When AI Lets Everyone Code and Engineering Still Owns Production

AI does not only help engineers write code faster. It lets PMs, designers, analysts, founders, and domain experts create software-shaped changes. That unlocks speed, but it creates a new production-governance problem: if everyone can generate code, who owns quality, architecture, security, observability, and rollback? This session explores the post-engineer org: not a world without engineers, but one where engineering leadership must redesign ownership, review, and guardrails around a company where everyone can code.

From Ticket-Taker to Product Engineer: A Practical Playbook for Shipping What Matters

Most engineers describe their work in activities: closed tickets, merged PRs, shipped features. Product Engineers describe their work in impact: adoption, retention, revenue, cost reduction, support tickets avoided, customer behavior changed. In this hands-on workshop, attendees will use the Product Engineer playbook to move a vague product request up the Clarity Ladder: from activity, to output, to result, to impact. We will define why the work matters, scope what should be built, use AI-assisted prototyping to pressure-test the plan, and design the measurement loop before shipping. Participants leave with practical artifacts they can reuse immediately: a problem brief, build scope, AI context packet, and ship-review template.

Product Engineering: The Role AI Made Inevitable

AI did not just make developers faster. It changed what makes an engineer valuable. When implementation becomes abundant, the scarce skill is no longer typing code: it is deciding what should exist, why it matters, and how to prove it worked. In this lightning talk, you will dive deep into the Product Engineering role and how to fully the idea-to-impact loop.

AI Made Code Cheap. Your Judgment Is the Product Now

AI made code cheap. That sounds like good news, until your team becomes 10x faster at building the wrong thing.
This session is about the judgment layer that must come before AI-assisted building. We’ll walk through practical product-engineering frameworks for defining the problem well first: customer jobs, problem trees, evidence quality, success metrics, scope boundaries, and the “should we build this?” decision.
The goal is not to turn engineers into product managers. It is to help engineers become sharper owners of product outcomes. Before you start prompting, or generate a prototype, you need to know who the customer is, what pain is real, what behavior should change, and how you will know the work mattered.

AI.Engineer World's Fair

June 2026 South San Francisco, California, United States

Connecting the Americas

May 2026 São Paulo, Brazil

Is SaaS dead, alive or just rebranding to AI?

April 2026 Atherton, California, United States

Felipe Barreiros 🔥

Senior Product Engineer at AWS

Austin, Texas, United States

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top