Backend
Design APIs, business logic, authentication boundaries, and the integrations that connect a platform together.
Adithya Dilum Senavirathna · Software engineering portfolio
Third-year IT undergraduate at the University of Moratuwa focused on backend engineering, system design, cloud infrastructure, and practical software engineering with C#/.NET, TypeScript, and PostgreSQL.
Multi-tenant operations platform on ASP.NET Core, PostgreSQL, and WhatsApp
Enterprise IT Asset Management System
Real-time quadcopter control and telemetry firmware

I’m Adithya Dilum Senavirathna—Adithya Dilum day to day and Adithya Senavirathna professionally. My interest in technology started when I was young, driven by curiosity about how digital systems work and how simple ideas can become useful tools. That curiosity eventually led me into Information Technology, where I began turning concepts into real applications, dashboards, automation flows, and connected systems.
Today, in my third year, that curiosity has narrowed into something more specific: I build backend systems. APIs, relational data models, authentication and tenant boundaries, and the deployment workflows that carry them to production. I still work across the stack, because knowing how an interface consumes an API makes me better at designing one — but the part I go deep on is what happens behind it.
Beyond the code, I care about ownership, communication, and learning fast. Whether I am leading a team project, improving a feature, or debugging a system issue, I try to approach problems with structure: understand the context, break the problem down, build carefully, and keep improving.
A system-oriented view of the tools I use to design, build, and operate backend software.
Design APIs, business logic, authentication boundaries, and the integrations that connect a platform together.
Model relational data, structure schemas, and keep persisted state correct as a system grows.
Containerize, deploy, and operate services, with the system design and Linux fundamentals underneath.
Build the product surface that consumes those APIs, responsive and data-driven.
A trace of the moments that shaped how I build software.
This is not a straight line. It started with curiosity, moved through code, hardware, data, teams, and product systems — each stage adding a new layer to how I think about engineering.
Every node in this log represents a shift: from learning how software works, to building systems that collect data, support workflows, and stay maintainable when real users depend on them.
Building a hospital management system connected programming fundamentals to real application flows: how data, interfaces, and business logic come together to support everyday operations.
An ESP32 flight controller and environmental telemetry drone changed what correctness meant. Software now had to answer to task rates, noisy sensors, coordinate frames, and failsafes rather than only to a screen.
Leading TIQRI Assets meant requirements, team coordination, data integrity, and deployment workflows — and learning that an enterprise system is a problem of custody and audit history, not form count.
DayBoard pushed the hard problems behind the interface: tenant isolation enforced at several independent layers, durable webhook processing, and authorization derived from server-side membership rather than client input.
Third year, and the direction has narrowed deliberately: backend design, databases and concurrency, Linux and networking fundamentals, and how reliable systems are actually deployed and operated.
Have a project, opportunity, collaboration, or technical conversation in mind? Send a message — I'm open to connecting with teams, builders, and engineers working on meaningful software systems.
Best fit: software engineering · full-stack · backend · cloud-ready systems