Adithya Dilum
Portfolio

Adithya Dilum Senavirathna · Software engineering portfolio

I build reliable backendand full-stack systems.

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.

Adithya Dilum
Sector 05 · About me

Curiosity shaped how I build software.

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.

Away from the keyboard · 3D render studies
Systems thinking
Backend depth
Sector 07 · Core skills

Core stack map

A system-oriented view of the tools I use to design, build, and operate backend software.

Node 01

Backend

Design APIs, business logic, authentication boundaries, and the integrations that connect a platform together.

C#.NETASP.NET CoreNode.jsREST APIsTypeScript
Node 02

Data

Model relational data, structure schemas, and keep persisted state correct as a system grows.

PostgreSQLSQLData modelingRedis
Core I/O
API
DB
OPS
UI
Node 03

Systems and cloud

Containerize, deploy, and operate services, with the system design and Linux fundamentals underneath.

LinuxDockerCI/CDGitHub ActionsAWSSystem design
Node 04

Interface

Build the product surface that consumes those APIs, responsive and data-driven.

ReactNext.jsTailwind CSS
ModeBuild / ship / operate
PrimaryBackend and systems engineering
Stack nodes19
Sector 06 · Journey

A trace of the moments that shaped how I build software.

The path so far

From curiosity to engineering.

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.

Nodes
05
Mode
Adaptive
Axis
Scroll
01
Stage 01/2023–2024/Foundation

Code became the first working system.

Building a hospital management system connected programming fundamentals to real application flows: how data, interfaces, and business logic come together to support everyday operations.

Output
A desktop application for patient records, appointments, and hospital administration workflows.
+ C#+ .NET+ SQL Server+ Database design
Programming basics to structured softwareLogged
02
Stage 02/2024–2025/Embedded and real-time

Physical constraints entered the software layer.

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.

Output
Real-time firmware with FreeRTOS tasking, RF telemetry, and saturation-aware motor mixing.
+ ESP32+ C+++ FreeRTOS+ Control systems
Sensors and timing as first-class concernsLogged
03
Stage 03/2025–2026/Enterprise systems

Building expanded from features to ownership.

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.

Output
A full-stack IT asset management platform for lifecycle operations, custody, financial reporting, and compliance.
+ Next.js+ PostgreSQL+ Drizzle ORM+ Keycloak
Team leadership to delivery workflowsLogged
04
Stage 04/2026/Backend platform

Multi-tenancy made the backend the product.

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.

Output
A multi-tenant operations platform with tenant-isolated .NET APIs and a durable WhatsApp booking engine.
+ C#+ ASP.NET Core+ PostgreSQL+ Docker+ Meta APIs
Isolation, durability, and trust boundariesLogged
05
Stage 05/Now/Backend, systems, cloud

Going deeper rather than wider.

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.

Current signal
Building backend systems and writing up what each one teaches.
+ Backend+ Databases+ Linux+ Cloud+ Distributed systems
Depth over breadthCurrent phase
Sector 08 · Contact

Let's work together.

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

Availability
Open to internships
Response
Async-friendly
Location
Sri Lanka · Remote
Return to top