Game Development Interview questions

Unreal Engine Developer (C++) interview questions

These Unreal Engine Developer interview questions come from our vetting, where 3.4% of applicants pass 5 gates. You get 20 questions with answer hints, a task, red flags and a scorecard.

Updated: October 2026Remote Pro Ai · Game Development20 questions

Build my squad

How we assess

Every applicant goes through 5 gates: application, an AI-assisted screen, a live technical assessment scored by a practice lead, a client-fit interview, and reference and credential checks. The questions below come from the live assessment. We score answers on reasoning and trade-offs, not on recalling definitions.

20 technical questions with model-answer hints

Questions 1–⁠10 (role-specific)

  1. When do you write logic in C++ rather than Blueprints?

    Model-answer hint

    C++ for core systems and performance; Blueprints for designer iteration; expose clean APIs.

  2. Explain Unreal’s gameplay framework classes.

    Model-answer hint

    GameMode, GameState, PlayerController, PlayerState, Pawn, and where each exists on server and client.

  3. How does property replication work, and how do you limit bandwidth?

    Model-answer hint

    replication conditions, relevancy, net update frequency, dormancy.

  4. How do Server, Client and NetMulticast RPCs differ?

    Model-answer hint

    direction, reliability, validation and when each is appropriate.

  5. How does GAS handle prediction?

    Model-answer hint

    prediction keys, local prediction of abilities and effects, server reconciliation.

  6. How do you find the cause of a hitch on console?

    Model-answer hint

    Unreal Insights, GC spikes, asset loading, shader compilation, async loading.

  7. When are Nanite and Lumen the wrong choice?

    Model-answer hint

    lower-end targets, unsupported content types, tight budgets; plan fallbacks.

  8. How do you manage memory and garbage collection in Unreal?

    Model-answer hint

    UPROPERTY references, pooling, fewer runtime allocations, GC tuning.

  9. How do you structure a large Unreal project for a team?

    Model-answer hint

    modules and plugins, data assets, naming conventions, Perforce streams.

  10. How do you expose tunable values to designers safely?

    Model-answer hint

    data assets and tables, metadata specifiers, validation, hot reload.

Questions 11–⁠20 (Game Development core)

  1. How do you find and fix a frame-time spike on target hardware?

    Model-answer hint

    platform profiler, isolate CPU, GPU or I/O, per-system budgets, verify on device.

  2. How do you manage memory budgets on mobile?

    Model-answer hint

    per-category budgets, texture compression, streaming, leak tracking on low-end devices.

  3. How do you keep gameplay data-driven for designers?

    Model-answer hint

    config assets or tables, hot reload, validation, simple tooling.

  4. A mechanic “doesn’t feel right”. What do you do?

    Model-answer hint

    quick prototype, exposed tuning values, playtests, combine feel with telemetry.

  5. How do you organise version control for large binary assets?

    Model-answer hint

    Perforce streams or Git LFS, file locking, branch strategy, CI builds.

  6. What makes a build pipeline dependable for a live game?

    Model-answer hint

    automated builds, smoke tests, versioned content, staged rollout, fast rollback.

  7. How do you prepare a title for platform certification?

    Model-answer hint

    requirements checklist from day one, automated checks, an internal pre-certification pass.

  8. How do you use telemetry after soft launch?

    Model-answer hint

    funnels, D1/D7/D30 retention, cohorts, A/B tests, guardrail metrics.

  9. How do you handle Arabic text and RTL layouts in game UI?

    Model-answer hint

    glyph shaping, mirrored layouts, font fallback, text expansion, culturalisation review.

  10. Describe a feature you cut or rescoped to hit a milestone.

    Model-answer hint

    trade-off logic, stakeholder alignment, effect on the player.

Interviewer tip: Ask for a real example after every answer. Strong candidates describe what they built, what broke and what they changed.

Practical task

In a provided UE5 project, implement a replicated dash ability with GAS, including cooldown and cost, that feels responsive under 150 ms of simulated latency. Add a short note on how you profiled it and kept network cost low.

How to run it Share the brief 24 hours ahead or run it live. Ask the candidate to talk through trade-offs as they work; reasoning matters more than a finished artefact.

Red flags our practice leads watch for

  • Builds everything in Blueprints with no thought for performance.
  • Cannot explain authority and network roles in Unreal.
  • Has never profiled on target hardware.
  • Ignores designer workflows when building systems.
  • Universal flag: Vague answers that never reach a concrete system, number or decision the candidate personally owned.

The scorecard we use

Score each dimension 1–⁠4 (1 = no evidence, 2 = partial, 3 = solid, 4 = exceptional):

DimensionWeightWhat a 4 looks like
Technical depth, production judgement and security40%Explains how and why, designs for failure and sensitive data, and knows each tool’s limits
Practical task and problem solving30%Delivers a working solution with tests and documented decisions
Communication and documentation20%Explains clearly to technical and non-technical audiences, in English or Arabic
References and regional context10%References confirm the claimed scope; knows the frameworks and data-residency rules that apply

Pass bar: weighted average of 3.0 out of 4 or higher, with no dimension below 2. The practice lead approves the final result.

Skip the interview loop

Every specialist on our shortlist has already passed this assessment. Working in 4 working days.

Frequently asked questions

Yes. The questions, hints, practical task and scorecard are free to use. They work best when every interviewer scores the same dimensions independently and compares notes afterwards. Ask for a concrete example after each answer, because recalled definitions say little about how someone performs on a live system.

They come from the same live technical assessment, but practice leads rotate and adapt questions so candidates cannot rehearse them. What stays fixed is the scope being tested, the practical task format and the scorecard, which is why the published version is safe to share.

Plan for a technical conversation covering 8 to 10 of the questions, plus the practical task either live or as a short take-home. Use the remaining questions as follow-ups. If you would rather skip the loop, Remote Pro Ai shortlists already-assessed specialists within 48 hours.

Our pass bar is a weighted average of 3.0 out of 4 or higher across the 4 dimensions, with no dimension below 2. Production judgement and security, scored inside the 40% technical dimension, often separate strong candidates from those who interview well but struggle once they own a live system.

The task mirrors the first week of real work in this role and never uses client data. It runs live or as a short take-home of a few hours, and the candidate then explains the trade-offs behind each decision. Reasoning and production habits count for more than a polished final artefact.