Gameplay Engineer
Montreal, QC · Remote
Remote-first habits: clear async communication, writes things down, doesn't create silent dependencies Preferred * Online multiplayer systems - Actor replication, GameplayEffects replication, ability ...
Gameplay Engineer
Montreal, QC · Remote
Remote-first habits: clear async communication, writes things down, doesn't create silent dependencies Preferred * Online multiplayer systems - Actor replication, GameplayEffects replication, ability ...
Async Remote information
What is an async remote job?
Async Remote jobs are positions where employees work remotely and communicate asynchronously, meaning they don't need to be online or respond in real time. This allows team members to work across different time zones and manage their own schedules, focusing on productivity rather than constant availability. Async Remote work relies heavily on clear written communication and documentation, as well as tools like project management platforms and shared documents. These roles are popular in tech, writing, design, and other digital fields where independent, outcome-oriented work is possible.
What skills and qualifications are needed to thrive as an async remote worker?
To thrive as an async remote worker, you need strong time management, self-discipline, and the ability to work independently, often supported by experience in remote or distributed teams. Familiarity with collaboration tools such as Slack, Trello, Notion, and asynchronous communication platforms is typically essential. Excellent written communication, proactiveness, and adaptability set top performers apart in this environment. These skills enable effective collaboration, maintain productivity, and ensure project success across different time zones and flexible schedules.
What are common challenges of working in an async remote environment, and how can they be addressed?
One common challenge in async remote roles is maintaining clear and effective communication, as team members often work in different time zones and may not be available simultaneously. To address this, it's important to document discussions thoroughly, use project management tools to track progress, and set clear expectations for response times. Building trust through regular updates and proactively sharing your work can also help foster collaboration and keep everyone aligned, even without real-time interactions.
What is the difference between Async Remote vs Full-Stack Developer?
| Aspect | Async Remote |
|---|
| Required Credentials |
|---|
| Work Environment |
|---|
| Employer & Industry Usage |
|---|
| Comparison Summary |
|---|
Async Remote refers to a work style emphasizing flexible, asynchronous communication, often used across various roles including developers. Full-Stack Developers are specific technical professionals responsible for both front-end and back-end development. While Async Remote describes how work is done, Full-Stack Developer describes the job role. Many Full-Stack Developers work remotely, sometimes asynchronously, but Async Remote can include roles beyond development. Understanding this distinction helps job seekers identify roles that match their skills and preferred work style.
Full-time
Re-posted 14 days ago
Job description
Description
Devoted Studios is a globally remote game development company specializing in Co-development, Porting, and End-to-End Art Production for the global gaming industry. We collaborate across time zones to support projects on all major platforms, engines and styles - from AAA titles to emerging technologies.
Our team includes world-class talents who bring deep expertise in external development, pipeline optimization, and creative problem-solving. Whether it's porting games to new systems, enhancing gameplay features, or crafting stunning visuals, Devoted Studios operates as a trusted, flexible extension of our partners' internal teams.
We are proud to be the development partner of choice for industry leaders such as:
- Epic
- Xbox
- Meta
- Obsidian Entertainment
- Riot
- Gearbox Software
We are seeking a Gameplay Engineer who is a specialist e a specialist - deeply fluent in C++ and Unreal Engine, experienced shipping AAA systems, and capable of taking a brief from a gameplay designer and turning it into production-quality code that holds up on every platform and survives every patch.
Key ResponsibilitiesCore Gameplay Systems (~50%)- Implement gameplay systems from designer briefs: combat, abilities, movement, AI behaviours, progression, inventory, interaction, camera - scope varies by engagement
- Build reusable, maintainable, testable gameplay code in C++ (and Blueprint where appropriate) within Unreal Engine 5
- Own Gameplay Ability System (GAS) implementation - AttributeSets, Abilities, GameplayEffects, GameplayCues - on engagements where GAS is in use
- Implement animation-gameplay integration: Anim Notifies, state-driven Anim BPs, root motion handling, blendspaces
- Implement multiplayer-safe gameplay code on engagements with networking requirements - replication, client-server authority, lag compensation
- Profile and optimise gameplay code to target platform budgets - CPU frame time, tick overhead, replication cost
- Write code that is reviewable: clean, commented where logic is non-obvious, consistent with project standards
- Catch and fix gameplay bugs - including edge cases, exploit patterns, and regression from live updates
- Participate actively in code review: review peers' PRs with specificity, receive and act on feedback without defensiveness
- Work directly with gameplay designers to translate design intent into engine behaviour - close the gap between what is specced and what ships
- Identify implementation risks in design briefs early - before they become rework - and propose alternatives when the spec is not buildable as written
- Expose gameplay parameters to designers in a way that is tunable without engineering involvement (Blueprint exposed properties, Datatable-driven tuning, etc.)
- Document systems clearly - architecture decisions, integration points, known limitations
- Support technical handoffs between phases or teams: leave the codebase in a state that the next engineer can understand without a phone call
Requirements
- 5+ years of professional game development experience with at least 3 years in AAA or mid-tier shipped titles
- At least 2 shipped commercial titles on PC or console as a gameplay engineer - prototypes and internal tools do not count
- Deep Unreal Engine 5 experience in C++: Gameplay Framework (Actor, Component, GameMode, GameState, PlayerController), GAS, CharacterMovement, Anim BP integration
- Strong C++ fundamentals: memory management, data-oriented thinking, performance-aware coding
- Blueprint proficiency - not just reading it, but building designer-facing tooling in it
- Experience with multiplayer gameplay replication (nice to have, not required for all engagements)
- Strong game design sensibility - can tell good gameplay from broken gameplay and can articulate why
- Remote-first habits: clear async communication, writes things down, doesn't create silent dependencies
- Online multiplayer systems - Actor replication, GameplayEffects replication, ability prediction and correction
- Console platform experience: certification pipelines, platform-specific constraints
- Gameplay AI systems in UE5: Behavior Trees, EQS, AI Perception - not required but valuable for certain engagements
- Prior co-development or external development experience
Benefits
This would he a full-time employment role with standard industry benefits in Canada