Navigate
Workingames
Full-stack game development job board
Live product!
Introduction
Workingames is a live job board for game developers, built as a full-stack product with a public website, custom search, backend APIs, automated job data pipeline, payment flow, internal audit tools, and monitoring systems.
The project started from a real problem I noticed in the game industry: job listings are spread across many studio websites, expire quickly, and are often difficult to search through in one place. Workingames solves this by collecting, validating, organizing, and publishing game development jobs in a focused platform.
Project details
-
Role: Founder / Full-stack Developer
Type: Live web product
Frontend: Next.js, React, TypeScript
Backend: Supabase, API routes, Google Sheets API
Automation: Playwright, Node.js scripts, validation pipeline
Integrations: Stripe, email alerts, Google indexing workflow
Status: Live product
VISIT WORKINGAMES
Overview
Workingames combines four main systems: a public job board, a custom search/API layer, an automated job data pipeline, and internal tools for auditing, monitoring, and maintaining job quality.
PUBLIC PRODUCT
Focused job discovery
The public site is designed around one main goal: helping game developers find relevant jobs faster. Instead of mixing game roles with generic tech listings, Workingames focuses on studios, disciplines, seniority, work mode, locations, and job details that matter to game developers.
The goal was to make the product feel useful quickly, with search, filters, job cards, and dedicated job pages that help users decide whether a role is worth opening.
Search and filters
The job list supports search, discipline filters, seniority filters, work-mode filters, sorting, pagination, related-search suggestions, saved searches, applied-job state, and promoted listings.
This required the frontend and backend to agree on clean job fields such as role, studio, location, seniority, work mode, discipline, and promotion status.
Job detail pages
Each job has its own detail page with structured information and a clear apply link. This improves the user experience, but it also supports search visibility because jobs can exist as individual pages instead of only being hidden inside a list.
DATA PIPELINE
Job collection workflow
The main backend challenge was keeping the job board updated from hundreds of inconsistent studio career pages. I built a staged data pipeline that scans career pages, extracts possible job links, validates them, checks whether they are game-development roles, and turns them into structured job data.
Validation stages
The pipeline does not publish every scanned link automatically. It first checks whether a link is a real job detail page, then checks whether the job is relevant to game development, then extracts role, seniority, location, and work mode.
This reduces false positives from career index pages, expired jobs, social links, PDFs, login pages, duplicate listings, and unrelated corporate roles.
Structured job data
After a job passes validation, the detail extractor normalizes inconsistent pages into a consistent format for the live site. It reads page titles, headings, metadata, visible text, iframes, links, and structured data, then outputs the fields needed for search, filters, and job detail pages.
Pipeline diagram
Picture should be a diagrom of the pipeline
APIs, SYNC & BUSINESS LOGIC
Search API
The public job board is powered by a custom search API connected to Supabase. It handles role taxonomy matching, relevance sorting, filters, facet counts, related-search suggestions, promoted ordering, pagination, and search correction.
Sync workflow
The validated job data starts in Google Sheets, then syncs into Supabase for the public website. The sync process handles new jobs, removed jobs, approved manual rows, promoted listings, and Google indexing events.
Payments and alerts
Workingames also includes a Stripe-based purchase flow for enhanced listings and recommended tags. Paid submissions go into an approval workflow before publishing. The site also supports saved search alerts, where users can receive email updates for matching jobs.
AUDIT & MONITORING TOOLS
Audit dashboard
I built an internal audit dashboard to inspect how each job link moves through the pipeline. It groups data by studio and link, shows which stage each job reached, flags missing or failed stages, and lets me close, reopen, watch, or add notes to problem items.
The pipeline status parser turns raw log output into structured progress data. It tracks the current run, active stage, current studio, progress percentage, batch writes, recent errors, and remaining work, then writes that status to JSON and Supabase.
Pipeline monitoring
Mobile monitor app
I also built an Expo/React Native monitor app for operational tasks. It shows recent generated LinkedIn posts, related jobs, generated images, and includes a mobile review flow for checking whether apply links are still valid.
Closing thoughts
Workingames helped me grow as a software developer because it forced me to work with real production problems instead of isolated exercises.
The hardest part was not building one page or one script. It was connecting many systems together: a public frontend, search API, database, payment flow, job scanning pipeline, validation logic, manual review tools, sync workflow, and monitoring tools.
This project taught me how important it is to design for unreliable data, failed requests, expired links, duplicate entries, unclear edge cases, and long-term maintenance.