Skip to content
The Tech Trek cover art

Elevano

The Tech Trek

A Technology podcast

Good podcast? Give it some love!

About the show

The Tech Trek is a podcast about how founders, operators, and technology leaders build and scale technology companies. Each episode explores the decisions behind building products, teams, and technical organizations, with conversations spanning engineering, AI, data, product, hiring, leadership, and growth. Guests share what they are building, what they are learning, and how they are navigating the challenges that come with turning technology into a successful company.

Newest episodes

Building Custom AI Models and Rethinking Engineering With Agents

31 min

Catching phishing attacks is only half the challenge. An AI security model also has to avoid blocking legitimate emails. Ryan Luo, Founder and CTO of Aegis AI, joins The Tech Trek to explain why his team moved beyond commercial AI model APIs and began building its own models for email security. Existing models were surprisingly capable of identifying attacks, but distinguishing suspicious activity from actual threats required more precision. Ryan explains the tradeoffs between detection accuracy, cost, and control, including why the last few percentage points of model performance can be the hardest to improve. The conversation also explores how AI coding agents are changing engineering work. Ryan shares why his engineers spend time understanding real security threats, how junior engineers can develop better judgment, and why defining clear outcomes matters more as agents take on additional implementation work. Key Takeaways Custom models can offer greater control over accuracy and compute costs. False positives can undermine an otherwise effective security product. Engineers need domain expertise to evaluate and improve AI output. Effective agentic development starts with clear goals and constraints. Episode Highlights 01:52 Why Aegis AI moved beyond commercial model APIs 05:06 The difficult tradeoff between precision and recall 07:08 Cost and compute advantages of custom AI models 14:30 Why detection engineers must understand real attacks 16:27 What makes junior engineers valuable in the AI era 28:21 How AI agents are changing engineering leadership One Line That Stuck "They can't turn off the adversaries, but they can turn off you." Follow The Tech Trek for more conversations about engineering, AI, and building technology companies.

AI in Healthcare: Faster Models, Human Judgment, and Trust

23 min

AI is helping healthcare teams move faster. But faster models do not always mean better patient care. Hetal Patel, VP of Healthcare Economics and Data Science at Harmony Care, joins The Tech Trek to discuss where AI is delivering value in healthcare and where human expertise remains essential. Hetal shares how her team uses AI for clinical documentation, contract analysis, coding, data migration, and predictive modeling. In one example, AI helped shorten the development time for a patient readmissions model by more than 50%. But speed creates new challenges. Clinicians need time to adopt new tools, models need careful testing, and biased data can lead to biased decisions. The conversation also explores healthcare data sharing, patient privacy, and the need for responsible AI governance. Key Takeaways AI is reducing administrative work and helping healthcare analytics teams handle more projects. Faster model development creates new expectations for clinicians adopting those models. Human expertise and bias testing remain essential when models influence patient care. Better access to clinical data could improve predictions, but raises privacy concerns. Episode Highlights 01:49 How AI scribes, agents, and coding assistants are being used 04:02 Measuring ROI beyond simple time savings 05:52 Cutting predictive model development time by more than 50% 08:03 Why faster deployment is not always the right choice 10:34 How bias enters models and why testing matters 16:51 The promise and privacy challenges of connected healthcare data One Line That Stuck "Data is dirty. Data is biased. If you build on that, you're gonna have a biased model." Follow The Tech Trek for more conversations about AI, data, and technical leadership.

What Healthcare Teams Really Want From AI

24 min

Some healthcare professionals want to brainstorm about AI. Others are reluctant to use it. And many simply want technology that helps them do their jobs. Dany Jradi, Head of Product at Abby Care, joins The Tech Trek to discuss what healthcare stakeholders actually care about when AI enters their workflows. For engineers and product teams, the technology itself can be exciting. For clinicians and operators, the outcome often matters more than how the system works. Dany explains why AI adoption remains uneven, even for tools like AI scribes that have been available for years. He also discusses why reviewing administrative documents requires a different level of scrutiny than providing clinical guidance. The conversation turns to family caregiving and the potential of daily care notes. Could AI help clinical teams identify changes in a patient's condition before those changes lead to a serious event? Key Takeaways Healthcare stakeholders often prioritize their work over how an AI system operates. AI adoption varies widely, even among technology savvy clinicians. Administrative automation and clinical guidance require different standards. Daily caregiver notes could reveal patterns that individual events miss. Episode Highlights 02:02 Why healthcare professionals respond differently to AI 04:20 What builders care about versus what stakeholders need 08:09 AI scribes and the uneven pace of adoption 11:44 Why clinical and administrative AI have different standards 15:42 Finding useful signals in daily caregiver notes 20:09 How AI could identify trends between major health events Follow The Tech Trek for more conversations about AI, product development, and building technology that solves real problems.

Similar podcasts

All episodes

The newest 50 of 724 episodes

Building Custom AI Models and Rethinking Engineering With Agents

31 min

Catching phishing attacks is only half the challenge. An AI security model also has to avoid blocking legitimate emails. Ryan Luo, Founder and CTO of Aegis AI, joins The Tech Trek to explain why his team moved beyond commercial AI model APIs and began building its own models for email security. Existing models were surprisingly capable of identifying attacks, but distinguishing suspicious activity from actual threats required more precision. Ryan explains the tradeoffs between detection accuracy, cost, and control, including why the last few percentage points of model performance can be the hardest to improve. The conversation also explores how AI coding agents are changing engineering work. Ryan shares why his engineers spend time understanding real security threats, how junior engineers can develop better judgment, and why defining clear outcomes matters more as agents take on additional implementation work. Key Takeaways Custom models can offer greater control over accuracy and compute costs. False positives can undermine an otherwise effective security product. Engineers need domain expertise to evaluate and improve AI output. Effective agentic development starts with clear goals and constraints. Episode Highlights 01:52 Why Aegis AI moved beyond commercial model APIs 05:06 The difficult tradeoff between precision and recall 07:08 Cost and compute advantages of custom AI models 14:30 Why detection engineers must understand real attacks 16:27 What makes junior engineers valuable in the AI era 28:21 How AI agents are changing engineering leadership One Line That Stuck "They can't turn off the adversaries, but they can turn off you." Follow The Tech Trek for more conversations about engineering, AI, and building technology companies.

AI in Healthcare: Faster Models, Human Judgment, and Trust

23 min

AI is helping healthcare teams move faster. But faster models do not always mean better patient care. Hetal Patel, VP of Healthcare Economics and Data Science at Harmony Care, joins The Tech Trek to discuss where AI is delivering value in healthcare and where human expertise remains essential. Hetal shares how her team uses AI for clinical documentation, contract analysis, coding, data migration, and predictive modeling. In one example, AI helped shorten the development time for a patient readmissions model by more than 50%. But speed creates new challenges. Clinicians need time to adopt new tools, models need careful testing, and biased data can lead to biased decisions. The conversation also explores healthcare data sharing, patient privacy, and the need for responsible AI governance. Key Takeaways AI is reducing administrative work and helping healthcare analytics teams handle more projects. Faster model development creates new expectations for clinicians adopting those models. Human expertise and bias testing remain essential when models influence patient care. Better access to clinical data could improve predictions, but raises privacy concerns. Episode Highlights 01:49 How AI scribes, agents, and coding assistants are being used 04:02 Measuring ROI beyond simple time savings 05:52 Cutting predictive model development time by more than 50% 08:03 Why faster deployment is not always the right choice 10:34 How bias enters models and why testing matters 16:51 The promise and privacy challenges of connected healthcare data One Line That Stuck "Data is dirty. Data is biased. If you build on that, you're gonna have a biased model." Follow The Tech Trek for more conversations about AI, data, and technical leadership.

What Healthcare Teams Really Want From AI

24 min

Some healthcare professionals want to brainstorm about AI. Others are reluctant to use it. And many simply want technology that helps them do their jobs. Dany Jradi, Head of Product at Abby Care, joins The Tech Trek to discuss what healthcare stakeholders actually care about when AI enters their workflows. For engineers and product teams, the technology itself can be exciting. For clinicians and operators, the outcome often matters more than how the system works. Dany explains why AI adoption remains uneven, even for tools like AI scribes that have been available for years. He also discusses why reviewing administrative documents requires a different level of scrutiny than providing clinical guidance. The conversation turns to family caregiving and the potential of daily care notes. Could AI help clinical teams identify changes in a patient's condition before those changes lead to a serious event? Key Takeaways Healthcare stakeholders often prioritize their work over how an AI system operates. AI adoption varies widely, even among technology savvy clinicians. Administrative automation and clinical guidance require different standards. Daily caregiver notes could reveal patterns that individual events miss. Episode Highlights 02:02 Why healthcare professionals respond differently to AI 04:20 What builders care about versus what stakeholders need 08:09 AI scribes and the uneven pace of adoption 11:44 Why clinical and administrative AI have different standards 15:42 Finding useful signals in daily caregiver notes 20:09 How AI could identify trends between major health events Follow The Tech Trek for more conversations about AI, product development, and building technology that solves real problems.

Rethinking Engineering Sprints in the Age of AI Agents

29 min

