“How Ankur Mattoo Built the AI Foundations That Made Enterprise Machine Learning Scalable”

“How Ankur Mattoo Built the AI Foundations That Made Enterprise Machine Learning Scalable”

EPISODE SUMMARY: In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Ankur Mattoo, technology leader, architect, and AI practitioner, to discuss why the most successful AI initiatives begin years before generative AI ever reaches production. While helping build the machine learning foundation at Iterable, Ankur faced a challenge common to many fast-growing SaaS companies: enormous amounts of customer data with little consistency. Serving enterprise customers across industries including DoorDash, Spotify, Zillow, and many others, the platform collected highly diverse datasets that were invaluable for marketers—but extremely difficult to transform into scalable machine learning systems. Rather than rushing to deliver ambitious AI products, Ankur made the strategic decision to invest in foundational infrastructure first. By introducing an incremental product strategy through a feature called Brand Affinity, his team demonstrated immediate business value while quietly building the feature engineering pipelines, machine learning platform, and data foundation that would later support far more advanced AI capabilities. The conversation explores why strong data architecture, feature stores, and semantic understanding remain essential for successful AI deployments—even in the era of large language models. Ankur explains why organizations that skip foundational investments often struggle to deliver meaningful AI outcomes, while those that balance short-term wins with long-term infrastructure create lasting competitive advantages. For engineering leaders building AI platforms, this episode offers practical lessons on earning organizational trust, scaling machine learning across complex enterprise environments, and making engineering decisions that continue paying dividends years later. KEY TAKEAWAYS: * Successful AI products are built on strong data foundations rather than AI models alone * Incremental product wins help secure organizational trust for long-term infrastructure investments * Diverse customer data requires scalable feature engineering instead of customer-specific machine learning models * Feature stores create reusable signals that accelerate future AI capabilities * Enterprise AI success depends on semantic understanding and high-quality data pipelines * Large language models are only as valuable as the data they can access * Engineering leaders should balance short-term product delivery with long-term architectural investments * Building AI infrastructure iteratively reduces technical and organizational risk * Strong data architecture enables future AI innovation long before it becomes visible to customers * Curiosity and continuous learning remain essential as AI technologies continue evolving CONNECT WITH ANKUR MATTOO: LinkedIn: linkedin.com/in/ankurmattoo [linkedin.com/in/ankurmattoo] Website: capgemini.com [capgemini.com] Listen Now & Subscribe: Apple Podcasts, Spotify, Amazon Music, YouTube, iHeartRadio, Captivate, or wherever you get your podcasts. "Engineering Choices You Have to Defend explores the real technical decisions behind AI systems, enterprise architecture, and scalable software engineering.

“How Gautamdev (Gautam) Chowdary Built Healthcare AI That Prioritizes Interoperability, Reliability, and Trust at Scale”

EPISODE SUMMARY: In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Gautamdev (Gautam) Chowdary, Co-Founder and CTO of Zynix AI, to discuss one of healthcare AI's most difficult engineering challenges: building intelligent systems that work reliably across fragmented healthcare environments. Rather than optimizing for a single electronic medical record (EMR) platform, Gautam and his team made the difficult architectural decision to build an EMR-agnostic platform from day one. Serving healthcare organizations that may operate hundreds or even thousands of EMR instances, Zynix AI, focuses on automating care coordination, scheduling, outreach, documentation, and operational workflows across highly fragmented systems. The conversation explores why interoperability should be treated as a reliability problem instead of simply an API integration challenge. Gautam explains how healthcare workflows extend far beyond structured APIs, requiring intelligent automation through robotic process automation (RPA), adaptive AI agents, and resilient workflow orchestration capable of handling real-world operational complexity. A major focus of the discussion is the balance between AI automation and human oversight. Rather than replacing healthcare professionals, Zynix AI, uses confidence thresholds, governance, and human checkpoints to ensure sensitive clinical and operational decisions remain accountable while AI eliminates repetitive administrative work. For engineering leaders building AI systems in regulated industries, this episode offers valuable lessons on designing deployable architectures, building trust into AI systems, and creating operationally resilient platforms that succeed in production—not just in demonstrations. KEY TAKEAWAYS: * Interoperability should be treated as an operational reliability problem, not simply an API integration project * Building EMR-agnostic architecture creates long-term scalability across fragmented healthcare environments * Healthcare AI must integrate with multiple systems beyond EMRs, including telephony, fax, scheduling, and manual workflows * AI-powered RPA creates more resilient automation by adapting to changing interfaces and operational variability * Human oversight remains essential for clinical ambiguity, regulatory accountability, and low-confidence AI decisions * Infrastructure flexibility is critical for healthcare organizations with varying compliance and deployment requirements * Deployable architecture often matters more than model sophistication in healthcare AI * Trust, governance, and operational reliability drive adoption more than raw AI performance * Engineering teams should optimize for production reliability rather than polished demonstrations * Successful healthcare AI platforms are built to survive operational complexity at scale CONNECT WITH GAUTAMDEV (GAUTAM) CHOWDARY: LinkedIn: https://www.linkedin.com/in/cgautamdevc/ [ linkedin.com/in/gautamchoudhury2007] Website: ZYNIX.ai [http://ZYNIX.ai] Listen Now & Subscribe: Apple Podcasts, Spotify, Amazon Music, YouTube, iHeartRadio, Captivate, or wherever you get your podcasts. "Engineering Choices You Have to Defend explores the real technical decisions behind AI systems, enterprise architecture, and scalable software engineering.

