About Me

Hi, I'm Gaurav — a software engineer who enjoys understanding how things work and turning ideas into useful software.

I learn best by building. Instead of studying technologies in isolation, I like to take a real problem, design a solution, build it, and then improve it as I discover new challenges.

What I Do

My interests are centered around software engineering, backend systems, AI, system design, and building products.

I enjoy working on problems such as:

• Designing backend systems and APIs
• Building scalable and reliable applications
• Understanding databases and distributed systems
• Working with AI, LLMs, and agentic systems
• Designing SaaS products
• Turning ideas into working products
• Improving performance, reliability, and developer experience

What I'm Learning

I'm continuously expanding my understanding of modern software engineering.

Some of the areas I am currently exploring include:

AI & Agentic Engineering

I'm interested in building applications that use LLMs, tools, agents, workflows, and automation to solve practical problems.

The goal is not simply to call an AI API, but to understand how reliable AI-powered systems can be designed, evaluated, deployed, and scaled.

Backend Engineering

I'm interested in APIs, databases, authentication, asynchronous processing, caching, queues, and the architectural decisions required to build reliable backend systems.

System Design

I enjoy understanding how systems behave as they grow.

This includes topics such as:

• Scalability
• Availability
• Consistency
• Caching
• Load balancing
• Database design
• Distributed systems
• Fault tolerance
• Observability

Product Engineering

I also want to become better at taking an idea from an initial concept to a real product.

That means thinking about more than code:

• Who has the problem?
• What is the simplest useful solution?
• How should the product work?
• How should the system be designed?
• How can it scale?
• What should be measured?
• How can it eventually become a sustainable business?

How I Learn

I prefer learning through projects.

A typical learning cycle for me looks like:

Idea
  ↓
Build a simple version
  ↓
Understand the underlying technology
  ↓
Find the limitations
  ↓
Improve the architecture
  ↓
Add reliability and scalability
  ↓
Measure the result
  ↓
Document what I learned