Koffeecup

Koffeecup is a game studio brewing worlds and games. We build creator-first UGC experiences on Roblox, UEFN and Meta Horizon, develop and port for console, and make our own games: Hoomanz!, Mine Maniac, Gunslingers, Wild West Saloon, Maloka - and more on the way.

Here’s our problem: behind every great game studio is a mountain of spreadsheets, repetitive admin and held-together workflows. We’ve got no interest in climbing that mountain every day. We need someone whose entire job is to turn the grind into software.

You’ll be our internal tools builder. The person who spots a clunky process, sits down with the people stuck doing it, and ships something better - fast. You’ll build the dashboards, apps, integrations and automations that keep Koffeecup moving, then own them, improve them and make sure the whole studio can depend on them.

Role Purpose

The Maker builds and maintains the internal tools that keep Koffeecup running — the dashboards, small web apps, and automations the studio relies on day to day. This role exists to turn recurring problems and manual grind into working software, fast, and then keep it alive. Success looks like a growing toolkit of dependable, well-built internal apps that everyone trusts — all built to the KC house standard so they're consistent, secure, and cheap to run. This is a builder's role: high autonomy, high output, close to the people who use what they make.

Key Responsibilities

• Owns internal tools end to end — from a rough idea to a live, maintained app.
• Build new internal tools and dashboards against the KC standard stack — Next.js (TypeScript, App Router) on Cloud Run, Cloud SQL Postgres via Drizzle, IAP + Google Workspace auth, deployed from GitHub via Cloud Shell.
• Maintain the existing toolset — fix bugs, run schema migrations safely, refresh data, handle incidents, and keep dependencies and costs in check.
• Scope with the people who'll use it — sit with the team, understand the real workflow, and ship the smallest thing that solves it rather than gold-plating.
• Integrate with the tools KC already runs — HubSpot, Notion, HiBob, Slack — pulling and pushing data cleanly and deduping on stable keys.
• Keep it secure and consistent — secrets in Google Secret Manager, one GCP project per app, IAP-gated access, and the KC brand theme applied so every tool looks and behaves the same.
• Broadcast changes — post deploys and notable events (migrations, data refreshes, incidents) with plain-English release notes to #ai-tools-build.
• Improve the foundations — keep the starter template and reference implementation current so the next tool is faster to build.