Code Story episode
S7 E26: The 40 Million SKU Bottleneck: Engineering an Algorithmic Ad Bidding Engine with Liam Patterson of Bidnamic
Mar 7, 2023 · Season 7 · Episode 26 · 29 min
Manage your Google Shopping campaigns the smart way
Liam Patterson has been an entrepreneur since the early days of his life. He was the kid that was selling sweets at school, undercutting the local store. He journeyed into e-commerce as he got older, continuing his entrepreneurial journey. Outside of tech, he is a runner and is into fencing. Recently, he completed his first marathon, after training for about a year. In regards to fencing, he started when he was a kid, and did it all the way through college - which is actually where he met his now co-founder.
Liam's prior business was a print on-demand company, which allowed locally printing and shipping. As they scaled that business, they came to be hooked on Google Shopping and started using off the shelf tech to manage the campaigns. They found them to be lacking, and eventually built their own - and it became their competitive advantage.
This is the creation story of Bidnamic.
Sponsors
AirbyteDopplerHost.ioIPInfomablSupportZebraLinks
Website: https://www.bidnamic.com/en-us/LinkedIn: https://www.linkedin.com/in/liam-patterson/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Technical due diligence checklist for startups
A technical due diligence checklist for founders and investors: what reviewers examine across architecture, security, team and process, and how to prepare before a raise.
Fractional CTO vs full-time CTO: which does your startup need?
A practical comparison of a fractional CTO and a full-time CTO: cost, scope, when each makes sense, and the questions to ask before you hire either one.
CTO vs VP of Engineering: how the two roles actually differ
CTO vs VP of Engineering explained: who owns architecture, who owns delivery, when to split the roles, and how to avoid the overlap that breaks engineering teams.