• Java Software Engineer — 10 years
  • Kathmandu, Nepal · UTC+05:45
  • Now: Media Fusion, Japan (remote)

Ashim Regmi, Java software engineer. Most of what I build, you’ll never see.

That’s the point.

Ten years of Java and Spring behind things that have to work: APIs for a fleet and contract platform used by Volvo, BMW and Daimler Truck, payments across 7+ gateways, and notifications that reach millions of people within minutes.

years in Java engineering
10
companies across Nepal, Poland & Japan
6
payment gateways integrated
7+
news sources aggregated every minute
80+

System status — operational · 10 yrs uptime

How I build: Principles, with receipts.

Seven working principles, each footnoted with something I’ve actually shipped.

  1. Architecture

    Draw the boundaries first.

    Most architecture is deciding what talks to what, and through which contract. Get the boundaries and the APIs right, and the framework underneath becomes a detail.1

  2. Scalability

    Design for the millionth user.

    Scale isn’t a phase you reach; it’s a requirement you design in. Assume the audience is huge, the target keeps moving, and the deadline is measured in minutes.2

  3. Performance

    Treat time as a budget.

    When a job runs every minute, every second of it has to be accounted for. Fast is a feature. Predictable is a better one.3

  4. Developer experience

    Automate the road to production.

    The fastest teams trust their pipeline. Build and release steps belong in code — versioned, reviewed and boring.4

  5. Product thinking

    Meet people where they already are.

    Integrations are product work. The best checkout isn’t the one with the nicest API — it’s the one people already use.5

  6. Maintainability

    Leave it easier to change.

    Legacy code earned its keep; it deserves a careful exit, not a heroic rewrite. Modernize in steps, keep it running, and make the next change cheaper.6

  7. Leadership

    Lead close to the code.

    Leadership is mostly clarity — about goals, ownership and what “done” means. I practised it as an engineering manager, leading a cross-functional team at Hamro Patro.7

Selected work: Four systems, made visible.

Backend work doesn’t screenshot well. So instead of screenshots: schematics — illustrations of what each system does, not exact architecture.

01 / 04

Fleet & contract management

LEO System

Backend services and APIs for an enterprise leasing platform used by Volvo, BMW and Daimler Truck.

Role
Java Developer
Company
Asseco Data Systems
Where
Poland
When
Oct 2022 – Dec 2025
Schematic: the work at Asseco Data Systems Illustrative map. Legacy Java EE modules (WildFly, JSF/RichFaces) modernized toward microservices built with Java, Spring Boot, Apache Camel and Hibernate/JPA, using RabbitMQ for asynchronous processing. Separately, LEO System, a fleet and contract platform used by Volvo, BMW and Daimler Truck, with REST APIs for its contract, customer and invoicing modules. Angular admin apps for licenses, users and workflows, and Bamboo Specs CI/CD for NPM front-ends and Java microservices. Legacy Java EE WildFly · JSF / RichFaces modernized toward Microservices RabbitMQ async processing Java · Spring Boot · Apache Camel · Hibernate / JPA LEO System contract REST API customer REST API invoicing REST API fleet & contract management Used by Volvo BMW Daimler Truck Angular admin apps licenses · users · workflows CI / CD Bamboo Specs — CI/CD for NPM front-ends and Java microservices Schematic: the work at Asseco Data Systems Illustrative map. Legacy Java EE modules (WildFly, JSF/RichFaces) modernized toward microservices built with Java, Spring Boot, Apache Camel and Hibernate/JPA, using RabbitMQ for asynchronous processing. Separately, LEO System, a fleet and contract platform used by Volvo, BMW and Daimler Truck, with REST APIs for its contract, customer and invoicing modules. Angular admin apps for licenses, users and workflows, and Bamboo Specs CI/CD for NPM front-ends and Java microservices. Legacy Java EE WildFly · JSF / RichFaces modernized toward Microservices RabbitMQ async processing Java · Spring Boot · Apache Camel · Hibernate / JPA LEO System contract REST API customer REST API invoicing REST API Used by Volvo BMW Daimler Truck Angular admin apps licenses · users · workflows + Bamboo Specs CI/CD for NPM & Java
Fig. 01 The work at Asseco, mapped: LEO System’s APIs, the microservices, the modernization and the tooling. Illustrative.

