Skip to main content
Jamal Balya
HomeAboutPortfolioCertificationsContact

Jamal Balya

Fourteen years making complex, high-traffic systems provably reliable — across banking, retail, fintech and government platforms.

Open to senior QA roles

Pages

  • Home
  • About
  • Portfolio
  • Certifications
  • Contact

Connect

  • jamal.balya@gmail.com
  • LinkedIn
  • GitHub

© 2026 Jamal Balya. All rights reserved.

Next.js · Cloudflare Workers · D1

Portfolio

Building the tools I needed

When commercial test management stopped fitting the way the team worked, the answer was to build something that did.

Hero project

Exelion

An enterprise test management platform built to covering test case management, execution tracking and reporting for distributed QA teams.

Screenshots pending

Try Exelion

The panel below is a working wireframe of Exelion, not a picture of one. Scope a sprint, let the local AI draft the test cases, approve them, run them, and read the release verdict it builds out of your own decisions.

Exelion — QA Control PanelINTERACTIVE WIREFRAME
Solara RetailSprint 24STAGINGQA_LEAD

Step 1 of 5

Scope the sprint

Exelion reads Jira and never writes back to it. Choose the requirements this run has to prove.

SOL · Solara CheckoutREAD-ONLYSelected: 0

Select at least one ticket to continue.

A wireframe of Exelion, not the product itself. The layout, the lifecycle rules and the six-signal confidence model are Exelion's; the company, the tickets and the test cases are invented for this demo. Nothing here connects to a real Jira or a real test database.

  1. 01 · Problem

    Commercial test management tools charge per seat, and the cost scales with exactly the thing a growing QA organisation cannot avoid — more testers. Their AI features make it worse: drafting test cases means sending requirements and acceptance criteria to a third-party service, which is simply not available to teams working in banking, healthcare or government. So the choice was an expensive tool without AI, or an expensive tool that regulated work cannot use.

  2. 02 · Solution

    Exelion runs the AI on your own hardware. A CPU-only ONNX pipeline embeds each Jira ticket, retrieves similar existing cases, and drafts Gherkin scenarios — positive, negative and edge — with no request ever leaving the network and no GPU required. The AI is deliberately fenced in: it drafts and never approves, flags its own assumptions when acceptance criteria are thin, and skips empty tickets rather than inventing coverage. Every case moves through an enforced lifecycle — DRAFT, REVIEWED, APPROVED, ACTIVE, STALE, DEPRECATED — and every transition is written to an immutable audit log. Jira integration is read-only by design, so the system can never corrupt the source of truth. Built on Python 3.12 and FastAPI over PostgreSQL, with a React and TypeScript control panel, all business logic held in the backend so it can be audited in one place.

  3. 03 · Impact

    Removes per-seat licensing entirely, and makes AI-assisted test authoring available to teams that are contractually barred from sending requirements to an external service — the banks, insurers and government platforms this CV is built on. Release decisions stop being a judgement call: a six-signal confidence score combines coverage, execution results, skipped-test risk, defect quality, requirement traceability and flakiness into a GO / NO-GO assessment that can be exported and defended. Because every action is audited as it happens, an ISO 27001 or SOC 2 review reads existing evidence instead of triggering a scramble. Roughly 340 backend modules and 100 test files, with Playwright end-to-end coverage — built and maintained alongside a full-time QA role.

Selected engagements

The work behind the record

Three engagements told in full — what was wrong, what I owned, what I did about it, what changed, and why the change mattered to the business.

Rapor Pendidikan, a national education platform

GovTech Edu · 2023–2024

Problem
Every regression cycle before a release was run by hand. That made the release cadence, rather than the risk, decide how much got tested.
Responsibility
Quality for the platform end to end, from test design through to the release call.
Approach
Automated the regression suite and wired it into the delivery pipeline so it ran on every change, and validated the services directly at the API rather than only through the interface.
Result
Releases stopped waiting on a manual regression pass. The suite ran on every change instead, and faults that used to be found in production were being caught in the pipeline before merge.
Business impact
A platform used by schools across Indonesia could ship more often with fewer faults reaching the people who depend on it.
Tools
Selenium · Postman · GitLab CI/CD

Standardising the QA function

INA Digital Edu · 2025

Problem

Projects

