← All speakers

Bio, Work & Ideas

Rania Khalaf

Conference affiliation: Chief AI Officer · WSO2 · 2026

On this page

Rania Khalaf is Chief AI Officer at WSO2, where she leads AI strategy and agent-platform development. Her career spans distributed business processes, cloud-based deep learning, and AI for biological discovery. Across that work, she has addressed the infrastructure and organizational changes needed to turn research into systems people can use.

From distributed workflows to AI platforms

Khalaf earned bachelor’s and master’s degrees from MIT and a PhD from the University of Stuttgart. At IBM, her early research addressed how independently operated systems could carry out a shared business process reliably.

She co-authored research on implementing BPEL, a language for composing web services into workflows. Her subsequent work with Frank Leymann examined distributed business processes: splitting a workflow across participants while preserving its behavior, including loops and recovery. Their coordination approach used protocols to make separately executing fragments behave like the original process. Dividing the work required preserving the relationships between its pieces.

As her focus expanded into cloud computing and AI, Khalaf took on AI engineering leadership at IBM Research, connecting research with commercial Watson products and open-source initiatives.

Her collaborative research treated deep learning as a service as a systems problem. She co-authored the IBM Deep Learning Service paper, which described infrastructure for running learning frameworks across cloud resources. A distribution layer coordinated training across machines, while resource provisioning managed jobs on CPUs and GPUs. She also co-authored work on FfDL, an open-source, multi-tenant training platform designed to balance reliability, scaling, flexibility, and efficiency. That work examined scheduling performance alongside the costs and failures encountered when operating a shared platform.

Building computing capabilities for seed design

Khalaf subsequently became Chief Information and Data Officer at Inari, where she built the company’s digital and AI organization, including deep-learning and knowledge-graph platforms for gene discovery. Inari’s technology platform combined predictive design with multiplex gene editing to develop seeds with improved productivity and resource use. It addressed interacting biological pathways through multiple edits rather than a single genetic change.

The move broadened her responsibility from developing technology platforms to supporting a business whose products were seeds. Computing capabilities had to serve scientific discovery and the organization around it. Her account of an agricultural-biotechnology task in which simple blob detection outperformed machine learning illustrates her practical approach: choose the method that solves the problem, even when it requires less sophisticated technology.

Making agents useful inside enterprises

At WSO2, Khalaf’s remit brings that research and operating experience together. She leads a company-wide AI strategy spanning how developers build software and how enterprises incorporate AI into their applications. Several connected ideas define this work:

  • AI for Code, Code for AI: Khalaf treats AI-assisted development and infrastructure for AI applications as connected changes. WSO2’s approach pairs tools that help developers produce software with capabilities for building, integrating, managing, and securing AI systems. Improving the coding workflow is one part of reshaping the application stack.
  • Natural programming: Khalaf advocates combining natural language with the determinism of code. In her account of this work, the aim is to make programming more expressive while developing the scalability and governance needed for AI applications. She connects this to a practical decision: how much autonomy a system should have, given its performance, limitations, and the organization’s tolerance for risk.
  • Agent identity and operational control: In writing co-authored with Asanka Abeysinghe and Sanjiva Weerawarana, Khalaf argues for an enterprise architecture that lets agents act under policy. An agent’s identity must be distinguishable from the human it represents; access to tools needs authorization; and actions need traceability. Connected observability and evaluation across APIs, integrations, models, and agents help organizations manage autonomous work within existing business systems.

Shaping the Chief AI Officer role

Khalaf’s Scientist, Architect, and Coach framework extends these technical concerns to leadership. She treats the three responsibilities as adjustable commitments whose balance depends on the company, its AI maturity, and the leader’s skills. The role must accommodate both technology development and the work of helping an organization adopt it.

Her measurement choices follow the same logic. She rejects token consumption as her measure of progress and instead tracks workforce AI fluency, depth of adoption, products that agents can consume through interfaces such as MCP servers and CLIs, and AI revenue. These measures connect investment to changes in how people work and how products reach customers. She also emphasizes strong CEO backing: a broad AI remit needs organizational support to become an effective role.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Rania Khalaf explains how company type, AI maturity and personal strengths shape the Chief AI Officer role—and how to measure useful change without turning token consumption into the goal.

  • Shape the Chief AI Officer role around company type, AI maturity and personal strengths. Scientist, architect and coach describe both an allocation of work and ranges within that work.
    1:12 ↗
  • Start with the operation that needs help. In the corn embryo example, basic blob detection supplied the needed measurement without machine learning.
    11:14 ↗
  • Measure distributed AI fluency, adoption depth and useful outcomes. Token consumption is easy to game, and the measurement set should change as the company matures.
    12:52 ↗
  • Agent use changes product interfaces, documentation and pricing. Internal product use also needs a feedback loop that leads to improvements.
    15:18 ↗
  • Cross-company AI leadership needs strong CEO support, while a sustainable personal mandate needs work that fits the leader’s skills and interests.
    20:00 ↗

References