Gamify — Workplace-Engagement SaaS

Senior frontend developer and mentor on Gamify — a multi-tenant workplace-engagement SaaS with a back-office portal (where each client company administers and configures its own program) and a front-office portal (for that company’s employees). I joined a five-person team (two frontend) for roughly five months, picking up an existing codebase forked from a similar SaaS app and extending it with dashboards for tasks, achievements, and leaderboards, while mentoring the team’s junior frontend developer.

This engagement followed the Oil & Gas ERP work at the same employer.

Engagement shape

• Product: a multi-tenant workplace-engagement SaaS — each client company is a separate tenant that administers and configures its own program in the back-office, while that company’s employees use the front-office (task / achievement / leaderboard views).
• Team: five people total, two frontend.
• Duration: ~5 months.
• Codebase origin: inherited / forked from a similar SaaS app — a single repository, which I restructured into a Turborepo monorepo (below). I onboarded into existing code rather than starting greenfield.

My role

Senior frontend on a two-FE team plus mentor for the junior frontend developer. I led planning and code reviews. Frontend work was split by feature area rather than by portal: I owned tasks, achievements, and leaderboards end-to-end across both the back-office and front-office portals, while the other developer owned the remaining areas.

Tech stack

• React, Next.js, TypeScript, Apollo Client, GraphQL.
• MUI (Material UI) for components and Chart.js for visualizations.
• Turborepo monorepo — a shared UI component library plus common libraries (utilities, types, GraphQL artifacts) consumed by both portals, keeping the same design-system primitives across both surfaces with no drift.

Selected work

• Converted the inherited single repository into a Turborepo monorepo. Restructured the forked codebase into Turborepo packages — a shared UI component library plus common libraries (utilities, types, GraphQL artifacts) — consumed by both the back-office and front-office portals, so both surfaces share the same design-system primitives with no drift.
• Tasks — back-office configuration (company admins create and assign tasks) plus front-office consumption (employees see and complete them). Owned end-to-end on the frontend.
• Achievements — back-office definition plus front-office display. Owned end-to-end.
• Leaderboards — front-office employee-performance views built with MUI and Chart.js. Owned end-to-end.
• Mentoring — supported the team’s junior frontend developer primarily through design and code reviews, and led team planning.

Cross-project stack fluency

Across this employer I shipped with both Ant Design (on the Oil & Gas ERP) and MUI (here) as primary component libraries — useful evidence of fitting into a team’s existing frontend design-system stack rather than imposing one.

State at roll-off

When I rolled off, Gamify was multi-tenant by design but internal-only — functional, not yet exposed to external client companies. The engineering scope (mentoring, a dual-portal multi-tenant SaaS, feature-area ownership) is the story here rather than a business-outcome line.