Other projects

  • jemzsync

    jemzsync is a small helper you add to Obsidian, an app people use for writing notes. It has one job: check that your notes are really reaching your other devices — your phone, your tablet, your laptop — and show you proof. It works out what device you're on and checks the right service by itself. Mac, iPhone or iPad? It checks iCloud. Windows, Android or Linux? It checks Google Drive. You don't have to set anything up. While Obsidian is open, it keeps watching. If you type something, or a note arrives from your other device, it checks again a few seconds later. It's free, and anyone can look at how it's built.

    Live demo ↗
  • Jemz Vault Assistant

    Jemz Vault Assistant is a helper you add to Obsidian, an app where people keep all their notes. Think of your notes app like a giant notebook that never runs out of pages. After a year or two, you have thousands of pages. This helper gives you one screen with three tools: Inbox — a place where new, messy thoughts land, so you can clean them up one by one. Health — a check-up for your notebook, like a doctor's visit, that tells you what's broken. Find — a smart way to find any note, even when you forgot where you put it. Everything happens on your own computer. Nothing is sent to the internet, ever.

    Live demo ↗
  • Jemz Cleaner

    Imagine your computer is your bedroom. Every time you play, do homework, or watch something, the computer leaves little scraps behind — like wrappers, old drawings, half-finished snacks. It does this on purpose, so things load faster next time. But it never throws the scraps away. After a year, your bedroom floor is covered. Jemz Cleaner is a tidying helper for that room. It's an app for Windows and Mac computers. It walks around, finds the junk, shows you exactly what it found, and cleans it up — but only the stuff you say yes to. Two things make it different from other cleaning apps: It shows you everything first. Every single file, with its name, size, and a little badge saying "safe to remove" or "hmm, look at this one first." No surprises. It never really deletes anything right away. Files go into a Quarantine Vault — think of it as a box under the bed. If you realize you needed something, you press undo and it comes right back. It also runs completely on your own computer. Nothing about your files ever gets sent anywhere on the internet. Not even a list of names.

    View source ↗
  • Recension

    Recension — compare any two files with forensic precision. Free for everyone, forever. Text, code, JSON, PDF, Word, PowerPoint, spreadsheets, images, and entire folders. It produces legal-grade redlines, exports native Word tracked changes, reads scanned documents with OCR, and runs fully offline on your own machine. Recension — compare any two files with forensic precision. Free for everyone, forever. Text, code, JSON, PDF, Word, PowerPoint, spreadsheets, images, and entire folders. It produces legal-grade redlines, exports native Word tracked changes, reads scanned documents with OCR, and runs fully offline on your own machine. One Rust engine compiles to WebAssembly for the browser and native for the desktop, so the web and the desktop never disagree about the same files. That parity isn't a claim, it's a test that runs in CI.

    Live demo ↗

Tooling

Tools directory

Tools built to solve a specific problem in the quality workflow.

  • Exelion

    Test Management

    Enterprise test management platform replacing TestRail — test case management, execution tracking and reporting.

  • Recension

    Process Improvement

    Recension compares any two files — documents, code, images, spreadsheets, whole folders — and produces legal-grade redlines, Word tracked changes, and OCR of scanned pages. It runs fully offline on your own machine, free for everyone, with no account required.

Quality practice differed from team to team, so coverage was uneven and nobody could say before a release which parts of the product had actually been exercised.
Responsibility
The QA function itself: the standard, the tooling behind it, and adoption across the teams.
Approach
Wrote one QA playbook for every team, introduced risk-based prioritisation so the highest-risk paths got the deepest coverage, and brought AI-assisted tooling into test authoring.
Result
Every team worked to the same written standard, the riskiest paths were covered first by design rather than by luck, and issues that had been surfacing after a release were being found before it.
Business impact
Release decisions stopped being a judgement call and became a reading of evidence the whole organisation could see.
Tools
Risk-based testing · TestRail · JIRA

Migrating a core banking platform

PT Collega Inti Pratama · 2011–2016

Problem
A bank's core platform had to be replaced. Banking data does not tolerate a partial success, and KYC processes had to keep meeting their regulatory obligations throughout.
Responsibility
Quality control for the migration and for the KYC and core banking flows around it, across system and user acceptance testing.
Approach
Structured SIT and UAT over the whole migration path, verifying at the database rather than settling for screen-level confidence.
Result
The migration completed with zero data loss.
Business impact
A bank moved to a new core platform without losing a single customer record — the outcome that mattered more than the schedule.
Tools
SIT · UAT · SQL Server · PowerBuilder

Before

The TestRail era

  • ✕Per-seat licensing that grows with every new tester hired
  • ✕Reporting shaped by the vendor, not by how the team works
  • ✕Workflow changes depend on someone else's roadmap

After

The Exelion era

  • ✓No recurring per-seat licence cost
  • ✓Reporting built from the metrics the team actually reviews
  • ✓The workflow is owned by the team and changes when they need it to