Skip to main content

Pharmacy Education / Web Platform

PACU

At Pharmacy & Acute Care University, I worked on the details learners depend on: progress that adds up, certificates that stay recorded, and content that moves safely into production.

Orange PACU wordmark for Pharmacy & Acute Care University with a medical caduceus integrated into the letter U.
PACU is a live pharmacy education platform spanning public course discovery, clinical learning resources, board preparation, and account access.

The problem

Learners could see completion above 100%, miss required readings, or find FastTrack status out of sync. I also needed to keep certificate achievements consistent and give administrators a safer way to promote content.

When course information, subscription entitlements, or operational records disagree, learners can lose access and administrators can be blocked from supporting them.

My contribution

Full-Stack Engineer (Contract)

PACU product team · February–August 2026 · Live client platform; contract completed

I worked with the PACU product team on learner and administrator workflows across custom React, TypeScript, Node.js, and PostgreSQL features, alongside WordPress and Airtable-supported operations.

My work connected production debugging with feature delivery: repairing learning progress, recording certificate achievements, promoting content, and correcting enrollment-based access decisions.

The choices behind the work

I worked across the interface, APIs, and database to align learning progress, record certificate achievements consistently, and make content promotion reviewable and reversible.

Enforce certificate uniqueness in the database

Repeated writes must not create duplicate certificate achievements.

I combined idempotent writes with database uniqueness constraints, migration and backfill support, and authorization coverage.

The database enforces the same rule even when a write is retried.

Make content promotion recoverable

Content needs to move from development to production with its identifiers and relationships intact.

I added completeness checks and snapshots before transactional writes, then rollback support and post-write integrity verification.

The tooling checks what is being promoted and provides a recovery path when a change needs to be undone.

Outcome

I unified completion checks across five code paths to address progress above 100%, missing required readings, and FastTrack status mismatches.

The certificate achievement change was validated with 51 passing tests, including authorization coverage.

I delivered development-to-production content-promotion tooling with completeness checks, snapshots, transactional writes, rollback, and post-write integrity verification.

Combined WordPress publishing, Airtable-supported operations, and custom full-stack features in one client platform.

Covered learner-facing study, reading, reminder, and subscription flows alongside the administrative workflows that support them.

What I learned

This work reinforced that a correct interface depends on consistent checks and records beneath it; fixing one screen is not enough when several paths calculate progress.

I learned to make recovery part of content-promotion tooling through snapshots, transactions, rollback, and integrity checks.

What comes next

Continue strengthening cross-system regression coverage and operational documentation as learning products and subscription paths evolve.

The live site demonstrates delivered capabilities, but it does not by itself attribute learner growth, certification outcomes, or revenue changes to this engineering work.

Stack

  • WordPress
  • Airtable
  • React
  • TypeScript
  • Node.js
  • PostgreSQL