The system

LEO System is a fleet and contract management platform used by Volvo, BMW and Daimler Truck.

What I did

  • Delivered REST APIs for LEO System’s contract, customer and invoicing modules.
  • Tested with JUnit and integration tests.

Also at Asseco

  • Built and maintained backend microservices with Java, Spring Boot, Apache Camel and Hibernate/JPA, using RabbitMQ for asynchronous processing.
  • Modernized legacy Java EE modules (WildFly, JSF/RichFaces) toward microservices.
  • Built the Angular admin apps used to manage licenses, users and workflows.
  • Contributed Bamboo Specs to automate CI/CD for NPM front-ends and Java microservices.

Outcome

Shipped to production. The contract, customer and invoicing APIs went live inside a platform used by Volvo, BMW and Daimler Truck.

  • Java
  • Spring Boot
  • Apache Camel
  • Hibernate / JPA
  • RabbitMQ
  • Java EE / WildFly
  • JSF / RichFaces
  • Angular
  • JUnit
  • Bamboo

02 / 04

Payments

Gateway integration layer

One integration across global and Nepali payment gateways, for a consumer platform.

Schematic: one integration layer, many payment gateways Illustrative. A checkout on a consumer platform and a single integration layer spanning global gateways (Stripe, PayPal, Cybersource) and Nepali gateways (ConnectIPS, eSewa, Khalti). Six shown; 7+ integrated in total. Consumer platform checkout One integration layer Global Nepal Stripe PayPal Cybersource ConnectIPS eSewa Khalti Six shown · 7+ integrated in total Schematic: one integration layer, many payment gateways Illustrative. A checkout on a consumer platform and a single integration layer spanning global gateways (Stripe, PayPal, Cybersource) and Nepali gateways (ConnectIPS, eSewa, Khalti). Six shown; 7+ integrated in total. Consumer platform checkout One integration layer Global Nepal Stripe PayPal Cybersource ConnectIPS eSewa Khalti Six shown · 7+ integrated in total
Fig. 02 One integration layer, six gateways. Illustrative.

6gateways behind one integration layer — 7+ integrated in total

Role
Senior Software Engineer
Company
Hamro Patro, Inc.
Where
Kathmandu
When
Mar 2019 – Oct 2021

The problem

A consumer platform needed to take payments through international providers and through Nepal’s own payment networks — each with its own API and flow.

What I did

Integrated Stripe, PayPal, ConnectIPS, Cybersource, eSewa and Khalti behind one unified integration layer.

The hard part

Six providers, six different APIs and flows — presented to the rest of the platform as one.

Outcome

Shipped to production. Six gateways, global and Nepali, behind one integration layer for a consumer platform.

  • Stripe
  • PayPal
  • Cybersource
  • ConnectIPS
  • eSewa
  • Khalti

03 / 04

Messaging at scale

Notification service

An in-house service that sends targeted email and mobile campaigns to dynamic segments of millions of users — within minutes.

Fig. 03 A campaign reaching a dynamic segment. Every run draws a new one.
Audience
Millions
Time to reach
Minutes
Targeting
Dynamic segments
Channels
Email + mobile
Role
Engineering Manager
Company
Hamro Patro, Inc.
When
Nov 2021 – Sep 2022

The problem

Send targeted email and mobile campaigns to dynamic segments of millions of users — and reach them within minutes.

What I did

Built an in-house notification service for targeted email and mobile campaigns, capable of reaching dynamic segments of millions of users within minutes.

The hard part

Targeting dynamic segments of millions of users, and still reaching them within minutes.

Outcome

Shipped to production. Targeted campaigns reaching dynamic segments of millions of users within minutes.

04 / 04

Content pipeline

News aggregation, rebuilt

A pipeline that gathers news from more than 80 portals every minute and publishes it to millions of readers.

