Lenny's PodcastSebastian Barrios: How 18k engineers deploy 30k times a day
At Mercadolibre the engineering leadership runs product strategy: about 1,000 PMs work alongside 18,000 engineers shipping 30,000 deploys per day.
CHAPTERS
- 0:00 – 6:07
Mercado Libre in numbers: 18k engineers, 30k deploys/day, 5M packages/day
Lenny introduces Sebastian Barrios and sets the scale of Mercado Libre: one of Latin America’s most valuable companies with an enormous engineering org and logistics footprint. Sebastian clarifies what he leads and why Mercado Libre’s operating model is uniquely technical and vertically integrated.
- •Mercado Libre’s scale: 18,000+ engineers across 18 countries
- •Operational pace: ~30,000 deployments/changes to production per day
- •Logistics reach: own trucks and planes; 5M+ packages/items delivered per day
- •Two major pillars: e-commerce marketplace + fintech ecosystem
- •Context for the episode: operating principles + Sebastian’s personal stories
- 6:07 – 8:28
What Mercado Libre actually is: vertically integrated commerce + fintech ecosystem
Sebastian explains Mercado Libre as a marketplace with deeply integrated logistics and a fintech business of comparable size. The discussion highlights why the company must build world-class routing, risk, and platform capabilities to operate across many countries and regulations.
- •Definition of ‘vertically integrated’ for Mercado Libre (planes, trucks, distribution)
- •Fintech offerings: accounts, credit cards, loans tightly integrated with commerce
- •Scale markers: ~100M users/customers/sellers interacting with the platform
- •Growing headcount toward 100,000 employees to run operations
- •Latin America coverage and ‘capillary’ reach into many regions
- 8:28 – 12:02
Engineering and product as one: fewer PMs, more technical ownership
Lenny digs into Mercado Libre’s uncommon org design: a small PM org and engineering leaders owning product outcomes. Sebastian explains why ownership isn’t determined by titles and how a single ‘full-context’ owner can accelerate execution and product quality.
- •Hard boundary between product and engineering is intentionally minimized
- •PM ratio is unusually low (less than ~1,000 PMs vs 18k engineers)
- •Product ownership often sits with engineering leads/tech leads
- •Rationale: keep decisions close to the problem, users, and technical constraints
- •Hiring and expectations favor technical depth and fluency in details
- 12:02 – 14:49
Why it works at scale: technical leadership, deep reviews, and user-first culture
Sebastian attributes the model’s success to top-down technical leadership and intense attention to product details—even at the C-level. They focus on user experience before revenue, while building complex systems across logistics, search, risk, moderation, and more.
- •Leadership discussions go deep (copy, UX flows, even pixel-level issues)
- •CEO’s first question: user experience and evidence users like it
- •User-first as a long-term revenue strategy
- •Highly technical problem space: routing, picking in DCs, robotics, moderation, risk
- •Culture reinforced by leaders’ hands-on engagement in key initiatives
- 14:49 – 19:13
AI in practice: internal platform ‘Verde,’ agents, and building features from microservices
The conversation turns to how AI changes execution: accelerating demos, development, and even feature assembly without writing new code. Sebastian describes Mercado Libre’s platform approach—abstracting data, authorization, and model tooling to enable teams broadly.
- •AI enables more people (including product-leaning folks) to build demos and prototypes
- •Coding copilots evolving into agentic workflows (Cursor/Windsurf, agents)
- •Platform mindset: internal dev platform for security/testing/compliance + AI platform Verde
- •Experimental approach: agents compose existing microservices to generate end-to-end features incl. UI
- •Future direction: more automated/personalized UI generation based on predicted user intent
- 19:13 – 24:03
Operating principles for 18k engineers: autonomy, risk-taking, and observing users
Sebastian outlines the core ways Mercado Libre operates at high velocity: minimizing fear of failure, granting independence, and keeping feedback loops tight. He also emphasizes observing users over relying only on what users say they want.
- •Encourage ‘safe’ failure: bold bets that don’t work aren’t punished
- •Low tolerance for quality failures that cause outages or instability
- •No strict OKR cascade; teams have freedom within high-level objectives
- •Balance autonomy with a holistic product vision so the full experience isn’t fragmented
- •Prefer observing user behavior (research sessions, real usage) vs only interviewing users
- 24:03 – 30:42
Keeping alignment without micromanaging: candid reviews + 30k production changes/day
Lenny probes how Mercado Libre maintains direction while teams act independently. Sebastian explains the role of design/product reviews and radical honesty, plus why perfect centralized oversight is impossible at their deployment rate.
- •Alignment mechanism: frequent design/product reviews across initiatives
- •Direct, candid leadership feedback on what works/doesn’t (while staying cordial)
- •Fast pivots when a direction proves wrong
- •Throughput reality: ~30,000 deploys/production changes daily (including automated)
- •Competitive pressure (e.g., Brazil e-commerce) reinforces speed and quality
- 30:42 – 34:15
Making ‘failure is okay’ real: culture is what leaders reward, promote, and praise
Sebastian distinguishes performative culture from real culture: it’s shaped by leadership actions, performance reviews, promotions, and public recognition. He clarifies the difference between acceptable experimentation failures and unacceptable reliability/quality failures.
- •Culture isn’t slogans; it’s visible in consequences and incentives
- •Acceptable failure: wrong market bet or hypothesis; not punished and may be rewarded
- •Unacceptable failure: outages and poor quality that harms reliability
- •Leaders must model behavior and set norms via praise, promotions, and accountability
- •Culture scales by hiring people who propagate the norms into their teams
- 34:15 – 38:28
Radical candor across cultures: fighting hierarchy and politeness defaults
The discussion explores directness and candid communication—especially important in regions where hierarchy and politeness can suppress dissent. Sebastian explains how Mercado Libre selected for and ‘exported’ a more direct style (influenced by Argentine roots) while keeping feedback non-personal.
- •Radical candor is particularly valuable in high-hierarchy cultural contexts
- •Latin America stereotypes: politeness, avoidance of saying ‘no,’ deference to bosses
- •Mercado Libre’s Argentine influence: more direct disagreement is normalized
- •Key skill: separate critique of work/product from critique of the person
- •Company as ‘high-performance sports team,’ not ‘family’—clear expectations on performance
- 38:28 – 41:02
Weekly updates: the non-meme version of ‘what did you do this week?’
Lenny brings up Sebastian’s weekly email habit, which became controversial elsewhere as a meme. Sebastian clarifies it’s primarily a self-management and alignment tool: summarizing progress, learnings, releases, and blockers to reduce meeting overhead and improve feedback loops.
- •Weekly update email shared upward (exec team/CEO) and with his org
- •Not a mandated reporting system; a personal practice for tracking progress and learnings
- •Includes what worked/didn’t, notable releases, and where help is needed
- •Creates async context so meetings focus on decisions rather than status
- •Connects to Lenny’s ‘State of Me’ concept for manager communication
- 41:02 – 44:25
Avoiding hype cycles: fundamentals, real-world constraints, and pragmatic adoption
Sebastian explains how he evaluates hype-driven technologies like crypto and AI: he doesn’t ignore them, but pressures them with fundamentals and scale realities. He notes crypto’s real utility in Latin America while rejecting exaggerated ‘everything will be blockchain’ narratives.
- •Engage early but skeptically: research deeply before betting big
- •Crypto: loves distributed consensus tech; questions throughput and practical limits
- •Mercado Libre uses crypto (including its own initiatives), especially valuable in certain economies
- •Red flag: absolutist claims that a tech will ‘take over everything’
- •Apply ‘real-world’ business scaling constraints to filter exaggerated narratives
- 44:25 – 49:51
Steve Jobs called: the battery-draining app and the rule made ‘for me’
The episode pivots to Sebastian’s personal stories, starting with Steve Jobs personally calling about an app Sebastian built to rapidly drain iPhone batteries. Jobs explains Apple won’t allow it—and adds a new App Store rule to enforce that decision.
- •Sebastian’s app turned on sensors to intentionally drain battery (originally ‘useful’ for battery cycling)
- •Early App Store era: Apple execs called developers to reduce PR blowups over rejections
- •Jobs tells Sebastian the app must be removed; Sebastian pushes back citing the rules
- •Jobs replies they added a new rule prohibiting excessive battery drain
- •Sebastian realizes later it really was Steve Jobs; he even emailed feedback afterward
- 49:51 – 55:29
Early app business wins: #1 app in 19 countries → consulting agency → taxi marketplace
Sebastian recounts building a simple app to avoid ‘5 minutes free calling’ overage charges—motivated by talking to his girlfriend (now wife). The app’s success launched a consulting business, which he later shifted toward scalable products, including a taxi-ordering app that prefigured ride-hailing marketplaces.
- •The ‘five-for-five’ calling plan inspired a timer/alert app to avoid charges
- •App became top-selling in Mexico and across many countries; paid app with minimal marginal costs
- •Demand led to a mobile app development company: hiring friends, learning from Stanford course
- •Shift from consulting to scalable products; desire to iterate deeply on products
- •Built taxi ordering with scrappy ops (calling taxi companies, intermediary call centers) until marketplace flywheel formed
- 55:29 – 1:04:01
Personal operating system: only water, little music, minimal news/social media, follow curiosity
Sebastian shares unusual personal habits and how they support focus: he avoids alcohol and stimulants, prefers silence while coding, and limits news/TV to avoid negativity and distraction. His guiding principle is following curiosity, which tends to align with where he can add the most value.
- •Drinks only water; avoids alcohol/coffee/tea/juice—prefers stable sleep and mental state
- •Programs in silence; limited self-initiated music listening (dad is an orchestra conductor)
- •Minimal TV/news; uses smaller screens and selective sources to reduce addiction/negativity
- •Belief: humans aren’t designed to absorb unlimited global bad news daily
- •No strict routine; relies on intuition and curiosity as a prioritization system
- 1:04:01 – 1:19:24
Raising independent kids: curiosity + agency, ‘spy training,’ and the tatami-room maker story
Sebastian connects his childhood to his leadership philosophy: his mother cultivated independence and agency through intense real-world challenges. In the lightning round, he shares books, favorite media, kids’ learning products, a life motto about the world being malleable, and a maker project where he cut a hole in his room to build a tatami space.
- •Traits for kids: curiosity plus agency (ability to act and solve problems)
- •Mother’s ‘spy training’: survival camping without gear, navigating home from city center, solo trips
- •Lightning round picks: High Output Management, The Odyssey, The Dream Machine; movies like Everything Everywhere All at Once
- •Parenting/learning products: Mentava for reading, Beast Academy for math
- •Life motto: the world is malleable; you can reshape systems—plus ‘tatami project’ DIY room rebuild story
