Suraj LabAmazon software engineer building backend systems and side projects.

Suraj · Software Engineer at Amazon

Experienced backend software engineer.

My day job is backend engineering: distributed systems, Java microservices, and AWS-backed services that operate at scale. Separately, I build side projects like pai, coding-agent, and related memory systems work.

Role

Amazon · Software Engineer

Side projects

Independent projects include pai, personal-knowledge-base, coding-agent, and memory systems experiments.

Distributed SystemsJavaAWSMicroservices

Agent-ready content

Public profile data for AI tools, crawlers, and search systems.

Side Projects

Things I’m working on.

Side projects and independent systems work outside my full-time role at Amazon.

Other side projects and threads

Public repository

personal-knowledge-base

A local-first knowledge base with markdown notes in `kb/`, a shared core library, a Next.js UI, a `kb` CLI, MCP tools, optional S3 sync, and local semantic search.

Active thread

Memory Policy

How memory persists, flows, and stays inspectable across multiple agents.

Public repository

coding-agent

A Claude Code plugin for building software end to end with five agents, deterministic gates, runtime evaluation, and a dedicated diagnosis mode.

Direction

The broader direction is a local-first Personal AI platform with specialized agents for finance, research, and visualization, backed by full-text search and deep MCP tool integration.

Approach

How I think about systems.

The throughline is backend systems discipline: explicit contracts, operational rigor, and architecture that stays inspectable under repeated use.

Foundation

Backend / Java / AWS

Production-grade backend engineering

At Amazon I have worked across retail, AWS, and robotics systems, primarily building and operating Java microservices on AWS with a focus on scale, reliability, and operational clarity.

Focus

Agents / Memory / Architecture

Agent infrastructure as a real systems problem

Independently building reusable multi-agent memory architecture in TypeScript, using event-sourced ideas, append-only logs, read and write separation, search, and MCP tooling.

Method

Strategy / Systems Thinking / First Principles

First-principles thinking across domains

The same rigor applied to code shows up everywhere else: decomposing systems, challenging defaults, and building independent models instead of borrowing inherited assumptions.

Experience

My main line of work is Software Engineer at Amazon. The side projects above are separate and draw on the same backend systems discipline.

Timeline

  1. Aug 2016 - Present

    Amazon · Software Engineer

    Worked across retail, AWS, and robotics teams at Amazon since 2016, primarily building distributed Java microservices and AWS-backed systems with a focus on scale, reliability, and production rigor.

  2. Education

    The University of Texas at Arlington · MS in Computer Science

    Graduate study in computer science, with the foundations that later shaped my work in distributed systems, cloud infrastructure, and software architecture.

Approach

Software Engineer at Amazon. Outside work, I build side projects around memory, orchestration, and reliable software systems.

  • Production systems need explicit contracts, observability, and operational rigor.
  • Side projects should solve real systems problems, not just stage demos.
  • I work from first principles instead of inherited AI defaults.

Writing

Writing on continuity, memory, and reliable agent systems.

The archive is organized into two tracks: systems with continuity and reliable agent systems.

Archive

10 essays across 2 tracks.

The archive is split into two active tracks: systems with continuity and reliable agent systems.

Open writing archive

Contact

Open to conversations around backend systems and agent infrastructure.

I’m especially interested in conversations around backend architecture, agent infrastructure, memory systems, and orchestration.