Software Engineer · Builder · Open-Source Contributor

Hey, I’m Water.

Software engineer building software, backend systems, and developer tools — from storage internals and APIs to full products.

Loading local portfolio banter…

Software Engineer building backend systems and products.

I build software, systems, and products that work in the real world.

I started building software before university, and I still learn the same way: by taking ideas from concept to working software. I work across backend services, storage and real-time systems, and full products — with attention to architecture, reliability, and how things behave beneath the surface.

|
Story

Software Engineer by craft. Building since before university.

I started writing software before university, after discovering web development in secondary school. That early start shaped how I learn: build real things, understand the underlying system, then make it better.

I study physics alongside engineering, but I came to software by building it. My work spans backend services, real-time platforms, storage systems, blockchain programs, and full products — from first sketch to working software.

I care about how software behaves beneath the surface — architecture, data flow, failure modes — and about shipping things that are reliable, maintainable, and actually useful.

Technologies

Technologies I've worked with.

Languages, databases, and infrastructure I've used to ship backend services, systems, on-chain programs, and products.

Systems Programming

Key-value storage, networked servers, and event-driven engines — with attention to concurrency, persistence, and failure modes.

RustTokioGo

Backend Engineering

APIs with authentication, role-based access, queues, caching, docs, and clean REST design.

Node.jsExpressAxumTypeScriptBullMQ

Data and Storage

Relational data models, query design, in-memory storage, Redis-backed workflows, and persistence layers.

PostgreSQLMongoDBPrismaRedis

Web3 & Product Engineering

On-chain programs and user-facing products — PDA-based state and Devnet settlement alongside realtime, full-stack product delivery.

SolanaAnchorJavaScriptReactWebRTCSocket.IO

Architecture first

I think in modules, boundaries, data flow, failure modes, and long-term maintainability.

Performance aware

I care about latency, resource usage, responsive UI, and systems that stay predictable under load.

Product minded

I build for real workflows, not demos alone: useful defaults, clear APIs, and polished user paths.