Dhio Rahmaputra / Software Engineer
Dhio Rahmaputra — Software Engineer

Software Engineer · Backend Specialist

Engineering with intention & clarity.

Software Engineer focused on backend systems, data integrity, and long-term maintainability. Currently working as a Web Developer at RA-ATAP, Telkom University, building internal enterprise platforms and operational systems.

Portfolio · Engineering notes · Experiments
01 / Philosophy

The architecture of decision making.

Software engineering is less about producing code and more about making deliberate decisions under constraint. Every system reflects a series of trade-offs between speed, correctness, maintainability, and long-term behavior. I aim to build systems that remain understandable as they evolve.

I view technical debt as an explicit, managed cost rather than a flaw to eliminate entirely. For core systems, I favor proven and predictable technologies, introducing complexity or experimentation only when it delivers clear, measurable value.

Scale is not solely a matter of traffic volume, but of developer cognition. Well-designed systems are resilient to change, observable by default, and structured around clear boundaries, explicit contracts, and failure-aware design.

02 / Selected Work

Certification Registration & Management Platform

Backend Systems / Enterprise Workflow

  • ScopeInternal
  • Data ModelRelational
  • FocusAuditability

Architected and implemented an internal certification platform to replace manual registration, document review, and enrollment workflows.

The system was designed around explicit workflow states, strict relational constraints, and trigger-based audit logging to ensure traceability and long-term correctness.

Enterprise Information System (CMS Platform)

Internal Systems / Administrative Tools

  • ScopeInternal
  • Access ModelRole-based
  • FocusMaintainability

Designed and built an internal enterprise CMS to support structured content management and administrative workflows.

Key considerations included authorization boundaries, auditability of administrative actions, and a normalized relational schema that could evolve without breaking existing data.

Production Web Platform

Production Systems / Infrastructure

  • DeploymentVPS
  • Web StackLaravel + MySQL
  • FocusReliability

Owned end-to-end development and deployment of a production web platform, including infrastructure setup and operational automation.

The system emphasized operational clarity, predictable deployments, and basic monitoring and backup automation over premature scaling complexity.

Experience

Bandung, Indonesia

Built internal enterprise systems supporting certification workflows and administrative operations.

  • Designed and implemented enterprise CMS and certification platforms using Next.js, Laravel, and PostgreSQL
  • Built normalized relational schemas with audit logging, constraints, and role-based access control
  • Delivered production-ready systems with technical documentation and maintainable architecture

Semarang, Indonesia

Owned end-to-end development and deployment of a production web platform for a business client.

  • Developed backend systems using Laravel and MySQL with a focus on correctness and reliability
  • Configured and operated Linux-based VPS infrastructure with Nginx and TLS
  • Automated monitoring and backup workflows to reduce operational overhead

Bandung, Indonesia

Mentored students in backend development and database fundamentals.

  • Reviewed student projects and provided code-level feedback
  • Explained backend concepts, databases, and system design principles

Languages

  • TypeScript · JavaScript
  • PHP (Laravel)
  • SQL (PostgreSQL, MySQL)

Infrastructure

  • Linux (VPS-based)
  • Nginx (reverse proxy, TLS)

Focus Areas

  • Backend Architecture
  • Relational Data Modeling
  • Operational Reliability

Tools are selected pragmatically, prioritizing explicit data modeling, reproducible environments, and operational clarity over trend-driven adoption.

2026 Focus

Deepening hands-on experience with Docker-based workflows while exploring architectural trade-offs around ,, informed by production-adjacent systems and controlled experimentation.

Let’s discuss systems.

Open to software engineering roles focused on backend systems, platform infrastructure, and long-term system ownership.