Fetching routeLoading page contentGraphical Playground
Loading the next page
Hold on while the requested content finishes loading.
Preparing content
Hold on while the requested content finishes loading.
Graphical Playground is not open for paid roles right now. Because the platform is free and open source, we cannot hire staff yet, while pull requests and open-source contributors are welcome across every public repository.
Formal roles are loaded directly from our CMS. When sponsorship or grant funding supports a hire, the listing appears here automatically.
Graphical Playground runs on volunteer maintainers and community backing, so we do not have payroll budget for salaried or contract roles today. If you still want to contribute code, lessons, shaders, or documentation, check the repository skills below. Academic teams and students proposing research projects can email careers@graphical-playground.com.
Filter by engineering track or browse all 11 public repositories accepting external pull requests and issue reports.
Low-level C++23 rendering, GPU APIs, sample scenes, and experimental shaders.
The open-source C++23 graphics engine at the core of Graphical Playground, targeting Vulkan, DirectX 11/12, OpenGL/OpenGL ES, and Metal across desktop, mobile, and console platforms.
A collection of guided sample projects demonstrating core graphics engineering concepts, rendering techniques, and system-level implementations used throughout the learning platform.
Experimental graphics systems, prototypes, and research-oriented implementations. Used to explore new rendering techniques, abstractions, and performance optimizations.
Web frontend and backend systems, interactive lessons, references, and docs.
The Next.js monorepo powering the Graphical Playground platform: marketing site, app, admin, and backend.
Structured learning paths covering graphics engineering from foundational algorithms to advanced GPU systems. Defines progression, learning objectives, and module dependencies across the platform.
A practical reference for graphics engineering concepts taught within Graphical Playground. Focuses on theory-to-implementation explanations, design patterns, and best practices.
Technical documentation for the Graphical Playground ecosystem, including engine internals, platform architecture, APIs, and contributor guidelines.
Remote GPU runners, cross-platform CMake orchestration, CI workflows, and org compliance.
Infrastructure and DevOps configuration for Graphical Playground. Manages cloud resources, remote GPU execution, scalability, security, and deployment of rendering workloads.
The core build orchestrator for Graphical Playground, abstracting CMake configuration, dependencies, and source management.
A collection of reusable GitHub Actions designed for automation and continuous integration. Provides standardized workflows over modern development pipelines, enabling contributors to build, test, and maintain core graphics projects and ecosystem infrastructure.
Centralized source of truth for organization-wide community files, compliance templates, and automated configuration sync.
Low-level C++23 rendering, GPU APIs, sample scenes, and experimental shaders.
The open-source C++23 graphics engine at the core of Graphical Playground, targeting Vulkan, DirectX 11/12, OpenGL/OpenGL ES, and Metal across desktop, mobile, and console platforms.
A collection of guided sample projects demonstrating core graphics engineering concepts, rendering techniques, and system-level implementations used throughout the learning platform.
Experimental graphics systems, prototypes, and research-oriented implementations. Used to explore new rendering techniques, abstractions, and performance optimizations.
Web frontend and backend systems, interactive lessons, references, and docs.
The Next.js monorepo powering the Graphical Playground platform: marketing site, app, admin, and backend.
Structured learning paths covering graphics engineering from foundational algorithms to advanced GPU systems. Defines progression, learning objectives, and module dependencies across the platform.
A practical reference for graphics engineering concepts taught within Graphical Playground. Focuses on theory-to-implementation explanations, design patterns, and best practices.
Technical documentation for the Graphical Playground ecosystem, including engine internals, platform architecture, APIs, and contributor guidelines.
Remote GPU runners, cross-platform CMake orchestration, CI workflows, and org compliance.
Infrastructure and DevOps configuration for Graphical Playground. Manages cloud resources, remote GPU execution, scalability, security, and deployment of rendering workloads.
The core build orchestrator for Graphical Playground, abstracting CMake configuration, dependencies, and source management.
A collection of reusable GitHub Actions designed for automation and continuous integration. Provides standardized workflows over modern development pipelines, enabling contributors to build, test, and maintain core graphics projects and ecosystem infrastructure.
Centralized source of truth for organization-wide community files, compliance templates, and automated configuration sync.
Console graphics backends are kept private due to platform holder NDA agreements and cannot accept external open-source pull requests. Public engine work happens in gp-engine.
A short path from browsing a repository to getting your first pull request merged cleanly.
Choose a codebase from the list above based on whether you prefer C++ rendering, TypeScript web tooling, curriculum writing, or cloud GPU ops.
Check local build commands, coding rules, and pull request expectations in the contribution guide before writing code.
Open an issue on GitHub or ask maintainers in Discord first so your patch fits the architecture before you invest hours.
No. Graphical Playground is a free, open-source platform and we cannot offer paid jobs or funded employment right now. Whenever funded positions open, they are published here through our CMS.
All open-source contributions right now are voluntary. You keep credit in git history and contributor pages, and sponsors fund our hosting and GPU server bills.
Pick one of the 11 public repositories above that matches your skills, read CONTRIBUTING.md, and look at open issues or ask in Discord before opening a pull request.
Console SDKs for PlayStation, Nintendo Switch, and Xbox require vendor NDAs. Those three backend repositories stay private and do not accept outside pull requests.
Yes. If you want to propose a supervised student project, research topic, or academic collaboration, email careers@graphical-playground.com.