Muhammad Bintang Al Akbar

I'm a front end engineer who builds complex business software end-to-end — the kind of systems companies actually run on. I've architected and shipped ERP and internal business platforms from scratch: multi-module dashboards, inventory and finance workflows, role-based access control, approval chains, and data-heavy tables that stay fast under real load.

I'm not just a screen-builder. I design the information architecture, model the data, build a reusable design system so features ship consistently, and connect it all to the API. When the backend isn't ready, I build it myself.

What I bring to a team:

• 🏢 Business-domain depth — I've built ERP and internal tools from zero: complex forms, multi-step workflows, permissions, reporting, and audit trails. I understand the messy real-world logic behind enterprise software.
• 🎯 Design systems that scale — a typed token system with cross-platform adapters so web and React Native ship from one source of truth, keeping large teams consistent.
• 🧱 Full ownership — comfortable from Figma to frontend to Go/Gin API to deployment. I close gaps instead of waiting for them.
• ✅ Engineering discipline — strict TypeScript, clean layered architecture, automated tests, semantic HTML, and accessibility as a baseline, not an afterthought.

Looking for: Front end / React Native / product engineering roles — especially building data-rich business apps, internal tools, or design systems. Remote or hybrid.

I'm a Front End Engineer from Indonesia who builds the software businesses run on — ERP modules, internal admin platforms, operational dashboards, and the design systems that hold them together.

What I care about:

1. Solving real business problems — inventory, finance, approvals, permissions, reporting. I learn the domain, model the data, and turn tangled requirements into interfaces people actually want to use.
2. Architecture that lasts — typed contracts, layered structure, reusable components. Code that a team can extend two years from now without fear.
3. Craft in the details — strict TypeScript, automated tests, accessibility, and performance that holds up when the data tables get big and the workflows get real.

I take features from blank screen to production: design, frontend, API, deploy. I close the gaps nobody else wants to own.

Beyond the public projects, the bulk of my work is business software — the systems that run day-to-day operations. Things I've designed and built:

I take these from requirements → data model → UI → API → deploy. I'm the engineer who turns a vague internal spec into software people rely on.

Dominated by TypeScript across React, React Native & Next.js, with Go powering the backend layer and CSS / SQL rounding out the full-stack business-app work.

c3f9a1b  feat: shipped an ERP module from blank screen to production
8b21e04  arch: layered the codebase so the next dev never has to guess
6d4c0e7  feat: role-based access control that survived a security review
3ae7f02  refactor: extracted a design system — feature velocity +40%
f01c233  perf: virtualized a 50k-row data table, kept it at 60fps
a12b877  chore: strictest TypeScript config money can't buy
2c6d8aa  test: automated the workflows so releases stopped being scary

PID   NAME                              CPU    MEM    STATUS
001   solve-the-business-problem        ████   ███    running
002   strict-typescript                 ████   ██     running
003   clean-layered-architecture        ███    ████   running
004   reusable-design-systems           ███    ██     running
005   own-it-end-to-end                 ██     ███    running
006   accessibility-WCAG-AA             ███    ██     running
007   automated-tests-before-push       ██     █      running
008   performance-under-real-load       ██     █      running

Last updated: June 2026

• 🏢 Building ERP & internal business modules — workflows, RBAC, reporting, and data-heavy admin screens
• 🚢 Shipping @stareezy-ui/components — 17+ cross-platform components that keep product teams consistent
• 🏗️ Architecting scalable frontend structure: typed contracts, clean layers, automated tests
• 📖 Sharing what I learn about design systems and real-world business-app engineering

I'm open to front end, React Native, and product engineering roles — especially building data-rich business apps, internal tools, ERP platforms, or design systems. Remote or hybrid. If you're building something where engineering craft and ownership matter, I'd love to hear about it.

The best interfaces are invisible. The best systems are inevitable. Build things that respect the people who use them.