20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You usually start with a short stand-up meeting (15 minutes) to sync with programmers, artists, and producers using Atlassian JIRA to track tasks. Mornings often involve writing or refining design specs, creating level layouts, or building gameplay prototypes in C# or C++.
Afternoons are for playtesting, fixing issues from feedback, and committing code or assets to Git. You’ll also meet artists to tweak visual style in Photoshop or Illustrator and update JIRA tickets with next steps.
Expect to use C# and C++ for gameplay code, JavaScript and HTML/XML for UI or web tools, and Git for version control. Design docs and specs are often written in plain text, XML, or tools linked to JIRA.
Artists use Adobe Photoshop and Illustrator; you’ll coordinate with them and place their assets into the game. JIRA is the main hub for tasks, bugs, and feature requests.
Yes, AI can speed brainstorming, prototyping, and NPC dialogue drafts. Use AI to generate first drafts of story beats or item descriptions, then filter and edit everything—never ship AI text without human review.
Keep proprietary code and design secrets out of public AI tools. For anything sensitive, run models on private infrastructure or use tools approved by your studio. Track changes in design docs and JIRA so reviewers see what came from AI.
According to the U.S. Bureau of Labor Statistics (BLS), there were 113,330 game developers employed and the median pay is $104,000 per year. The lowest 10% earned $53,750 and the highest 10% made $201,550.
Salaries vary with location, studio size, role (designer vs. lead), and experience. Use the BLS data as a baseline, then check local job listings for current market rates.
Learn one language well—C# for Unity or C++ for Unreal—and make small prototype games that show core mechanics: a movement system, an enemy, and a scoring loop. Use Git from day one to track your work.
Also practice writing clear design documents and specs, and build simple UI with HTML/JS or Unity UI. Share builds with friends for playtesting and iterate based on feedback.
'Game developer' is a broad name that can mean programmer, designer, or technical artist. A game designer focuses on mechanics, balance, story, and level layouts—writing specs and conducting playtests.
A producer manages schedules, stakeholders, and JIRA workflows. Developers (programmers) implement systems in C# or C++, and artists make visuals in Photoshop/Illustrator. Many roles collaborate closely and overlap on tasks like prototypes and UX.
Shipable iteration: the ability to take a small feature from idea to playable prototype, test it, and improve it based on feedback. That covers design, coding (C# or C++), version control (Git), and communication.
Show this by linking Git repos or builds and attaching short design specs and JIRA-like issue notes. Employers prefer people who can deliver working gameplay and explain the choices they made.