Full-stack Engineer
Full-stack systems for public institutions, regulated operations, and long-lived business platforms.
I build across frontend, backend, and operations so systems stay understandable, auditable, and maintainable as policies, teams, and requirements change over time.
Public institutions, a regional Islamic bank (non-core internal logistics), commercial F&B, and SaaS products.
Also develop Government-to-Citizen (G2C) public service applications.
Based in Indonesia.
Selected Work
System case studies covering both internal platforms and public-facing services, with emphasis on constraints, architectural decisions, and long-term operational reality.
Municipal Audit, Survey & Public Service (G2C) Platform
Full-stack Engineer
Public Sector
Internal Operations
Audit & Survey
G2C Service
Context
A centralized platform used by local government to manage surveys, audit findings, follow-up actions, and reporting across multiple internal units, while also supporting a public-facing Government-to-Citizen (G2C) service that connects citizen submissions with internal review and resolution workflows.
Core Constraints
Mandatory audit trails and long-term retention, policy changes that affect scoring rules, and incremental adoption without interrupting ongoing audits.
Architectural Decisions
Separated survey definition, scoring logic, findings, and reporting into distinct domains; used explicit state transitions for traceable reviews and corrections; designed guided UI workflows for constrained actions rather than free input.
Operational Considerations
Introduced changes through additive rules and versioned structures; preserved historical records even when evaluation criteria evolved; optimized interfaces for review and accountability, not speed.
Outcome
Provided a stable internal audit platform while enabling a public-facing G2C service that improved traceability from citizen input to official follow-up.
Internal Logistics Workflow System (Bank)
Full-stack Engineer
Financial Operations
Non-Core Systems
Compliance
Context
An internal logistics and workflow system supporting branch operations and compliance processes outside the core banking system.
Core Constraints
No interaction with core banking transactions, strong separation between operational workflows and financial records, and compliance requirements that limit direct data modification.
Architectural Decisions
Defined boundaries between operational commands, approvals, and reporting; modeled role-based workflows around responsibility; built staged approval interfaces instead of real-time overrides.
Operational Considerations
Used conservative defaults when processes fail or stall; maintained audit visibility into who initiated, reviewed, and approved actions; introduced change through controlled paths to avoid untraceable corrections.
Outcome
Predictable internal operations while maintaining compliance boundaries and audit clarity.
Multi-Outlet POS & Inventory Platform
Full-stack Engineer
F&B
POS
Inventory
Context
A POS and inventory platform for multi-outlet restaurant operations, designed to work reliably across outlets with varying connectivity and operational practices.
Core Constraints
Intermittent connectivity, real-world inventory discrepancies, and high operational pressure during peak hours.
Architectural Decisions
Implemented offline-tolerant transaction handling with deferred reconciliation; separated transactional flows from reporting views; minimized operator decisions during critical flows through focused UI design.
Operational Considerations
Prioritized continuity of operation over strict real-time consistency; handled reconciliation through explicit adjustment workflows; degraded gracefully so failures do not block daily operations.
Outcome
Improved consistency across outlets and reduced manual correction effort without changing existing operational habits.
SaaS Invoicing & Subscription Platform
Full-stack Engineer
SaaS
Billing
Multi-tenant
Context
Billing and invoicing systems used across multiple SaaS products with evolving business rules and subscription models.
Core Constraints
Changing pricing policies, long-lived financial records, and multi-tenant isolation.
Architectural Decisions
Used configuration-driven billing logic; modeled explicit lifecycle states for invoices and subscriptions; built review-oriented interfaces for exceptions instead of direct raw edits.
Operational Considerations
Handled anomalies conservatively; separated billing events from reporting; evolved schemas safely to preserve historical correctness.
Outcome
A stable foundation reused across products while keeping billing behavior transparent and controllable.
Capabilities
Full-Stack System Design
Working across frontend, backend, and operations so workflows, rules, and interfaces remain aligned as systems evolve.
Business Logic & Workflow Modeling
Translating institutional and operational rules into explicit, reviewable system behavior.
Operational Reliability
Designing for auditability, traceability, and predictable failure modes in real environments.
Long-Term Stewardship
Maintaining systems beyond delivery through documentation, migrations, and controlled change.
Collaboration
I work with public institutions, a regional Islamic bank on internal (non-core) logistics systems, and commercial businesses across F&B and SaaS products.
Principles
- Clarity is more valuable than cleverness.
- Systems must be understandable by people who did not build them.
- Change should be reversible when data is long-lived.
- Auditability is part of system design, not an afterthought.
- Operational simplicity matters more than architectural novelty.
- A system is only successful if it can be maintained over time.
About
I approach software systems as long-term responsibilities rather than short-term deliverables. My focus is building full-stack platforms that remain reliable and understandable through organizational change, policy updates, and years of operational use.