What happens when AI makes writing code faster, but your engineering process still operates on two week sprints? Junaid Warwani, VP of Engineering at Brellium, joins The Tech Trek to explain how he restructured engineering at his previous company after adopting AI development tools. His team moved away from traditional sprints, gave individual engineers ownership of priorities, and shifted toward weekly planning with faster feedback. But moving faster introduced new problems. Engineers had to manage more context, product managers needed different responsibilities, and the rest of the organization had to adapt. Junaid shares what worked, where the model fell short, and what he would change as he brings those lessons into his new role. Key Takeaways Why traditional sprint planning started losing its value as AI accelerated development. How one engineer can own delivery while product managers focus on what comes next. Why feedback loops can become a bigger bottleneck than writing code. How hiring priorities are shifting toward communication, customer understanding, and critical thinking. Episode Highlights 02:48 Why Junaid returned from parental leave ready to rethink engineering. 06:22 Rethinking the relationship between product managers and engineers. 10:45 Replacing traditional sprints with individual ownership and weekly priorities. 14:20 Why faster feedback matters more than faster code. 19:23 What Junaid now looks for when hiring engineers. 27:31 Why engineering leaders need to become better at change management. A Moment Worth Pulling Out "What we're doing does not make sense anymore." Junaid describes the realization that led him to rethink his team's development process. If you're reconsidering how your engineering team works with AI, this conversation offers practical lessons from a leader who has already experimented with a different model. Follow The Tech Trek for more conversations about technology, engineering, AI, and leadership.

What AI Native Really Means for Engineering Teams

25 min

What actually makes a company AI native? Is it using AI across every department, building more agents, or changing how the organization works? Eswar Vandenapu, Cofounder and CTO of NovaWorks AI, shares what his team is learning as it moves from basic AI adoption toward a shared context model that shapes how decisions are made. The discussion explores why giving everyone access to AI tools is only the beginning. Eswar explains how NovaWorks is using shared context to improve collaboration, why an agent that understands its environment can be more useful than dozens of specialized agents, and how the boundaries between product and engineering are changing. We also discuss the skills engineering teams need as AI handles more coding work, including systems thinking, domain expertise, and the ability to ask better questions. What You'll Learn Why AI adoption alone does not make a company AI native. How shared context changes collaboration and decision making. Why agent quality matters more than the number of agents. How AI is changing engineering roles, hiring, and technical skills. Episode Highlights 00:40 How NovaWorks is rethinking HR and workforce management 03:37 The journey from AI awareness to shared organizational context 07:54 Why building more agents is not necessarily better 11:07 How AI is changing the relationship between product and engineering 14:41 Why systems thinking and domain knowledge matter more in engineering 18:57 Learning to question AI rather than simply give it instructions One Line That Stuck "Quantity of the agents doesn't matter." Follow The Tech Trek for more conversations about engineering, AI, product development, and building technology companies.

AI Agents, Deepfakes, and the Problem of Trust

24 min

A few seconds of audio can now be enough to clone a voice. But the bigger challenge is knowing who, or what, is on the other end of an interaction. That question matters when someone calls a bank, joins a job interview, or sends an AI agent to act on their behalf. Vijay Balasubramaniyan, CEO and Co Founder of Pindrop, joins The Tech Trek to discuss how identity and security are changing as deepfakes and AI agents become easier to create. He shares why Pindrop's apparent overnight success took 15 years, how fraudsters are automating account attacks, and why companies need to think beyond a single identity check. The conversation also gets into hiring. Vijay describes fake applicants, different people appearing across interview rounds, and the case for verifying identity throughout the hiring process and after onboarding. His larger point is that stronger, ongoing identity signals could also make security less intrusive for legitimate users. Key takeaways - Deepfake detection needs to keep pace with tools that can clone voices from seconds of audio. - Companies must distinguish legitimate AI agents from agents attempting fraud or unauthorized access. - Recruiting teams are increasingly part of an organization's security defenses. - Continuous identity can protect interviews, accounts, and employee access without adding constant friction. Episode highlights - 01:38 Why Pindrop's success took years to build - 03:44 Voice cloning goes from 20 hours to three seconds - 06:44 How fraudsters use AI agents to make calls at scale - 11:51 Who takes responsibility when an AI agent makes a bad decision? - 16:28 Fake candidates and the risks hiding in hiring funnels - 21:34 How continuous identity could make security feel invisible A moment worth pulling out: “They are now part of security. They're the front end.” Vijay on recruiting teams. Follow The Tech Trek for more conversations about the decisions behind modern technology companies.

Building AI Agents by Removing Features

26 min

The goal is not to do less. It is to give agents the flexibility to handle more of the work customers actually need. Henry Hopcroft, Chief Product Officer at Gradial, joins The Tech Trek to discuss how building AI products is changing traditional approaches to product development, engineering, and customer delivery. Henry explains why his team has moved away from building individual agent features toward a smaller set of core capabilities. He also shares how Gradial tests agents against difficult enterprise environments, uses forward deployed engineers to learn directly from customers, and approaches product planning when AI capabilities are improving so quickly. What You'll Learn Why adding more features can limit an AI agent's flexibility. How real customer failures shape Gradial's agent evaluations. Why forward deployed engineers play a central role in product development. How coding agents are bringing product and engineering roles closer together. Episode Highlights 03:59 Why Gradial started deleting agent features. 07:31 Why traditional software testing falls short for enterprise AI agents. 08:35 Building a nightmare marketing stack to test agents. 12:03 How forward deployed engineers improve the core product. 15:56 Why great engineers increasingly need product judgment. 21:55 Why long term roadmaps are becoming harder for AI companies. A Moment Worth Pulling Out "Features can be something of an anti-pattern, I think, for agentic software." Follow The Tech Trek for more conversations about AI, engineering, product strategy, and building technology companies.

AI Productivity, Code Reviews, and Domain Expertise

26 min

Jayeeta Putatunda, AI Engineering Lead at Turing, joins The Tech Trek to explore what happens after AI generates the first draft. She explains how excessive code can create maintenance challenges, why growing pull request volumes put pressure on code reviews, and how teams can build AI review agents around their own business rules. The conversation also explores how AI is changing product development. Teams can test ideas, create prototypes, and gather customer feedback faster. But taking those ideas into production still requires testing, security, and engineering discipline. Jayeeta also discusses LLM observability, the growing importance of domain expertise, and why sharing lessons across engineering teams matters as AI tools evolve. Key Takeaways More AI generated code can create additional review and maintenance work. Code review agents need business context, not just generic rules. Faster prototypes still require careful testing before production. Domain expertise and human judgment remain important in AI systems. Episode Highlights 00:34 Why AI generates more code and documentation than teams may need. 03:46 How growing PR volumes create new review challenges. 06:44 Measuring productivity beyond the number of features delivered. 12:10 Managing stakeholder expectations when prototypes become easier to build. 14:34 Why LLM observability matters in regulated industries. 18:44 The role of domain experts in building more specialized AI models. One Line That Stuck "Who's reviewing those 10 PRs?" Follow The Tech Trek for more conversations about engineering, AI, data, and technical leadership.

Forward Deployed Engineering: Building AI That Businesses Can Use

38 min

AI teams can build solutions faster than many organizations can make decisions. That gap is changing how engineers work with the business and what companies need from technical leaders. Ash Pembroke, Managing Director of AI Strategy at Accordion, joins The Tech Trek to discuss the growing role of forward deployed engineers. She explains why technical depth alone is not enough and how successful teams combine engineering, product thinking, and business knowledge. The conversation covers leading lean engineering teams, finding the right mix of skills, working alongside business stakeholders, and navigating the tension between rapid AI development and slower organizational adoption. Key Takeaways Strong forward deployed engineers combine technical expertise with curiosity and business understanding. Lean teams need complementary skills rather than one engineer who can do everything. AI agents can extend existing SaaS systems, but replacing those systems requires careful decisions. Faster development does not automatically mean faster adoption or better business decisions. Episode Highlights 01:30 What makes a strong forward deployed engineer? 03:18 Leading small engineering teams with overlapping responsibilities 08:25 How AI agents are changing the role of traditional SaaS 16:50 Moving from software engineering or product into forward deployed roles 25:13 Why business decisions can become the bottleneck to AI adoption 33:48 Giving business teams the ability to automate their own workflows safely A Moment Worth Pulling Out "Nobody knows the work better than the person doing the work." Ash makes the case for giving employees the tools, access, and guardrails to improve their own workflows. Follow The Tech Trek for more conversations on AI, engineering, and technical leadership.

AI, Human Evidence, and Better Business Decisions

32 min

AI can generate answers in seconds. But what happens when the information needed to make a decision isn't available online? Sagar Kadakia, founder and CEO of Qualitate, believes reasoning is becoming abundant while real world evidence remains scarce. His company uses AI moderators to interview experts, capture their knowledge, and make that information accessible to businesses. In this episode of The Tech Trek, Sagar explains how AI can change the economics of primary research. We discuss why human knowledge still matters, how AI interviews work, and what happens when companies can gather expert insight faster and at lower cost. The conversation also explores AI's impact on jobs, why Sagar is hiring more engineers, and how early AI adoption could create lasting advantages for businesses. Key Takeaways AI reasoning is becoming widely available, but firsthand human knowledge remains difficult to access. AI moderators can reduce the cost and complexity of collecting expert insights. AI may affect coordination roles differently from engineering, sales, and physical services. Companies adopting AI early could build advantages that compound over time. Episode Highlights 00:55 | How Qualitate captures human knowledge using AI 04:20 | Why reasoning is abundant but real world evidence is scarce 08:20 | How AI could reshape research and consulting services 12:00 | Inside an AI moderated expert interview 23:00 | Which jobs could change as AI adoption increases 28:00 | Why AI adoption could separate competing companies One Line That Stuck "Reasoning is no longer scarce." Follow The Tech Trek for more conversations about AI, engineering, technology leadership, and company building.

Building an AI First Company With a Lean Team

19 min

