These skills do not affect the main grade but show the breadth of your profile.
AI Coding Assistants
▼
Uses ChatGPT/Claude to generate content ideas: item descriptions, NPC dialogues, lore. Can formulate prompts for quality game text and narrative. Understands AI assistant limitations and reviews generated content for quality.
Applies AI assistants for prototyping game mechanics, balancing, and generating test data. Creates complex prompt chains to automate routine game design tasks: balance tables, loot tables. Integrates AI tools into the game content creation pipeline.
Defines AI assistant usage strategy for the game project to accelerate development. Standardizes LLM practices for the entire team: prompt templates, review processes. Evaluates risks and opportunities of AI-generated content for commercial game products.
Uses GitHub Copilot to speed up writing simple scripts: game events, config parsers, utility functions. Understands AI generation limitations for game-specific code. Checks suggestions for correctness regarding game logic and balance parameters.
Effectively uses Copilot for game design tasks: generating config files, balance formulas, test scripts. Writes quality prompts for game-specific code. Understands when Copilot is useful (boilerplate, formulas) and when manual approach is needed (core mechanics logic).
Defines AI-assisted game development strategy for the team. Establishes best practices for Copilot and other AI tool usage. Evaluates AI tool impact on game design team productivity. Trains designers on effective AI assistant usage.
Algorithms & Data Structures
▼
Understands basic search and sorting algorithms for game system applications. Knows the Big-O concept and can evaluate performance of simple game loops. Uses knowledge to optimize iterations over game object collections.
Applies graph algorithms for pathfinding (A*, Dijkstra) when designing levels. Evaluates game system complexity: matchmaking, procedural generation, AI decision trees. Selects appropriate algorithms for load balancing in real-time games.
Defines algorithmic optimization standards for the game project. Reviews team architectural decisions for computational complexity. Establishes performance budgets for each game subsystem and trains designers on evaluating algorithmic cost of solutions.
Understands basic data structures and their application in game systems: arrays for inventory, dictionaries for object parameters, trees for dialogues. Selects appropriate structures for storing game data in ScriptableObjects and config files.
Designs data structures for game systems: graphs for NPC navigation, decision trees for AI, priority queues for event systems. Optimizes balance data access for runtime performance. Creates efficient data schemas for game config.
Defines game data organization standards for the project: data schemas, naming conventions, serialization formats. Reviews data structure choices for critical systems. Trains the designer team on effective data structure usage when designing mechanics.
Application Security
▼
Knows main OWASP vulnerabilities and their applicability to game servers and services. Understands basic security principles: input validation, injection protection in game APIs. Recognizes the importance of protecting player data: accounts, payment information, progress.
Applies OWASP Top 10 when designing game servers and APIs: protection against XSS, CSRF, SQL injection. Implements secure player authentication and protection against game data manipulation. Conducts basic security review of game endpoints and client-server protocol.
Defines security strategy for the entire game project: servers, clients, infrastructure. Standardizes security practices across the team and conducts regular architecture security reviews. Coordinates with the security team and manages the vulnerability disclosure process.
CI/CD
▼
Understands basic CI/CD concepts and the purpose of GitHub Actions for automating game project builds. Can read pipeline YAML configurations and understands workflow triggers. Can run an existing pipeline for building a test game version.
Configures GitHub Actions for automatic building and testing of game projects across platforms. Sets up build matrices for cross-platform builds: PC, consoles, mobile. Integrates automated code quality checks and tests into the PR process.
Defines CI/CD strategy for all game project repositories and supporting tools. Standardizes GitHub Actions workflows for the team: templates, reusable actions, secrets. Ensures pipeline reliability and speed as the team scales.
Clean Code & Refactoring
▼
Understands clean code principles when writing game scripts in Unity/Unreal. Follows naming conventions for game objects, prefabs, balance variables. Uses comments to explain game mechanic logic in Blueprint/C# scripts.
Applies design patterns in game scripts: State Machine for AI, Observer for events, Strategy for enemy behavior. Structures game config files for convenient balancing. Refactors mechanic prototypes to production quality.
Defines code and configuration quality standards for the game project. Establishes coding guidelines for game designers working with Blueprint/Visual Scripting. Implements automated testing for game systems and code review process for design scripts.
Cloud Providers
▼
Understands basic AWS services for game server hosting: EC2, S3, RDS. Knows cloud infrastructure concepts and their application for game backend: data storage, CDN, compute. Can deploy a simple game server on EC2 following instructions.
Uses AWS services for game infrastructure: GameLift, DynamoDB, CloudFront for asset delivery. Configures auto-scaling for game servers during peak loads and global launches. Sets up S3 + CloudFront for efficient game content delivery across regions.
Defines cloud strategy for the entire game project: architecture, budget, scaling. Standardizes AWS practices across the team: IaC, security groups, cost optimization for game workloads. Coordinates with AWS team for game infrastructure optimization.
Code Review
▼
Participates in game mechanic script reviews under mentor guidance. Checks correctness of balance parameters in config files. Reads other designers' Blueprint/Visual Scripting and asks questions about mechanic logic.
Conducts reviews of game scripts and configs: checks balance parameters, mechanic logic, state machine correctness. Identifies potential exploits and edge cases in game systems. Provides constructive feedback on game design decision implementation.
Defines code review process for the game design team: checklists for balance configs, guidelines for mechanic scripts. Conducts architectural reviews of key game systems. Mentors designers in conducting quality reviews.
Concurrency & Parallelism
▼
Understands asynchronous programming concepts and callbacks in the context of loading game resources. Knows basic async/await patterns for working with server APIs and saving progress. Can write simple async code for loading data from backend.
Implements asynchronous content loading and asset streaming in game engines. Manages parallel network requests for multiplayer systems with proper error handling. Optimizes async operations to minimize freezes in the game loop.
Defines asynchronous programming standards for the game project and a library of common patterns. Reviews team async system architecture for race conditions and deadlocks. Trains developers on safe async/await usage in real-time context.
Containerization
▼
Knows basic Docker commands for running game servers in containers. Can use docker-compose for local development environment deployment. Understands the containerization concept and its benefits for reproducible game build environments.
Creates Dockerfiles for building and deploying game servers and tools. Configures multi-stage builds to optimize server component image sizes. Sets up docker-compose environments for local multiplayer scenario testing.
Defines containerization strategy for all game project services. Standardizes Docker practices for the team: base images, security policies, monitoring. Trains the team on effective container usage for game development and testing.
Docs-as-Code
▼
Creates simple game system diagrams: core loop flowcharts, mechanic interaction schemas, game content mind maps. Uses Miro, draw.io, or Figma to visualize game design ideas. Understands basic notations for describing game flows.
Creates detailed game system diagrams: state machines for AI behavior, progression flow diagrams, economic cycle schemas (sink/source). Visualizes dependencies between game systems. Uses UML to describe complex interactions.
Defines visual documentation standards for the game design team. Builds a diagram template library: economy flows, system architectures, player journey maps. Trains the team on effective visual communication of game design decisions.
Shapes visual communication culture at the studio level. Creates methodology for documenting complex game systems through diagrams. Defines enterprise tools and standards for game design visualization across multiple projects.
Game Engines
▼
Uses Unreal Editor for prototyping: BSP modeling, Blueprint visual scripting, basic Actor setup. Creates simple levels and game mechanics prototypes in Blueprint. Works with Level Editor for blockout and playtesting design ideas.
Confidently works with Unreal for game design: Blueprint for complex mechanics, Sequencer for cutscenes, World Partition for open world. Creates gameplay systems via Blueprint: AI behavior trees, UI widgets, interaction systems. Uses Data Tables for data-driven design.
Defines Unreal workflow strategy for the game design team. Establishes Blueprint coding standards and best practices. Coordinates with C++ engineers to create designer-friendly systems. Evaluates Unreal features for the project: Nanite, Lumen, MetaHuman.
Shapes enterprise Unreal strategy for the studio: licensing, custom engine modifications, technology pipeline. Evaluates Unreal 5+ features for future projects. Defines engine choices for different project types. Coordinates with Epic Games at the enterprise level.
Game Platforms
▼
Understands web game design specifics: browser limitations, load time, casual audience. Designs mechanics for web: simple input, quick onboarding, shareable gameplay. Knows web-specific technologies: HTML5 Canvas, WebGL, Web Audio API and their game design limitations.
Designs web-first game systems: instant play, cross-device experience, social sharing mechanics. Creates game design for web platforms: Facebook Instant Games, itch.io, CrazyGames. Optimizes UX for web: loading experience, responsive layout, keyboard/mouse + touch.
Defines web game strategy for the studio: target platforms, technology stack, market positioning. Builds web game development team and process. Coordinates with web platform partners for distribution. Defines quality standards for web game production.
Game QA
▼
Understands game localization basics: text externalization, string tables, and locale-aware UI layout considerations. Prepares content for localization by using placeholder-based dialogue systems and avoiding hardcoded strings. Follows team guidelines for writing localizable game text and cultural notes.
Designs localization system for the game project: string management, dynamic text, localization-friendly UI. Works with translation agencies: preparing lockits, context documents, voice-over scripts. Ensures culturalization — content adaptation for different markets.
Defines localization strategy for the game project: target markets, languages, budget, timelines. Builds localization team and processes. Coordinates with external partners. Ensures quality standards through LQA metrics and vendor management.
Git & Workflows
▼
Uses Git for versioning game design files: GDD, balance configs, mechanic scripts. Performs basic operations: commit, push, pull, creating branches. Understands the importance of version control for game design team collaboration.
Applies Git branching strategies for game design workflow: feature branches for new systems, release branches for builds. Resolves merge conflicts in config files. Uses Git LFS for storing large game assets. Works with Pull Requests for design change reviews.
Defines version control standards for the studio: Git conventions, branching policies, code review process. Establishes best practices for game design files in version control. Trains the team on effective Git usage in game development context.
Integration Testing
▼
Understands the difference between unit and integration testing in game system context. Can run existing integration tests to verify game subsystem interactions. Knows basics of client-server interaction testing in multiplayer games.
Writes integration tests for verifying game system interactions: inventory-economy, AI-navigation. Sets up test environments for multiplayer scenario testing with network condition emulation. Tests game service integration: authentication, payments, analytics.
Defines integration testing strategy for the entire game project and CI/CD pipeline. Standardizes approaches to testing interactions between teams: client, server, infrastructure. Implements quality metrics and release readiness criteria for each release.
Logging
▼
Understands the importance of logging for debugging game systems and knows basic log levels. Can add structured logs to game code for tracking events: connections, errors, states. Reads logs to diagnose simple issues in test sessions.
Implements structured logging in game servers with JSON format and correlation IDs. Configures logging levels for different subsystems: gameplay, network, AI, rendering. Uses logs for player behavior analysis and multiplayer network issue diagnosis.
Defines observability strategy for the game project: logs, metrics, traces. Standardizes logging format and policies for all project teams. Builds a data-driven debugging culture through structured game event log analysis.
Metrics & Monitoring
▼
Understands basic Prometheus & Grafana for game metrics: reading player analytics dashboards, understanding gameplay metrics (session duration, retention), navigating Grafana panels for game economy and balance data. Follows team conventions for monitoring game KPIs.
Configures Prometheus for collecting game server metrics: TPS, matchmaking time, player sessions. Creates Grafana dashboards for monitoring game subsystem performance and health. Sets up alerts for critical game metrics: crash rate, queue length, server lag.
Defines monitoring and observability strategy for the entire game project. Standardizes metrics and dashboards for all teams: gameplay, infra, analytics, QA. Builds a data-driven operations culture through game system monitoring and alerting.
Shapes corporate monitoring strategy for the studio's game product lineup. Defines unified observability platform architecture for all projects. Researches and implements advanced monitoring approaches: AIOps, predictive alerting for live-service games.
OOP & Design Patterns
▼
Knows basic design patterns: Singleton, Observer, Factory in the context of game systems. Understands pattern applications for organizing game code: scene managers, object pools. Can recognize typical patterns in game engine codebase.
Applies game design patterns: State Machine, Command, Strategy for AI and gameplay. Uses Component/ECS for flexible game entity architecture and modularity. Combines patterns for specific tasks: quest system, dialogue trees, combat system.
Defines the architectural style and standard pattern set for the game project codebase. Reviews team architectural decisions and recommends optimal patterns for each subsystem. Conducts architecture sessions and trains the team on applying patterns in game development.
Understands basic OOP principles: encapsulation, inheritance, and polymorphism in the context of game objects. Can create simple class hierarchies for game entities: characters, items, abilities. Reads and understands object-oriented game system code.
Applies SOLID principles when designing game systems: inventory, combat system, AI. Chooses between inheritance and composition for modeling game entities and behaviors. Designs extensible systems using interfaces and abstract classes.
Defines OOP design architectural standards for the entire game project codebase. Reviews team class hierarchies for SOLID compliance and game patterns. Trains developers on proper OOP application in the context of high-performance games.
Relational Databases
▼
Understands basic PostgreSQL concepts for game design: how game data (items, quests, progression) is stored in relational tables, basic queries for game balance data analysis, understanding data schemas for level and content design. Follows team conventions for game data documentation.
Designs PostgreSQL schemas for game data: player profiles, economy, leaderboards, statistics. Optimizes queries using indexes and EXPLAIN for high-load game tables. Uses transactions and JSONB for flexible game content and configuration storage.
Defines PostgreSQL usage strategy for the game project: sharding, backups, DR. Standardizes database practices for the team: migrations, naming conventions, performance review. Coordinates database scaling for growing game audience.
Shapes corporate PostgreSQL strategy for the studio's game product lineup. Defines data storage architectural patterns for large-scale online games. Publishes best practices and influences PostgreSQL tool development for gaming workloads.
REST API
▼
Understands basic REST API principles and HTTP methods in the context of game servers. Knows the difference between GET/POST/PUT/DELETE and can read server API documentation for game system integration. Can describe simple endpoints for saving player progress.
Designs REST APIs for game services: leaderboards, inventory, matchmaking. Considers API versioning during client updates and backward compatibility. Defines endpoint structure for live-service games accounting for mobile client limitations.
Defines API strategy for the entire game project, including public APIs for mods and UGC. Standardizes interface design approaches between game subsystems. Reviews team API contracts and ensures documentation consistency.
System Design
▼
Understands basic system design concepts: client-server, databases, caching in the gaming context. Knows main online game architecture components: game server, matchmaking, persistence layer. Can describe a simple casual mobile game architecture.
Designs game subsystem architecture: lobby, party system, chat, leaderboard with scaling considerations. Evaluates trade-offs in architectural decisions: latency vs consistency, cost vs performance. Develops system design for medium-scale multiplayer games.
Defines system architecture for the entire game project and coordinates technical vision across teams. Conducts design reviews and makes key architectural decisions considering business requirements. Mentors senior engineers in game platform system design skills.
Unit Testing
▼
Understands basic testing for game design assets: balance formula verification, progression curve validation, probability distribution checks for loot tables. Follows team practices for documenting expected outcomes and validating game mechanic calculations.
Writes unit tests for complex game systems: balance, economy, AI behavior. Uses mocks and stubs to isolate tested components from engine and server. Maintains test coverage for critical game mechanics with each release.
Defines testing strategy for the entire game project: unit, integration, playtest. Standardizes game system testing approaches across the team and establishes coverage metrics. Implements TDD culture for critical gameplay subsystems.
User Documentation
▼
Documents knowledge about game systems in wiki/Confluence: mechanic descriptions, balance rules, design decisions. Creates structured entries about game design decisions with rationale. Uses templates for standardizing the knowledge base.
Creates a structured knowledge base for the game design team: design patterns, balance formulas, postmortem insights. Organizes knowledge sharing: design reviews, brown bag sessions, retrospectives. Ensures searchability and documentation currency.
Defines knowledge management strategy for the game design team. Establishes documentation processes: GDD templates, balance decision logs, design rationale. Ensures knowledge transfer during new designer onboarding and between projects.
Creates user documentation for the game: tutorial texts, help screens, FAQ, mechanic descriptions for players. Writes clear instructions: how-to guides, control references. Considers different player skill levels when writing help content.
Designs in-game documentation system: contextual help, tooltips, codex/bestiary, tutorial system. Creates player-facing documentation for community: patch notes, dev blogs, game guides. Writes user documentation considering player journey and discovery.
Defines documentation strategy for the game project: in-game help, community resources, developer documentation. Establishes writing guidelines and tone of voice for player communication. Coordinates documentation with community management and marketing.