CD Projekt Red interview, decoded.

Updated · Sources at the end

CD Projekt Red publishes its hiring as four steps: it reads your CV, talks to you about your experience and motivation, checks your skills with a test assignment when the role needs one, and tells you the result either way. Its Recruitment and Employer Branding Director describes the recruiter and the hiring manager running the whole process together, through behavioural and technical interviews, and interviews built on real situations you have been in. What sets it apart for engineers is the test assignment and the pay: all twelve engineering ads CD Projekt Red had open in September 2026 printed a gross monthly pay range.

CD Projekt Red makes The Witcher and Cyberpunk 2077, with its headquarters and main studio in Warsaw, studios in Kraków and Wrocław, and a second hub in Boston with a studio in Vancouver. At the end of June 2026 it employed 1,476 people, 1,027 of them developers; the Warsaw hub alone had 1,201. Its engineering ads now ask for Unreal Engine 5 experience.

Free · 2 minutes · no account

The questions for your exact CD Projekt Red role and level.

See the questions CD Projekt Red asks ↓Run a free mock interview →

Interviewing at CD Projekt Red? Below are the questions its job ads point to. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who CD Projekt Red hires

Almost all of CD Projekt Red's engineering hiring is in Warsaw: in September 2026, every engineering role it advertised was in Warsaw or open to remote work from Europe. The roles span gameplay (combat, animation, locomotion, NPC behaviour), core engine work on Unreal Engine 5, online and multiplayer C++, full stack tools, QA engineering, DevOps and IT. Senior gameplay roles ask for five or more years in games and at least one shipped AAA title; the lead NPC behaviour role asks for seven. The ads are written in English, and half of them ask for fluent English outright.

02

What is the CD Projekt Red interview process?

The four steps below are the ones the company publishes, with detail from its Recruitment and Employer Branding Director on the AnsweRED podcast (November 2025). The company says most of its recruiting happens online and that feedback takes about two weeks on average.

01
Let's see: your CV
Reviewed by the recruitment team

The company says it reads every CV. If you are a fit, a recruiter gets in touch by email or phone to set up a meeting.

02
Let's talk: the interview
Online, with the recruiter and the hiring manager

Your experience, your motivation and what drives you, plus your questions about the studio and the role. The recruitment director describes behavioural questions about specific cases you have handled, and technical interviews with the hiring manager in the same process.

03
Let's check: the test assignment
For some roles

Set when a job needs a specific skill set the team wants to see in action, or when a portfolio does not show enough and the candidate has potential. If the role needs a particular language, expect a few questions in it here too.

04
Let's go: the result
By phone or email

The company says it tells every candidate the outcome directly, and its recruitment policy says candidates get feedback whatever stage they reach.

03

The CD Projekt Red test assignment: when it comes and how to take it

What the company says about it

The test assignment is the third of the four steps, and it is not set for every role. The company says it uses one when a job needs knowledge and skills it wants to see used in action. Its art director adds, speaking about art roles, that a test is how the studio checks a candidate with potential when the portfolio is not complete enough, and that a busy candidate may have only one weekend to do a test given two weeks.

  • Ask what is being assessed, and how long you have: Before you start, confirm the brief, the deadline and what the reviewers will look at. If the deadline clashes with your current job, say so early.
  • Scope it to the time you really have: Finish something that works and is clean inside your real hours, then list what you would add. A finished, readable result is easier to judge than an ambitious one that does not run.
  • Write it the way the job ads describe the work: Modern C++ with good practices, clear structure and tests where they fit. For engine or gameplay tasks, name the trade-offs you made about performance and threading.
  • Be ready to talk it through: The recruiter and the hiring manager run the process together, so expect to explain your choices and take feedback on them. The studio says it values people who handle feedback well.

The company's FAQ puts the average wait for feedback after an interview at about two weeks.

The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at CD Projekt Red.

Predict my CD Projekt Red questions →
04

What CD Projekt Red screens for

The recruitment director says the studio has become strongly attitude-focused in the last decade, and the podcast names the values it looks for.

  • Ambitious: the drive to make games at the studio's scale
  • Resilient: a tough skin for feedback on big, long projects
  • Transparent and respectful: open with each other and with players
  • Being a player and thinking about players
  • Collaboration across very large teams; the podcast describes projects with 500 people working on one thing
05

CD Projekt Red interview questions

Drawn from the job ads

No candidate account we could verify lists CD Projekt Red's interview questions. The technical themes below come from its engineering job ads, and the behavioural questions follow what its recruitment director says the interviews ask: specific situations, told the way they happened.

Behavioural & motivation

  • Why CD Projekt Red, and why this team?Listening for: Specificity · Connection · Research
  • Tell me about a specific time you disagreed with a technical decision on a large team. What happened?Listening for: A specific real case · Transparent and respectful · How it ended
  • Describe feedback on your work that was hard to hear, and what you did with it.Listening for: The feedback itself · How you handled it · What you changed
  • Walk me through a feature you shipped on a game, and your exact part in it.Listening for: The feature, concretely · Your exact part · The player's side