AI can help a small company move faster. But a leaner team also has fewer people to rely on when someone leaves. Kevin Bradt, founder and CEO of CasaPerks, joins The Tech Trek to discuss building an AI first company as a nontechnical founder. Drawing on his experience in hospitality and multifamily housing, Kevin explains how he uses AI to rethink business operations, engineering, hiring, and customer delivery. Kevin shares how CasaPerks uses AI to support software development and quality assurance, accelerate product requests, and generate business insights. He also explains why domain expertise and customer relationships may become more valuable as AI makes software development more accessible. What You'll Learn How AI changes staffing decisions across a growing company. Why smaller engineering teams need stronger retention and specialist coverage. How automated QA helps CasaPerks deliver features faster. Why Kevin invests more heavily in customer support while automating internal work. Episode Highlights 00:55 How hotel loyalty experience led to CasaPerks 03:00 Thinking like a business engineer 05:34 Building lean teams without losing coverage 07:18 Casa Flow and automated development workflows 12:31 How faster feature delivery helps win enterprise customers 17:18 Using automation to help residents after a flood One Line That Stuck "We're a service company first, and how we deliver service is through the medium of technology." Follow The Tech Trek for more conversations about AI, engineering, leadership, and building technology companies.

Technical Founders, AI Pivots, and the Value of Focus

31 min

The original idea may not be what makes a startup successful. As AI changes markets and creates new opportunities, the ability to learn and change direction becomes increasingly important. Tim Chen, Managing Partner at Essence Venture Capital, invests in highly technical founders building infrastructure and developer tools. A former engineer and founder himself, Tim started his fund to provide the kind of support he wished he had when raising capital. In this episode, Tim explains why his investment approach has evolved as AI accelerates change. He shares how he evaluates technical teams, what makes a pivot worth pursuing, and why he believes specialization helps investors stand out. The conversation also explores his decision to operate as a largely solo investor, the importance of founder autonomy, and what it means to build a venture fund around a specific area of expertise. Key Takeaways Why a team's ability to learn matters beyond its initial product idea. How AI is changing investment decisions in infrastructure and developer tools. Why specialist investors can offer founders more relevant connections and guidance. How Tim approaches pivots without making decisions for founders. Episode Highlights 00:30 Why Tim started Essence Venture Capital. 03:32 The advantages of making independent investment decisions. 12:08 How specialist investors demonstrate value before investing. 17:03 What the Tabular investment revealed about technical opportunities. 18:04 Why some of Tim's strongest investments have involved major pivots. 22:33 How Tim evaluates the reasoning behind a founder's decision to pivot. A key quote: "Don't be too religious about the approach you take because you most likely are wrong." Follow The Tech Trek for more conversations about engineering, AI, startups, and technical leadership.

AI Observability: Measuring Quality, Risk, and ROI

25 min

An AI agent can be fast, available, and still get the answer wrong. That changes what engineering teams need to measure. Jeetendra Soneja, VP of Engineering, AI Platform at iHerb, joins The Tech Trek to discuss why AI observability goes beyond traditional software monitoring. Teams need to understand not just latency and errors, but also response quality, groundedness, cost, and whether an agent completes its intended task. We also explore how to measure AI ROI without relying on misleading productivity metrics. Jeetendra shares his perspective on risk based guardrails, the skills engineers need, and why observability should begin during development rather than waiting until production. Key Takeaways Monitor agent quality and task completion alongside latency, availability, and cost. Build evaluations around the specific business problem the AI system is solving. Connect AI spending to business outcomes, not just token usage or code output. Start with basic observability, then expand controls as AI adoption grows. Episode Highlights 01:00 Why AI observability requires more than traditional monitoring. 06:00 The metrics that matter for cost, quality, and reliability. 08:00 How to measure AI ROI beyond productivity claims. 11:00 Setting risk tolerances and choosing appropriate guardrails. 16:00 The engineering skills becoming more valuable with AI. 22:00 Proving value before scaling AI systems. One Line That Stuck "It's one thing to get it done, it's another thing to get it done economically." Follow The Tech Trek for more conversations about building and operating modern technology teams.

How AI Is Changing Engineering Teams and Hiring

22 min

What happens to engineering teams when everyone can code? Bali Raghavan, cofounder and CTO at Hero Safety, joins Amir Bormand to discuss how AI is changing team structures, engineering skills, and hiring. At Hero Safety, designers, product managers, and operations teams are using AI to build and solve problems that once required engineering support. That shift changes what companies need from engineers. Bali explains why systems thinking, architecture, judgment, and problem solving are becoming more valuable. He also shares why he now expects engineering candidates to use AI during interviews. The conversation explores where specialized expertise remains essential, including computer vision and edge AI, and how public safety organizations are approaching AI adoption with both interest and skepticism. Key Takeaways AI is expanding who can build software across a company. Engineering judgment and architecture matter more as code generation becomes easier. Coding interviews should reflect how engineers actually use AI at work. Specialized skills remain essential for complex AI systems and edge computing. Episode Highlights 02:15 | Why Bali considers his entire company an engineering team 04:00 | How AI changes the value of programming skills 08:30 | Judgment, first principles, and evaluating AI output 11:45 | Why using AI is now expected in engineering interviews 14:25 | Generalists, specialists, and the need for edge AI expertise 16:15 | AI adoption, privacy, and skepticism in public safety One Line That Stuck "The bug has become a feature." Bali explains how AI use went from something employers tried to prevent in interviews to something they now want to evaluate. Follow The Tech Trek for more conversations about engineering leadership, AI, and building technology companies.

Voice AI Agents: Testing, Trust, and Scale

22 min

Getting a voice agent to talk is one challenge. Knowing whether it can handle real conversations is another. Brooke Hopkins, founder of Coval, joins The Tech Trek to discuss how teams test, evaluate, and scale voice AI agents. Drawing on her experience leading evaluation infrastructure at Waymo, Brooke explains why testing voice agents shares surprising similarities with testing autonomous vehicles. The conversation explores why older voice assistants struggled, how better reasoning models changed what's possible, and what it takes to earn users' trust. Brooke also shares how her engineering team works with multiple AI agents, why technical interviews need to assess AI skills, and how she balances automation with human judgment as a founder. Key Takeaways - Voice AI evaluations must account for interruptions, background noise, and complex conversations. - Simulations identify failures before deployment, while production QA reveals what testing missed. - Engineers need new ways to divide work when running several AI agents in parallel. - Hiring should assess problem solving, system design, and how candidates use AI. Episode Highlights 00:32 How Coval tests voice agents before and after deployment 01:26 What autonomous vehicle simulation teaches us about voice AI 03:24 Why better speech recognition wasn't enough 08:00 Could voice AI change how we use screens? 14:43 How AI is changing engineering interviews 16:43 Where a founder uses AI and where human judgment matters A Moment Worth Pulling Out "We had the eyes and the mouth, but we didn't have the brain." Follow The Tech Trek for more conversations about engineering, AI, and building technology companies.

AI Engineering, Small Teams, and Public Demo Days at Omni

23 min

What happens when AI changes more than coding speed? Chris Merrick, Co Founder and CTO at Omni, explains how his engineering team is adapting around AI, autonomy, product ownership, and a lighter operating model. Omni has about 25 engineers working in groups as small as one to three people. Engineers are expected to make product decisions, move without waiting for detailed specifications, and show unfinished work during a weekly company demo day. Those demos are also posted publicly. Customers watch them, join betas, and see features often move into production soon after. Chris also shares how Claude Code changed development across the team. Commits to main increased roughly two to three times without comparable team growth, but the added output created another constraint: code review. Takeaways • Small teams can operate with less process when engineers have real ownership. • Public demos create feedback loops between engineers, customers, and the rest of the company. • AI can increase engineering output while moving the bottleneck somewhere else. • Token costs still matter when AI usage scales across products and engineering teams. Key Moments 01:15 Building AI into the engineering workflow 03:38 Why Omni works in teams of one to three engineers 06:48 The weekly demo day that replaces heavier process 10:29 Why Omni publishes unfinished product demos publicly 17:14 Measuring AI engineering productivity through commits to main 19:52 When token economics start affecting engineering decisions One Line That Stuck “I’m not married to the process. I’m married to the outcomes.” Follow The Tech Trek for more conversations about how modern engineering and product teams are changing.

From Token Maxing to Outcome Maxing in AI Engineering

24 min

AI coding tools are helping engineers write code faster. But faster code does not automatically mean better business outcomes. Vitaly Gordon, cofounder and CEO of Faros, joins The Tech Trek to talk about the gap between AI adoption and measurable results. The conversation looks at why engineering teams are spending more on AI, how enterprises are thinking about ROI, and why existing processes can become the bottleneck even when code generation speeds up. Vitaly also explains why AI adoption inside large organizations looks different from simply giving engineers access to new tools. Teams still have to deal with security, legacy processes, risk, integration, and organizational change. Key takeaways • More AI usage does not automatically create more customer value. • Engineering leaders need to connect AI spend to actual outcomes. • Enterprise adoption requires process changes, not just new tools. • AI ready engineers increasingly need both domain expertise and AI skills. Key moments 00:36 Stop token maxing and start outcome maxing 02:51 Why FOMO accelerated AI adoption 06:32 Measuring ROI on engineering AI spend 09:19 Change management inside large engineering organizations 14:23 Why AI ready engineers are harder to hire 17:13 Will AI reduce engineering jobs? Best Line “Stop token maxing and start outcome maxing.” Follow The Tech Trek for more conversations with technical leaders building and operating modern teams.

Problem Statements, Business Outcomes, and Better Technology Decisions

23 min

Technology teams are often asked to solve something before everyone agrees on what the actual problem is. Chad Carrington, CIO at Golden1 Credit Union, joins The Tech Trek to talk about listening to business partners, defining the outcome first, and resisting the instinct to jump immediately to a technology solution. The conversation also looks at how AI is changing this skill. As tools make building easier and faster, people still need to articulate what they actually want, ask better questions, and understand what success looks like. What You Will Hear • Why listening and hearing are not the same thing • When solving 85 percent of a problem may be enough • Why technology teams need more time with business users • How AI is increasing the value of asking better questions Key Moments 01:20 Listening versus actually hearing the business problem 03:47 When immediate customer impact matters more than technical debt 06:31 Bringing the business into decisions about speed and tradeoffs 09:47 Why technologists need to spend more time with business teams 13:20 How easier tools change the importance of defining the problem 18:33 Why AI is still a tool, not a substitute for expertise One Line That Stuck “There’s a difference between listening and hearing.” Follow The Tech Trek for more conversations with the people building and leading modern technology teams.