“How Eban Bisong Transformed Engineers into AI Orchestrators to Eliminate Delivery Bottlenecks”

Episode Summary: In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Eban Bisong to discuss how AI-native workflows are reshaping software engineering teams and changing what it means to be an engineer. While leading engineering at Part DNA, Eban faced a challenge familiar to many growing organizations: a small team supporting multiple clients, constant context switching, increasing delivery demands, and pressure to maintain quality while moving faster. Traditional approaches were no longer enough. Rather than simply introducing AI coding tools, Eban led a broader organizational transformation that redefined how work moved through the company. By integrating AI agents into engineering, support, documentation, ticket creation, code review, testing, and knowledge management workflows, the team dramatically reduced operational bottlenecks and increased delivery capacity without increasing headcount. A key part of the transformation was the introduction of an AI teammate named R2-D2, powered by OpenClaw. Initially deployed as a refactoring and code-quality agent, R2-D2 evolved into a company-wide knowledge assistant capable of supporting engineering, customer support, documentation, and operational workflows. The result was a system where AI handled repetitive execution tasks while humans focused on judgment, architecture, customer conversations, and product strategy. The conversation explores how engineering roles are evolving from writing code to orchestrating systems that generate code, why specification quality is becoming more important than technical implementation, and how organizations can build AI-native processes that improve both speed and quality. For engineering leaders, this episode offers a practical framework for moving beyond AI experimentation and building organizations where humans and agents work together to create scalable, high-performing engineering systems. Key Takeaways: • AI adoption requires a mindset shift, not just new tools • Engineers are increasingly becoming orchestrators rather than code producers • AI agents can eliminate context-switching bottlenecks across organizations • Knowledge management and specifications are critical for successful AI workflows • Support, documentation, and engineering processes can all benefit from AI automation • Verification systems must scale alongside development velocity • AI agents should be separated across testing and implementation workflows • Product thinking and systems thinking are becoming more valuable than framework expertise • Organizations should optimize for judgment and decision-making, not manual execution • Successful AI-native teams focus on improving systems rather than fixing isolated problems Connect with Eban Bisong: * LinkedIn: linkedin.com/in/ebanbisong [linkedin.com/in/ebanbisong] * Website: ebanbisong.com [ ebanbisong.com] Listen Now & Subscribe: Apple Podcasts, Spotify, Amazon Music, YouTube, iHeartRadio, Captivate, or wherever you get your podcasts. "Engineering Choices You Have to Defend explores the real technical decisions behind AI systems, enterprise architecture, and scalable software engineering.

“How Pavel Spesivtsev Argues That Knowledge Infrastructure Matters More Than AI Models”

