Resume

Imam Ramadhan

Software engineer

Location
Greater Jakarta, Indonesia
Role focus
Backend-focused and full-stack software engineering roles
Availability
Contact me directly for current availability and work arrangement

Last reviewed: July 2026

Professional summary

Backend-focused software engineer with experience developing and maintaining enterprise and business applications. I work across application logic, APIs, relational data models, integration, and troubleshooting, with particular attention to explicit business rules and reliable transaction flows.

Experience

  1. Full-stack developer - Enterprise banking applications

    February 2026–present · Greater Jakarta, Indonesia

    Developing and maintaining enterprise applications, supporting system integration, troubleshooting issues, and contributing to transaction-oriented business workflows.

    Technologies: .NET, ASP.NET Core, SQL Server

  2. Full-stack developer - Business applications

    October 2024–February 2026 · Yogyakarta, Indonesia

    Built and maintained point-of-sale, HRIS, CRM, and loyalty workflows, including backend APIs and relational data models.

    Technologies: Laravel, REST APIs, MySQL

  3. Programming instructor - Technical education

    September 2022–August 2024 · Yogyakarta, Indonesia

    Supported learners as they developed programming fundamentals and practical problem-solving skills.

Core skills

Backend application design, REST APIs, relational data modeling, transaction-oriented workflows, integration, troubleshooting, code maintenance, and technical communication.

Technologies: .NET, ASP.NET Core, SQL Server, Laravel, MySQL, and Git.

Selected engineering evidence

These articles explain decisions related to the domains and workflows summarized above.

Engineering principles

  • Make business rules explicit: Model rules and boundaries so they can be reviewed, tested, and explained.
  • Prefer understandable systems: Choose the smallest design that preserves the boundaries the product actually needs.
  • Design failure behavior deliberately: Consider retries, partial failure, recovery, and data integrity before they become production incidents.
  • Treat maintainability as a product concern: Optimize for the people who will operate, change, and support the system after delivery.

Education

Bachelor of Informatics

2020-2024

Current technical interests

Distributed systems, Database engineering, Go.