Physical AI and the Real Time Supply Chain

21 min

AI has learned from the digital world. Physical AI brings real world data into the picture. Doron Hazan, Director of Products and AI at Wiliot, joins The Tech Trek to explain how physical AI connects AI systems with objects, environments, and supply chains. The challenge is not simply processing data. It is collecting accurate, current information from the physical world. Doron explains how ambient IoT, sensors, statistical inference, and cloud systems can help companies understand where assets are, what condition they are in, and what may happen next. The conversation also covers the role of human judgment. Supply chains require many decisions, often with consequences that spread across the system. That makes guardrails and human involvement especially important. Key Takeaways • Physical AI connects AI systems with data from the real world. • Better supply chain visibility starts with accurate, current physical data. • Real time decisions matter, but decision accuracy matters more. • Human judgment remains important when AI affects physical operations. Highlights 01:53 What separates physical AI from traditional AI 03:18 Why real world data collection changes the problem 07:19 Supply chain visibility and practical use cases 11:57 How quickly physical AI systems can make decisions 12:48 Why guardrails matter in supply chain automation 15:28 Robotics, distributed physical AI, and connected systems Follow The Tech Trek for more conversations about AI, engineering, product, and technical leadership.

From Smart Dust to Edge AI: Building Intelligence Everywhere

26 min

Scott Hanson went straight from a PhD program at the University of Michigan to building a semiconductor company. Today, as Founder and CTO of Ambiq, he is working on the same core idea that inspired the company years ago: putting intelligence into the devices around us. What changed is what those devices can now do. Scott shares what it was like becoming CEO without prior industry experience, why moving into the CTO role was harder than expected, and how the rise of AI accelerated Ambiq’s original vision. The conversation also looks at what happens as more AI processing moves closer to the device, from wearables and smart homes to factories, medical devices, infrastructure, and smart glasses. Key Takeaways • Founder roles may need to change as the company grows. • Edge AI can reduce how much personal data needs to leave a device • Low power computing expands where AI can operate. • AI tools are changing engineering work from coding toward architecture and design. Key Moments 01:57 Going directly from a PhD program into a startup 06:42 Why Scott moved from CEO to CTO 10:40 Smart dust and Ambiq’s original vision 13:43 Why AI is moving beyond the cloud 17:52 Privacy, security, and processing data locally 20:04 Industrial, medical, and smart glasses use cases A Moment Worth Pulling Out “Be present where your feet are.” Follow The Tech Trek for more conversations with the people building and operating modern technology companies.

Early Stage AI Investing: Moats, Expertise, and Founder Anti Patterns

27 min

Building an AI product is getting easier. Building an AI company that lasts is not. Itamar Novick, Founder and General Partner at Recursive Ventures, joins The Tech Trek to explain what he looks for when investing at the earliest stages of AI companies. The conversation covers how lower development costs could change venture funding, why subject matter expertise matters more as software becomes easier to build, and what actually creates defensibility when competitors can move quickly. Itamar also shares how Recursive Ventures thinks about founder anti patterns. Rather than trying to copy the paths of successful startups, he argues that founders can improve their odds by recognizing common mistakes that repeatedly create unnecessary risk. Key Takeaways • AI may let companies reach scale with much less outside capital. • Subject matter expertise matters more when building software is no longer the main barrier. • Proprietary data, feedback loops, hardware, and exclusive access can create stronger moats. • Founders can reduce risk by learning to recognize repeatable startup mistakes. Episode Highlights 00:38 What Recursive Ventures looks for in early AI companies 05:42 How AI could change the amount of capital startups need 10:04 Why subject matter expertise is becoming more valuable 12:02 What creates an AI moat when software is easy to copy 17:47 Why studying failure can be more useful than copying success 23:13 How AI could reshape venture investing itself Follow The Tech Trek for more conversations with founders, investors, and technology leaders building what comes next.

AI Agents, Engineering Workflows, and the Cost of Being Wrong

28 min

AI coding agents can produce software faster, but they do not replace the judgment needed to understand the system. Shaun Patterson, CTO at Titan, joins The Tech Trek to discuss how agentic coding is changing problem solving, development workflows, project management, and technical hiring. Shaun explains why engineers still need a strong mental model of the systems they are building. AI can generate code, reproduce bugs, research implementation options, and automate repeated debugging work. But it can also keep working on the wrong problem long after a human debugger would have found the answer. The conversation also gets into a bigger shift in software delivery. If agents can work across much larger pieces of a project, engineering teams may move from managing work at the story level to working at the epic level. Key Takeaways • AI speeds up implementation, but engineering judgment still matters. • Repeated debugging work can become reusable agent skills. • Faster implementation lowers the cost of testing different technical approaches. • Hiring increasingly needs to measure how engineers work with AI. Highlights 02:08 Why AI can abstract work, but not engineering wisdom 06:04 Turning repeated debugging sessions into reusable agent skills 09:47 Why faster development may change traditional project management 12:42 Moving engineering work from stories to epics 16:19 Where agentic coding still creates problems 19:29 How Titan evaluates engineers who use AI One Line That Stuck “It abstracts your thinking, but it doesn’t abstract your wisdom.” Follow The Tech Trek for more conversations with the people building and leading technology companies.

AI Agents, Identity, and the Security Gap

31 min

AI agents create a different security problem from traditional software. They can operate at software speed and scale while behaving in ways that are much less predictable. Ev Kontsevoy, CEO and cofounder of Teleport, joins The Tech Trek to discuss what happens when companies deploy agents into security systems designed around humans, applications, and relatively static organizational structures. The conversation gets into authentication, impersonation, infrastructure identity, access control, and a harder question: what actually defines the identity of an AI agent when its model, memory, skills, and capabilities can change? Ev also explains why the combination of speed, scale, and unpredictable behavior changes the risk of mistakes. Later, he explores the tension between agents being useful because they can do new things and security systems that often depend on predictable behavior. Key takeaways • Agent identity gets harder when memory, models, and capabilities can change. • Traditional access controls often reflect static organizational structures. • Agents combine software speed with behavior that can be difficult to predict. • Useful agent behavior can conflict with security systems built around anomaly detection. Highlights 00:41 What Teleport does and why infrastructure identity matters 08:37 Why companies may already be behind on agent security 13:47 Why an electronic account is not the same as identity 15:11 What actually defines the identity of an AI agent? 22:49 Why agent speed and unpredictability change the risk equation 29:04 The conflict between useful agent behavior and anomaly detection One Line That Stuck “Agents are just as unpredictable as humans, but they are way, way, way faster.” Follow The Tech Trek for more conversations with the people building and leading technology companies.

Can AI Agents Help One Founder Run a Company?

31 min

AI agents are moving beyond helping with individual tasks. The bigger question is how much of a company they can actually run. Ben Cera, founder of Polsia, joins The Tech Trek to discuss what happens when AI handles engineering, support, marketing, research, and other parts of company execution. Ben explains how Polsia uses specialized agents that can take direction from a founder or decide what to work on autonomously. He also shares how he uses similar systems inside his own company, which he says has more than 10,000 paying customers and is approaching a $10 million run rate without a traditional full time team. The conversation gets into where humans still matter, why AI mistakes may be acceptable, and how faster execution changes the way founders test ideas. Key Takeaways • AI agents can move from completing tasks to coordinating entire business functions. • Faster execution gives founders quicker feedback on what works and what does not. • Humans still matter most for judgment, direction, and authentic storytelling. • Autonomy requires accepting some mistakes instead of demanding perfect AI output. Highlights 02:43 What changes when AI becomes part of how a founder operates 04:03 Turning customer support into a system that can also fix problems 06:19 Running a company without a traditional full time team 13:47 Why founder judgment still matters when AI gives the options 18:49 How specialized agents coordinate engineering, marketing, and outreach 22:10 What happens when autonomous AI makes the wrong decision One Line That Stuck “You have to trust your gut and you have to be willing to make mistakes.” Follow The Tech Trek for more conversations with the people building and leading technology companies.

How AI Is Changing Engineering Workflows and Software Teams

31 min

AI coding agents can help engineering teams ship more code. But the bigger change may be what engineers spend their time doing. Viren Baraiya, Co-Founder and CTO of Orkes, joins The Tech Trek to discuss how AI is changing workflow orchestration, engineering productivity, project delivery, and hiring. As agents take on more implementation work, engineers are spending more time on design, architecture, review, and verification. Viren shares how his team measures the return on AI through product velocity, stability, and the ability to build things that previously required more time or outside resources. He also explains how Orkes manages model costs by using stronger models for difficult reasoning and smaller models for implementation. Key Takeaways • Coding agents increase output, but they also increase the need for verification. • Engineers are shifting from pure implementation toward design, review, and orchestration. • Repeated AI tasks can become reusable workflows that reduce ongoing token usage. • Hiring should test how engineers actually work with agents, not just manual coding. Highlights 01:21 Why agents are workflows and where orchestration fits into AI systems 05:19 How AI changed feature velocity, testing, and customer engineering at Orkes 07:44 Measuring AI ROI through velocity, stability, and new product capabilities 09:19 Why engineers increasingly look more like tech leads 12:56 Turning repeated AI requests into reusable workflows to reduce token usage 19:34 Why Orkes changed engineering interviews to include agentic coding One Line That Stuck “That has become a more important skill than actually writing the code now.” Follow The Tech Trek for more conversations with the people building and leading technology companies.

How AI Agents Are Changing Who Can Build Software

23 min

