About

I'm an engineer in Bengaluru. Right now I build GenAI systems at EY, pulling structured data out of US tax and property documents. That sounds narrow until you find out there are fifty states and more than a thousand counties and none of them agree on what a form should look like.

Before that I spent two years rebuilding infrastructure at a healthcare startup in Singapore. Four internet-facing Linux servers became forty-odd hardened ones. SSL went from a D rating to A+. The Windows stack moved to Docker with a pipeline behind it. When I started we were investigating a crash two or three nights a month. Over the two years after, it happened about once. All of it ran on open source, which saved a few thousand dollars a month and was also just more interesting to work on.

Before that I was in a bank's IT department. That's where I actually learned to build things.

Operators there were moving reports branch by branch, pasting credentials and paths out of a spreadsheet, because the tool had no batch mode. Seven hundred branches. Every day. I wrote a Python TUI that pulled each branch's config from the database and synced its reports in sequence. Nothing clever about it. A loop and a config lookup that nobody had been given the time to write.

The other one was search. Fraud investigations meant digging through a few hundred gigabytes of daily and weekly reports, in files too large for any editor on those machines to open, so the work took most of a day. I put a Python front end over a C-backed search library and it came down to two or three hours.

Both are still running. I left in 2023. That's the part I'm proudest of and it never fits on a résumé.

The thread through all of it is that I care how a system behaves at 2am, not how it demos. That's a cloud engineer's instinct and I've kept it through the move into AI, which is a field with a demo problem.

Lately I've been going deeper into agentic systems. LangGraph, multi-agent memory, keeping state honest across turns. On the side I'm building an open source calendar, a finance manager, and a single-binary resource monitor, mostly because I wanted them to exist and to be small.

This site is where I write things down. Notes are short things I learned and didn't want to look up twice. Runbooks are steps I've actually run on a real machine, with the date I last ran them. Writing is longer and has an argument.

Reach me at kiran@kiranetic.com.