LARRY BRONX
80+ Visitors
Hi, I'm Kirthi!
Hi, I'm Kirthi!
Software Engineering
HTML5/CSS3 Mastery
Product Design
Branding
Collaborative Team Player
About Me
Hi, I'm Kirthi. I'm a computer engineer who spent five years at IBM working hands-on with Watson AI and SAP, before turning that experience toward a question I couldn't stop thinking about: as AI systems get more autonomous, how do we make sure they stay trustworthy?
Hi, I'm Kirthi. I'm a computer engineer who spent five years at IBM working hands-on with Watson AI and SAP, before turning that experience toward a question I couldn't stop thinking about: as AI systems get more autonomous, how do we make sure they stay trustworthy?
Hi, I'm Kirthi. I'm a computer engineer who spent five years at IBM working hands-on with Watson AI and SAP, before turning that experience toward a question I couldn't stop thinking about: as AI systems get more autonomous, how do we make sure they stay trustworthy?
My path started with a computer engineering degree from The George Washington University, where I built a foundation in the systems-level thinking I still rely on today. Five years at IBM sharpened that further — working closely with Watson AI and SAP gave me a front-row seat to both the power and the fragility of large-scale AI systems, and planted the question that now drives most of my work: capability isn’t the same as trustworthiness, so how do you build the difference in from the start?
My path started with a computer engineering degree from The George Washington University, where I built a foundation in the systems-level thinking I still rely on today. Five years at IBM sharpened that further — working closely with Watson AI and SAP gave me a front-row seat to both the power and the fragility of large-scale AI systems, and planted the question that now drives most of my work: capability isn’t the same as trustworthiness, so how do you build the difference in from the start?
My path started with a computer engineering degree from The George Washington University, where I built a foundation in the systems-level thinking I still rely on today. Five years at IBM sharpened that further — working closely with Watson AI and SAP gave me a front-row seat to both the power and the fragility of large-scale AI systems, and planted the question that now drives most of my work: capability isn’t the same as trustworthiness, so how do you build the difference in from the start?
My focus spans a few directions that share one instinct: build the guardrails into the system, not around it. That’s meant building governance layers that control what AI agents can write to production systems, architecting security systems that don’t rely on software trusting itself, and exploring what speech can reveal beyond the words themselves. I care less about chasing every new tool and more about picking the right foundation for problems where “it mostly works” isn’t good enough.
My focus spans a few directions that share one instinct: build the guardrails into the system, not around it. That’s meant building governance layers that control what AI agents can write to production systems, architecting security systems that don’t rely on software trusting itself, and exploring what speech can reveal beyond the words themselves. I care less about chasing every new tool and more about picking the right foundation for problems where “it mostly works” isn’t good enough.
My focus spans a few directions that share one instinct: build the guardrails into the system, not around it. That’s meant building governance layers that control what AI agents can write to production systems, architecting security systems that don’t rely on software trusting itself, and exploring what speech can reveal beyond the words themselves. I care less about chasing every new tool and more about picking the right foundation for problems where “it mostly works” isn’t good enough.
