PC.

Senior Developer · PHP / Laravel

Phạm Đặng Cường

I turn scattered legacy systems into one reliable platform, and ship it with the people who have to use it.

Senior Developer (PHP/Laravel) · Full-stack, system integration & legacy modernization

Ho Chi Minh City, Vietnam

5 → 1 RMIT University · internal

01 About

Portrait of Phạm Đặng Cường

I am a Senior Developer who works mostly in PHP and Laravel, with a full-stack habit: I read the old system, find the business rules inside it, and rebuild them into something a small team can run.

My recent work at RMIT University is the clearest example. I read and extracted business logic from legacy Java Spring Boot and Symfony projects and built five modules of the new Laravel platform myself.

Around the code, I do the work that makes delivery land: requirements analysis (there is no dedicated BA on my team), demos to users, change requests and deployment plans with vendors, and mentoring interns on test automation.

Education: College diploma, Electronics and Telecommunications (Điện tử truyền thông), Cao Thang Technical College (2019)

02 Experience

  1. Apr 2024 – Present

    Senior Developer · RMIT University

    through CMC Global

    Legacy modernization, internal tooling and delivery coordination for a university's campus systems.

    • Read and extracted business logic from legacy projects (Java Spring Boot, Symfony) and, as the sole developer of these five modules, consolidated 5 legacy apps into one Laravel + jQuery platform: Redirect (short links + QR codes), Contract Management, Inventory & Loan, Scriptor (scheduled-script management), Event Management System. The Event Management System is the highest-stakes module: events can exceed 8,000 guests.
    • Built Power BI dashboards for contract managers (check contract status) and for inventory staff (check equipment status). Automated approvals with Power Automate: requests go straight to the people with approval rights, who only click approve or reject, saving a lot of manual follow-up.
    • Technical liaison and delivery coordination: advise campus users on vendor-built systems, work with vendors, prepare change requests and deployment plans, coordinate production releases, support incident resolution.
    • 2025: helped build a Playwright end-to-end test automation project (about 500 test cases); mentored and managed 4 students on structuring and writing tests, then merged their work into the main project, still in use today.
    • Requirements analysis and user demos done in-team (no dedicated BA).
    • Laravel
    • PHP
    • jQuery
    • MySQL
    • Playwright
    • Power BI
    • Power Automate

    ★ Team award, 2026

  2. Oct 2023 – Mar 2024

    Developer · Centrala

    small outsource company

    Six months of greenfield builds and site maintenance for outsourced clients.

    • Built a Udemy-like e-learning platform from scratch (Laravel, jQuery).
    • Built a document upload, review and approve workflow app for a Japanese client (ReactJS + Ant Design).
    • Maintained and fixed customer websites. Moved local development from XAMPP to Docker.
    • Laravel
    • jQuery
    • ReactJS
    • Ant Design
    • Docker
  3. Mar 2021 – Sep 2023

    Developer · FPT Telecom

    Customer-care tooling for call-center agents at a major telecom operator.

    • Built a customer-care support web app for call-center agents: suggested replies, service recommendations and built-in utilities so any agent can support customers with little training. Used by more than a thousand users.
    • Flagship feature: automatic distribution of customers to the most suitable agent based on customer data. Won the internal IKhiến award. 2022
    • Real-time notifications with Socket.IO, logging with Kafka + Kibana, caching with Redis, monthly table partitioning for large data volumes.
    • Laravel
    • jQuery
    • Socket.IO
    • Kafka
    • Kibana
    • Redis
    • MySQL

    ★ IKhiến internal award

  4. Apr 2019 – Feb 2021

    Developer, later Lead on one project · Bin Corporation Group

    Payment integrations and two products built from scratch.

    • Built payment-integration APIs and plugins for CMS platforms (WordPress, Magento, OpenCart, Drupal) and for customers' own websites.
    • Worked on Visa-related projects and payment gateways (Stripe, PayPal).
    • Built from scratch a flight-ticket booking system and a banking platform for the EU market (mostly third-party API integration). Led a team of 3 other people on the banking project.
    • Stack included Phalcon, jQuery, Azure Search, AWS S3, Google reCAPTCHA and SSO.
    • Phalcon
    • jQuery
    • Stripe
    • PayPal
    • Azure Search
    • AWS S3
    • reCAPTCHA
    • SSO

    ★ Best Employee

  5. Jan 2019 – Mar 2019

    Intern · VNPT

    First production-style project, on telecom network monitoring.

    • Built a pure-PHP web app that connected to multiple databases (Oracle, SQL Server, MySQL) to raise alerts on network incidents automatically.
    • PHP
    • Oracle
    • SQL Server
    • MySQL

03 Selected work

Client and project names are intentionally left out: these are internal systems and their names change often. Each is described by type, domain, role and impact.

