TH
/ Loading — please wait
/ Loading — please wait
Backend engineer focused on system design, multi-tenant architectures, and writing code that stays readable when the project grows. CS student by day, building production-grade systems by night.
/ About
The unglamorous stuff: clear boundaries, predictable data flow, code that reads like prose.
I'm a CS undergrad at United International University who enjoys the unglamorous parts of backend engineering — clean boundaries, predictable data flows, and code my future self can still understand. I spend most of my time on multi-tenant SaaS design, concurrency, and small but pragmatic framework experiments. Outside of that, I mentor students at Softsasi and write about what I'm learning.
Salon Management SaaS — multi-tenant booking, scheduling, billing.
NextRush framework internals — middleware pipeline v2.
Distributed systems, consensus protocols, and event sourcing patterns.
Short-form notes on backend patterns over on Medium.
/ R&D
Framework sketches, design probes, and learning projects — the same engineering rigor, different shipping bar than client work. Each has a public case study.
A learning-driven Node.js framework with a middleware pipeline, routing layer, and plugin system.
An experimental JVM framework inspired by Javalin — simple routing, minimal surface area.
/ Focus Areas
Six areas where most of my engineering hours go — mostly backend, mostly about keeping systems readable and predictable.
Shared-database tenant isolation using tenant_id scoping, permissioned queries, and clear domain boundaries.
Booking and time-slot logic where two users shouldn't be able to grab the same thing. Queues, locks, retries.
PostgreSQL schema and indexing decisions, migrations that don't scare me, and sensible caching patterns.
Service/repository separation, dependency inversion, and modules a teammate can navigate without a map.
Practical AWS setups — EC2, RDS, S3, load balancers — and the small amount of DevOps a small team actually needs.
LLM-driven workflows and small agent experiments, usually focused on developer tooling rather than chatbots.
/ Experience
Softsasi / Remote
Softsasi / Remote
/ Signals
The facts, not the flex. A short snapshot of things that happened along the way.
Finished 1st Runner Up at the global NASA Space Apps Challenge, building a working solution with a team under a 48-hour constraint.
Participated and shipped an AI feature using the browser's built-in AI capabilities.
/ Writing
Notes on system design, backend architecture, and the small engineering lessons I collect along the way.
A deep dive into the pattern that keeps pages static when your app needs to know who’s logged in You build a product page in Next.js. Statically generated. Served from the CDN. Fast. Then someone says: “The header...
Most developers learn Next.js. Experienced engineers learn how it thinks. There’s a tell-tale sign when you’re reviewing code from someone who learned Next.js from tutorials: everything is a client component. Not...
When developers first move from a monolith to microservices, they usually focus on splitting services. They rarely think about how those services will find each other . That’s where things start breaking. The Real...
/ Say hi
Open to backend engineering roles, side projects with solid engineering, and mentorship conversations. I reply to most emails within a day.
/ Selected Work
Backend for salon operations — booking, scheduling, and subscriptions on a multi-tenant foundation.
VS Code extension to generate and preview project folder trees before files hit disk — small surface area, steady adoption.
A learning-driven Node.js framework with a middleware pipeline, routing layer, and plugin system.