Tishan Yasiru

AI/ML forward deployed engineering

Tishan Yasiru

Associate AI/ML Forward Deployed Engineer, RealAIzation

I turn language-model capabilities into production systems for client organizations. As a forward deployed engineer at RealAIzation, I work inside client teams to scope the problem, build the system on their own data, and measure whether it is right.

RoleAssociate AI/ML Forward Deployed Engineer
CompanyRealAIzation, Texas, USA, since Dec 2025. Remote.
Based inColombo, Sri Lanka
DeliveredThree client systems in 2026, across nonprofit software and private credit
Contacttishanyasiru@outlook.com
ProfilesLinkedIn, GitHub

Work

Three systems built with client teams in 2026.

Clients are described by industry. None of this work is public, so each entry records what was built, my part in it, and how it was measured.

Flagship

Text-to-SQL for a nonprofit CRM

Plain-English questions answered from each organization's own live database, with every query checked before it runs.

Nonprofit CRM software
May to Jul 2026

Stack

AWS Bedrock AgentCore, Claude Sonnet, Amazon Neptune, Bedrock Knowledge Bases, Bedrock Guardrails, TypeScript, Node, MySQL, Terraform

Problem

Staff needed answers from CRM data without writing SQL or waiting on a report queue. Every organization has its own schema, questions are often ambiguous, and a wrong answer is worse than none, so every query had to be checked before it ran and every answer had to be measurable.

Built

An agent on AWS Bedrock AgentCore. A deterministic compliance gate runs before any model call and declines cross-organization asks, raw card or ID numbers, bulk exports, and out-of-domain questions. A rules-based classifier marks each question simple or ambiguous, and answers small talk, how-to questions, and the ten home-screen prompts with no model call at all. Retrieval runs two ways in parallel: a schema graph on Amazon Neptune, where business terms map to columns, tables, and domains with foreign-key expansion, and a Bedrock Knowledge Base over column and enum descriptions. Claude Sonnet writes the SQL through a single tool call, with session memory from AgentCore and a cached system prompt. The SQL is parsed to a syntax tree, recompiled, rewritten by eighteen deterministic rules, validated, and checked against an EXPLAIN cost threshold; expensive queries are detached to an export job. Execution goes through a tenant broker with a read-only session, one organization's schema, and a statement timeout. Results return as a value, a table, or a chart, with a plain-English summary from a smaller model.

Measured

94%of answers exact or correct on 100 golden questions

~5 centsof model cost per question

Graded end to end against golden SQL, each answer exact, correct, or wrong. Clarifications forced by the classifier fell from 59 to 30 of 143 questions as the glossary grew from 140 to 462 terms.

My part

Designed and built the engine's first version in June 2026: the classifier, graph and vector retrieval, the SQL validator, the executor, and the tenant broker. Later added the compliance gate and the cost gate with its export path. One of twelve engineers who have extended it since.

How a question flows

  1. 1Question arrives, with session memory from AgentCore
  2. 2Compliance gate, deterministic, before any model
  3. 3Classifier, rules only: simple or ambiguous; small talk answered without a model
  4. 4Retrieval in parallel: schema graph on Neptune, vector search over column descriptions
  5. 5Claude Sonnet writes the SQL through one tool call
  6. 6Syntax-tree parse, rewrites, validation, EXPLAIN cost gate
  7. 7Read-only query through the tenant broker; value, table, or chart

Private credit, Feb to Apr 2026

Credit-agreement extraction for a private-credit firm

Loan agreements of about 250 pages turned into structured data in the lending platform's schema, amendments included.

Problem

Facility terms sit across agreements of about 250 pages and their later amendments, too long to read in full for every loan.

Built

Each agreement's text is cached once and read by Claude on Amazon Bedrock in five schema-constrained passes: core terms, tranches, rate options, covenants and borrowing base, qualitative covenants, each validated against Pydantic models and grounded against the source text. Amendments are extracted as structured deltas, checked by regex for anything the model missed, and applied in effective-date order with a change log.

My part

Co-built with the RealAIzation team: the text extraction with OCR fallback, source grounding, the amendment overlay, the prompt rewrite, and the accuracy scoring.

Python, Claude Sonnet on Amazon Bedrock, Pydantic, PDF text extraction with OCR fallback

Nonprofit software, Jul to Aug 2026

Learning platform for a nonprofit-software company

A training academy with about 1,900 lessons, courses, and paths, and search that answers a question, not only a keyword.

Problem

A catalog of nearly two thousand items needed search that answers a question, not only a keyword match.

Built

Search powered by OpenSearch. Each query runs a hybrid semantic and keyword search, then a keyword rescue pass, fused by reciprocal-rank fusion so typos still find their target. Lesson text and video transcripts are chunked into overlapping windows and embedded, so a result can deep-link to the moment inside a video.

My part

Lead engineer, from design to delivery.

OpenSearch, FastAPI, PostgreSQL, Next.js, TypeScript

Experience

RealAIzation, since December 2025.

RealAIzation

Associate AI/ML Forward Deployed Engineer

Dec 2025 to present
Remote, Texas, USA

RealAIzation places engineers with private-equity firms and their portfolio companies to build AI systems with them. I am placed with client teams to design, build, and run language-model systems on their own data. Three client systems in 2026.

BSc (Hons) in Information Technology, specializing in Data Science

2023 to 2027

Sri Lanka Institute of Information Technology (SLIIT)

Writing

Notes on how models work underneath.

Published on LinkedIn.

About

Based in Colombo. Working inside client teams anywhere.

I started in data engineering, building ETL pipelines, and moved into language-model systems as the work shifted from moving data to answering questions from it.

Email is the quickest way to reach me.