Skip to content
Dipesh Chaulagain

Mid-Level Frontend Developer

Dipesh Chaulagain — Frontend Developer. Building experiences, not just interfaces.

Building experiences, not just interfaces.

Scroll to explore

01 — The beginning: how I started

Every interface starts with a problem. Somebody has something they need to do, and the machine is in the way.

Mine started in Kathmandu, in 2022. A React admin dashboard for an enterprise client. Real users, real data, and a component structure that had to survive whoever touched it next.

So I stopped shipping screens and started shipping systems. Reusable component libraries, shared across projects. Standardised patterns instead of a slightly different button on every page.

Then the work got heavier. A storefront with real traffic. Filters, search, infinite scroll, authentication — and every decision now visible in the numbers.

Thirty percent faster loads. Not from a rewrite. From taking server state seriously: caching, background refetching, invalidation, and the redundant requests nobody had counted.

Four years in, the surface changed again. Wallets. Signatures. Encryption keys that never leave the browser tab.

Same discipline. Higher consequences. Get a button wrong and someone clicks twice. Get a signing flow wrong and someone loses money. The craft is identical; the margin for error is not.

That is the whole job. Making a complicated system feel obvious — and being able to prove why it is fast, indexable and correct when someone asks.

The beginning

My evolution

Nobody arrives fully formed.

Five stages, four years, three companies and one degree — in the order they actually happened.

02 — My evolution as a developer

  1. 2019

    Learning

    Computer Systems Engineering. Fundamentals before frameworks.

  2. 2022

    Building

    First professional React work. Dashboards, marketing sites, component libraries.

  3. 2023

    Shipping

    A live storefront with real traffic. Search, auth, SEO, 30% faster loads.

  4. 2024

    Leading

    Owning the frontend end to end. Design systems, API contracts, code review.

  5. 2025

    Exploring

    Polkadot and Cardano wallets. End-to-end encryption. Mentoring.

03 — The tools I work with

The tools I speak

A stack is a vocabulary, not a trophy shelf.

01

Interface

What the user actually touches. Four years of it, in production.

02

State & Data

Where most frontend bugs are born. Server state and client state are not the same problem.

03

Web3 & Security

The part where a wrong interface costs more than a wrong click.

04

Backend & Adjacent

Enough of the other side to design a frontend that does not fight it.

05

Testing & Craft

How the work stays correct after it ships.

04 — Things I've built

Things I've built

Four products. Two of them you can open right now.

The other two are client products behind a login — so instead of a screenshot, here is a diagram of what each one actually does.

012025 — present

Vola Wallet

Polkadot & Cardano dApp wallet

Vola Wallet: a dark mobile wallet showing a VOLA balance of 11389.9642 alongside 1299.83 ADA, with send, receive and bridge actions and an asset list for Vola and Cardano.

A wallet that has to be right the first time.

Holding assets across two different chain ecosystems normally means two wallets, two mental models and a lot of trust in a UI you cannot verify. Vola Wallet puts Polkadot and Cardano behind one interface.

Wallet connect flows
Detecting installed extensions, negotiating accounts and handling every rejection path — no connection, wrong network, user cancels mid-signature — as a first-class state rather than an error toast.
On-chain data reads
Chain state is asynchronous, occasionally stale and never guaranteed. Reads are modelled as cached queries with explicit loading, refetch and invalidation, so the interface never quietly shows a number that is no longer true.
Transaction signing
Building, previewing and signing transactions for dApp and smart-contract interactions. The signature step is deliberately slow and legible: the user sees exactly what they are approving before the key is touched.

Role · Frontend Developer — Web3 features

  • Shipped wallet connect, on-chain reads and transaction signing for dApp and smart-contract interactions.
  • Built as reusable, strictly typed React components against Figma mockups.
  • React
  • Next.js 14
  • TypeScript
  • Polkadot
  • Cardano
  • Wallet extensions
  • React Query

Private client product — no public link

022025 — present

Nuvola Drive

End-to-end encrypted cloud drive

Nuvola Drive dashboard: a storage ring showing 2.56 GB of 100 GB used, tiles counting images, videos and documents, and a grid of recently visited encrypted files.

Storage where the server never sees the file.

Ordinary cloud storage asks you to trust the provider. Nuvola Drive removes that requirement: files are encrypted in the browser before they leave it, and the password never travels either.

Encryption in the browser
Encrypted upload, storage and access implemented on the client. Keys are derived and used in the browser; the server stores ciphertext it cannot read.
Passwordless login over SRP
Authentication via the Secure Remote Password protocol — the client proves it knows the password without ever transmitting it, so there is no password on the wire and none at rest.
Keeping crypto invisible
The hard part is not the cryptography, it is making an encrypted drive feel like a normal one. Upload progress, previews and sharing all had to survive the constraint that plaintext exists only in the tab.

Role · Frontend Developer — E2EE and auth

  • End-to-end encrypted upload, storage and access shipped as part of the product.
  • Passwordless login over the Secure Remote Password protocol.
  • React
  • TypeScript
  • E2EE
  • SRP protocol
  • Web Crypto
  • Next.js

Private client product — no public link

03Selected work

Himalayan Trekkers

himalayantrekkers.com

Himalayan Trekkers home page: a full-bleed photograph of a climber on a snow ridge behind the Island Peak Climbing headline and a Book My Trip call to action.

Turning a mountain of itineraries into one clear decision.

A trekking operator's catalogue is deep and irregular — dozens of routes across three countries, each with its own duration, difficulty and season. The site has to let someone find the right trek without reading all of them.

Itineraries as structured content
Day-by-day itineraries modelled as data rather than prose, so the same trek renders as a summary, a full plan and a search result without duplicating content.
Search, cart and inquiry
Search across the catalogue, a cart, and inquiry flows for a product nobody buys in one click — the conversion is a conversation, so the UI keeps that thread intact.
Search visibility
Built on Next.js with SEO in mind: server-rendered trek pages that search engines can actually index, which is how this kind of business is found at all.