AI is doing more than helping engineers write code faster. It is starting to change who can participate in software development, how teams divide work, and where technical talent creates the most value. Shaosu Liu, Co Founder and CTO at Loop, explains how his team is using AI agents across the software development lifecycle while also enabling highly technical people outside traditional software engineering roles to build customer specific workflows. The result is a different model for scaling technical work, one that matters for founders and technical leaders thinking about team design in the age of AI. Loop is also using forward deployed engineers as core product engineers who can work directly with customers, understand difficult edge cases, and turn those requirements into product improvements. Takeaways • AI agents can now support much more than coding, including specifications, testing, deployment, validation, rollout, and production management. • Giving technical people better AI tools can expand who is capable of contributing to software development. • The final few percent of a customer workflow may consume most of the manual effort. AI makes that customization more practical. • Forward deployed engineers need both technical ability and the judgment, communication skills, and confidence to work directly with customers. Key Moments 04:37 How Loop uses AI across the software development lifecycle 07:05 Why people outside traditional engineering roles are writing significant amounts of code 09:03 Why automating the final few percent of a workflow can remove most of the remaining manual work 11:01 Why forward deployed engineers matter when customer requirements get complicated 16:37 Why forward deployed engineering is often a path to another role rather than a long term career 19:50 How Loop evaluates technical ability and customer facing skills when hiring One Line That Stuck “That last 5% automation ends up saving 100% of time.” Follow The Tech Trek...

How to Build a Data Team Ready for AI

29 min

AI can make teams faster, but it can also expose every weakness in the data underneath it. Elizabeth Stanford, VP of Data at PandaDoc, joins The Tech Trek to talk about what it takes to prepare a growing company to actually execute on AI. That means more than giving engineers access to Claude or Cursor. It means getting the data foundation, team skills, stakeholder expectations, and ownership model right. Elizabeth explains how PandaDoc is preparing its data organization for AI while keeping a small team from becoming the company’s quality control department. She also shares how AI is changing what she looks for when hiring data professionals, and why expertise, problem framing, and judgment may become more valuable as coding gets easier. What you’ll take away • AI readiness starts with reliable data, shared definitions, and systems that can provide consistent context. • Giving stakeholders easier access to data creates a new problem when the data team becomes responsible for checking everyone else’s AI generated work. • Technical execution is becoming easier, which puts more value on knowing what questions to ask and whether an answer is actually correct. • Hiring standards are changing. Candidates need to show how they think with AI, not simply that they can use it. Best Line “It’s not whether you know today’s technology, it’s whether you can figure out tomorrow’s technology.” Follow The Tech Trek for more conversations about building and leading modern technology teams.

How AI Startups Can Challenge the Enterprise Services Model

30 min

AI is not just changing software. It may also change the economics of the services businesses built around it. Anirudh Sriram, CTO at Tessera Labs, joins The Tech Trek to explain how his company is using AI to take on enterprise transformation work traditionally handled by large systems integrators. Tessera focuses on migrations, ERP upgrades, code, data, and planning, but the bigger story is how a startup can compete by replacing large teams and long projects with automation, smaller teams, and a focus on outcomes. The conversation also gets into a harder problem. AI can produce work much faster than people can verify it. In one example, Tessera completed code migration work in three days, but functional testing still required roughly two months. That gap between production and verification may become one of the biggest constraints on enterprise AI. What Stood Out • AI creates an opening for startups to compete in markets where incumbents have historically won through scale and headcount. • Selling outcomes instead of large project teams can change both pricing and customer expectations. • Enterprise migrations can be a wedge into a much larger opportunity because they require understanding a customer's systems, data, code, and business processes. • Faster AI output does not remove the need for human review. In some cases, verification becomes the new bottleneck. Key Moments 02:12 Where AI can take work out of the enterprise migration process 04:39 How transformation projects can stretch years beyond their original plan 08:27 Why AI may change the economics of services businesses 13:42 Why verifying AI output is becoming a major constraint 22:17 How Tessera approaches security, governance, and enterprise data 24:56 Using migration as the entry point into broader enterprise automation One Line That Stuck “We sell the outcome and not the process.” Follow The Tech Trek for more conversations on building, operating, and competing with AI.

From Head of AI to CTO: How AI Is Changing Engineering and Product

31 min

AI changes more than the product roadmap. It changes how engineering teams build, how data flows through the company, and what a CTO needs to own. Andrew Rabinovich, CTO and Head of AI at Upwork, joins The Tech Trek to talk about his move from leading AI into the broader CTO role. His view is simple: AI is no longer just another component inside a software system. Increasingly, AI is the system, and infrastructure, data, engineering, and product need to be designed around that reality. Andrew explains how that shift is changing Upwork's product development, from adding AI to individual features to building systems that learn across the entire user journey. He also discusses faster iteration, the importance of real time data, and how software engineering changes when machines can generate most of the code. What Stood Out • AI first development requires thinking about the entire system, not adding AI capabilities to isolated product features. • Product iteration can move from months between versions to daily updates when systems continuously learn from user interactions. • Engineers are moving from writing every line of code toward reviewing, steering, simplifying, and evaluating machine generated code. • Asking the right question and knowing when a result is good enough may become more valuable than the mechanical work between those two points. Key Moments 03:39 AI moves from being a component of software to becoming the foundation of the system. 07:35 How an AI background changes the role of the CTO and the relationship between technology and product. 10:48 Why Upwork moved from AI inside individual features toward end to end learning across the user journey. 16:04 AI makes feature creation easier, but faster creation does not automatically mean adoption. 20:41 Software engineering shifts toward reviewing and steering code generated by AI agents. 27:01 The skills that become more valuable when AI handles more of the execution. One Line That Stuck “AI is no l...

Where VCs See Opportunity in Regulated AI

23 min

AI is making software faster and cheaper to build. It is not making trust any easier to earn. Simon Wu, Partner at Cathay Innovation, joins The Tech Trek to discuss how AI is changing investment opportunities across healthcare, fintech, insurtech, legal services, and other regulated industries. The conversation looks at a major shift in software economics. Instead of simply selling seats, licenses, and tools, AI companies can increasingly perform more of the work and deliver the outcome a customer actually wants. That creates opportunities for new business models, especially in industries where customization and services historically made it difficult to scale. Regulation adds another dimension. Compliance, accuracy, governance, and complex workflows make these markets harder to enter. But Simon argues that the same friction can create defensibility once a company earns the trust of its customers. Key Takeaways • Regulation can become a moat. AI may lower the cost of building software, but companies still have to earn the right to operate inside sensitive workflows. • Software is moving closer to outcomes. Customers increasingly care about the result, not how many seats or licenses they purchased. • AI changes the economics of customization. Companies may no longer have to choose as sharply between scalable software and labor intensive services. • Human involvement still matters. In healthcare, wealth management, and legal services, AI can make professionals more efficient without requiring them to disappear from the workflow. One Line That Stuck “AI has dramatically lowered the cost of building software. It doesn't lower the cost of earning trust.” Follow The Tech Trek for more conversations on AI, engineering, product, data, and building modern technology companies.

Why AI Makes Work Faster but Teams Slower

24 min

AI can make individual tasks faster while leaving the organization with the same old coordination problems, or even making them worse. Sergei Sorokin, CEO and co founder of Highlight, joins The Tech Trek to discuss why faster output does not automatically mean better work. Teams can generate documents, code, notes, and analysis faster, then spend the time they saved reshaping that output, moving information between tools, and figuring out what matters. The bigger problem, Sergei argues, is often not access to information or model intelligence. It is context. AI needs to understand what matters to a specific person, team, and moment rather than simply searching across everything available. The conversation also covers proactive AI assistants, privacy and security, team specific customization, and why trust will shape how quickly people allow AI to act on their behalf. Key Takeaways • Faster task completion does not eliminate the coordination tax between people and tools. • The challenge is increasingly signal versus noise. AI needs to understand which information matters now. • AI that adapts to individual teams could help companies preserve what makes their work distinct rather than producing increasingly similar output. • Adoption will depend on trust. Drafts, approvals, undo options, and clear boundaries can help people become comfortable giving AI more control. Key Moments 02:09 Why faster AI output can still create more work across teams 05:02 The coordination tax that existed before AI and why AI can amplify it 08:19 Why chat alone may not be the right starting point for workplace AI 13:58 How AI could adapt to teams rather than forcing teams to adapt to software 18:16 Why human behavior and trust will determine AI adoption 22:05 Why greater agent autonomy may create a demand for more user control One Line That Stuck “It’s not an intelligence gap. It’s a context gap.” Follow The Tech Trek for more conversations about AI, engineering, product, data, an...

AI Deepfakes and Hiring Fraud: Can You Trust Who You’re Interviewing?

25 min

AI is changing hiring in ways that go far beyond candidates using ChatGPT to answer interview questions. The harder problem is knowing whether the person on screen is actually who they claim to be, whether their answers are their own, and what happens if someone with malicious intent gets access to company systems. Yagub Rahimov, CEO and founder of Polygraf AI, joins The Tech Trek to discuss the growing trust problem surrounding AI assisted interviews, deepfakes, impersonation, and security. He explains why organizations need more visibility into the hiring process without turning every unusual behavior, accent, or response into a reason for suspicion. What You’ll Take Away • AI interview fraud is not simply a recruiting problem. Once someone enters the company, identity and access become security concerns. • Detecting suspicious candidates based on human intuition alone can create false positives. Rahimov argues for using technology to create evidence and visibility. • Small pieces of public information can reveal far more about a company than leaders realize when they are combined through what Rahimov calls mosaic intelligence. • Protecting company information means thinking beyond traditional security controls to what employees, executives, and systems expose publicly. Key Moments 02:27 How AI tools can turn legitimate technology into an interview cheating mechanism 05:35 Why hiring fraud can become a security and data access problem 07:43 Using voice, conversation context, and AI detection to improve visibility during interviews 11:43 Why increased AI uncertainty should not lead companies to distrust everyone 14:28 What organizations should think about after a candidate actually gets hired 19:40 The continuing race between increasingly capable deepfakes and detection technology One Line That Stuck “Tech problems have tech solutions.” Follow The Tech Trek for more conversations about AI, engineering, data, product, and how technical teams are adapting.

