Why the Softest Fruit is the Hardest Engineering Problem, And Robotics’ Potential | Sid Shaikh

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 shiftHow Fieldwork moved from project-based trials to Harvest as a Service, charging per kilo picked rather than per machine deployedWhy Ocado's engineering team broke down at around 50 people, and what the right structure looks like when you need doers more than managersWhat Sid learned from Hypertunnel's administration about solving your own part of the stack brilliantly while the harder problem next door stands stillHow AI is being layered across the pick stack, from ripeness classification to berry-level yield forecasting that tells a farm operator exactly when to come backWhat Sid actually looks for when hiring engineers: not a list of CAD packages or coding languages, but the attitude to work from a blank sheet and the drive to pivot without freezingMemorable Quotes "I've never heard anybody say you over-communicate.""We went to suppliers and they laughed at us. And then the outcomes are there.""The endless prototype is the sign a robotics startup is heading for trouble.""If the horse next to you in the horse race isn't catching up, you're not going to be successful.""People in automation mix very well."Resources and Links 🎧 Listen on Spotify, Apple Podcasts, YouTube and Amazon -> whydesign.club👥 Join the Why Design community -> teamkodu.com/whydesign 📸 Follow @whydesignxkodu on Instagram🎥 Watch full episodes -> YouTube.com/@whydesignpod 🔗 Follow Chris Whyte -> linkedin.com/in/mrchriswhyte 🔗 Explore Fieldwork Robotics -> fieldworkrobotics.com 🔗 Connect with Sid Shaikh -> [https://www.linkedin.com/in/sid-shaikh]About the Episode Why Design is powered by Kodu, a specialist recruitment partner for the hardware and physical product development industry.Through honest conversations with designers, engineers and creative leaders, we explore not just what they build but why they build it; the beliefs, decisions and responsibility behind meaningful work.About Kodu Why Design is produced by Kodu, a recruitment partner for ambitious hardware brands, design consultancies and product-led start-ups.We help founders and leadership teams hire exceptional talent across industrial design, mechanical engineering and product leadership - bringing structure and clarity to one of the hardest parts of scaling.🔗 Learn more -> teamkodu.com