Sources
80+
Cycle
60 s
Readers
Millions
Role
Senior Software Engineer
Company
Hamro Patro, Inc.
When
Mar 2019 – Oct 2021
0 s 15 30 45
80+ portals, every minute
Fig. 04 80 ticks for 80+ portals. The sweep takes exactly one real minute to go round — the same cycle as the pipeline.

The problem

A minute-by-minute pipeline across 80+ sources, publishing to millions of readers, had to be rebuilt for reliability at scale.

What I did

Revamped the pipeline that gathers news from more than 80 portals every minute and publishes it to millions of readers.

The hard part

Keeping a one-minute cycle across 80+ portals while publishing to millions of readers.

Outcome

Shipped to production. Rebuilt for reliability at scale — 80+ portals every minute, published to millions of readers.

More from the log

Smaller entries, same care.

  • 2021–22 Let’s Read Asia Led the cross-functional team building its web and mobile apps, as Engineering Manager at Hamro Patro.
  • 2019–22 Tele-services calling Built audio/video calling for tele-services, then led the team behind it.
  • 2021–22 Bare-metal cloud Managed the company’s bare-metal cloud infrastructure on Proxmox.
  • 2017–19 Google Cloud backends Java services on App Engine, backed by Cloud Datastore, alongside web apps in various JS frameworks.
  • 2026 Writing on AI data foundations Two articles on Markdown and YAML as the plain-text backbone of AI workflows.
  • 2013–17 Where it started Pixel-perfect responsive sites and small HTML5 games, then internships in banking and services.

Career: Ten years of uptime.

From intern to engineering manager — and back to hands-on backend work. Six companies, across Nepal, Poland and Japan.

  1. Feb 2026 – Present Current

    Media Fusion Co., Ltd.

    Java Software Engineer Current

    Kathmandu · remote for a Japan-based company

    Backend systems in Java and Spring — continuing a decade-long focus. Also writing about the plain-text foundations of AI workflows.

    • Java
    • Spring
  2. Oct 2022 – Dec 2025 3 yrs 3 mos

    Asseco Data Systems

    Java Developer

    Poland

    Built and maintained backend microservices, and delivered REST APIs for the contract, customer and invoicing modules of LEO System, a fleet and contract management platform used by Volvo, BMW and Daimler Truck. Modernized legacy Java EE modules toward microservices, built the Angular admin apps, and contributed Bamboo Specs to automate CI/CD.

    Case study: LEO System
    • Java
    • Spring Boot
    • Apache Camel
    • Hibernate / JPA
    • RabbitMQ
    • Angular
    • JUnit
    • Bamboo
  3. Jun 2017 – Sep 2022 5 yrs 4 mos

    Hamro Patro, Inc.

    Three roles, one company

    Kathmandu

    1. Engineering ManagerNov 2021 – Sep 2022

      Led a cross-functional team building Let’s Read Asia’s web and mobile apps and audio/video calling for tele-services. Built an in-house notification service reaching dynamic segments of millions of users within minutes. Managed the company’s bare-metal cloud infrastructure on Proxmox.

      Case study: Notification service
    2. Senior Software EngineerMar 2019 – Oct 2021

      Integrated Stripe, PayPal, ConnectIPS, Cybersource, eSewa and Khalti as payment gateways. Built audio/video calling for tele-services. Revamped a pipeline gathering news from 80+ portals every minute for millions of readers.

      Payments News pipeline
    3. Software EngineerJun 2017 – Feb 2019

      Backend services in Java on Google Cloud App Engine, backed by Google Cloud Datastore, alongside web apps built with various JS frameworks.

    • Java
    • Google App Engine
    • Cloud Datastore
    • Payment APIs
    • Proxmox
    • JUnit
  4. 2013 – 2017 Early career

    Trainee & intern roles

    Leapfrog Technology · Agricultural Development Bank Ltd. · Deerwalk Services

    Started out building pixel-perfect responsive sites and small HTML5 games, then interned in banking and services environments before moving into professional Java development.

    • HTML5
    • Responsive web

Technical expertise: Depth, by domain.

