Portfolio

Session 00:00:00.00

Sector 01 · Profile

Adithya Dilum Senavirathna · Software engineering portfolio

I build reliable systemsfor web and cloud.

Second-year IT undergraduate at the University of Moratuwa building full-stack products, backend services, and deployable cloud workflows with TypeScript, Next.js, .NET, and PostgreSQL.

FocusFull-stack

DepthBackend systems

DirectionCloud delivery

Download resume Get in touch

Sector 02 · Work

Featured projects

View all

Project 01

Engineering this portfolio

Building a personal system from a blank canvas

Continuously evolving

TIQRI Assets

Enterprise IT Asset Management System

ESP32 Flight Controller

Real-time quadcopter control and telemetry firmware

Sector 03 · Focus

Engineer status

Availability

Open to software engineering internships in 2026

Full-stack leaning / backend curious / delivery minded

Current focus

Product engineeringResponsive interfaces, clear user flows, and maintainable React code.
Backend systemsAPIs, relational data models, business logic, and integrations.
DeliveryDocker, CI/CD, deployment workflows, and release discipline.

Sector 04 · Metrics

Profile snapshot

CGPA

3.77

Status

Seeking internship

Published projects

Location

Sri Lanka / UTC+5:30

Latest GitHub activitySYNCING / PUBLIC_EVENTS_API

Core stackTS / Next.js / .NET / SQL

Coding activity

Last 7 days

SET_WAKATIME_API_KEY

Coding telemetry offline

@adithyadilum

Online

Adithya Dilum

IT undergraduate

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, as an IT undergraduate, I focus on building full-stack software that is practical, maintainable, and reliable. I enjoy working across the stack, from interfaces and APIs to databases, deployments, and system workflows, because it helps me understand how each layer affects the final product.

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

Identity

IT undergraduate

Academic profile

University of Moratuwa · FIT · CGPA 3.77

Engineering focus

Full-stack systems

Current goal

Seeking an internship

Curious builder

Systems thinking

Sector 07 · Core skills

Core stack map

A system-oriented view of the tools I use to design, build, connect, and ship full-stack software.

Node 01

Interface layer

Build responsive, accessible, and data-driven product interfaces for users.

ReactNext.jsTypeScriptTailwind CSSGSAPMotionshadcn/uiRadix UI

Node 02

Service layer

Design APIs, business logic, auth flows, and integrations that connect the product together.

Node.jsASP.NETREST APIsExpressExpoNextAuthMeta APIs

Core I/O

SRE

API

Node 03

Data layer

Model relational data, structure schemas, and build reliable persistence for application workflows.

PostgreSQLSQLDrizzle ORMData modelingRedisFirebaseNeon

Node 04

Delivery layer

Containerize, deploy, inspect, and automate application releases with cloud-ready workflows.

DockerGitHub ActionsVercelCI/CDAWS — exploringGCP — exploring

ModeBuild / ship / operate

PrimaryFull-stack software engineering

Stack nodes20

Sector 06 · Journey

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

Scroll to explore

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

Mode

Adaptive

Axis

Scroll

Stage 01/Early signal/Curiosity

Technology started as curiosity.

Before it became coursework, projects, or a career path, technology was something I wanted to understand. I was curious about how computers worked, how software responded to input, and how small pieces of logic could turn into something useful.

Output

A long-term interest in building, experimenting, and understanding systems from the inside.

+ Curiosity+ Problem solving+ Self learning

The first signal was interestLogged

Stage 02/2023–2024/Foundation

Code became the first working system.

My early software work helped me connect programming fundamentals with real application flows. Building a hospital management system taught me 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

From programming basics to structured softwareLogged

Stage 03/2024–2025/Hardware telemetry

Physical data entered the software layer.

The environmental monitoring drone changed how I looked at software. It was no longer just screens and forms — it had to respond to sensors, noisy readings, live feedback, and real-world behavior.

Output

A real-time dashboard that visualized environmental telemetry from an ESP32-powered drone.

+ ESP32+ C+++ React+ TypeScript+ Firebase

Sensors to dashboard UILogged

Stage 04/2024–Present/Academic journey

Theory started connecting with real builds.

At the University of Moratuwa, my academic work gave structure to what I was already building. Data structures, databases, object-oriented design, web programming, and software engineering started becoming practical tools for making better decisions.

Status

IT undergraduate focused on software engineering, full-stack development, and scalable system design.

+ UOM+ Software engineering+ DSA+ Databases+ OOAD

Classroom concepts to engineering practiceLogged

Stage 05/2025–Present/Enterprise systems

Building expanded from features to ownership.

Leading the EITAMS project pushed me beyond writing code. I had to think about requirements, team coordination, data integrity, deployment workflows, and how an enterprise system should stay understandable as it grows.

Output

A full-stack IT asset management platform for lifecycle operations, custody, financial reporting, maintenance, and compliance.

+ Next.js+ PostgreSQL+ Drizzle ORM+ Keycloak

Team leadership to delivery workflowsLogged

Stage 06/2026/Exploration mode

The next layer is still being mapped.

Right now, I am focused on expanding the depth of my engineering skills — building full-stack products, improving backend design, exploring cloud infrastructure, and learning how reliable software systems are designed, shipped, and maintained.

Current signal

Learning through real projects, team-based development, and continuous experimentation.

+ Full-stack+ Backend+ Cloud+ System design+ Reliability

Learning / building / refiningCurrent 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 for 2026

Response

Async-friendly

Location

Sri Lanka · Remote