Episode Summary: In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Pavel Spesivtsev, CTO, AI strategist, and agentic engineering practitioner, to explore why many AI-driven software initiatives fail long before coding becomes the problem. After spending the last eighteen months helping organizations implement agentic development workflows, Pavel has observed a surprising pattern: the models themselves are rarely the weakest link. Instead, failures typically emerge from incomplete specifications, missing organizational knowledge, weak governance, and poor context management. Pavel explains why traditional software development assumptions are being challenged by agentic engineering. While Agile methodologies were designed around human decision-making and implementation, AI agents require far more structured specifications and complete knowledge systems to operate effectively. When requirements contain gaps, agents fill them with assumptions drawn from training data, often leading to unexpected or incorrect outcomes. The conversation explores Pavel’s concept of “Gap Trap,” a framework designed to identify missing requirements before they enter an agentic workflow. He also discusses why knowledge bases and ontologies are becoming critical infrastructure for AI-powered development, how retrieval systems can introduce hidden hallucination risks, and why context engineering is rapidly becoming one of the most valuable skills in modern software organizations. Pavel shares his perspective on the evolution of software engineering roles as AI adoption accelerates. As implementation becomes increasingly automated, engineers are spending less time writing code and more time designing systems, orchestrating agents, validating outputs, and building the knowledge frameworks that guide intelligent systems toward reliable outcomes. For engineering leaders, this episode highlights a major shift in software delivery: as coding becomes increasingly automated, competitive advantage will come from designing better systems, creating higher-quality specifications, and building the knowledge infrastructure that enables AI agents to make reliable decisions. Key Takeaways: • Most agentic AI project failures stem from specification and knowledge gaps, not model quality • Incomplete requirements cause AI agents to make unpredictable assumptions • Knowledge bases and ontologies are becoming critical infrastructure for AI systems • Context engineering is emerging as a core engineering discipline • Retrieval systems can introduce hidden hallucination risks when information is incomplete • Software engineers are evolving from code authors into system architects and orchestrators • Agentic workflows require stronger specification practices than traditional Agile processes • Documentation is increasingly becoming operational infrastructure, not just reference material • Governance, security, and knowledge management are essential for successful AI adoption • Organizations should focus on knowledge quality before investing heavily in AI tooling Connect with Pavel Spesivtsev: * LinkedIn: linkedin.com/in/pspesivt [inkedin.com/in/pspesivt] Listen Now & Subscribe: Apple Podcasts, Spotify, Amazon Music, YouTube, iHeartRadio, Captivate, or wherever you get your podcasts. "Engineering Choices You Have to Defend explores the real technical decisions behind AI systems, enterprise architecture, and scalable software engineering.

"How Paul Baker Stopped Feature Development to Save Engineering Velocity"

Episode Summary: In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Paul Baker to discuss one of the most difficult decisions an engineering leader can make: stopping feature development in order to rebuild the engineering foundation. While working at Capshare, Paul inherited a growing product with strong market traction but a fragile engineering system plagued by regressions, manual testing, multi-day deployments, and the absence of automated quality controls. Faced with mounting production issues and increasing customer risk, Paul proposed an unconventional solution: pause all new feature development for an entire quarter and focus exclusively on improving software quality, testing, and deployment infrastructure. Paul shares how the team implemented automated testing, continuous integration, and systematic refactoring strategies to transform a legacy codebase into a maintainable platform capable of supporting future growth. He explains why engineering foundations are often the true drivers of delivery velocity and how technical debt can quietly undermine even successful products. The conversation also explores the evolving role of AI in software development, including the use of LLMs to accelerate legacy system modernization, generate large-scale test suites, and support engineering workflows. Paul offers practical insights into the limitations of agentic coding systems, the importance of prompt accuracy, and why human oversight remains essential as AI-assisted development becomes more common. For engineering leaders, this episode provides a powerful reminder that sustainable innovation depends on confidence in deployment, disciplined engineering practices, and investing in the foundations that make rapid delivery possible. Key Takeaways: • Engineering velocity depends on strong testing and deployment foundations • Pausing feature development can sometimes accelerate long-term delivery • Automated testing reduces production regressions and deployment risk • Legacy systems can be modernized through incremental refactoring strategies • Continuous integration creates confidence in software changes • Golden master testing can help stabilize complex legacy applications • AI can dramatically accelerate test generation and modernization efforts • Agentic coding systems still require human guidance and oversight • Deployment anxiety often reveals gaps in engineering infrastructure • Successful engineering organizations continuously invest in foundational quality Connect with Paul Baker: * LinkedIn: linkedin.com/in/pbaker3 [linkedin.com/in/pbaker3] * Website: paulbaker3.com [paulbaker3.com] Listen Now & Subscribe: Apple Podcasts, Spotify, Amazon Music, YouTube, iHeartRadio, Captivate, or wherever you get your podcasts. "Engineering Choices You Have to Defend explores the real technical decisions behind AI systems, enterprise architecture, and scalable software engineering.