Episode
Why the Softest Fruit is the Hardest Engineering Problem, And Robotics’ Potential | Sid Shaikh
- Podcast
- WHY DESIGN?
- Published
- Apr 8, 2026
- Duration seconds
- 4102
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/why-design-7007437/episodes/why-the-softest-fruit-is-the-hardest-engineering-problem-and-robotics-potential-sid-shaikh/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/why-design-7007437/why-the-softest-fruit-is-the-hardest-engineering-problem-and-robotics-potential-sid-shaikh.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
What does it take to solve a problem nobody else is willing to attempt, in a country 10,000 miles away, with a 15-person team and an active fundraise running in the background? In this episode of Why Design, Sid Shaikh shares the belief that sits at the heart of his work: that the hardest engineering problems are the right ones to go after, and that the difference between a startup that scales and one that stalls is almost always about whether the team is solving the actual bottleneck or just the comfortable one. Rather than staying in large corporations where the problems were well-defined and the teams were fully resourced, Sid has spent his career choosing the inflection point: the moment a company has something that works and needs to figure out how to make it real. That decision led him to Ocado when it was still thought of as a grocer, through a company administration at Hypertunnel, and eventually to Fieldwork Robotics, where he is now CTO building a raspberry-picking robot designed to operate in polytunnels across three continents. This conversation is about what honest engineering leadership looks like when the stakes are high and the answers aren't in any textbook. Join the Why Design community -> teamkodu.com/whydesign What You'll Learn Why a reachability analysis of berry height, depth, and obstacles explained six months of performance data that improvements to the vision and motion stack simply couldn't shift How Fieldwork moved from project-based trials to Harvest as a Service, charging per kilo picked rather than per machine deployed Why Ocado's engineering team broke down at around 50 people, and what the right structure looks like when you need doers more than managers What Sid learned from Hypertunnel's administration about solving your own part of…