Skip to content
www.gimesha.com

Gimesha Nirmal · Systems and platform engineering

Building software systems with clear ownership boundaries.

I work across backend platforms, developer tooling, document-processing systems, and multi-client products—making state, service, and failure boundaries explicit.

View selected workRead engineering case studiesDownload CV

Portfolio-owned systems

Selected systems

A small set of systems where the architecture, ownership boundaries, and engineering decisions are the story.

Explore all systems
FeaturedActiveSystems software

Termstead

A native terminal product shell built around daemon-owned sessions and a client-owned workspace.

Problem
Build a native terminal product without mixing GUI layout policy with PTY, process, and terminal-session authority.
Primary boundary
Daemon and session authority
RustterminaldPTYsGPUIUnix sockets
Portfolio-owned systemExplore system
FeaturedActiveDeveloper tools

Platen PDF

A multi-repository document platform that separates the web workspace, Go API, and Python processing boundary.

Problem
Coordinate browser workflows and document processing without turning every PDF operation into a separate, inconsistent implementation.
Primary boundary
Web application
Next.jsReactTypeScriptGoFiber
Portfolio-owned systemExplore system
FeaturedActiveFinancial systems

Banking Platform

A multi-client banking system spanning a Spring Boot core, Next.js web application, Android client, and FastAPI KYC service.

Problem
Keep core banking, web, mobile, and identity-verification concerns explicit while the clients and services evolve together.
Primary boundary
Core banking backend
Spring BootJavaHibernate/JPAMySQLFlyway
Portfolio-owned systemExplore system

How I build

Make boundaries visible.

The strongest project stories start with ownership, lifecycle, and failure boundaries—not a list of tools.

Termstead

Boundary

Daemon and session authority

ResponsibilityOwn PTYs, child processes, authoritative terminal state, terminal modes, revisions, and daemon-session lifetime.

Decision

Keep layout client-owned while sessions remain daemon-owned.

Explore Termstead

Platen PDF

Boundary

Web application

ResponsibilityProvide the Next.js/React/TypeScript document workspace, tool routes, shared UI, and browser-side workflow.

Decision

Represent the frontend, Go backend, worker, and related SDK as one portfolio project with explicit repository roles.

Explore Platen PDF

Banking Platform

Boundary

Core banking backend

ResponsibilityOwn the authoritative Spring Boot banking API, authentication, authorization, customers, accounts, financial workflows, ledger, MySQL/Flyway persistence, KYC orchestration, and server-side banking rules.

Decision

Represent four independently versioned repositories as one Banking Platform.

Explore Banking Platform

Selected case studies

Read the decisions behind the systems.

Short technical write-ups on the problems, boundaries, and trade-offs behind selected work.

View all case studies
Platen PDF3–4 min

Designing a Modular Document Platform

A shared Next.js and Go architecture turned many PDF actions into one consistent product experience.

Platform architectureRead study
Platen PDF3–4 min

Handling Real-World PDF Edge Cases

Upload failures, crop issues, and tricky file states were handled with guarded flows and safer validation.

Validation and failure handlingRead study
Banking Platform3–4 min

Architecting a Modular KYC Microservice Platform

Modular Spring Boot, Next.js/React, Android, and FastAPI KYC boundaries with an explicit component-check and review path.

Cross-stack service boundariesRead study

Supporting evidence

Recent engineering activity

Repository activity and external demos are supporting signals. The curated systems above remain the source of portfolio identity.

Recent repository activity

  • merged PR in gimesha-adikari/pdfnest-backend
  • Created branch in gimesha-adikari/pdfnest-backend
  • merged PR in gimesha-adikari/pdfnest-backend
  • Pushed code to gimesha-adikari/pdfnest-backend

Next step

Start with a system, not a statistic.

Explore the project boundaries first, then read the case studies when you want the reasoning behind them.

Browse selected workGet in touch