Julian's journey from chemistry to AI leadership, how GenAI is reshaping data engineering at Matillion, and practical lessons for leaders.
In this episode of The Executive Outlook, we speak with Julian Wiffen, a senior leader in AI and data science at Matillion. Julian is known for taking AI out of theory and turning it into practical tools that real teams can use, especially in data engineering, where speed, accuracy, and usability matter. His journey and examples offer a grounded view of what GenAI can actually deliver today, how it’s changing ETL, and what leaders should focus on to get measurable value.
Julian’s path into AI started unexpectedly. He studied chemistry, and in his final year (a research-focused master’s year in the 1990s), he chose a project in computational chemistry, a relatively new area at the time. His work involved genetic algorithms, experimenting with ways to “breed” solutions that could map input variables to outputs and predict behavior. He recalls the excitement of being able to extract fundamental relationships like the gas laws, something that seems trivial now but was a major milestone then. That early exposure gave him two things that shaped his career: comfort with data-heavy experimentation and an interest in prediction and optimization that later became central to machine learning.
Prefer to listen on the go? Tune in to the full podcast episode on Spotify below:
After university, Julian went into management consulting, where he stayed close to data—data warehousing, heavy analytics, and early ML at the edges. Like many professionals, he didn’t start as a “data scientist.” His early work was largely BI and data engineering: getting raw, inconsistent data into warehouses and preparing it for reporting. It’s the unglamorous but essential work that enables everything else. He also spent time contracting, which offered great hands-on delivery and variety, but he noticed a common drawback: contractors often don’t get to see whether the solution they built becomes business-critical or ends up unused.
Watch the full conversation on YouTube by clicking the link below:
Julian then spent several years at Cisco in data-focused roles, including leadership across software/IT teams. One major area was Cisco’s service catalog—the system people used to order services such as infrastructure (on-prem or AWS) and other internal IT capabilities. A key discovery from that work was counterintuitive: when you make provisioning easy, people tend to over-order less. Julian describes it with a simple analogy: if you live next door to the supermarket, you buy what you need; if it’s far away, you stock up and waste more. Translating this to enterprise services, making ordering clear and convenient reduced excessive capacity requests and helped avoid unnecessary infrastructure spending.
After years at larger companies, Julian decided to join Matillion. He described a difference many leaders feel: in big organizations, you can spend more time making the case to experiment than it would take to do the experiment. In a startup/scale-up environment, there’s often more hunger to move quickly, take risks, and learn through action. His lesson for GenAI innovation was direct: progress often comes from “just doing stuff.” Sometimes it’s faster to build and learn than to wait for perfect alignment. At Matillion, Julian’s role was to explore how AI could improve the product—both by understanding how customers use it and by embedding AI capabilities into the software Matillion provides to data engineers.
At Matillion, Julian and his team recognized early that GenAI enables a major shift in data engineering : unstructured data becomes usable. Suddenly there’s real value in processing text documents, audio, video, messy wikis, and other formats that traditionally never entered corporate warehouses. Instead of leaving that information buried in file shares (or requiring analysts to manually read and summarize it), large language models can help extract structured insights—making unstructured data something the business can actually measure, query, and act on.
Julian emphasizes a simple method that makes GenAI far more dependable in pipelines: constrain the output. Instead of asking open questions, ask the model for structured decisions—often yes/no answers. For example, given thousands of customer reviews, you can ask:
Those answers become clean, measurable fields that can feed dashboards and workflows. This approach helps teams process large volumes quickly and send humans only the items that truly need attention.
A turning point in Matillion’s AI journey came from an internal surprise. Matillion pipelines, built via drag-and-drop components and parameters (joins, filters, aggregations), are stored behind the scenes in a YAML format. The team didn’t expect LLMs to handle it because the YAML configuration is internal to the product, but because YAML is human-readable, the models could read and edit it effectively. That discovery unlocked a major leap: an assistant could go beyond “explaining” pipelines and actually help build and modify them. This became a foundation for Matillion’s copilot approach and ultimately Maia.
Julian frames Matillion’s work in two buckets:
This matters because it clarifies where value comes from: not just a chat interface, but real workflow acceleration and better data outcomes.
One strong example was a customer support workflow. Incoming support tickets are processed through a pipeline that uses RAG (retrieval-augmented generation) against documentation, known issues, and internal knowledge. The system then drafts a first-response email that a support agent can copy, edit, or reject. The big learning wasn’t just that it saved time; it also revealed a foundational truth: ambiguous documentation creates ambiguous answers. In one memorable case, the model answered “yes” to a connector capability, and even humans were split when reading the docs. The final truth was “no,” but the documentation was vague enough that both people and the model were misled. The takeaway was clear: if you write documentation clearly for humans, it becomes far more effective for AI systems too.
Julian described a customer in financial services that must process large volumes of regulatory feedback every year and a manual process consuming thousands of person-hours. The data is mostly free text, which historically makes analysis slow and inconsistent. The solution followed a practical multi-pass approach:
This created far more insight than an “average” sentiment score. A single response could be strongly positive about advice quality but highly negative about fees—insight that gets lost when sentiment is averaged into one number.
Another interesting example was a medical app concept: patients record daily voice notes describing symptoms during a clinical trial. The system transcribes the recording and asks structured questions (e.g., medication taken, appetite, mood indicators). Two benefits stood out:
On the “AI in the product” side, Matillion built Maia, a product-embedded assistant. Users can type requirements in natural language—connecting to APIs using their documentation, building transformations, generating pipeline steps, explaining logic, and helping debug issues. Julian notes Matillion had an earlier copilot precursor focused more on transformations and later launched Maia in June as a more advanced and accurate version.
Julian shared quantified customer outcomes. In one “bake-off” at a large pharmaceutical company, two engineers built the same complex pipeline:
Other customers reported 5–10x productivity gains across teams. In one case, a customer said they planned to hire five additional engineer but instead hired one because the assistant removed so much repetitive workload. He also highlights modernization: LLMs are “polyglot,” so they can interpret older tools and languages. Teams can take legacy Informatica jobs, Talend jobs, or long SQL scripts, ask the assistant to explain them in plain language/pseudocode, and then rebuild them in Matillion. A graphical pipeline makes it easier to validate logic step-by-step.
Julian also mentioned an unexpected benefit: Maia can effectively support multilingual interaction. Users can request responses in languages like German, Arabic, or Urdu. Without heavy localization work, this reduces friction for global users who otherwise must translate their work into English mentally while using software.
Looking ahead, Julian Wiffen believes data engineering will shift in two major ways:
Data engineers will increasingly work with messy formats—transcripts, videos, wikis, audio—and convert them into something structured and useful for analytics and AI.
As “chat with your data” tools grow (text-to-SQL, conversational BI, assistants), success depends on well-curated schemas and context:
Julian believes data engineers will spend more effort not just wrangling data, but ensuring documentation, semantics, and “gold layers” are well organized so both humans and ML systems can use them reliably.
Julian’s guidance is practical:
Julian Wiffen’s story—from computational chemistry to AI product leadership—highlights a consistent theme: the most valuable AI is the AI that becomes a daily tool for real teams. At Matillion, that shows up in two ways: GenAI-driven pipelines that structure unstructured data and product-embedded assistance through Maia that accelerate how data engineers build, debug, and modernize pipelines. His message is clear: try things, constrain outputs for reliability, invest in documentation and context, and let domain experts define what “good” looks like. That’s how AI moves from demos to durable business impact.
For more stories of leaders shaping the future of data, AI, and strategy, stay tuned with The Executive Outlook.
Listen in for business strategies and interviews with business experts to help you build a business and a life that you love.
About Us
