A Senior Frontend Engineer
for scalable product teams
I build frontend systems for SaaS platforms, dashboards, and mobile products, with a focus on performance, maintainability, and collaboration across product, design, and backend teams.
My ResumePRODUCT SYSTEMS
I build the interface layer where complex products become usable.
Instead of repeating my resume here, this page highlights the product surfaces I have spent the most time shaping: dashboards, multi-tenant SaaS, and mobile delivery systems.
Enterprise dashboards
Data-heavy admin surfaces, reporting flows, and operational tools built for teams that need clarity under pressure.
users supported
Multi-tenant SaaS
Frontend foundations for tenant-aware products with configurable roles, reports, branding, and product behavior.
tenant setups
Mobile delivery
React Native workflows, white-label UI systems, and release automation for teams shipping across platforms.
shorter release cycles
Current focus
Senior frontend systems for SaaS, dashboards, and product teams
Recent environment
Telkom Group products, multi-tenant platforms, and mobile workflows
Side practice
MiCA Studio experiments around tooling, deployment, and product ideas
HOW I WORK
A calm path from ambiguity to shipped UI.
Product sense first
I start by understanding what users need to do, what the business needs to learn, and what the interface must make obvious.
Shape the frontend system
I turn unclear requirements into component boundaries, data contracts, state flow, and delivery slices the team can reason about.
Ship with restraint
I build typed, accessible, performance-aware UI without adding ceremony that slows the next iteration.
Protect the release
I use review, checks, performance attention, and follow-up polish so the feature holds up after launch.
SIGNALS
Small proof, honestly framed.
Jun 2024
Best Stunting Risk Management System
Recognition for a healthtech platform supporting structured stunting risk management and reporting.
Dec 2018
Hacktiv8 Bootcamp Graduate
Completed intensive fullstack JavaScript training before moving into product engineering roles.
REMOTE STYLE
Clear enough for async, polished enough for users.
Readable decisions
Tradeoffs are written down, not hidden in chat history.
Calm ownership
I keep scope, risks, and follow-ups visible without drama.
Good taste in details
The UI should feel considered, not merely complete.
Timezone-friendly flow
Work should be easy to pick up, review, and continue async.