Not a logo wall. What I work with, grouped by the problems it solves — and where it shipped.

  1. Backend

    • Java
    • Spring / Spring Boot
    • Hibernate / JPA
    • Java EE / WildFly
    • REST APIs
    • Microservices

    Shipped in: Media Fusion · Asseco (LEO System) · Hamro Patro

    Ten years of Java — from App Engine services to Spring Boot microservices.

  2. Integration & messaging

    • Apache Camel
    • RabbitMQ
    • Stripe
    • PayPal
    • Cybersource
    • ConnectIPS
    • eSewa
    • Khalti

    Shipped in: Asseco (LEO System) · Hamro Patro (payments)

    RabbitMQ for asynchronous processing; Camel routes; six gateways behind one integration layer, 7+ integrated in total.

  3. Architecture

    • Microservices
    • Legacy modernization
    • Asynchronous processing
    • Multi-gateway integration
    • High-frequency ingestion
    • Segment fan-out

    Shipped in: LEO System · Payments · News pipeline · Notifications

  4. Frontend

    • Angular
    • JSF / RichFaces (legacy)
    • JavaScript frameworks
    • Responsive web
    • HTML5 games

    Shipped in: Asseco (admin apps) · Hamro Patro (web apps) · Early career

  5. Cloud & infrastructure

    • Google Cloud App Engine
    • Proxmox (bare-metal)
    • Docker

    Shipped in: Hamro Patro · Docker Essentials certification

    Managed the company’s bare-metal cloud infrastructure on Proxmox as Engineering Manager.

  6. Data

    • MySQL
    • PostgreSQL
    • MongoDB
    • Elasticsearch
    • Google Cloud Datastore
    • Hibernate / JPA

    Shipped in: Hamro Patro (Datastore) · Asseco (Hibernate / JPA)

    Relational, document and search stores — MySQL and PostgreSQL, MongoDB, Elasticsearch — plus Google Cloud Datastore.

  7. Testing & quality

    • JUnit
    • Unit tests
    • Integration tests

    Shipped in: TalkFun Japan · LEO System (Asseco) · Hamro Patro

  8. Delivery & tooling

    • Bamboo Specs (CI/CD as code)
    • NPM
    • Docker
    • Claude Code

    Shipped in: Bamboo Specs & NPM — Asseco · Docker — certified

  9. AI-assisted engineering

    • Markdown & YAML for AI workflows
    • Claude Code

    Shipped in: Published on note · 2026

  10. Leadership

    • Engineering management
    • Cross-functional teams
    • Infrastructure management
    • Technical writing

    Shipped in: Hamro Patro (Engineering Manager) · note (writing)

About: Hello from UTC+05:45.

I work from Kathmandu — on one of the world’s few time zones with a 45-minute offset.

I’m Ashim Regmi, a Java software engineer with a decade-long focus on backend systems: at Hamro Patro in Kathmandu, on systems serving millions of users; at Asseco Data Systems in Poland, including APIs for LEO System, an enterprise fleet and contract platform; and now, remotely, at Media Fusion, a company based in Japan.

It started with pixel-perfect responsive sites and small HTML5 games. Since then I’ve been an engineer, a senior engineer and an engineering manager — and gone back to hands-on backend work.

Lately I write about the plain-text foundations of AI workflows: why Markdown matters, and how YAML keeps AI workflows manageable.

Outside the day job I keep learning: a master’s in IT, earned alongside work, and certifications in IBM blockchain and Docker.

KathmanduUTC+05:45

JapanJST · UTC+09:00

Based in
Kathmandu, Nepal
Working with
Media Fusion Co., Ltd. — Japan, remote
Languages
English — full professional
Nepali — native
Education
M.S., Information Technology Islington College Kathmandu · 2022–2024 B.Sc., Computer Science & IT Deerwalk Institute of Technology · 2012–2016
Certifications
IBM Blockchain Foundation Developer IBM Blockchain Essentials Docker Essentials: Extend Your Apps With Containers

Contact: Let’s build the part nobody sees.

Open to Java backend and platform engineering roles.

It’s in Kathmandu right now.