https://ucarecdn.com/cd3e9b09-ea89-4e07-8a3f-5bd8345021ae/ cover

Season 12

19 cards
Season 12 of the Code Story podcast.
Main Content Image
codestory.co
E1: Dylan Ratcliffe, Overmind

Dylan was deploying Puppet at a financial services company, and was pushing to get a win. When a late Friday afternoon deployment went haywire, he decided to leave his company and set out to build something to automatically discover dependencies on a network, to prevent deployment outages.

Main Content Image
codestory.co
Bonus: Sharad Kumar & Harshit Omar, FluidCloud

In their previous startups, Sharad was leading sales and ops and Harshit was leading on the product side. When the company got acquired, it took them 8-9 months to integrate to a different cloud provider. They realized the model was broken, requiring expensive consulting services, and not convenient at all - and they wanted to figure out a better way.

Main Content Image
codestory.co
E3: Arsham Ghahramani, Ribbon

In the past, Arsham was the head of machine learning at a prior company. His now co-founder and he worked closely together, and they were both pressured to hire good people quickly. They started to notice some patterns in how they were hiring... including the regular submission of AI generated resumes.

Main Content Image
codestory.co
E4: Arto Minasyan, Krisp.ai

Arto and his colleague got breakfast together, and started talking through an idea around clean audio for conferencing and beyond. They built a prototype, and then COVID hit - which made their tool very popular.

Main Content Image
codestory.co
E7: James Davies, Kinetic Data

James was working for the state department as a consultant, and was a customer of his current venture. He was chosen to implement the solution, which turned out to be a successful project. Post that project, he was approached by the company to lead projects on the east coast and eventually landed in the CEO role.

Main Content Image
codestory.co
Bonus: Daniel Shnaider, Warmy.io

As I mentioned, Daniel started and ran many businesses in the past. One of them was centered around physical products, and led him to send emails to the mom and pop' shops they wanted to work with. To fight the spam trap, he and his team built a solution to solve the problem for themselves... and then took the next step.

Main Content Image
codestory.co
E6: Michael Fester, 14.ai

Michael and his team noticed that despite the continual improvement of models, the process of maintaining systems was tedious. Not only did this impact support operations, and building software for this area of a business, but negatively impacted the customers themselves. He and his wife wanted to build the new standard for how support operations are run.

Main Content Image
codestory.co
Bonus: Prashanth Tondapu, Innostax

Prashanth has worked for companies in the past focused on products - companies like McAffee and the Advisor Board Company. Outside of that, he started to build product after product, but no one wanted to buy his product. Eventually, he was tasked to advise a company in product delivery, which then changed everything.

Main Content Image
codestory.co
The Gene Simmons of Data Protection - AI Inference-time Guardrails

Today, we releasing our final episode of the series entitled The Gene Simmons of Data Protection - the KISS Method, brought to you by none other than Protegrity.

Main Content Image
codestory.co
E5: Marc Gyöngyösi, OneTrack

Marc Gyöngyösi has had a lifelong passion for building and technology, shaped early on by time spent crafting wooden projects and tinkering with

Main Content Image
codestory.co
Bonus: Johnny Halife, Southworks

Twenty one years ago, Johnny started working for Microsoft Engineering behind the scenes, helping them shape products. Eventually, he and his team started asking the question - if we are helping Microsoft, why don't we help other companies?

Main Content Image
codestory.co
Impact: How to Inspire, Align and Amplify Innovative Teams with Keith Lucas

In our chat, Keith is going to walk us through key concepts in the book, surrounding centering your team around the vision and mission of what you are driving towards, from recruiting to execution to "coaching out".

Main Content Image
codestory.co
Bonus: Marlena Sarunac, The Company Advice

Marlena and her now co-founder met at a prior company, and worked well together promoting that brand. The built a playbook, and always dreamed of starting their own thing to push those playbooks. The stars aligned later in life, and they decided to give it a go.

Main Content Image
codestory.co
Bonus: Dmytro Ovcharenko, Alcor

Dmytro very much enjoyed working at his prior company. But he noticed the large gap between what his business was charging, and what the engineers themselves received. He thought he could close this gap, to provide a better wage for the workers while saving businesses money.

Main Content Image
codestory.co
Bonus: Arjun & Tito, Teambridge

While Tito and Arjun were at Uber, they quickly understood that the reason people drove for the company was not the pay, but the flexibility and self service aspect of the platform. With this, they started to wonder... why can't we give this to everyone else?

Main Content Image
codestory.co
Bonus: David Sztykman, Hydrolix

In his prior role, David was consistently alerted about poor performance on the video streaming. He started to dig into the data streaming portion of, to be alerted on shifts in the stream itself. After a few other opportunities, he was approached to build real time CDN observability, for distributed infrastructure.

Main Content Image
codestory.co
E2: Pukar Hamal, SecurityPal AI

In his past venture, Pukar was on the one yard line for making a deal on his company. Before it could close, his team was hit with a security due diligence questionnaire that halted the process. Having that experience drove him to build something to speed up the execution and experience of customer assurance.

Main Content Image
codestory.co
Bonus: Harman Narula, Canary Technologies

Harman spent a lot of his early career in hospitality. His now co-founder worked in this space as well, but primarily on the technology size. So all the conversations he and his friend were having were referencing this eco-system. Eventually, they landed on a thesis that the "hotel tech stack" or operating system - should be customer facing.

Main Content Image
codestory.co
Code Story – Bonus: Niko Papademetriou, Qu

Niko has observed the restaurant business change, moving towards many different ordering methods - mobile, web, in person, etc. At the end of whatever method, the order needed to land inside the black box of the POS system. He wanted to create the plumbing, better yet the ultimate system to connect it all.