A scroll-driven sequence: a lone figure stands over a city in the rain, a signal comes up behind him, and the skyline breaks apart into the things it stood for — API routes, containers, databases, branches — which then organise themselves into a technology network. It is the metaphor this portfolio runs on: find the root cause, then engineer the system that fixes it. The portfolio itself continues below; nothing here is needed to read it.
Online — available for work
The KnightArchitect
Bikesh Chaudhary·Full-Stack Developer
Full-stack developer since 2022, specializing in React, Next.js, TypeScript, and Node.js. Passionate about clean architecture, system design, and building products that scale.
- Years Building
- 4+
- Projects Shipped
- 15+
- Technologies
- 20+
- Milestones
- 5
Bikesh Command
System onlinePress ⌘K
Detective mode
The record, under analysis
Every number, case file and technology below is read off the same portfolio data — nothing here is decorative and nothing is invented.
Subject imaging
The Knight Architect
Subject analysis
- Subject
- Bikesh Chaudhary
- Classification
- Full-Stack Developer
- Specialisation
- Web applicationsSystem designBackend engineering
- Status
- Active
- Based
- Nepal
- Current post
- Software Engineer · Citytech Group Pvt Ltd
Full-stack developer since 2022, specializing in React, Next.js, TypeScript, and Node.js. Passionate about clean architecture, system design, and building products that scale.
- Experience
- 4+ yrs
- Case files
- 6
- Technologies
- 26
Detection
Technology detected
Targets identified in the working stack. Select one for its reading.
Standby
Standby — select a target for its reading.
Investigation
Case files
Each build opened as an investigation: the objective, the problem, the solution and what it left behind.
Architecture
System forensics
The shape of a system I build, layer by layer. Select a layer for the technologies behind it.
Trace
Standby
Select a layer to reveal its technologies.
Profile
Behavioural analysis
An engineering profile, each reading tied to the record it was taken from.
Profile
Self-reported readings, each corroborated by an entry in the record below.
System thinking
HIGHSystem Design and Clean Architecture carried in the tracked stack; every case file records the trade-offs behind its build.
Problem solving
HIGHA timing-out API traced to one missing index and an N+1 in a service layer — 47 lines, 1.2s down to 480ms.
Architecture
HIGHSOLID, DDD and hexagonal boundaries on the record; contributed to architecture and best-practice decisions at E-Signature.
Debugging
HIGHCode review, debugging and performance optimisation named in the Citytech and Virtuosway records.
Learning
HIGHTwo professional certifications, a BCA in progress, and 'researched and adopted modern technologies' on the current role.
Collaboration
STRONGPeer code review across three teams, agile delivery cycles, and signed testimonials from former colleagues.
Connections
Evidence board
How the record connects: the subject, the systems, the stack and the milestones.
Board
- BikeshSubject
Standby
Bikesh
Full-Stack Developer · 4+ years on the record
Select a node to trace its connections.
Chronology
Case history
The career as an investigation timeline. Select a year to open its records.
- Investigation ongoingSoftware Engineer · Citytech Group Pvt Ltd · in post
Node.jsExpress.jsMongoDBReact.jsNext.jsAnt Design
Ongoing
Current investigation
Case status
Case status
Ongoing
Mission status
Active
Software Engineer · Citytech Group Pvt Ltd · since Sep 2024
Current objective
- 01Build better systems.
- 02Solve harder problems.
- 03Keep learning.
Users shouldn't pay for our architectural decisions. Every abstraction should make the surface simpler, not the internals more clever.
About Me
Bikesh Chaudhary
Full-stack developer since 2022, specializing in React, Next.js, TypeScript, and Node.js. Passionate about clean architecture, system design, and building products that scale. Open source contributor and technical writer.
Complexity belongs in the code, not the interface
Users shouldn't pay for our architectural decisions. Every abstraction should make the surface simpler, not the internals more clever.
Build for the maintainer at 2 AM
The true test of code isn't how it runs on launch day — it's how easily a tired engineer can fix it six months later without breaking three other things.
Performance is a feature, not an afterthought
A slow experience excludes users on modest devices and fragile connections. Optimizing for the baseline raises the ceiling for everyone.
“Craftsmanship means sweating the details that most won't notice — the 200ms micro-interaction that makes a flow feel alive, the error message that guides instead of blames, the migration script that runs silently while users sleep. It's the discipline to refactor not because it's broken, but because it could be clearer.”
On craftsmanship
The 60% latency reduction that started with a question
A critical API was timing out under load. The team wanted to throw more servers at it. I spent two days reading the query plans and found a single missing index and an N+1 pattern buried in a service layer. The fix took 47 lines of code. Latency dropped from 1.2s to 480ms. The lesson? Before scaling out, understand what's actually happening inside.
Engineering Lab
What's on the bench.
Published work, current builds, and what I'm deliberately learning. The unfinished half of engineering, kept visible.
01 /Published01
02 /On the bench02
Active
Portfolio Platform v2
Dual-mode portfolio with PostgreSQL, Drizzle, and cinematic UI
Active
Multi-Tenant SaaS Platform
Enterprise SaaS with event-driven microservices
03 /Under study03
In progress
Rust
Systems programming for performance-critical services
In progress
Kubernetes
Container orchestration at scale
In progress
System Design
Distributed systems, consensus algorithms, and scalability patterns
Writing
Featured articles.
Thoughts on development, architecture, and the lessons learned building real products.
dev.to
Understanding JavaScript Closures
A practical guide to closures in JavaScript with visual examples and common use cases.
Read article
Hashnode
How I Built My First NPM Package
A breakdown of the development, publishing, and versioning process of my first package.
Read article
Medium
Deploying React Apps on Vercel
A step-by-step deployment tutorial for frontend developers using React and Vercel.
Read article
Signals
What people say.
Feedback from colleagues and collaborators I've worked with.
Engineering Notes
Articles & insights.
Deep dives into architecture, performance optimization, and the engineering decisions that shaped production systems.
Now
Current focus.
Currently Reading
Designing Data-Intensive Applications
By Martin Kleppmann
Building Microservices
By Sam Newman
Currently Exploring
Event-Driven Architecture
Patterns for resilient microservice communication
Street Photography
Capturing everyday moments in Kathmandu
Interested In
Distributed SystemsOpen SourceSystem DesignPhotographyMusic
Get in touch
Let's build something together.
Whether you have a project in mind, a question, or just want to say hello — I'd love to hear from you.