Legacy modernization · Higher education, campus operationsFive legacy apps consolidated into one platformInternal / confidential2024 – present
  • Laravel
  • PHP
  • jQuery
  • MySQL
  • Java Spring Boot (legacy)
  • Symfony (legacy)
Problem
Separate internal tools, written in different frameworks, each with its own deployment, data and upkeep. Business rules lived only in old code. There was no dedicated BA to document them.
My role
Senior Developer. Built these five modules myself: read the legacy code, extracted the business rules, designed and implemented them, ran requirements analysis and user demos.
Architecture
One Laravel application with domain modules behind a single sign-in with the organization's Microsoft accounts and per-app roles. Each legacy app was read, its rules extracted and written down, then re-implemented: Redirect (short links with QR codes, expiry, redirect delay, API token, blocked-domain list), Contract Management (licenses and contracts with expiry and payment reminder emails, renewal tracking), Inventory & Loan (equipment per campus space, lending, returns, advance booking), Scriptor (monitoring of scheduled scripts with alerts when a run is late or fails) and the Event Management System.

Key decisions

  • Read the code first and write the rules down before building, so behavior could be checked with users instead of assumed.
  • A modular monolith: one deployment, one login, shared services, instead of many small systems to keep patched.
  • Server-rendered Laravel + jQuery: proven, easy for the next developer to pick up, and cheap to host.
  • Demo each module to its users before retiring the old app.
  • Treat the Event Management System as the critical module: with 8,000+ guests at a single event, a failure means chaos on the day, so it got the most care and testing.

Outcome

  • 5 legacy apps that I built replaced by 1 platform.
  • Single codebase, deployment and login for all of these functions.
  • Used by hundreds of staff and thousands of students. Events handle 8,000+ guests.
Event registration, ticketing and check-in · Higher education, campus eventsEvent management system for events with 8,000+ guestsInternal / confidential2024 – present
  • Laravel
  • PHP
  • jQuery
  • MySQL
  • Microsoft SSO
  • Microsoft Forms
  • Barcode / QR scanning
Problem
Events can exceed 8,000 guests. Guests must be registered, ticketed and checked in at the gate in a short time, and staff at food and game counters must enforce per-guest limits. If the system fails on the day, the result is chaos at the gate.
My role
Senior Developer. Built this module myself, end to end: extracted the business rules from the legacy event app, designed and implemented it, ran requirements analysis and user demos.
Architecture
Organizers create an event (capacity, accompanying guests, coupon limits) and fill the guest list by manual entry, CSV import (with an error report for bad rows) or self-registration through Microsoft Forms. Each guest receives a ticket by email with a barcode. Staff scan tickets with a scanner or a phone camera at the gate, then at food and game counters. Game counters award points that guests exchange for gifts. Access is role-based: Admin, Manager, Normal User, Counter Manager and Counter User, plus per-event sharing with people and groups.

Key decisions

  • Make the gate the first step: counters refuse a guest who has not checked in at the gate, so one scan decides who is on site.
  • Enforce limits in the system, not by staff memory: maximum uses per counter, maximum meal coupons per guest, event capacity, and an early check-in window (2 hours before start).
  • Give every accompanying guest an own code, so each person is checked in separately.
  • Require two conditions for counter staff (member of the counter, event shared with them), and keep gate staff out of counters, so a scan can never be interpreted as the wrong action.
  • Let guests self-register through Microsoft Forms and track every email as Pending, Failure or Delivered, so organizers can find tickets that did not arrive.
  • Recommend a dry run before event day: scan a sample ticket at the gate and at every counter.

Outcome

  • Supports events with 8,000+ guests, from registration to gift exchange, in one system.
  • Replaces the legacy event app as one of the 5 apps I consolidated into the platform.
  • 140 events run on the platform.
Customer-care web application · Telecom operatorCustomer-care platform with automatic agent routingInternal / confidentialMar 2021 – Sep 2023
  • Laravel
  • jQuery
  • Socket.IO
  • Kafka
  • Kibana
  • Redis
  • MySQL
Problem
Call-center agents needed to support customers across many services with little training, and customers needed to reach the agent best suited to their case.
My role
Developer. Built features across the app, including the customer-to-agent distribution feature.
Architecture
Laravel web app for agents. Customer data drives a distribution step that picks the best-suited agent. Socket.IO pushes real-time notifications, Redis caches hot lookups, events stream through Kafka into Kibana for logging, and large tables are partitioned monthly.

Key decisions

  • Route on customer data instead of round-robin, so cases reach the right agent first.
  • Built-in utilities and suggested replies inside the agent screen, so agents need little training.
  • Redis for caching and Socket.IO for push: agents see updates without refreshing.
  • Monthly table partitioning to keep queries fast as data volume grew.

Outcome

  • The distribution feature won the internal IKhiến award. 2022
  • Used by more than a thousand users.
  • Used by customer-care agents across Vietnam, from Hanoi to Ho Chi Minh City.
Payments / fintech integration · Payment gateways, e-commercePayment-integration APIs and CMS pluginsInternal / confidentialApr 2019 – Feb 2021
  • Phalcon
  • jQuery
  • Stripe
  • PayPal
  • AWS S3
  • Azure Search
  • reCAPTCHA
  • SSO
Problem
Merchants on different platforms needed one way to accept payments without each building their own integration.
My role
Developer. Built the APIs and plugins and worked on Visa-related projects.
Architecture
A payment API layer with thin plugins on top for WordPress, Magento, OpenCart and Drupal, plus direct API integration for customers' own sites. Gateway adapters wrap Stripe and PayPal.

Key decisions

  • Keep plugins thin and put logic in the API, so a fix ships once for every platform.
  • Wrap each gateway behind one adapter interface.
  • reCAPTCHA and SSO at the edges for abuse control and sign-in.

Outcome

  • Plugins for 4 CMS platforms plus direct integrations.
  • Recognized as Best Employee before leaving.
Greenfield products · Banking, travelBanking platform (EU) and flight-ticket booking systemInternal / confidential2019 – 2021
  • Phalcon
  • jQuery
  • Azure Search
  • AWS S3
  • SSO
Problem
Two products built from scratch. The banking platform for the EU market depended mostly on integrating third-party APIs.
My role
Developer on the booking system. Led a small team on the banking project.
Architecture
Web applications that orchestrate external provider APIs, with Azure Search for search, AWS S3 for document storage and SSO for sign-in.

Key decisions

  • Isolate each third-party API behind one integration module, so provider changes stay local.
  • Azure Search for fast lookup instead of heavy database queries.

Outcome

  • Both systems built from scratch and delivered.
  • Led a team of 3 other people (4 in total). 3 third-party APIs integrated, covering the banking features and travel booking and ticket search.
Data reporting and automation · Higher education, internal operationsReporting and workflow automation on Microsoft Power PlatformInternal / confidential2024 – present
  • Power BI
  • Power Automate
  • SQL Server
  • MySQL
Problem
Contract managers and inventory staff needed a current view of contracts and equipment, and approval requests had to be chased by hand.
My role
Senior Developer. Designed dashboards and flows, analysed requirements, demoed to users.
Architecture
Power BI dashboards read from the operational data: contract status for contract managers, equipment status for inventory. Power Automate flows send approval requests automatically to the people with approval rights, who only click approve or reject.

Key decisions

  • Use the Power Platform where staff already live, instead of custom code for every small flow.
  • Demo each flow and report to its users before release.

Outcome

  • Contract managers check contract status in a dashboard; inventory staff check equipment status.
  • Approvers only click approve or reject, which saves a lot of time.
Test automation and mentoring · Higher education, quality engineeringPlaywright end-to-end test automation, built with internsInternal / confidential2025
  • Playwright
Problem
Regression checks on campus systems were manual, and there were interns who could contribute if given structure.
My role
Helped build the project. Mentored and managed interns and students, reviewed and merged their work.
Architecture
A shared Playwright project with a common test structure. Interns wrote tests to the agreed pattern, which were reviewed and merged into the main project.

Key decisions

  • Agree on a test structure first, so many contributors produce consistent tests.
  • Review and merge intern work into the main project instead of keeping side projects.

Outcome

  • Intern-written tests merged into the main project and still used today.
  • About 500 test cases. Mentored 4 students.

04 Skills & tech

Deliberate, proven technology that runs at scale. I pick the tool that fits the problem and the team that will maintain it.

Backend

The core of my daily work.

  • PHP
  • Laravel
  • Phalcon

Frontend

Server-rendered UIs and React where it fits.

  • jQuery
  • ReactJS
  • Ant Design

Data

Relational databases at different scales.

  • MySQL
  • SQL Server
  • Oracle
  • Redis

Real-time & observability

Live updates and traceable systems.

  • Socket.IO
  • Kafka
  • Kibana

Cloud & integrations

Connecting systems and third parties.

  • Docker
  • AWS S3
  • Azure Search
  • Stripe
  • PayPal
  • SSO
  • API integration

Testing & Power Platform

Quality and automation around the code.

  • Playwright
  • Power BI
  • Power Automate
  • Data reporting
  • Workflow automation

Delivery & practice

What makes projects land.

  • Legacy migration
  • Requirements analysis
  • Mentoring
  • Release / change management

05 Achievements

  • 2026Team award · RMIT University
  • 2022IKhiến award · FPT Telecom

    For the automatic customer-to-agent distribution feature.

  • 2021Best Employee · Bin Corporation Group

    Awarded before leaving the company.

06 Contact

Have a legacy system to modernize, or an integration that needs to just work? Let's talk.