Code Story: Insights from Startup Tech Leaders

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.QuestionsBefore 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?SponsorsUnblockedBraingrid.TECH DomainsMezmoLinkshttps://catchersjob.com/https://www.linkedin.com/in/vadim-dedov-060b8935a/Support this podcast at — https://redcircle.com/codestory/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

S12 E9: Mitesh Agrawal, Positron

Mitesh Agrawal has a background in Mechanical Engineering. He was one of the co-founders of Lambda, a company in the supercomputing space, where he spent 8.5 years working on everything under the sun. He's very grateful to be in an industry that is booming, but also aligns with his personal interests. Outside of tech, he is married to an ultra supportive wife, and is enjoying being a new father. He enjoys playing tennis, when he can find time to get to the court, and enjoys a good sci-fi book. He mentioned the Foundation series was one of his favorites, but admits it changes depending on the season.In 2023, the officers at Mitesh's current venture noticed all of the advancements of AI - in particular, model sizes getting larger. What they realized was that when it comes to inference, memory capacity quickly became a problem... and with this, he and the team got excited about building a new architecture to make it better.This is the creation story of Positron.SponsorsUnblockedTECH DomainsMezmoBraingrid.aiLinkshttps://www.positron.ai/https://www.linkedin.com/in/mitesh7/Support this podcast at — https://redcircle.com/codestory/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

S12 Bonus: Ashwin Agrawal, MobiusEngine

Ashwin Agrawal came to the US when he was 17, to Rochester for school. He now lives in the Bay Area, and admits he misses his friends on the east coast, as they all stayed back in that area - but he does NOT miss the winters. He has been building his current venture for 3-4 years, and prior to that, he was as at Google for a decade, apart of Google Cloud's huge growth trajectory. Outside of tech, he has a family with 2 middle school sons, with whom he likes to spend a lot of time with, hiking or eating good sushi.Ashwin was laid off from a few jobs in the past. After experiencing this, he vowed to build a solution that would help people going through this sort of experience. After the last layoff, he formed his company at 4:30 am in the morning, to help anyone in point A wanting to go to point B.This is the creation story of MobiusEngine.ai.SponsorsUnblockedTECH DomainsMezmoBraingrid.aiLinkshttps://mobiusengine.ai/https://www.linkedin.com/in/agrawalashwin/Support this podcast at — https://redcircle.com/codestory/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

Developer Chats - Oleksandr Piekhota

Today, we are continuing our series, entitled Developer Chats - hearing from the large scale system builders themselves.In this episode, we are talking with Oleksandr Piekhota, Principal Software Engineer at Teaching Strategies. Oleksandr helps to show us at what point of scale platform approaches are required, when to run experiments and when to stop, and perhaps more importantly - engineering ownership beyond the code.QuestionsYou’ve moved from hands-on engineering into principal and technical leadership roles, working on architecture and platforms.At what point did you realize your work was no longer about individual features, but about the system as a wholeAcross several projects, growth didn’t break functionality — it exposed architectural limits.Can you recall a moment when it became clear that shipping more features wouldn’t solve the problem, and a platform approach was required?You’ve designed and supported APIs end-to-end, from architecture to real customers. How do you distinguish between an API that simply works and one that can truly support business scale?Internal systems like invoicing and HR workflows began as automation, but evolved into real products.What tells you that an internal tool is worth developing seriously rather than treating as a temporary workaround?In R&D, you explored CI/CD automation, server-less, and infrastructure experiments — not all reached production. How do you decide when an experiment should continue, and when it’s no longer worth the engineering cost?You’ve hired teams, set standards, and shaped long-term technical direction. At what point does an engineer stop being a contributor and start owning business-level outcomes?You contributed to open-source tools that later became part of your company’s infrastructure. Why do you see open source contributions as part of serious engineering work rather than a side activity?Looking across your projects, how do you now recognize a truly mature engineering system? Is it code quality, process, or how teams respond when things go wrong?If we look five to seven years into the future, which architectural assumptions we treat as “standard” today are most likely to turn out to be naive or limiting?SponsorsIncogniLinkshttps://www.linkedin.com/in/oleksandr-piekhota-b675ba53/https://teachingstrategies.com/Support this podcast at — https://redcircle.com/codestory/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

S12 E8: Satya Mishra, Waylit

Satya Mishra was born and raised in India, in one of the smaller tech hubs on the eastern coast. He came to the states 25 years ago on an H1B visa, working in semiconductors. In 2015, he decided he wanted to do something entrepreneurial and set out to do so. Outside of tech, he is married with 3 kids, which takes up most of his time. When he lived in CO, he did lots of skiing and hiking, including snowshoe hiking. Once he went to California, he switched to beaches. Finally, when he moved to St. Louis, he took up improv, enjoying connecting with people and thinking on your feet.Satya and his co-founder, Raj, both when through the immigration process in all of its forms. They realized that no one group owns the process, as it's highly specialized, and usually fell onto the employee to keep track of. One day, they set out to solve this problem, to assist business teams to take ownership of the entire process.This is the creation story of WayLit.SponsorsUnblockedTECH DomainsMezmoBraingrid.aiLinkshttps://www.waylit.com/https://www.linkedin.com/in/satyamishra/Support this podcast at — https://redcircle.com/codestory/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy