Experienced software engineer with 8+ years of experience, specializing in backend development with Golang as my primary programming language.
Years of experience
8+
Designing, prototyping, and delivering scalable backend systems.
Primary backend language
Golang
My strongest production experience is in Go-based backend systems.
Team leadership
5 engineers
Led backend teams and coordinated critical delivery work.
Domains
Fintech / HR / Transport
Hands-on experience in several business-critical sectors.
I am a senior software engineer specializing in backend development, distributed systems, and scalable product delivery. My strongest experience sits around Golang-based backend services, infrastructure planning, clean architecture, and backend-heavy product execution across fintech, HR, transportation, and internal operations platforms.
Formally, I have 8+ years of experience designing, prototyping, and developing scalable backend solutions across fintech, HR, and transportation domains. I am a strong advocate for clean architecture and SOLID principles, with a proven track record of leading critical projects and resolving complex technical challenges.
I am also familiar with JavaScript, TypeScript, C#, PHP, and Dart, and I can quickly adapt to these languages when needed to deliver practical and maintainable solutions.
I am deeply curious about technical implementation and consistently seek to expand my knowledge beyond immediate responsibilities so I can solve complex backend problems, improve delivery quality, and help teams move with confidence.
Clean Architecture
I use explicit boundaries to keep services easier to scale and maintain.
Go + PostgreSQL
Production backend services, APIs, integrations, and transaction-heavy systems.
CI/CD + Infra
Pipelines, orchestration, proxies, secret management, and environment reliability.
Lead and execute
I like owning critical backend work while staying close to business needs and delivery.
I am a senior software engineer with more than seven years of experience building backend systems and scalable business platforms. My strongest specialization is backend development with Golang, supported by working knowledge of JavaScript, TypeScript, PHP, C#, and Dart when product context requires flexibility.
Across fintech, HR SaaS, transportation, and internal operational products, I have worked on architecture design, API development, multi-tenant systems, observability, CI/CD, infrastructure setup, and large-scale backend improvements. I care about clean architecture, operational clarity, and building systems that stay maintainable as they grow.
This portfolio is structured to show not only what I built, but how I think: problem framing, technical decisions, architecture, security awareness, and measurable delivery impact.
| Category | Skills | Proficiency |
|---|---|---|
| Languages | Golang, JavaScript, TypeScript, PHP, C#, Dart | Advanced |
| Databases | PostgreSQL, MySQL, MariaDB, MongoDB, Redis, SQL Server | Advanced |
| Backend & Architecture | REST API, Microservices, Multi-tenant Design, Clean Architecture, SOLID, System Integration | Advanced |
| DevOps & Platform | Docker, Docker Swarm, Jenkins, GitLab CI, GitHub Actions, Traefik, Kong | Advanced |
| Observability & Security | ELK Stack, Prometheus, Grafana, New Relic, APM, RBAC, Rate Limiting | Intermediate to Advanced |
These featured projects emphasize context, decisions, diagrams, APIs, and results rather than only screenshots.
Digital finance and resident operations platform for transparent community management.
Built the product foundation for a digital finance and services ecosystem that helps housing clusters and neighborhood operators manage dues, resident data, introduction letters, reporting, and communication in one platform.
Digital finance platform work inside Amartha's inclusive financial ecosystem.
Architected and delivered a full e-wallet platform from scratch inside Amartha's broader digital finance ecosystem, with a strong focus on clean architecture, observability, migration safety, and reusable backend modules.
Interactive maps, integrated data sources, and operational reporting.
Drove redevelopment of internal maps data visualization with interactive features, integrated several data sources, and improved the cost and effort of existing implementation flows.
Want the full backend portfolio structure?
A practical snapshot of the tools and technologies I have used most often in real backend delivery.
Node.js
JavaScript
TypeScript
PostgreSQL
MySQL
MongoDBRedis
Docker
GitHub
Next.js
ReactTraefikMapLibreJenkins...and many more.
I treat security as part of delivery quality. Even when a project is not explicitly a security product, backend systems should document how access control, safe integration, observability, and operational safeguards are handled.
| Vulnerability | Status | Implementation |
|---|---|---|
| Broken Access Control | Mitigated | Role-aware permissions and approval boundaries on sensitive workflows. |
| Cryptographic Failures | Addressed operationally | Sensitive flows designed around provider-backed integrations and secure environment handling. |
| Injection | Mitigated | Backend validation and structured query handling in service layers. |
| Insecure Design | Mitigated | Clean architecture, tenant separation, and explicit workflow modeling. |
| Security Misconfiguration | Mitigated | Secret management, proxy routing, and infrastructure setup treated as first-class concerns. |
| Logging and Monitoring Failures | Mitigated | ELK, APM, Prometheus, Grafana, New Relic, and operational dashboards. |
Use clean architecture boundaries so wallet business rules remain isolated from delivery and infrastructure layers.
Direct framework-centric service design (Rejected)
Pros: Faster at the beginning
Cons: Harder to change safely later
Standardize reusable logging and monitoring modules and connect them to dashboards and APM.
Minimal service-specific logging only (Rejected)
Pros: Lower initial effort
Cons: Poor cross-service observability
Use Docker Swarm as the orchestration layer together with CI/CD, proxies, and secret management.
More complex orchestration platform (Rejected)
Pros: Broader orchestration feature set
Cons: Higher complexity for the team at the time