Lessons from a lifelong software engineer scaling food delivery globally

Executive overview

Scaling a global food delivery platform means coordinating hundreds of interdependent steps under tight time constraints — with no tolerance for error. At massive scale, even a 0.01% failure rate affects thousands of people.

The biggest traps are skipping problem definition, under-communicating context to growing teams, and letting engineers lose sight of the customer experience.

Leaders set culture by behavior, not instruction — your team will always do what you do, not what you say.

On building and leading engineering teams

• Trust is the hardest team problem to solve; one mistake resets it to zero
• Tried management, hated it, returned to principal engineering — then tried again and never looked back
• New team members lack the history behind past decisions; you must constantly repeat both the history and the direction
• Every leader thinks they over-communicate but is actually under-communicating
• At scale, engineers need reminding of how big the system has become — 0.01% of millions is a lot of affected users

Handling technical debt

• Frame debt around a concrete future cost: when and under what conditions will it hurt the business?
• Quantifying the timing removes vagueness from stakeholder conversations
• The question isn't "is it important?" but "when does it become a problem?"

Customer focus and problem definition

• Outstanding customer experience is a prerequisite for a long-lasting profitable business
• Engineers under pressure tend to jump to solutions before clearly defining the problem — that's dangerous
• Always return to: what problem are we actually solving for the customer?
• A failed feature that teaches you what customers hate is still a valuable output

Operating in chaos (COVID and hyper-growth)

• Food delivery shifted overnight from luxury to essential service during COVID — reliability requirements changed completely
• The platform was not built for the demand spike; the first priority was keeping it running, even rough around the edges
• Government mandates (e.g., cash-only to electronic payments overnight) required immediate response with no lead time
• Being comfortable in chaos is a core CTO skill