Back to Projects

English Listening Assessment

Built an assessment platform with admin-key access, student sessions, teacher dashboards, pre/post-test scoring, and class-level progress reporting.

Students working in a classroom setting.

Problem

Listening assessments need a clear student path and a reliable teacher view. Students should be able to start only after valid access, while teachers need enough reporting to understand pre-test and post-test movement without manually compiling scores.

Solution

I built a deployed assessment app with admin-key verification, student identification, protected student assessment routes, teacher/admin views, admin-key management, and score reporting. The reporting flow compares pre-test and post-test scores and summarizes class-level movement, improvement distribution, and student breakdowns.

What I Owned

  • Built the student access flow from admin confirmation through assessment route entry.
  • Integrated backend API calls for admin-key verification, student session creation, and score retrieval.
  • Created teacher-facing admin key management with shared access, expiry handling, and active/inactive status.
  • Built reporting views for class averages, improvement distribution, and individual student progress.

Tech

  • React for route-like client state, student screens, and teacher dashboards.
  • Tailwind CSS for the illustrated student UI and dashboard layouts.
  • Railway API for deployed backend endpoints that manage keys, sessions, and scores.

Key Decisions

  • Used admin-key gating so public access stays controlled while still keeping the student flow simple.
  • Stored short-lived route/session state in browser session storage to keep assessment navigation lightweight.
  • Separated student and teacher experiences because each audience has very different priorities.
  • Made pre/post-test comparison central to the dashboard so the app reports progress, not only raw scores.

Tradeoffs

  • Session storage keeps the frontend simple, but it requires careful validation against the backend when a route reloads.
  • The UI favors clarity for classroom use over dense enterprise reporting controls.

Outcome

  • Delivered a working deployed assessment app with student lifecycle routes and teacher/admin reporting.
  • Showed full-stack product thinking across access control, session flow, scoring, and analytics.
  • Created a project that demonstrates education-focused workflow design beyond static portfolio pages.