Enterprise systems & integration

Rian Fathany

I build the layer between a core platform and everything around it.

See the work ↓

Eleven years on insurance, HR and certification platforms. I write the requirements document and the stored procedure, and I own what happens between them.

Read a case study Email me

Selected work

Two-way partner integration for an insurance core

A national general insurer · Architect and engineer

The insurer sells through partners, each with their own system and their own idea of what an API should look like, and every submission was typed into the core by hand. Rather than one API per partner, I built a single gateway with two patterns: one-way for partners who only need a policy number back, two-way for those whose customer needs the real document.

LaravelPostgreSQLREST API Insurance corePartner onboardingMonitoring
Read the case study →

A retail insurance portal tied to core, finance, and payments

A national general insurer · IT representative on the task force

A B2B2C distribution portal where the sale, the policy, the invoice, and the payment used to move between three divisions by email and spreadsheet. I hold the architecture and write the requirements document with underwriting, finance, and operations, then build the flow that ties the portal to the insurance core, to SAP for finance and billing, and to the payment gateway. Claim validation and partner registration use LLM image vision to read the documents people upload.

B2B2CSAPPayment gatewayLLM vision
Read the case study →

Replacing a rigid vendor LMS with one that talks to its neighbours

A hospitality and lifestyle group · HR systems architecture

Three HR systems that had to exchange data with each other and with the payroll platform. The vendor learning platform could not reach any of them, so I built the replacement in house and wrote the integration layer over the payroll platform's API that the native product could not provide. The vendor licence went with it.

HRISLMSATSBuild vs buy
Read the case study →

How I work

  1. Sit with the business units firstBoth sides of an integration, not only IT. Most integration failures are disagreements about the data, discovered late.
  2. Find the pattern before writing codeFour partners with one shared flow beats four bespoke ones. The second integration is where the design is proven.
  3. Leave the core alone where possibleThe business runs on it. New behaviour goes in a layer that can be changed on a Tuesday.
  4. Ship the thing people watchA status screen and a document that reaches the customer are what make an integration feel finished to everyone outside engineering.

Stack

Partner channels into an insurance core, ERP and finance integrations, regulatory reporting. Laravel and PostgreSQL, with .NET and MS SQL Server where the legacy system calls for it.

Laravel
PostgreSQL
.NET
SQL Server
Node.js
Vue.js
React
MySQL
Oracle
Express
TypeScript
Google Cloud
Docker
Redis
Nginx
Linux

Usually on the other side of the integration: insurance core platforms, ERPs, HRIS, ATS and LMS products, e-certification and regulatory reporting. Lately with LLM vision for reading the documents people upload, on claims and partner onboarding.

Contact

Email · mrianfathany09@gmail.com

LinkedIn · linkedin.com/in/m-rian-fathany

Based in Jakarta, Indonesia