Nithish Subramaniyan — Backend Engineer

I build systems that keep working when things get complicated.

Focused on
Systems.

Backend engineer focused on cloud-native platforms, distributed systems, event-driven architecture, serverless computing, and production reliability.

View my workHow I think

Architectural domains

  • Backend Engineering
  • AWS
  • Distributed Systems
  • Serverless
  • Event-Driven Architecture
  • AI Systems
System overviewLive diagram

Hover a layer to see how it handles load, failure, and scale.

I don’t just build APIs. I think about what happens after they fail.

01

System thinking

I focus on how services interact, where systems fail, and how architecture behaves under real-world conditions.

02

Reliability

Retries, failure modes, observability, scalability, and recovery are part of the design, not an afterthought.

03

Data flow

Understanding how data moves through a system is as important as writing the code that moves it.

04

Product impact

Technology matters when it improves speed, reliability, customer experience, cost, and operations.

Selected work

Each case study is a short engineering story: the problem, the system, the decisions, and what changed.

Before I write code, I map the system.

  1. 01

    Understand the flow

    Where does the request start? Where does the data move? Where can it fail?

  2. 02

    Find the pressure points

    Traffic, latency, dependencies, data consistency, and failure modes — the places a system actually breaks.

  3. 03

    Design the system

    Sync vs. async. Monolith vs. services. Queues, events, caching, and where state actually lives.

  4. 04

    Plan for failure

    Retries, timeouts, dead-letter queues, fallbacks, and the observability to know which one fired.

  5. 05

    Optimize for reality

    Cost, scale, operations, maintainability, and the developer experience of the people who own it next.

Interactive architecture simulation

Let’s break the architecture.

This is a conceptual model, not a production system — it exists to show how the pieces are meant to behave under stress.

Client
API layer
Queue
depth: 1
Service A
Service B
Data layer

Event log

› Simulation ready. Traffic is steady, all services healthy.

Experience

TeleApps

January 2023 — Present

Software Engineer

Building backend systems for enterprise workloads.

  • Cloud-native modernization of legacy workflows
  • API and microservice design
  • Event-driven and serverless systems
  • Real-time processing and production reliability

TeleApps

January 2022 — December 2022

Software Engineer Trainee

Learning the systems, conventions, and failure modes of a production codebase.

  • Backend feature development
  • Debugging and root-cause analysis
  • Working directly with production incidents

Education

Bachelor of Commerce — Corporate Secretaryship & Computer Applications

What’s shaped the engineering more than the degree is the work itself: shipping production systems, owning incidents, and learning architecture by making it hold up under real load.

Career progression

  • Software Engineer Trainee

  • Software Engineer

  • System Ownership

Technical domains

Cloud architecture

  • AWS
  • Serverless
  • Amazon S3

Distributed systems

  • Event-driven architecture
  • Microservices
  • Async processing
  • Event streaming

Backend engineering

  • API design
  • System design
  • Data flow
  • Reliability

AI systems

  • Amazon Lex
  • Amazon Bedrock
  • Intelligent routing
  • AI-powered workflows

Production engineering

  • Failure handling
  • Performance
  • Scalability
  • High availability
  • Cost optimization

Things I think about when nobody asks.

  • Why systems fail in productionComing soon
  • Designing APIs for real-world scaleComing soon
  • When serverless is the wrong choiceComing soon
  • Event-driven architecture without the buzzwordsComing soon
  • Retries are harder than they lookComing soon
  • How I think about system design interviewsComing soon
Simple systems are rarely simple. They are usually the result of difficult decisions.

I enjoy breaking complex systems into understandable pieces, finding the pressure points, and designing software that survives real-world usage.

30 seconds?

Download resume
Role
Backend Engineer
Focus
Cloud-native systems
Strength
System architecture
Experience
Enterprise systems, 2022 — Present
Specialties
  • Distributed systems
  • Serverless
  • Event-driven architecture
  • AWS
  • AI systems
Looking for
  • Product engineering
  • Backend engineering
  • Platform engineering
  • Cloud systems
  • AI infrastructure

Let's build something that has to work.

I'm interested in solving difficult backend and infrastructure problems where architecture, reliability, and scale actually matter.

Start a conversationLinkedIn →Email →