Backend Engineer
Systems rarely seen, yet everything depends on them.
I design and build backend systems - Java & Spring Boot services backed by PostgreSQL, from single-deployable monoliths to service-oriented architectures, with the transactional logic often pushed down into the database itself.
Working as a professional Backend Developer since
About
I am a backend developer working mainly in the Java / Spring Boot / PostgreSQL stack. Most of what I build sits behind the interface most people see - authentication and account security, payment verification flows, notification systems, and the data model that has to stay correct no matter how the application on top of it changes.
I have worked across both ends of the architecture spectrum: tightly-scoped monolithic applications where a single deployable is the right call, and service-oriented systems where independent scaling and deployment matter more. I also spend a fair amount of time writing logic directly into PostgreSQL - stored procedures and transactional queries - when correctness or performance needs to live at the database layer rather than the application layer.
- Role
- Backend Developer
- Stack
- Java, Spring Boot, PostgreSQL
- Education
- B.Sc (Hons) Information Technology
- [email protected]
- GitHub
- github.com/bhimsen01
- linkedin.com/in/bhimsen-basnet
How I build
three architecturesThe right architecture depends on the project, not on which one is more impressive. Here's what I reach for and why.
Monolithic systems
One codebase, one deployment, layered cleanly - controller down to repository. This is my default for internal tools and systems with a single team and a bounded domain: it's faster to build, easier to reason about, and there's nothing to orchestrate between services.
Microservices
Bounded services behind a gateway, each independently deployable and scalable. I use this when parts of a system genuinely need to scale or fail independently - a notification service under bursty load shouldn't affect order processing.
Stored procedures
For paths where correctness under concurrency matters more than convenience, I push logic into PostgreSQL directly - procedures that run atomically inside a transaction rather than being coordinated from the application layer, cutting round-trips and race conditions.
Selected work
Government e-service platform consolidating citizen, municipal, and ward-level services, including citizen charter and budget information, government forms, PSC vacancies and applications, complaint management, alerts, and institutional information. Architected stateless JWT authentication with refresh-token rotation, RBAC and PBAC authorization, and secure role-based access across multiple service modules. Developed core government-service workflows and notification systems to provide a unified and scalable digital platform for citizen services.
Backend for a combined learning-management and HR platform, built on Spring Boot and PostgreSQL with a Next.js frontend.
Backend for a hiring platform: job postings, applications, and candidate management.
Task-management platform built directly on Core Java, JDBC and Servlet/JSP - no ORM, hand-written SQL and session handling.
Skills
Languages
- Java
- JavaScript
- Python
- C
- C#
- R
Backend
- Spring
- Spring Boot
- Spring Security
- JDBC
- Servlet / JSP
- ASP.NET
Database
- PostgreSQL
- PL/pgSQL & stored procedures
- MySQL
- MS SQL
- MongoDB
Frontend
- Next.js
- HTML
- CSS
Development & workflow
- Git
- GitHub
- Docker
- Postman
Design & 3D
- Figma
- Blender
Have an opportunity?
Open to backend roles and freelance work involving Java, Spring Boot and PostgreSQL systems.