dangamuwa.rasika@gmail.com
AVAILABLE FOR SELECT PROJECTS
Rasika Dangamuwa
Chapter 01 — The entry

I BUILDDIGITALSYSTEMS.

Software Engineer × AI Builder × Product Thinker

I design and build intelligent software, digital products and real-world systems where technology meets business.

BUILDING
  • Zergo Sales
  • VidLearn Academy
EXPERIMENTING
  • Agentic workflow automation
  • Interface motion systems
EXPLORING
  • Edge and streaming architectures
  • Micro SaaS economics
See all →
Scroll
01The entry
Most peopleuse technology.
I build the systemsbehind it.

I design and build software, AI-powered tools and digital products for real-world problems — the internal platform a business actually runs on, the screen a patient reads in a corridor, the workflow nobody wants to do by hand twice.

The work spans full-stack engineering, AI integration, business automation, SaaS product development, cloud deployment and database architecture. Not as a list of services — as one continuous problem: turning a messy operational reality into a system that holds.

FULL-STACK ENGINEERINGAI INTEGRATIONBUSINESS AUTOMATIONSAAS PRODUCTCLOUD DEPLOYMENTDATABASE ARCHITECTUREUI / UXFULL-STACK ENGINEERINGAI INTEGRATIONBUSINESS AUTOMATIONSAAS PRODUCTCLOUD DEPLOYMENTDATABASE ARCHITECTUREUI / UX
FULL-STACK ENGINEERINGAI INTEGRATIONBUSINESS AUTOMATIONSAAS PRODUCTCLOUD DEPLOYMENTDATABASE ARCHITECTUREUI / UXFULL-STACK ENGINEERINGAI INTEGRATIONBUSINESS AUTOMATIONSAAS PRODUCTCLOUD DEPLOYMENTDATABASE ARCHITECTUREUI / UX
02The work

Systems that
went live.

03The system

The stack is
a graph.

Nothing here is used in isolation. Hover a technology to see what it connects to in the systems I actually build.

04The lab

The lab.

Not everything becomes a product. Some of it stays unfinished on purpose.

● BUILDINGAI

AI-assisted extraction

Turning unstructured business input — messages, documents, notes — into structured records a system can act on.

● EXPERIMENTAUTOMATION

Workflow automation

Removing the human from the parts of a process where the human was only re-typing.

● PROTOTYPEINTERFACE

Interface experiments

Motion, cursor behaviour and typography treated as engineering problems rather than decoration.

● EXPERIMENTPRODUCT

Micro SaaS

Small products with one job, shipped without a roadmap committee.

● BUILDINGTOOLS

Developer tooling

Internal tools that remove a repeated twenty minutes from every week.

● ARCHIVEDCREATIVE

Creative coding

Canvas and generative systems, where the output is the experiment.

05The mind

Code
is not
the product.

The product is what changes when the software exists. The interface. The workflow. The business. The experience.

01

I question the workflow
before I write the code.

02

I remove complexity
before I add features.

03

I design the system
before I build the interface.

04

I care about what happens
after deployment.

  1. 01

    Understand the problem

    Before the schema, before the stack. Most bad software is a correct answer to the wrong question.

  2. 02

    Simplify the system

    Every entity that survives has to earn it. Complexity is the thing you pay for later.

  3. 03

    Design the experience

    The interface is where business logic meets a human being who is in a hurry.

  4. 04

    Build the product

    Typed, structured, and boring in the places that should be boring.

  5. 05

    Deploy

    Software that is not running is not software.

  6. 06

    Improve

    The first version is a hypothesis. Usage is the data.

05The mind
Rasika Dangamuwa
RD — 001Sri Lanka / Remote
Software engineer / builder

Rasika
Dangamuwa.

Software engineer / builder

I build software because I enjoy turning messy real-world problems into systems that are simple, useful and hold up under actual use.

Most of my work is real systems for real organisations: enterprise platforms, deployed public-facing systems, internal business tools. Around that, a constant stream of product and AI experiments — because the interesting part of this field moves faster than any single project.

Core
Full-stack software engineering
Builds
Products, platforms and internal systems
Edge
AI integration and business automation
Approach
Technology in service of a business outcome
05The mind

On the record.

Most software is written from outside the operation it serves. I have spent years on the inside — in the field, in the office, and running a company of my own.

  1. 2024 — PresentColombo · Hybrid

    Zergo Distributors

    • Founder & Managing DirectorFull-time

    Founded and run a distribution business. Stock, orders and cash flow are not a client brief here — they are the day job.

    Case studyZergo Sales→
  2. 2023 — PresentRemote

    Freelance

    • Full-Stack Software Engineer

    Websites and web applications for clients — scoped, built and deployed end to end, remotely.

  3. 2019 — 2026Sri Lanka

    Nestlé

    • PropagandistPart-time · 2022 — 2026
    • Administrative AssistantFull-time · 2020 — 2022
    • PropagandistFull-time · 2019 — 2020

    Brand promotion in the field, then administration in the office — the operations internal software is written for, seen from the side that has to use it.

05The mind

Right now.

BUILDING

Zergo Sales

Orders, delivery runs and the money trail behind every bill.

BUILDING

VidLearn Academy

SMS campaigns and tracked links that bring learners to the catalogue.

EXPERIMENTING

Agentic workflow automation

Model-driven systems that complete business processes rather than describe them.

EXPERIMENTING

Interface motion systems

Reusable motion primitives that stay fast on low-end devices.

EXPLORING

Edge and streaming architectures

Where the compute should actually live for real-time product surfaces.

EXPLORING

Micro SaaS economics

Small products, real revenue, no headcount.

06The contact

● System complete