Code Story episode
Founder Chats - Vadim Dedov
Apr 3, 2026 · Season 12 · 11 min
Founder Chats - Vadim Dedov
Today, we are dropping another episode in our "chats" series, specifically on the Founder side, - hearing from those scaling the companies themselves.
In this episode, we are talking with Vadim Dedov, CEO at Catchers. Vadim is going to walk us through what problem he wanted to solve with Catchers, and how his product development journey took him through architectural decisions, product optimization, team building and more.
Questions
Before we talk about Catchers, I’d love to understand you a bit better.What experiences or responsibilities earlier in your life shaped how you think about work, systems, and accountability today?What problem were you dealing with before Catchers existed? Not as a product idea yet, but as a real operational pain you kept running into.At what point did you realise this couldn’t be solved with people, spreadsheets, or manual coordination anymore and that technology was the only way forward?How did Catchers actually start taking shape as a product? What was the very first version you built, and what did “good enough” mean in a business where mistakes affect people’s income and compliance?How long did it take to get to something usable, and what constraints defined your MVP?Looking back, what were the most important trade-offs you made early on?Things you consciously postponed or simplified, knowing they might come back later.Let’s zoom in on the product itself. What is the core product insight behind Catchers — the thing you believe differentiates it from a typical HR or staffing platform?How did your thinking about architecture evolve as scale increased? Was there a moment when you had to stop moving fast and redesign parts of the system properly?How did you approach building your core team around such a complex, operations-heavy product? What qualities mattered most in the people you trusted with this system?Can you share a decision that didn’t go as planned and how you and your team dealt with the consequences?When you step back and look at what you’ve built today, what are you most proud of not in terms of features, but in terms of reliability, impact, or how the system holds under pressure?As you look ahead, how do automation and AI change the way you think about workforce platforms — and what advice would you give to someone building infrastructure-heavy products today?Sponsors
Unblocked (https://getunblocked.com/codestory)TECH Domains (https://get.tech/codestory)Mezmo (https://mezmo.com/codestory)Braingrid.ai (https://braingrid.link/code-story)Links
https://catchersjob.com/https://www.linkedin.com/in/vadim-dedov-060b8935a/
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
S12 E13: The Death of Legacy VDI: Ditching Costly Virtual Desktops to Secure Enterprise BYOD Laptops Locally with David Matalon, Founder & CEO of Venn
Apr 7, 2026
S12 Bonus: Intercepting Risky Prompts and Deploying Local LLMs to Neutralize Data Leakage via Pragatix with Yoav Crombie, Co-Founder & CEO of AGAT Software
Apr 2, 2026
Topics
Explore related conversations
How to choose a tech stack for a startup
A decision framework for choosing a startup tech stack: what actually matters, which choices are reversible, and how to avoid the rewrite that eats your Series A.
Startup engineering team structure that actually ships
How to structure a startup engineering team: the models that work at 5, 15 and 40 engineers, how to split teams, and the org mistakes that quietly slow delivery.
Build vs buy: a decision framework for technical leaders
When to build software in-house and when to buy it: a build vs buy framework covering total cost of ownership, differentiation, switching costs and vendor risk.