The Tech Trek

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.

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 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.

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.

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.