Skip to content
gctamizharasan@gmail.comDownload résumé ↓
Hop 00 — HandshakeShips full-stack products.
Understands the network under them.

TamizharasanG CEngineer

Four products in production · MERN · AWS · Docker · Protocol-level networking

HOP 01PayloadWho is being transmitted

I build products end to end — and I understand the network they run on.

PositioningFull-stack engineer
FocusMERN · Networks · Cloud
StatusMSc candidate · Intern
BaseCoimbatore, IN
Tamizharasan G C, full-stack engineer
Tamizharasan G CCoimbatore, IN
01

Most of my work lives in the MERN stack: React interfaces on the front, Node and Express in the middle, MongoDB and PostgreSQL underneath. Four of those builds are in production today, serving real vendors, real employees and real clients.

02

But the layer I care about most is the one nobody sees. TCP/IP, DNS, ARP, ICMP, reverse proxies, load balancing, Kafka streams — the plumbing that decides whether a product survives contact with users.

03

I learned that layer twice: once from simulating routing protocols in NS2, and once from shipping to AWS, Docker and a handful of cloud platforms where the abstraction leaks and you have to know what is actually happening on the wire.

↳

Currently an intern full-stack developer at Lil Humans, and an MSc Software Systems candidate at PSG College of Arts & Science.

0PROD

Products live in production

2025SINCE

Full-stack intern at Lil Humans

0%*

MSc Software Systems aggregate

0CERTS

Certifications — IIT, IBM, Coursera

HOP 02TopologyProximity to the hub = depth of use

Not a logo grid. A map of what I actually reach for.

01Languages5 NODES
Python
JavaScript
C
SQL
TCL / AWK
PrimaryWorkingFamiliar
HOP 03PipelineRequirements → production, and back

How I build, in the order it actually happens.

01Ask before building

Requirements

Requirements gathering and technical documentation — the part of my internship that taught me most. A feature you understood is cheaper than a feature you rewrote.

DocumentationScoping
02React + Tailwind

Interface

Responsive component trees built mobile-first. State kept close to where it's used, layouts that hold from 360px to ultrawide.

ReactTailwind CSS
03Node + Express

API

REST endpoints with real authentication and role separation, verified in Postman before a single component consumes them.

Node.jsExpress.jsPostman
04MongoDB + PostgreSQL

Data

Document models where the shape is fluid, relational schemas where integrity matters. Media offloaded to Cloudinary rather than the database.

MongoDBPostgreSQLCloudinary
05nginx · TCP/IP · Kafka

Transport

Reverse proxy in front, load balancing across instances, event streams where services shouldn't wait on each other. Protocol-level debugging when it breaks.

nginxLoad BalancingKafka
06AWS · Docker

Deploy

Containerised builds onto EC2 with IAM scoped down and S3 for static payloads. Vercel, Render and Railway where the workload doesn't justify more.

DockerAWS EC2AWS IAMVercel
07CloudWatch · SNS · Burp Suite

Observe & Harden

Metrics and alarms so failure reaches me before it reaches a user, plus vulnerability probing with Burp Suite to find what I missed.

CloudWatchAWS SNSBurp Suite
RequirementsObservability
HOP 04Deployments4 in production · 2 foundational

Six builds. Four of them have users.

01 / 06LIVE

Lil Humans

Multi-Vendor Ecommerce Platform · 2025

ShopperReact SPA
Vendor ConsoleReact SPA
Express APIREST
AuthSessions + roles
CatalogueProducts
MongoDBDocuments
Architecture6 services · 6 paths
React.jsNode.jsExpress.jsMongoDBTailwind CSS
lilhumans.in↗

A storefront that has to keep many sellers honest at once.

Problem

A single-tenant shop is a solved problem. A marketplace is not — every vendor needs their own catalogue, their own onboarding path and their own boundary, while shoppers still experience one coherent store.

My role

Full-stack developer — interface, API and data model.

The build

MERN throughout. React storefront and vendor console, Express services behind it, MongoDB modelling products, vendors and orders as separate but linked collections.

Hard part

Scale and separation at the same time: vendor onboarding, product management and secure user authentication had to coexist without one vendor ever reaching another's data.

Outcome

Built and maintained as a scalable multi-vendor platform covering product management, vendor onboarding and secure user authentication.

Project 1
02 / 06LIVE

HR Management

Enterprise Resource Planning Platform · 2025

EmployeeClient Panel
HR AdminAdmin Panel
Express APIRole-gated
AttendanceDaily log
LeaveBalances
PayrollPayslips
MongoDBRecords
Architecture7 services · 9 paths
React.jsNode.jsExpress.jsMongoDB
hrmanagement.lilhumans.in↗

Payroll is the least forgiving feature you can ship.

Problem

