Game Development Specialist (GDS)

It is recommended that candidates complete approximately 150 hours of structured coursework or equivalent hands-on studio time in foundational game-development skills before attempting the Game Development Specialist (GDS) Certification exam.

The exam gauges readiness across eight key domains that drive modern game production. Candidates must demonstrate they can design engaging core loops, author clean and optimized code, craft art- and audio-ready assets, ensure quality through disciplined testing, and publish a playable, portfolio-ready build—blending technical execution with professional best practices.

1. Game Design Fundamentals

• Identify key genre conventions and match them to appropriate target audiences.
• Deconstruct a reference game’s core loop, supporting loop, and meta-loop mechanics.
• Produce a concise game-design document that states vision, player goals, and success criteria.
• Draft a level-flow diagram showing progression, checkpoints, and difficulty ramp.
• Apply basic UX principles — readability, feedback, accessibility — to an early design concept.

2. Programming for Interactive Experiences

• C# Gameplay Logic – Build a short, well-commented C# script that drives a basic game mechanic—e.g., player movement, input mapping, or score-counter update.
• Physics & Collisions in C# – Implement input handling, collision detection, and simple physics/kinematics using the engine’s C# API (e.g., rigidbody forces, trigger callbacks).
• Structural Patterns – Organise game entities with C# classes that demonstrate at least one pattern: component-based, inheritance hierarchy, or data-oriented struct.
• Debug & Optimise – Use the engine’s debugger and profiler to locate a performance hot-spot in the C# update loop, apply an optimisation (e.g., object pooling, early exit), and verify improved frame time.
• External Service Integration – Call a lightweight cloud service (leaderboard, save slot, or REST endpoint) from C# using the engine’s HTTP or SDK wrapper, handle success/error responses, and follow basic security best practices (API key storage, rate limiting).

3. Digital Art & Animation

• Prepare 2-D assets or UI elements that follow an established style guide and import pipeline.
• Model and texture at least one low-polygon 3-D object suitable for real-time rendering.
• Rig and animate sprites or meshes using keyframes or timeline-based tools.
• Enhance visuals with parallax layers, particle effects, or entry-level shader techniques.
• Optimise asset sizes, formats, and level-of-detail settings to meet target-platform constraints.

4. Audio Design & Integration

• Acquire or create royalty-free sound effects and background music appropriate to the project theme.
• Edit audio assets (trim, normalise, compress) to meet engine-ready technical standards.
• Implement layered or event-driven music and basic spatial/positional audio cues.
• Balance mixes to avoid clipping and maintain clarity across devices.
• Apply consistent naming, metadata, and licence attribution for all audio files.

5. Engine Workflow & Toolchains

• Navigate core editor interfaces: scene hierarchy, property inspector, and timeline/sequencer equivalents.
• Configure camera behaviour, lighting setups, and optional post-processing for visual polish.
• Build reusable gameplay units using the engine’s prefab, blueprint, or packed-scene system.
• Create responsive UI menus and HUDs that support multiple resolutions and input devices.
• Generate and troubleshoot platform builds for web, mobile, or desktop targets.

6. Testing & Quality Assurance

• Plan structured play-tests linked to user personas and acceptance criteria.
• Execute test cases, record reproducible defects, and prioritise fixes by severity.
• Conduct at least one usability test session and summarise actionable feedback.
• Iterate on prototypes using data-informed adjustments such as A/B comparisons.
• Implement an introductory automated or scriptable test within the development environment.

7. Project Management & Collaboration

• Break project scope into epics, user stories, or task lists with effort estimates.
• Use version-control software to branch, merge, and tag releases while resolving conflicts.
• Participate in agile practices (stand-ups, sprint reviews, retrospectives) with clear, professional communication.
• Track work progress on a digital project board or issue tracker until completion.
• Demonstrate respectful, inclusive feedback during code or asset reviews.

8. Publishing, Portfolio & Professional Practice

• Select and justify an appropriate distribution model (free-to-play, premium purchase, educational licence, etc.).
• Align content with age-rating guidelines and relevant data-privacy regulations (e.g., COPPA, GDPR-K).
• Produce essential marketing assets such as store-page copy, screenshots, and a short gameplay trailer outline.
• Publish at least one playable build alongside accessible source or sample code in a public repository or portfolio site.
• Demonstrate foundational interview etiquette and outline a personal learning plan for continued growth.

The minimum system requirements are:

• Operating system: Windows 7/8/10 OS, MacOS X 10.0x or newer, Linux OS
• Minimum RAM: 1GB or more depending on the Operating System
• Minimum processor: 1.0 Ghz or more depending on the operating system and the architecture
• A color monitor with minimum display resolution: 1366px by 768px
• Internet access
• The latest version of the Chrome browser
• Automatic updates, notifications, other popup windows, and anything that can disrupt the examination process should be disabled