Technical

  • Practice: how would you manage ownership of game objects in modern C++, and where would you avoid smart pointers?Modern C++: C++11 at least, with C++17 and 20 welcome, and C++ best practicesListening for: Clear ownership model · Modern features used well · Performance awareness
  • Practice: how does world streaming work in Unreal Engine 5, and what would you watch for when a player moves fast through an open world?Unreal Engine 5: Engine architecture, and for core roles streaming, memory, Chaos physics or world-building toolsListening for: How streaming works · Memory budget · Avoiding hitches
  • Practice: an NPC needs to know whether a target is inside its field of view and within range. How would you compute that, and keep it cheap for hundreds of NPCs?Gameplay systems: Combat, animation, locomotion, physics or NPC behaviour, with 3D vector maths and linear algebraListening for: Correct vector maths · Scales to many NPCs · Edge cases
  • Practice: a crash happens once in a few hundred play sessions, only in release builds. How would you track it down?Multithreading and debugging: Multithreaded systems, and finding and fixing complex bugsListening for: Gathers evidence · Suspects the likely causes · Proves the fix
  • Practice: would you choose client-server or peer-to-peer for an online co-op mode, and how would you stop players cheating?Online and multiplayer: Client-server and peer-to-peer architecture, and network and server securityListening for: Architecture with reasons · Validation of player actions · Network and server security

These come from the job ads, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →

Predict my CD Projekt Red questions →
06

Pay

Software engineer, C++ online · adPLN 12.6–22.4K
Senior full-stack engineer · adPLN 17.8–30.6K
Senior engineer, gameplay · adPLN 23.7–37.5K
Lead gameplay engineer · adPLN 39.8–54.7K

These are the gross monthly ranges printed in CD Projekt Red's own Warsaw job ads in September 2026: software engineer (C++, online) PLN 12,600 to 22,400, senior full-stack engineer PLN 17,800 to 30,600, senior gameplay engineer PLN 23,700 to 37,455, senior core engineer PLN 23,700 to 37,000, and lead gameplay engineer (NPC behaviour) PLN 39,800 to 54,670. The ads say the final offer depends on experience and qualifications. For roles that need relocation, the ads describe a package covering a flight, a company apartment for the first month, moving your family and pet, and help with legal and tax formalities. Calibrd benchmarks the offer against your level and location in the report.

07

How to prepare for a CD Projekt Red interview

  1. Read the ad for the exact pay range and working mode before the first call: the ads print both.
  2. Prepare three or four true stories about specific situations on large teams, including one about feedback that was hard to take. The interviews ask about real cases.
  3. Brush up on modern C++ and Unreal Engine 5, and for gameplay roles on 3D maths, animation and multithreading.
  4. If a test assignment comes, agree the scope and the deadline first, and plan it around your real free time.
  5. Decide about Warsaw early. Most roles are office-first or need relocation; the ads say which, and some core roles allow remote work within Europe.
  6. Have a real answer to why this studio and this game. The values include being a player and thinking about players.

This guide covers CD Projekt Red's engineering and research hiring. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Supercell, King or EA DICE? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a CD Projekt Red mock: spoken answers, coached on the spot. Your first mock is free.

Run a CD Projekt Red mock →
08

FAQ & sources

What is CD Projekt Red's interview process?

The company says most of its recruiting happens online and that feedback takes about two weeks on average. The stages, in order: Let's see: your CV; Let's talk: the interview; Let's check: the test assignment; Let's go: the result.

What does CD Projekt Red look for in candidates?

The recruitment director says the studio has become strongly attitude-focused in the last decade, and the podcast names the values it looks for. Ambitious; Resilient; Transparent and respectful; Being a player and thinking about players.

What questions does CD Projekt Red ask in interviews?

No candidate account we could verify lists CD Projekt Red's interview questions. Technical themes: Modern C++; Unreal Engine 5; Gameplay systems; Multithreading and debugging; Online and multiplayer.

Does CD Projekt Red give a test task?

The test assignment is the third of the four steps, and it is not set for every role. The company says it uses one when a job needs knowledge and skills it wants to see used in action. Covered on this page: Ask what is being assessed, and how long you have; Scope it to the time you really have; Write it the way the job ads describe the work; Be ready to talk it through.

How do I prepare for a CD Projekt Red interview?

Read the ad for the exact pay range and working mode before the first call: the ads print both. Prepare three or four true stories about specific situations on large teams, including one about feedback that was hard to take. The interviews ask about real cases.

  • 01CD Projekt Red, recruitment processthe four steps (Let's see, Let's talk, Let's check, Let's go), the test assignment and language questions at step three, the result given either way, most recruiting online, and about two weeks' average wait for feedback
  • 02AnsweRED podcast, episode 24: behind game dev hiringthe Recruitment and Employer Branding Director and an art director on the recruiter and hiring manager working together, interviews about actual situations, tests when a portfolio is not complete enough, the two weeks and one weekend, attitude focus and the values (28 November 2025)
  • 03CD PROJEKT, recruitment policyfeedback to candidates whatever stage the process ends at
  • 04CD Projekt Red, open positions (SmartRecruiters)the 45 open roles on 26 September 2026, the engineering roles in Warsaw or remote in Europe, the printed gross monthly pay ranges, the requirements, the working modes and the relocation package
  • 05CD PROJEKT, Management Board report for H1 20261,476 employees and 1,027 developers at 30 June 2026, the Warsaw hub at 1,201 (65% developers), Boston at 275 (88% developers), and the Kraków, Wrocław and Vancouver studios (2 September 2026)
  • 06CD Projekt Red, summer internshipone or two interviews and a skill test for interns, and that all internships are paid

Prep for a real CD Projekt Red role

Practise your CD Projekt Red interview, out loud.

Paste a real CD Projekt Red posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the CD Projekt Red prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

CD Projekt Red Interview: Test Task, Pay — Calibrd