AI Is Changing Software Engineering: Engineers Need to Solve Problems, Not Just Write Code

25 min

If AI can produce the code, what becomes more valuable for engineers? John Kuhn, CTO and cofounder of Integral, joins The Tech Trek to discuss how agentic development is changing engineering work, product ownership, experimentation, and hiring. Integral helps companies de identify and anonymize data for model training, including unstructured data. John argues that the value of an engineer is shifting away from simply writing code. As AI handles more implementation work, engineers need stronger product judgment, better systems thinking, and the ability to make decisions when requirements are incomplete. That means asking better questions, understanding customer problems more directly, and taking greater ownership of the outcome. The conversation also looks at what happens when software becomes cheaper to produce. Teams can prototype and experiment faster, but lower development costs do not eliminate the cost of building something customers do not want. Good product discovery still matters, especially when engineers are expected to operate with more autonomy. What You’ll Take Away • Why engineers increasingly need to think like product managers • How agentic tools are changing the economics of prototyping and product experimentation • Why good product discovery requires questions that seek information instead of confirming an existing idea • Why engineering interviews may need to focus more on assumptions, constraints, systems thinking, and decision quality than manual coding speed A Moment Worth Pulling Out “Engineers are not meant to write code anymore. They’re meant to solve problems.” John also raises an interesting idea for the future of technical hiring: instead of giving candidates only a time limit, give them a fixed AI compute budget and evaluate how efficiently they use it to reach a solution. Follow The Tech Trek for more conversations about AI, engineering, product, data, and technical leadership.

How AI Is Changing Sports Analytics and Strategy

26 min

Sports organizations have more data than ever. The real advantage comes from knowing which problem to solve, which data matters, and whether people will trust the answer enough to change how they work. Rohan Nagi, VP of Strategy and Analytics at Sponsor United, explains how sports analytics is moving beyond basic reporting into AI supported decision making. He discusses how teams and brands can combine quantitative and qualitative information to evaluate athletes, identify sponsorship opportunities, understand audiences, and make better business decisions. The technology is only part of the challenge. Coaches, athletes, executives, and business teams may be asked to abandon routines and instincts that have worked for years. Successful AI adoption requires clear problems, organized data, executive direction, and tools that fit real workflows. Practical Takeaways • Start with the person and the problem, not the AI tool. • Identify the information people already use and the data gaps limiting their decisions. • Build adoption around practical individual workflows before expanding across departments. • Connect daily use cases to a clear executive vision and broader business goals. Approximate Episode Highlights 00:55 What Sponsor United does across sports, entertainment, brands, and sponsorships 02:50 How sports moved from intuition toward data informed decision making 05:35 Where traditional analytics ends and more advanced AI applications begin 08:55 How teams can combine performance, medical, and personality data when evaluating players 12:20 Why changing an athlete’s routine can be harder than collecting the data 18:00 Why an AI strategy must begin with a clearly defined problem Best Line “The tools are just meant to help solve a problem.” Follow The Tech Trek for more conversations on AI, data, engineering, product, and technical leadership.

How Do You Hire Engineers When AI Writes the Code?

28 min

AI is changing more than how engineers write code. It is changing what leaders hire for, how candidates are assessed, and which engineering skills may matter most. Raymond Wang, CTO and cofounder at Ease Health, joins Amir to discuss how an engineering team using agentic coding tools thinks about hiring, productivity, code review, token costs, and the future of software engineering. Raymond argues that syntax knowledge and familiarity with a specific language matter less than they once did. His team puts more weight on product instincts, engineering judgment, passion, drive, and the ability to break down problems and guide AI agents when they go in the wrong direction. The conversation also examines a growing interview challenge. Watching a candidate prompt an AI tool can introduce subjectivity, especially when different prompting styles produce equally strong results. Raymond recommends making interviews resemble the actual work and evaluating the quality of the output rather than whether the candidate used the same process as the interviewer. Practical Takeaways • Hire for product judgment, engineering instincts, and problem solving, not only language precision. • Design interviews around realistic work and evaluate results more than prompting style. • Use the strongest models for expensive mistakes, such as code review, and cheaper models for lower risk internal tasks. • Build an internal AI harness that engineers use and improve as part of their daily workflow. Episode Highlights 02:05 What Ease Health now values when hiring engineers 05:30 Why grading prompts can make interviews more subjective 08:40 The challenge of keeping coding interviews ahead of rapidly improving models 12:10 Why Raymond sees code review as one of AI’s strongest engineering use cases 14:40 How Ease Health compares token spend with engineering output 26:45 Why software engineering may split between elite generalists, narrower roles, and highly specialized experts One Line That Stuc...

AI Data Centers Are Outgrowing the Power Grid

26 min

AI infrastructure is expanding faster than the power systems required to support it. A data center can be built in two to three years, while a new power plant or transmission line may take seven to nine years. That gap puts utilities at the center of the next phase of AI growth. Vik Chaudhry, cofounder and CTO of Buzz Solutions, explains how utilities are using visual AI, computer vision, drones, and infrastructure data to find defects, prioritize maintenance, prevent outages, and reduce wildfire risk. He also discusses how AI can help utilities uncover existing grid capacity, forecast unpredictable demand, control operating costs, and preserve knowledge as experienced workers retire. What You’ll Take Away • Why electricity, not computing chips, may become the largest constraint on AI growth • How utilities can extract more capacity from existing infrastructure while new power generation is built • Where visual AI helps teams prioritize inspections, repairs, and maintenance spending • How AI can improve load forecasting and transfer knowledge to the next generation of utility workers A Moment Worth Pulling Out “The biggest problem for AI right now is not the chips. It’s the electrons.” Key Moments Approximate timestamps based on the transcript. 00:45 How Buzz Solutions uses visual AI to assess power infrastructure 03:05 Why utilities began building internal AI teams and governance processes 06:45 The energy constraint behind data center and AI expansion 08:20 Why data centers can be built much faster than new power infrastructure 11:50 Balancing data center demand with affordability for consumers 26:35 Using AI for load forecasting and utility workforce knowledge transfer Follow The Tech Trek for more conversations about how technical teams are building and operating around AI, data, platforms, product, and engineering.

How Coding Agents Are Changing Machine Learning Engineering

31 min

Machine learning teams are moving faster, but the hard part has not disappeared. The work is shifting from writing and debugging every line of code toward defining the right problem, setting requirements, reviewing outputs, and deciding what belongs in a durable platform. Niels Bantilan, Chief Machine Learning Engineer at Union AI, explains how machine learning work has changed, why coding agents are accelerating prototyping, and what engineers must consider when building infrastructure that supports many teams instead of optimizing one model. He also shares how customer needs become product decisions, why machine learning roles are becoming more specialized, and why measuring AI productivity remains difficult. Key Takeaways • Coding agents reduce time spent on implementation, debugging, and exploration, but engineers still need judgment around architecture, quality, and business value. • Platform teams must balance experimentation with stability by giving users freedom at the edges while protecting a reliable foundation. • Machine learning engineering now spans a wider range of skills, from low level performance work to customer empathy, education, documentation, and developer advocacy. • The best model for a task may depend on complexity. Smaller self hosted models can handle tightly scoped changes, while longer and more complex work may still require stronger hosted tools. Episode Highlights 00:50 What Union AI means by an AI runtime for production 02:10 How machine learning work has changed over the past five years 10:40 The mindset shift from model building to platform engineering 15:00 Turning customer problems into reusable product capabilities 19:00 Why machine learning roles are becoming more specialized 21:50 Using coding agents through specifications, tickets, and code review 26:50 Token costs, productivity measurement, and choosing the right model One Line That Stuck “I’m still solving problems. It’s just the level at which I’m doing it doesn’t re...

How AI Is Reshaping Healthcare Revenue and Access

27 min

Healthcare providers can wait 60 to 75 days to get paid, while many hospitals spend 5% to 7% of revenue on the collection process. That makes revenue cycle management more than a back office issue. It affects margins, staffing, patient experience, and access to care. Akash Magoon, cofounder and CEO of Adonis, joins The Tech Trek to explain how agentic AI can help medical groups and hospitals automate denials, accounts receivable work, and other manual billing processes. He also shares how Adonis applies AI internally across engineering, sales, and customer success. The conversation goes beyond automation. Akash explains why healthcare companies often win through distribution, not product quality alone, why focused solutions can create more progress than broad attempts to fix healthcare at once, and why leaders need to frame AI as a tool that helps people work at the top of their license. Practical Takeaways • Start with a narrow, material problem rather than trying to rebuild healthcare all at once. • Measure AI through business outcomes, including net collection rate and cost to collect. • Invest in marketing and distribution early, even when the product is strong. • Build employee trust by showing how AI improves effectiveness, not only efficiency. Approximate Highlights 00:45 How Adonis applies agentic AI to revenue cycle management 02:05 Lessons from building a second healthcare technology company 04:45 Using AI for customers and inside the company 08:55 Why healthcare progress often starts with focused swim lanes 14:25 The distribution lesson Akash carried into Adonis 20:40 How operational efficiency may improve patient access and rural healthcare One Line That Stuck “Healthcare ends up becoming a very humbling place to build.” Follow The Tech Trek for more conversations on AI, data, product, engineering, and technical leadership.

How AI Agents Are Rewriting Enterprise Analytics

22 min

