About

About my background and technical direction.

I have worked across software engineering for years, but the work I most identify with today sits around blockchain systems, applied AI/ML, and AI agents.

Ramakrishna Kiran

About

How I would describe my background today.

The broader engineering background still matters, but the clearest through-line in my work today is blockchain engineering, applied AI/ML, and the design of useful agent systems.

I am a software engineer with more than a decade of experience across backend systems, full-stack product development, web platforms, and mobile applications. That broader foundation still matters, but the technical work I most identify with today sits at the intersection of blockchain, applied AI/ML, and agent-based software.

A large part of my interest is in how intelligent systems should actually be built in practice: retrieval, structured outputs, tool use, evaluation, observability, and the tradeoffs required to make AI systems dependable outside of demos. I am especially drawn to AI agents that can reason through tasks, use tools carefully, and operate with clear guardrails.

On the blockchain side, I care about smart contracts, decentralized system design, and the boundary between on-chain trust and off-chain intelligence. This site is where I collect my writing, technical notes, and ongoing thinking across those areas.

Expertise

Technical depth I keep coming back to.

These are the domains I spend the most time building, studying, and writing about.

AI and agent engineering

Designing AI systems that can reason through work, retrieve context, call tools, and return structured outputs reliably.

  • LLM workflows
  • Tool orchestration
  • RAG systems
  • Structured outputs
  • Prompt design
  • Evaluation loops

Applied AI and ML systems

Turning AI/ML capabilities into practical systems with attention to product quality, operational behavior, and maintainability.

  • Python
  • TypeScript
  • OpenAI APIs
  • Embeddings
  • Semantic search
  • Automation pipelines

Blockchain systems

Building with smart contracts, decentralized infrastructure, and architecture patterns where trust and system design meet.

  • Solidity
  • Ethereum
  • Ethers.js
  • Web3.js
  • Hyperledger
  • Upgradeable contracts
  • DeFi
  • Identity systems

Broader engineering foundation

The wider engineering base behind the current focus areas, shaped by years of shipping products across backend, web, and mobile.

  • Next.js
  • Node.js
  • PostgreSQL
  • Docker
  • AWS
  • Web platforms
  • Mobile products

Approach

How I think about the work.

A few principles that show up repeatedly in how I build, evaluate, and write about systems.

I care more about production behavior and system clarity than demo-only polish.

I am interested in agents that can do real work with context, tools, and feedback loops.

I like combining AI capability with disciplined engineering and evaluation.

I see blockchain as infrastructure and system design, not as branding language.

I use writing as a way to sharpen technical thinking and document tradeoffs.

My broader web and mobile background still helps me think end to end.