Hi, I’m Nitya, an AI engineer.

I build AI agents that hold up in production.

Most of my days go into LLM agents: the MCP connectors they use, the evals that tell me they work, and the guardrails that keep people safe. I like the quiet part of the job, where I prove something works before anyone has to trust it.

Resume See my work
Nityashree S, smiling

Selected work

support-agent · logs

✕ turn failed · bad skill header

✕ turn failed · bad skill header

✓ test · bad header refused on save

✓ fixed · agent answers again

Case 01

An agent went offline. I found the one file that did it.

Building an AI agent platform. The engine, studio and gateways behind company-wide AI agents, and how I kept them running.

Read the case study
agentgatewayconnectorappvault · your own token
Case 02

Agents that see only what you’re allowed to see.

Building MCP connections. Connectors that let agents use real apps with each person’s own access, never a shared key.

Read the case study
edgeidentitytenantblockedmodelsandboxdependencies
Case 03

I attacked our agents before anyone else could.

Security across an agent fleet. Every layer closed by default, and every fix proven by replaying the attack.

Read the case study

How I work

One laptop, a team of agents,
and me in the loop.

I don’t hand-write code. I direct AI coding agents, and I prove every change before it ships. Subagents research, challenge and review in parallel, while I set the bar, read every line and own what goes out.

I like working close to the people who use what I build: real questions from Sales and Business Development shaped how I tested, and finance’s own rules shaped the agents I built for them.

  1. Plan
  2. Delegate
  3. Prove
  4. Own

Tools I work with: Claude Code and Claude Design every day, plus Cursor, DeepSeek and Grok. Personal agents in Slack run my pull-request workflow. My side projects, an LLM gateway and a multi-agent research API, are on my GitHub.

--:--
MacBook Proconnected

Running now

plannersplitting the task
coderqueued
reviewerqueued

Branches

feat/guest-accesstests pass · across services
fix/untrusted-fence-on-trimcoder · fence kept on trim
feat/mcp-connectorverified on dev
fix/tool-gateway-timeoutsin review

My path

From payments data to production AI.

  1. Studied

    Computer science, with a focus on AI and data science, at SASTRA University.

  2. Payments data

    I looked after the payments data an AI assistant answered from, and learnt how much an answer depends on its data.

  3. Testing AI

    I tested that assistant before launch and caught its wrong answers. That’s when AI engineering clicked for me.

  4. Shipping agents

    Then I moved to building and securing AI agents that people rely on at work: the platform, the tools and the guardrails.

When I’m not working

Away from the screen: books, classical dance, yoga, a stage and a mic. Everything on my desk comes with a note.

Tap anything on my desk.

Contact

Let’s talk.

An idea, a question about agents, or simply hello: I’d love to hear from you.

nityashreesundararajan@gmail.com