Most companies are not short on data. They are short on the time, cost, and coordination required to turn it into action. Ethan Ding, co founder and CEO of TextQL, joins The Tech Trek to explain how AI agents are changing enterprise analytics. The conversation moves beyond faster dashboards into a larger shift, analysts managing fleets of agents, business teams asking far more questions, and companies finding revenue and cost opportunities that were previously too expensive to pursue. What Technical Teams Can Take From This • Making answers cheaper does not reduce analytics work. It increases the number of questions people ask. • Analysts may spend less time assembling dashboards and more time managing agents, data sources, permissions, quality, and costs. • The clearest ROI comes from decisions with direct financial outcomes, including fraud prevention, upsell opportunities, churn risk, and unused vendor spend. • Faster analysis matters most when teams can act on valuable opportunities they previously could not afford to investigate. • Token costs will force AI companies and buyers to reconsider where software budgets go, especially across BI tools and data platforms. Moments Worth Hearing 00:00 Ethan explains how TextQL agents work across messy enterprise systems including Cognos, Teradata, Snowflake, Databricks, Tableau, and Power BI. 04:52 Why giving people faster answers does not create free time. It creates even more demand for analytics 07:10 How self service analytics quickly moves from asking what a number is to asking whether it matters and what to do next. 10:08 The analyst role shifts toward managing fleets of agents and tuning an insight factory for the business. 14:38 Why faster access to data can reveal valuable opportunities that were previously too expensive to investigate. 19:55 A practical way to measure analytics ROI through fraud prevention, upsell opportunities, and other direct financial outcomes. 24:18 How token costs, AI margins, and ea...

Scaling Enterprise AI Beyond the POC

28 min

Enterprise AI is easy to demonstrate. The real test begins when a promising POC meets production costs, security requirements, data movement, latency, and internal adoption. Shimon Ben-David, CTO at WEKA, joins Amir to discuss the gap between experimenting with generative AI and operating it at scale. They explore how classical AI differs from generative AI, why production exposes problems that demos hide, and how companies with limited AI maturity can start building useful internal capability. Practical Takeaways • A successful POC proves that an outcome is possible. It does not prove that the system will be affordable, secure, reliable, or fast at scale. • Enterprise AI adoption reaches across infrastructure, engineering, data, security, and business teams. It cannot be owned by one group in isolation. • Adding more GPUs will not fix slow data access, poor utilization, weak pipelines, or an experience users do not want to use. • External support can help, but the person or firm involved needs to stay through implementation and production, not stop at recommendations. • Companies that are behind should begin with proven use cases, build internal experience, and quickly stop experiments that fail to show value. Key Moments 00:00 Why moving enterprise AI into production remains difficult 01:55 The difference between classical AI and generative AI adoption 07:05 How companies can use AI without having a formal AI strategy 11:35 Why successful POCs often struggle when they reach production 17:35 Competitive pressure, AI FOMO, and the need to calculate real ROI 22:00 Why AI adoption requires cross organizational change 33:10 Where a company with limited AI maturity should begin One Line That Stuck “The promise is there. It is possible. You just need to do it properly.” Subscribe to The Tech Trek for more conversations about how technical teams are building, operating, and adapting around AI, data, product, platform, and engineering execution.

How Todoist Is Rethinking Engineering With AI

34 min

AI can generate code faster, but that does not make software delivery simple. It shifts the pressure to requirements, architecture, review, and technical judgment. Goncalo Silva, CTO at Doist, explains how AI is changing the way teams behind Todoist and Twist build software. He shares why greater individual autonomy has led to more collaboration, why deep expertise still matters, and how faster execution is reshaping product delivery, project planning, and engineering hiring. What Leaders Can Take From This • Faster code generation makes strong planning and clear requirements more important, not less important. • Designers, product leaders, and engineers can work from richer prototypes, but production systems still need experienced technical judgment. • Engineering capacity does not have to move into other functions. Teams can use it to improve reliability, performance, quality, and the amount of valuable work they ship. • Token counts are a weak measure of progress. Doist looks at team feedback and whether projects are staying on track. • Engineering interviews need to test architecture, decision making, curiosity, and depth, not simply whether a candidate can produce working code. Approximate Highlights 00:00 Meet GonCalo Silva and the products behind Doist 02:00 How broadly AI is being used across Doist 04:15 Why greater autonomy has brought teams closer together 09:45 Where nontechnical coding works, and where it creates risk 17:50 How AI compressed a major refactoring effort by 20 to 30 times 25:05 Measuring AI value without counting tokens 30:20 Why faster execution requires more up front planning 34:50 How Doist changed its engineering interview process One Line That Stuck “We are the bottleneck. Our attention span, our ability to memorize, our ability to understand, and deep expertise.” Follow The Tech Trek for more conversations on how technical teams are changing the way they build, hire, and operate.

The Future of Engineering May Have Fewer Handoffs

26 min

AI is not just changing how engineers write code. It is changing who gets close enough to shape the work. In this episode of The Tech Trek, Robert Stewart, CTO at Arbital Health, joins Amir to talk about how AI is bringing actuarial subject matter experts closer to product and engineering teams, especially in healthcare and risk based contracts. Robert shares how his team is pairing technically minded SMEs with software engineers, using AI tools in development, and rethinking technical hiring now that AI assisted coding is part of the job. Practical Takeaways • AI can reduce the distance between domain experts and engineering when the SMEs can clearly describe requirements, acceptance criteria, and edge cases. • Pairing a subject matter expert with an experienced engineer can be more powerful than traditional pair programming because each person brings a different kind of judgment. • Better written requirements matter more in an AI assisted workflow because tools can work directly from detailed tickets and context. • Technical interviews may need to test how candidates use AI, not whether they can avoid it. • Hiring teams need stronger signals around identity, environment fit, prompting skill, and how candidates respond to AI output. Timestamped Highlights 00:00 Robert Stewart on Arbital Health, value based care, and the role of actuarial expertise in healthcare infrastructure. 03:06 Why actuarial knowledge is hard to transfer into engineering teams through normal handoffs. 04:40 How AI helps subject matter experts move closer to product and engineering work. 06:08 Why engineering fundamentals still matter, even when AI makes code easier to create. 09:55 How Arbital Health is using Cursor, Claude Code, and human review in a regulated environment. 14:52 Why more detailed Jira tickets are becoming more valuable in AI assisted development. 17:10 How AI is changing technical interviews from “you may use AI” to “you must use AI.” 22:16 What suspicious candidates, re...

The Hard Part of Voice AI Is Not the Voice

21 min

Voice AI is moving from simple call routing into work that used to require trained human agents. The harder question is what happens when those conversations involve lending, collections, servicing, compliance, and real customer risk. In this episode of The Tech Trek, Amir Bormand speaks with Joshua March, founder and CEO of Veritus, about building AI voice agents for regulated financial services. Joshua shares why consumer lending is a demanding test case for voice AI, what makes regulated conversations different, and why the next version of the contact center may be built with much smaller teams overseeing AI systems. Practical takeaways AI voice agents only matter if they can actually resolve the issue. Joshua argues that users have been trained to distrust automated phone systems because most IVRs block progress instead of helping. Regulated communication is not just about what the agent says. It also includes who can be contacted, when they can be contacted, call frequency, TCPA rules, QA, and post call compliance. Complex voice agents require more than a prompt. Joshua talks about context engineering, state management, specialized background agents, compliance monitoring, KYC workflows, latency, and turn detection. AI changes startup execution. Small teams with experienced people can build and ship much more than before, but that also raises the pressure to move faster. Venture backed AI companies face a bigger bar. Joshua makes the case that higher seed valuations and larger funds increase the need for very large outcomes. Timestamped highlights 00:00, Why Veritus is focused on AI communications for financial services and voice agents in consumer lending 02:10, Joshua’s path from Facebook apps to social customer service, messaging, bots, and now voice AI 05:05, Why AI voice agents may replace a large share of traditional call center work 07:00, Why customers have learned to fight IVRs and what changes when AI can actually solve the problem 10:00, The...

Why Healthcare AI Is So Hard to Ship

18 min

Joanne Chen, VP of Data and AI at SimplePractice, joins The Tech Trek to talk about what it takes to build AI data products in a regulated, sensitive domain where privacy, consistency, monitoring, and customer trust have to be designed from the start. This conversation gets into why AI product development feels different from traditional software, how teams should think about quality control, and why not every valuable AI solution needs to be GenAI. Practical Takeaways • AI products need defense in depth, especially in healthcare, where privacy, confidentiality, and security cannot depend on one layer of protection. • The core product questions still matter. What customer pain does this solve, who benefits, and what does it take to ship responsibly? • AI changes the development life cycle because outputs are not always deterministic and quality can degrade after launch. • Teams need monitoring, validation, and a plan for edge cases before putting AI features in front of customers. • AI literacy is becoming part of every role involved in building, marketing, supporting, and operating software products. Timestamped Highlights 00:00 Joanne Chen on AI data products, deterministic outputs, and safely shipping AI features 01:20 What SimplePractice does for mental health practitioners and group practices 02:30 Why healthcare AI needs multiple layers of risk protection 05:00 What makes an AI data product different from a traditional data product 08:15 Why stakeholder expectations around AI have widened so much 10:40 How AI changes the work across engineering, CS, marketing, and support 13:10 Where AI can help reduce tedious administrative work in healthcare 16:45 Why leaders need to keep their hands dirty with new AI tools One Line That Stuck “Keeping hands dirty is important.” Subscribe to The Tech Trek for more conversations on how technical teams are building, operating, and adapting around AI, data, product, and engineering execution.

Engineers Are Becoming AI Orchestrators

24 min