HR operations at Lil Humans lived across disconnected processes — attendance, leave and payroll each tracked separately, each a source of disputes.

My role

Full-stack developer — dual-panel architecture, HR domain logic.

The build

A CRM-style platform split into a Client Panel for employees and an Admin Panel for HR, sharing one Express API and MongoDB store.

Hard part

Payroll and leave rules are stateful and audited. Attendance feeds leave balances, leave balances feed payroll, and payslip generation has to be reproducible — a wrong number here is a real-world problem, not a bug report.

Outcome

Delivered attendance, leave management, payslip generation and employee data tracking in one platform, streamlining HR processes end to end.

Project 2
03 / 06LIVE

Lil Humans Community

Kids Engagement Platform · 2025

KidsClient Panel
AdminOnboarding
Express APIREST
ContentCurated
MediaAssets
MongoDBStore
Architecture6 services · 6 paths
React.jsNode.jsExpress.jsMongoDB
lilhumanscommunity.com↗

Two audiences, one codebase, very different rules.

Problem

Children need an interface that is simple and safe. The people publishing to them need control over everything those children can reach.

My role

Full-stack developer — both panels, content pipeline.

The build

A two-panel MERN application: a Client Panel for kids' interaction and an Admin Panel for content onboarding and management, sharing a single content model.

Hard part

Nothing reaches the client panel unless an admin put it there. That constraint drove the content model and the boundary between the two panels.

Outcome

Shipped a two-panel platform where content onboarding and moderation are fully admin-controlled and the kid-facing surface stays simple.

Project 3
04 / 06LIVE

Nxtxcode

Online Enquiry & Quotation Platform · 2025

ClientEnquiry form
Express APIValidation
MongoDBEnquiries
MailerTrigger
Admin InboxNotified
Architecture5 services · 4 paths
React.jsNode.jsExpress.jsMongoDB
nxtxcode.com↗

A lead nobody reads is a lead you never had.

Problem

Enquiries for software projects arrived and then sat there. The bottleneck wasn't capturing the request — it was noticing it.

My role

Full-stack developer — client panel and notification path.

The build

A Client Panel where users submit enquiries and request quotations, backed by an Express service that triggers an email to admins the moment a record is created.

Hard part

Making notification part of the write path instead of a cron job someone forgets to check — the enquiry and the alert succeed or fail together.

Outcome

Admins are notified by email on every new enquiry, ensuring timely responses on quotation requests.

Project 4

Where the fundamentals came from

Simulation & hardware · 2024

Before the production work, two projects taught me the layers underneath it — one in simulation, one in solder.

05RESEARCH

Routing Protocol Analysis

Network Simulation Research — NS2 · 2024

Where I learned the network from the inside.

TCL ScenarioTopology
NS2 EngineSimulation
Trace FileRaw events
AWK ParserExtraction
PythonMetrics
MatplotlibComparison
Architecture6 services · 5 paths
Problem
AODV, DSR and DSDV all claim to route packets. Which one actually holds up depends on conditions you can only isolate in simulation.
Hard part
NS2 trace output is raw event lines, not data. Getting from those lines to defensible metrics meant building the parsing and visualisation layer myself.
Outcome
Compared throughput, end-to-end delay and packet delivery ratio across all three protocols, visualised in Python for insightful evaluation.
NS2TCLAWKPythonMatplotlib
06HARDWARE

AQUACARE

Embedded Monitoring & Alert System · 2024

Software that has to work when there is no internet.

Level SensorAnalog read
Arduino UNOThreshold logic
SIM ModuleGSM
OwnerSMS alert
RefillAction
Architecture5 services · 4 paths
Problem
An overhead tank gives no warning. You find out it's empty at the worst possible moment.
Hard part
No IP stack, no dashboard, no retries from a framework. Just a sensor, thresholds, and a message that has to actually leave the device.
Outcome
Real-time water level updates and automatic refill notifications delivered over SIM-based communication, in time to act on.
Arduino UNOSIM ModuleArduino IDEC
HOP 05Traceroute6 hops · 2019 → present

Every hop that got me here.

EDUCATION

SSLC

Sri Gopal Naidu Higher Secondary School

75.80%Score
  • Secondary school leaving certificate.

Certifications

IIT Madras · IIT Kharagpur · IBM · Maryland · UC Irvine
The Joy of Computing Using PythonIIT Madras — NPTELApr 2024
Database Management SystemIIT Kharagpur — NPTELApr 2024
Programming Mobile Applications for AndroidUniversity of Maryland — CourseraSep 2024
Python for Data Science, AI & DevelopmentIBM — CourseraFeb 2025
Introduction to Big Data with Spark and HadoopIBM — CourseraMar 2025
The Arduino Platform and C ProgrammingUniversity of California, IrvineMar 2026