Backend Engineer focused on building reliable backend applications with TypeScript (Node.js) and Java (Spring Boot).
I build backend systems with clear service boundaries, maintainable data models, and well-defined APIs — with a focus on multi-tenant architecture and PostgreSQL data modeling.
Alongside backend engineering, I have experience with React and Next.js, focusing on architecture, patterns, and maintainable frontend structure. I treat frontend as part of the overall system, ensuring clean integration between client and backend.
- Design backend systems with clear boundaries (controller → service → data layer)
- Prefer modular monoliths and introduce service boundaries only when they solve a real problem
- Build APIs with explicit contracts and backward compatibility in mind
- Design multi-tenant systems with strong isolation and RBAC-based authorization
- Use caching and background processing where they simplify application performance or user experience
- Prefer simple, maintainable solutions over early optimization or over-engineering
- Make trade-offs explicit (performance vs complexity vs operational cost)
- Multi-Tenant SaaS Platform — Solo-built booking platform (Next.js + NestJS + Postgres) with structural tenant isolation, RBAC, and idempotent Stripe billing.
- FileTree Pro — VS Code extension, 36,000+ installs, 5.0 rating on the Marketplace.
- NextRush — TypeScript backend framework, benchmarked against Fastify/Express/Koa/Hono (~14% overhead vs raw Node.js).
More case studies: 0xtanzim.dev/projects
- Backend systems in TypeScript (Node.js) and Java (Spring Boot), focused on modular design and long-term maintainability
- Designing APIs with clear contracts and backward compatibility in mind
- Building multi-tenant and RBAC-based systems with strong access control
- Applying clean architecture and service boundaries to keep systems maintainable and testable
- Working with PostgreSQL — schema design, indexing, transactions, and data consistency
- Using Docker and containerized environments for consistent deployment
- C++ for understanding memory, performance, and system-level behavior
- Explored Node.js internals and native addons
- Learning how low-level concepts influence backend performance and runtime behavior
- Consider failure scenarios during API and backend design
- Keep systems simple, predictable, and maintainable
- Make trade-offs explicit (performance vs complexity)
- Prefer simple, maintainable systems over early optimization
- Mentored developers at Softsasi — code reviews, debugging methodology, backend architecture fundamentals
- Taught backend and frontend fundamentals (JS, TS, React, Next.js, Express)
- Coached on project structure with a focus on clean architecture
- Learning backend architecture, distributed computing concepts, and software engineering through hands-on projects
- Explore AI systems (LLMs, on-device/browser AI) as part of real application design
- Focus on long-term thinking, decision-making, and engineering discipline
- Study trading and psychology to improve decision-making under uncertainty
- Enjoy contributing to open source and writing clear technical documentation
⚡ I like building systems that work smart and stay maintainable.
✨ Thanks for visiting — keep building, keep learning. 🚀