Kevin Haggard, Vice President of Engineering at Barracuda, joins The Tech Trek to talk about how AI is showing up across cybersecurity products, engineering workflows, team adoption, and software delivery culture. He shares how Barracuda is approaching AI with guardrails, why adoption varies across teams, and what happened when the company ran protected AI dev days for the engineering organization. What to take from this episode * AI adoption inside engineering teams will not be even. Some teams are already orchestrating agents from requirements to deployment, while others are still figuring out where AI fits into their day to day work. * Guardrails matter more in security sensitive environments. Barracuda uses an AI gateway and control plane so teams can experiment without leaking data or letting agents take uncontrolled actions. * Protected time changes behavior. Barracuda’s AI dev days gave teams three days with no meetings so they could work with the tools inside real projects instead of treating AI as a side experiment. * The coding bottleneck may move. AI can create more code faster, but QA, testing, release safety, problem definition, and rollback mechanisms become even more visible. * The engineer’s role is shifting from operator to orchestrator. Kevin argues that system design, review, context, and crisp instruction will become more valuable as agents take on more execution. Key moments 00:28, What Barracuda does and how AI pairs with people in cybersecurity 03:35, Why AI adoption varies across engineering teams inside a larger organization 05:06, The need for AI guardrails, gateways, and control planes 06:20, How Barracuda ran AI dev days across the organization 08:42, The light bulb moments from product, design, and engineering teams 13:07, Why AI velocity makes existing delivery bottlenecks harder to ignore 17:00, How engineers may move from writing code to orchestrating agents and reviewing systems One line that stuck: “Their role is going to eleva...

Your Team Is Using AI Anyway

26 min

AI adoption is no longer just a policy conversation. For many organizations, the bigger question is how to move faster without creating avoidable risk. In this episode of The Tech Trek, Amir Bormand sits down with Aimee Cardwell, CIO and CISO in residence at Transcend, to talk about responsible AI deployment, the tension between speed and control, and how leaders should think about security, compliance, productivity, and customer experience as AI moves through the enterprise. Aimee brings a rare view across the CIO, CISO, and board lens. The conversation gets into why blocking AI often backfires, how prompt redaction can help teams move faster safely, where companies should draw the line on risk, and why some teams may need to rethink old assumptions about tech debt, code ownership, and modernization. Practical Takeaways • Responsible AI depends on the lens. Security, compliance, business, board, and technology teams may all define it differently. • Blocking employee AI usage can create worse outcomes. People may use shadow tools anyway, or teams may fall behind in productivity. • Prompt redaction and enterprise agreements can give teams room to experiment while reducing exposure of sensitive data. • Moving fast is not the same as releasing half finished customer experiences. Bad AI tools can train customers to distrust the entire interaction. • AI may change how teams think about tech debt, refactoring, and whether some legacy systems should be rebuilt instead of patched forever. Timestamped Highlights 00:00 Responsible AI deployment and why the definition changes by role 02:35 Aimee explains the CIO, CISO, and board perspectives on AI adoption 05:14 Why companies that block AI may create shadow usage and slower teams 06:52 Prompt redaction as a practical way to let employees experiment safely 10:40 How AI risk changes when the data exposure model is different from traditional insider theft 15:10 Why releasing poor AI customer experiences can damage trust 21:50 Usi...

What AI Agents Need Before Production

26 min

AI agents are easy to demo. They are much harder to trust, maintain, govern, and put into production. In this episode of The Tech Trek, Amir Bormand talks with Lucas Thelosen, CEO and cofounder at Gravity, about the agent economy, AI analytics, and what changes when analysts move from doing every task themselves to managing AI systems that create more bandwidth. Lucas shares why Gravity built Orion, an AI analyst, after years working in analytics, product, and data teams at companies like Looker and Google. The conversation gets into the messy middle of AI adoption, why so many agent projects struggle to make it into production, and how context may become one of the most valuable assets a company owns. Practical Takeaways • Agent prototypes are easy. Production agents require support, maintenance, accuracy checks, and clear ownership. • Not every company should build every agent internally. If the capability is not core to what you sell, buying may be the faster path. • Context matters because it lets humans critique AI output with business judgment, not just technical review. • Analysts may shift toward data architecture, governed data models, and internal product management for analytics. • AI does not remove human responsibility. It raises the bar for review, delegation, and decision making. Timestamped Highlights 00:40, What Gravity is building with Orion, an AI analyst designed around the work analytics teams already know well. 02:28, Why mature companies still miss major insights, even when they already have data teams. 03:43, The agent economy reality check, easy prototypes, hard production, and the gap between demo and durable system. 06:28, Why companies still build agents internally, even when many projects never reach production. 09:48, The case for experimenting now instead of waiting for the AI stack to settle. 11:40, How AI shifts people from doing the work to managing the work. 18:50, What the future analyst role may look like as AI takes on...

Yahoo CTO on AI, Engineering Velocity, and Why the SDLC Has To Change

25 min

Yahoo is not just adding AI on top of existing products. It is using AI across product experiences, internal tools, engineering workflows, and modernization efforts. In this episode of The Tech Trek, Lee Zen, CTO at Yahoo, joins Amir Bormand to talk about modernizing at massive scale, moving from on prem infrastructure to the cloud, rebuilding internal tools with AI, and how engineering organizations need to rethink process when agents can move faster than people. Lee also shares how Yahoo views AI as a coworker, not just a tool, and why the next bottleneck in software delivery may be human judgment. Practical Takeaways • Modernization at scale often means operating in two worlds at once, keeping proven systems running while new cloud based services move faster. • AI can help teams move past legacy tools by reverse engineering requirements and rebuilding modern versions from scratch. • The real unlock is not only code generation. It is connecting agents to documents, chats, emails, production context, and internal knowledge with the right permissions. • As agents speed up execution, engineering teams need to rethink where human approval, judgment, and review should live. • The build versus buy equation is changing because some tools that were too expensive to build before may now be realistic to create internally. Timestamped Highlights 00:31, Yahoo’s mission and why the internet still feels hard to navigate 02:01, Where AI fits across Yahoo products and engineering work 03:30, The challenge of moving from on prem data centers to cloud based infrastructure 05:27, How Yahoo has used AI to rebuild internal tools and leave technical debt behind 07:25, Why agents need access to engineering context, not just code 10:20, AI as a coworker and the shift from human speed to machine speed 16:27, Why parts of the SDLC may need to change as AI increases delivery speed One Line That Stuck “AI as a coworker, not just as a tool.” The Tech Trek is for technical leaders thi...

Why AI Founders Need to Say No Faster

19 min

Mike Choi wanted to work at Apple for years. Then he got there and had the moment many ambitious builders eventually hit. Is this the thing I was sprinting toward? In this episode of The Tech Trek, Mike Choi, co founder at Koah, shares his path from Korea to the United States, mandatory military service, Apple, Twitter, and eventually building Koah, an AI monetization company helping AI app builders create sponsored experiences. The conversation is less about the glamour of startups and more about what founder work actually demands: making decisions without complete information, learning from Big Tech without copying it, and staying focused when AI moves faster than your team can absorb. Practical Takeaways • Big Tech can teach you strong operating patterns, but startups force you to build your own style. • Founder decisions rarely come with complete data. Moving creates the next data point. • In AI startups, speed can become a distraction if every new tool or feature changes the plan. • Clear vision helps teams make decisions without waiting on the founder. • Knowing when to share an idea matters as much as having the idea. Timestamped Highlights 00:38, Mike explains Koah and why AI products need new monetization models. 02:25, Mike shares how his father’s Korean Air Force service brought him to the United States as a child. 05:01, Mandatory military service, pausing college, and learning to code around strong engineers. 07:29, The long term goal of working at Apple and the unexpected feeling after getting there. 10:57, Why Mike chose to build from scratch instead of staying on the Big Tech path. 14:05, What Big Tech did and did not prepare him for as a founder. 17:03, The founder lesson of making decisions before the full picture is clear. 19:35, Why AI startups move so fast and how shiny object syndrome drains energy, time, and attention. One Line That Stuck “Just make the decision, produce data points that way through actions, and make a better decision...

Why Sovereign AI Matters Now

29 min

AI is moving fast, but the bigger question for companies and governments may be control. Who owns the data, the workflow, the output, and the risk? In this episode, Amir talks with Shaun Modi, cofounder and CEO of Capitol AI, about sovereign AI, shadow AI, model dependency, government use cases, and why organizations need repeatable, governed, auditable workflows before AI becomes part of core operations. Shaun also brings a design lens to the conversation, connecting AI adoption to user experience, voice interfaces, and the next wave of AI in the physical world. Practical Takeaways • Sovereign AI means having control over your data, outcomes, upside, and risk. • Shadow AI creates short term productivity, but can also create silos, governance gaps, and data exposure. • Organizations need repeatable, governed, auditable AI workflows, especially in regulated environments. • Model independence matters because model costs, performance, and capabilities keep changing. • Design will come back into focus as AI systems become more powerful and more embedded in work. Timestamped Highlights 00:40, What Capitol AI does and why decision ready artifacts matter 01:50, Shaun defines sovereign AI in plain language 02:36, The intelligence paradox, more data, less control 04:15, Why shadow AI can become a governance and accuracy problem 10:29, Zero data retention, model independence, and evaluation criteria 17:53, Why AI user experience may be entering a new design cycle 25:56, Where AI may create major impact in the physical world One Line That Stuck “Companies and governments have more data than ever, but they are losing control over the outcomes.” Practical Takeaways For Teams If AI is moving into real business processes, start by asking what needs to be controlled. Data rights, model choice, accuracy standards, workflow governance, and auditability all matter more once AI is producing work that affects customers, citizens, or critical operations. Follow The Tech Trek f...

See all 200 episodes

–

0 ratings from members

5
4
3
2
1

Rate this podcast

Log in to rate and review the shows you listen to.

No reviews yet — be the first member to rate "The Tech Trek".

This podcast, its content and its artwork are not owned by, affiliated with, or endorsed by Castquire.

Keep listening

Discover more podcasts like this.

Up next

  1. Nothing queued. Use + Queue on any episode to line it up.

0:00 0:00