Role · Frontend Developer

  • Live trek-booking platform covering Nepal, Bhutan and Tibet.
  • Itineraries, search, cart and inquiry flows built end to end on Next.js.
  • React
  • Next.js
  • Tailwind CSS
  • SEO
  • REST APIs
Visit live site
042023 — 2024

FurnitureHub Nepal

furniturehub.com.np

FurnitureHub Nepal storefront: a category navigation bar, a Making Your Home Beautiful hero carousel of living-room furniture, and a Hottest Deals promotion row.

An e-commerce frontend, owned end to end.

A furniture catalogue that has to be browsable, filterable and findable on Google — with pages that stay fast as the product list grows.

Filters, search and infinite scroll
Product filters, search and infinite-scroll pagination on Next.js 13, plus authentication flows — all sharing one server-state layer instead of each screen fetching its own way.
SEO with server rendering
SSR for dynamic product pages, Open Graph metadata and generated sitemap.xml and robots.txt, improving organic visibility and indexability.
A design system, not a stylesheet
A Tailwind CSS design system of reusable patterns, spacing tokens and breakpoints used platform-wide — and REST contracts and error states agreed with the backend team rather than discovered in production.

Role · Frontend lead

  • Load times cut by 30% by managing server state with React Query — caching, background refetching and query invalidation removed redundant API calls.
  • Platform-wide Tailwind design system adopted across the storefront.
  • Dynamic product pages made indexable through SSR, structured metadata and generated sitemap and robots.txt.
  • Next.js 13
  • React
  • React Query
  • Tailwind CSS
  • SSR / SEO
  • REST APIs
Visit live site

05 — Behind the interface: how I think

Behind the interface

The interface is only the surface.

Nine decisions that sit under the visual layer. Pick one — the diagram is the explanation, and the line underneath it says where I made it.

LAYOUTLISTDETAILCARDCARDMETAACTIONPROPS DOWNEVENTS UP

A component is a promise about what happens next.

Same props in, same output out. Composition over configuration, one owner per piece of state, and boundaries drawn where the data changes — not where the visual design happens to have a box.

Reusable component libraries shared across projects at Saptacode; strictly typed reusable architecture at Vola.

06 — Selected experience

Selected experience

Read it as chapters, not as a resume.

Same dates and titles as the PDF — with room to say what each one actually involved.

United Arab Emirates · Remote

Wallet flows on Polkadot and Cardano, end-to-end encrypted storage, and mentoring the developers coming up behind me.

  • Shipped client-facing projects in React, Next.js 14 and TypeScript, translating Figma mockups into pixel-perfect, responsive components with reusable architecture and strict typing.
  • Built Web3 frontend features for Vola Wallet on Polkadot and Cardano: wallet connect flows, on-chain data reads and transaction signing for dApp and smart-contract interactions.
  • Implemented E2EE for a secure cloud drive — encrypted upload, storage and access — plus passwordless login over the Secure Remote Password protocol.
  • Integrated REST APIs with React Query custom hooks and tuned performance via cache config, lazy loading, code splitting and next/image, lifting load times and Lighthouse scores.
  • Reviewed code, mentored junior developers and contributed to feature scoping and planning.
Download the one-page CV

BSc Computer Systems Engineering · University of Sunderland

07 — About Dipesh Chaulagain

The developer behind the screen

Based in
Kathmandu, Nepal
Working
Remote, UAE team
Experience
4 years, frontend
Studied
BSc Computer Systems Engineering

Hello — I'm Dipesh.

I build the front of things. Four years of it, from an office in Kathmandu to a remote team in the UAE, mostly in React, Next.js and TypeScript.

I studied Computer Systems Engineering, which is a long way of saying I like knowing what is happening underneath. That habit is why I ended up on the crypto and encryption side of the product rather than only the layout side — a wallet or an encrypted drive is a frontend problem right up until it very much is not.

What I actually enjoy: the moment a messy flow collapses into something obvious. Cutting a load time and being able to say exactly which request I removed. Writing the component that stops three other people from writing it.

I review code, I mentor the developers coming up behind me, and I would rather ask an awkward question during scoping than discover the answer in production.

Building experiences, not just interfaces.

Dipesh Chaulagain · Mid-Level Frontend Developer

08 — What I'm exploring

What I'm exploring

Where the next four years are pointed.

Honest signal strength. Two of these are in production today; the rest are somewhere between a side project and a stack of open tabs.

TopicStatus · Signal

  • Polkadot & Cardano

    Wallet flows and on-chain interaction in production right now — and there is a lot more of both ecosystems left to learn.

    Shipping

  • Applied cryptography

    E2EE and the Secure Remote Password protocol on a live product. Enough to respect how much more there is.

    Shipping

  • Frontend architecture

    How large React codebases stay navigable: boundaries, ownership, and the cost of every abstraction.

    Deepening

  • Web performance

    Web Vitals as a design constraint rather than an audit at the end.

    Deepening

  • Real-time applications

    Live state, subscriptions and optimistic updates — the UI problems that appear when data will not sit still.

    Exploring

  • 3D on the web

    Three.js and WebGL as a storytelling tool. This site is part of that experiment.

    Exploring

  • Distributed systems

    Consensus, eventual consistency, and what they imply for the interface sitting on top.

    Reading

  • AI-assisted development

    Where it genuinely accelerates the work, and where reviewing the output costs more than writing it.

    Reading

09 — Contact and links

The end of the scroll

You've reached the end.

But this could be the beginning of something else.

Let's buildsomethingdcdipesh1998@gmail.com

Elsewhere