open to opportunities

Shyam

Backend Engineer • DevOps • Full Stack

I build backend systems, full stack applications, and deployment workflows with a focus on clean architecture and practical engineering.

$
View Resume
2+
Freelance Projects
10+
Projects shipped
Coffee consumed
Shyam — Backend Engineer
uptime
99.99%
latency
< 12ms
scroll
01 / about

Building backend systems — one layer deeper at a time

I'm a backend-focused developer drawn to the parts of software most people don't see — how services are structured, how deployments work, how systems hold up when things go sideways.

Started with full stack, gradually moved toward backend architecture and DevOps. Currently going deeper into Go, distributed systems, and what it actually takes to run things in production.

terminal
$kubectl get pods -n justship
>deployment-worker 2/2 Running 0 1d
>api-service 1/1 Running 0 3h
$redis-cli XLEN deploy-events
>(integer) 3821

Distributed Systems

Exploring how services talk to each other — queues, workers, event streams, and the patterns that keep things from falling apart at scale.

Cloud Infrastructure

Getting comfortable with AWS — containers, storage, networking. Still learning, but building things that actually run in the real world.

Deployment Pipelines

Docker workflows, CI/CD setups, and the satisfying moment when a push to main just... ships itself.

Production Engineering

Less about writing code, more about what happens after. Logs, failures, recovery — the unglamorous part that actually matters.

03 / projects

Selected Work

Things I've built — personal and client.

Personal

JustShip

Deployment Orchestration Platform

A self-hosted deployment platform that automates build, versioning, and hosting — inspired by how Vercel works under the hood.

Worker ArchitectureRedis Pub/SubEvent StreamingCDN
Feb 2026 – Present
  • 01Docker-based build pipeline with automated versioning and hosting via AWS S3 + CloudFront CDN
  • 02Redis (BullMQ) queue-driven worker system with real-time log streaming over WebSockets
  • 03Version management, environment variable handling, and CDN caching for optimized delivery
Node.jsDockerRedisBullMQWebSocketsAWS S3CloudFrontNext.jsNginx
Freelance

Laridae

Multi-Category E-Commerce Platform

A scalable multi-category e-commerce platform built for a real client — full stack, production deployed.

SSRISRRBACFull Stack
Jul 2025 – Present
  • 01Next.js with SSR and ISR for performance and SEO across product catalog pages
  • 02Secure authentication, role-based access control, and admin dashboard workflows
  • 03REST API design with MongoDB, optimized for real-world e-commerce usage patterns
Next.jsTypeScriptMongoDBREST APIsSSRISR
Freelance

Goldfinch Teas

Real-World Tea Brand E-Commerce

Full-stack e-commerce platform for an actual tea brand — from product catalog to checkout and order tracking.

Full StackPayment IntegrationOrder Management
Mar 2025 – July 2025
  • 01Product catalog, cart, checkout, and full order lifecycle management
  • 02REST APIs with Node.js and Express, MongoDB schemas designed for scale
  • 03Razorpay payment integration with order tracking and admin product management
Node.jsExpressMongoDBRazorpayREST APIs
02 / skills

Tools & Technologies

What I've actually built with.

Backend

6 technologies
GoNode.jsREST APIsWebSocketsgRPCExpress
actively working with
04 / architecture

How I Think About Systems

Less a rulebook, more a set of habits picked up from building and breaking things.

01

Design for failure

Things break. I try to think about what happens when they do — retries, fallbacks, and not letting one bad service take everything else down with it.

retry(maxAttempts: 3, backoff: exponential)
02

Make it observable

Logs and errors are the first thing I reach for when something goes wrong. Good observability is what separates a frustrating debug from a quick fix.

log.Info("event", "latency", duration, "status", code)
03

Automate the repetitive

If I find myself doing the same thing twice, I try to script or pipeline it. CI/CD, build steps, deploys — the less manual the better.

on: [push] → build → test → deploy
04

Keep it simple to run

A system that works is only useful if someone can operate it. I try to keep configs readable, deployments predictable, and surprises rare.

// simple to run > clever to read
Deployment Pipeline
● typical flow
git push
Trigger
run tests
Validate
docker build
Package
lint & test
Validate
kubectl apply
Deploy
health check
Verify
05 / contact

Let's connect

Open to backend roles, DevOps-oriented work, and projects worth building. If something I've worked on caught your eye — feel free to reach out.

Currently available for new opportunitiesIST • UTC+5:30