Dibyajyoti Mahuri
Software Engineer / Backend-heavy Full Stack
I build web applications and the systems behind them. Backend engineering is my depth; working across the stack is how I bring the whole product together.
Booking systems / Payments / Education platforms / Data-driven APIs
01 / Selected work
A closer look at the systems I’ve contributed to through my professional work.
Hospitality / Backend systems
Backend services supporting the journey from hotel search to booking and payment.
Education / APIs & data
Backend APIs connecting education workflows with payments, analytics, and reporting.
Professional work summaries.
Explore my GitHub (opens in a new tab)02 / Engineering stack
Backend and data at the core. Frontend to complete the product. Infrastructure as a growing part of the toolkit.
APIs, business logic, and the services behind the product.
Relational data, document stores, and caching.
Responsive interfaces connected to real application data.
Taking applications from local development to deployment.
Tools and areas I work with or am building experience in; not a claim of production expertise in every technology.
03 / Experience
Engineering work across hospitality and education, with a focus on backend services and data.
Software Engineer
Building backend APIs and data-driven platforms across payments, analytics, reporting, and education workflows.
Software Engineer
Built booking, payment, authentication, search, and backend services for a hotel booking platform.
04 / Engineering approach
The principles I bring to design discussions, and the questions I use to reason about a system.
API design & security
Start with resource boundaries, validation, predictable errors, and explicit authorization. Make the API understandable to the next person integrating it.
Data & consistency
Model constraints before endpoints. Think through transactions, concurrent writes, and idempotency before adding a cache or a background job.
Reliability & operations
Consider timeouts, retries, rate limits, and useful logs. Test failure paths alongside the happy path, and make behavior observable.
System design & performance
Start with clear module boundaries. Measure bottlenecks before optimizing, and weigh the operational cost of queues and microservices against the problem.
05 / Behind the work
Bangalore, India
I enjoy connecting the pieces of a product: the interface someone uses, the API behind it, and the data that makes it useful.
My strongest depth is in backend engineering. My work has covered booking, payments, authentication, and data-driven platforms. I’m extending that foundation across frontend development, system design, and cloud infrastructure.
Let’s build something useful06 / Get in touch
Have a role, a project, or an engineering problem in mind? Let’s talk.
code.dibya@gmail.com