Code Story episode
S9 Bonus: Bypassing Paper-Based Safety Forms: Implementing Real-Time Risk Profiling and Algorithmic Employee Safety Guardrails with Ruslan Zaripov, Co-Owner of KRIT & Creator of RiskHunter
Feb 1, 2024 · Season 9 · 21 min
Gamifying the risk identification process
Ruslan Zaripov has been interested in computers since the early days. He started his career as a database developer, and eventually became a project manager. Essentially, he has been serving in information technology his whole life. Outside of tech, he is married with 2 kids and a dog. In the winter, he enjoys cross country skiing, and tries to keep a work life balance.
Eight years ago, Ruslan bought into the company KRIT, becoming a co-owner. KRIT builds software products for large enterprises, in the heavy energy and metallurgy plants. He and his team wanted to create a product that brought safety to the forefront each employees mind.
This is the creation story of RiskHunter, built by the team at KRIT.
Sponsors
CacheFlyClearQueryKiteworksLinks
https://krit.global/solutions/riskhunter/https://www.linkedin.com/in/ruslanzaripov-7619/
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
S9 E10: Breaking the AI Code Explosion and Democratizing Codebase Intent with Dennis Pilarinos, Founder & CEO of Unblocked
Feb 6, 2024
S9 Bonus: The Developer Retraining Blueprint: Bypassing Rigid CS Degrees and Overthrowing Static Tech Education with Erik Gross, Co-Founder of The Tech Academy
Jan 31, 2024
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.
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.
Scaling an engineering team from 5 to 50
How to scale a startup engineering team from 5 to 50 people: when to add managers, how communication breaks, what process to add at each size, and what to leave alone.