Code Story episode
S6 E17: The Real-Time Smoke Alarm: Engineering Automated Evidence Collection and GRC Architecture with Girish Redekar of Sprinto
May 10, 2022 · Season 6 · Episode 17 · 22 min
10X the speed of your compliance process
If you would have told Girish Redekar while he was in college that he would eventually be writing software, he would have been shocked. His studies focused on electrical engineering, and post school, he was a hard core analyst. After some time, he and his friend decided to do the whole start up thing - they tried a bunch of ideas, and taught themselves to code. He remembers in his previous company he was the top contributor to the codebase until it was finally sold. Outside of tech, he is a movie buff - but bent towards the obscure movies that most haven't heard of... so obscure that he couldn't remember the name of the last one he saw.
In his prior startup, he went through the painstaking process of becoming SOC2 certified. This experience stuck with him - so much so, that when he and his co-founder ventured out to start something new, they decided to create something to make this easier.
This is the creation story of Sprinto.
Sponsors
ImmediateOrbitPostmarkStytchVerb DataWebapp.ioLinks
Website: https://sprinto.com/LinkedIn: https://www.linkedin.com/in/girishredekar
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.