What you’ll do

You’ll turn designers’ tabletop prototypes into clean, reliable Tabletop Simulator builds, wiring up layouts, scripting, and quality-of-life helpers so playtests run smoothly.

• Import and organize assets (cards, boards, tokens, bags, etc.) into TTS.
• Set up snap points, zones, hidden areas, player hands, and cameras.
• Write Lua scripts for:
  • Setup / reset buttons,
  • Dealing, shuffling, and tracking key resources,
  • Simple A/B toggles for variant rules and components.
• Maintain clear object naming, grouping, and saved states for easy updates.
• Optimize tables for usability (readability, ergonomics, minimal fiddliness).
• Collaborate with designers to understand rules and edge cases before scripting.
• Document controls and features so testers and clients can use the build without hand-holding.
• Keep versioned backups and basic changelogs for each iteration.

What you bring

• Strong experience building games in Tabletop Simulator (beyond just loading mods).
• Comfortable writing and debugging Lua for TTS (object scripts and/or Global).
• Understanding of turn structure, setup, and common board game components.
• Solid sense for UX at the table: you care about reducing clicks and friction.
• Ability to read rulebooks and ask smart questions about edge cases.
• Reliable communication, time estimation, and follow-through on milestones.

Nice to have

• Experience with Unity/AssetBundles for custom 3D models or components.
• Familiarity with OBS or similar tools for capturing demo videos.
• Experience integrating basic analytics hooks or logging in TTS builds.
• Comfort working with remote teams (Discord, Google Docs, Airtable/Notion).
• Prior work on published or late-stage tabletop prototypes.

Compensation

• Freelance, remote role.
• Per-project or hourly, depending on the size and complexity of each build.
• Please include your preferred rate range and your approximate monthly capacity.

How to apply

Submit the following via the application form:

• 1–3 examples of TTS work (Workshop links, private videos, or screenshots with descriptions).
• A short note (150–250 words) on how you approach usability and scripting in TTS builds.
• A brief overview of your technical stack (Lua experience, any Unity/AssetBundle work, other tools).
• Your time zone, typical availability, and whether you prefer project-based or hourly engagements.

If you don’t have public Workshop items due to NDAs, share whatever you can (redacted screenshots, videos, or a small sample table you’re allowed to show).