King interview, decoded.
King's loop depends on the role, and for the tech teams it is not the loop most tech companies run. The public accounts describe no whiteboard algorithms and no system design round; the technical weight sits on homework, a take-home or an online test, which is then reviewed with you line by line. Around it, a run of interviews with the people you would work with, designer, technical director, producer, and a culture conversation, and candidates say that is where King reads hardest. For game engineers the homework is the famous one: a small match-3 game in C++ on a 2D engine King provides, about ten hours in one report. King was founded in Stockholm in 2003, has been part of Activision Blizzard since 2016 and of Microsoft since 2023, and still runs Candy Crush from Stockholm.
Both are free. Either one starts by pasting a King posting: that is what makes the read and the questions King’s rather than generic.
Who King hires
Different tracks, one barKing hires game engineers (C++ on the Candy Crush titles, and the central technology under them), backend and platform engineers, data scientists and analysts, designers, producers and product roles, in Stockholm, Barcelona, London, Berlin and Malmö. A King recruiter's public line on the bar: high, for technical and niche functional roles alike, and set for people who are innovative, focused on quality and committed to an agile but supportive team, with a real interest in games. Non-gaming backgrounds are welcome where the experience transfers.
One company, several loops. What a game designer or a producer meets is not what a backend engineer meets, and the reported accounts differ by craft; what they share is the homework-then-people shape.
Track · Game eng
Game engineering
A take-home match-3 game in C++ on King's own 2D engine, then a code review of it with a principal engineer, then a designer and the studio's technical director. Questions on clean C++, the C++11 features you use, and the ways a program can crash. The postings describe core client systems, engine-level technology and shared frameworks built at King, in large and long-lived C++ codebases, which is why the review reads fundamentals rather than a framework.
Track · Data
Data science and analytics
Statistics with an emphasis on A/B tests, then Python and SQL, then a culture-fit interview and the game producer. Two weeks end to end in a 2024 Stockholm account.
Track · EM
Engineering management
King's own postings set the bar: a servant leader to the team you support, values-based and team-first, who empowers and equips the team to take the right technical decisions, and who has a strong enough technical background to engage deeply in design and architecture and still contribute to a C++ codebase. Read that as two tests: can you follow the technical complexity and reason about the design, and do you give the team the room to own it. The public accounts describe no system design round for managers either.
Track · Other
Design, production, other tech
The people part is the loop: a recruiter, then several conversations with the crafts around the role. Some candidates report a one-way HireVue video as the first step. The public accounts do not describe algorithm rounds or a system design round for any King role.
What is the King interview process?
Round by roundGlassdoor's aggregate over 150 reported interviews puts the process at about 44 days on average, a difficulty a little under 3 out of 5, and under half of candidates calling the experience positive; the most common complaint is the number of interviewers. The shape below is what game-engineering and data candidates report.
Background, motivation, the studio and the game you would work on, and why games.
For game engineers, a simple match-3 game in C++ on a provided 2D engine that renders sprites and captures mouse events. For data roles, questions on statistics with an emphasis on A/B tests, then Python and SQL.
Game engineering, dataYour assignment, line by line: what clean C++ looks like to you, which C++11 features you reach for, the ways a C++ program can crash, and why you built it the way you did.
A UI/UX designer, the studio's technical director, the game producer or team lead: how you work with the craft next to yours, and how you think about the player.
Collaboration, quality, and whether you would enjoy making bite-size entertainment for players who play every day.
Offers are reported to follow quickly once the last interview is done.
What King screens for
What every round is really testingKing's recruiters and its candidates describe the same filter, and it is weighted towards fit: craft first, then collaboration, and an honest interest in games. Candidates describe the interviews as people-centric, and most of the loop is conversations rather than tests.
- Quality of craft, read directly from the homework and its review
- Collaboration with design, production and data, since every studio interview is with a neighbouring craft
- A real interest in games and players, not only in the engineering
- Comfort in an agile, team-run studio rather than a solo role
- Patience with a long loop and many interviewers, which is the reported cost of meeting the whole team
King interview questions
Candidate-reported themesThe reported questions are practical and craft-first. The homework carries the technical weight; the interviews ask how you built it and how you work. Do not prepare LeetCode for this loop; nobody reports being asked it.
Behavioural & motivation
- Why King, and why games?
- Walk me through your assignment: why this structure, and what would you change with more time?
- Tell me about working closely with a designer or a producer on something you shipped.
- How do you keep quality high when the team ships every week?
- Managers: how do you give a team the room to make the right technical decisions, and where do you step in?
- Managers: walk me through a design or architecture decision your team made, and what you understood of it.
Technical
- The match-3 take-home: A small game on King's 2D engine: sprites, mouse input, the board, matches, cascades, in clean C++
- Clean C++, from the foundations: What clean C++ code looks like, favourite C++11 features, the ways a C++ program can crash; memory and performance-critical work is named in the postings
- King's own technology: Core client systems, engine-level code, shared frameworks and tooling, and legacy systems in a large C++ codebase; nothing off the shelf to have already learned
- Data roles: Statistics with an emphasis on A/B testing, then Python and SQL
- Working with the craft next door: Design and production interviews on how you collaborate, not on your code
These are the reported themes — your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level.
Scan a King posting →Pay
What the offer looks likeLevels.fyi for software engineers at King in Greater Stockholm, read on 13 September 2026: the median package is SEK 743K, with a range from about SEK 593K and a highest report near SEK 920K. The submissions record base only, no stock and no bonus, so the parent company's equity, where a role carries it, is not in these numbers. For reference, Levels.fyi puts senior software engineers across Stockholm at roughly SEK 716K to 965K. Calibrd benchmarks the pay on any posting you scan against its level and location.
How to prepare for a King interview
In order- 01Prepare for homework and people, not for a whiteboard. The public accounts describe a take-home or an online test reviewed with you, then a run of conversations; the algorithm and system design rounds other tech companies run are not reported at King.
- 02Do the take-home properly. Ten hours is the reported cost; spend them on a clean, readable match-3 with the matches and cascades right, and write it so you can defend every structure in the review.
- 03Prepare the C++ conversation the review turns into: what clean C++ means to you with an example from your own code, the C++11 and later features you actually use and why, and a short list of ways a program crashes and how you guard against each. The technology is King's own, so the fundamentals are what transfer: memory, performance, ownership of a large codebase, not a framework you can name.
- 04Expect to meet many people. Have a version of your story for a designer, a producer and a technical director, each about how you work with their craft.
- 05Play the game you are interviewing for, seriously, for a week. The studio interviews are with people who make it every day.
- 06Data roles: brush up A/B testing end to end, from design to reading a result, then Python and SQL under time.
- 07Managers: prepare the technical conversation even though the loop is not a whiteboard. The postings ask you to engage deeply in design and architecture; have one real decision your team made that you can explain at the level of trade-offs, and one story of stepping back so the team could own a call. Servant leadership is the phrase King uses itself.
This guide is written from public sources only, listed below. Calibrd's founder worked at King; nothing here comes from inside the company, and the guide is held to the same rule as every other one on this site: only what a candidate could find and cite themselves. 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.
FAQ & sources
The short answersWhat is King's interview process?
Glassdoor's aggregate over 150 reported interviews puts the process at about 44 days on average, a difficulty a little under 3 out of 5, and under half of candidates calling the experience positive; the most common complaint is the number of interviewers. The shape below is what game-engineering and data candidates report. Recruiter call: Background, motivation, the studio and the game you would work on, and why games. Take-home: For game engineers, a simple match-3 game in C++ on a provided 2D engine that renders sprites and captures mouse events. For data roles, questions on statistics with an emphasis on A/B tests, then Python and SQL. Code review: Your assignment, line by line: what clean C++ looks like to you, which C++11 features you reach for, the ways a C++ program can crash, and why you built it the way you did. Studio interviews: A UI/UX designer, the studio's technical director, the game producer or team lead: how you work with the craft next to yours, and how you think about the player. Culture fit: Collaboration, quality, and whether you would enjoy making bite-size entertainment for players who play every day. Decision: Offers are reported to follow quickly once the last interview is done.
What does King look for in candidates?
King's recruiters and its candidates describe the same filter, and it is weighted towards fit: craft first, then collaboration, and an honest interest in games. Candidates describe the interviews as people-centric, and most of the loop is conversations rather than tests. Quality of craft, read directly from the homework and its review Collaboration with design, production and data, since every studio interview is with a neighbouring craft A real interest in games and players, not only in the engineering Comfort in an agile, team-run studio rather than a solo role Patience with a long loop and many interviewers, which is the reported cost of meeting the whole team
What questions does King ask in interviews?
The reported questions are practical and craft-first. The homework carries the technical weight; the interviews ask how you built it and how you work. Do not prepare LeetCode for this loop; nobody reports being asked it. Why King, and why games? Walk me through your assignment: why this structure, and what would you change with more time? Tell me about working closely with a designer or a producer on something you shipped. How do you keep quality high when the team ships every week? Managers: how do you give a team the room to make the right technical decisions, and where do you step in? Managers: walk me through a design or architecture decision your team made, and what you understood of it. The match-3 take-home Clean C++, from the foundations King's own technology Data roles Working with the craft next door
How do I prepare for a King interview?
Prepare for homework and people, not for a whiteboard. The public accounts describe a take-home or an online test reviewed with you, then a run of conversations; the algorithm and system design rounds other tech companies run are not reported at King. Do the take-home properly. Ten hours is the reported cost; spend them on a clean, readable match-3 with the matches and cascades right, and write it so you can defend every structure in the review. Prepare the C++ conversation the review turns into: what clean C++ means to you with an example from your own code, the C++11 and later features you actually use and why, and a short list of ways a program crashes and how you guard against each. The technology is King's own, so the fundamentals are what transfer: memory, performance, ownership of a large codebase, not a framework you can name. Expect to meet many people. Have a version of your story for a designer, a producer and a technical director, each about how you work with their craft. Play the game you are interviewing for, seriously, for a week. The studio interviews are with people who make it every day. Data roles: brush up A/B testing end to end, from design to reading a result, then Python and SQL under time. Managers: prepare the technical conversation even though the loop is not a whiteboard. The postings ask you to engage deeply in design and architecture; have one real decision your team made that you can explain at the level of trade-offs, and one story of stepping back so the team could own a call. Servant leadership is the phrase King uses itself.
- 01Glassdoor, King interview experiencesthe aggregate over reported interviews: about 44 days on average, a difficulty score a little under 3 out of 5, and under half of candidates rating the experience positive; a 2024 Stockholm data-science account (HR contact, statistics with an emphasis on A/B tests, Python and SQL, culture fit, the game producer, two weeks end to end), the complaint about the number of interviewers, and the description of the interviews as people-centric
- 02Glassdoor, King C++ developer interview experiencesthe take-home match-3 game on a provided 2D engine with sprites and mouse events, the code review with a principal engineer, the UI/UX designer and technical director interviews, and the questions on clean C++, C++11 features and the ways a program can crash
- 03Glassdoor, King game developer interview experiencesthe one-way HireVue interview, the take-home of about ten hours writing a game in C++ on a given engine, the face-to-face with a tech lead and a senior developer, and the two-month account of one recruiter call, four interviews with five people and a coding challenge
- 04JobFluent, an interview with a King recruiterthe hiring bar set high for technical and niche functional roles, the innovative, quality-focused, agile-team profile, the passion for games, and the note that non-gaming backgrounds need transferable experience
- 05King, Senior Software Engineer (C++), Candy Crush Soda Saga (posting, mirrored)the Central Technology team's scope (core client systems, engine-level technology, shared frameworks and tooling, large-scale architecture), the requirement to be highly proficient in C++ with experience in large codebases, end-to-end ownership, and the memory and performance-critical, graphics and legacy-systems experience listed as bonuses; the original is job R026184 on careers.king.com
- 06King, Engineering Manager, Gameplay and Monetisation (posting, mirrored)the values-based, team-first leader with a down-to-earth, collaborative style who leads by example; the strong technical background able to engage deeply in design and architecture and contribute to a C++ codebase regularly; line-managing and growing engineers across feature teams; partnering with product, design and QA on roadmaps
- 07King, Engineering Manager (posting, mirrored)the servant leader to the team you support, helping them grow as engineers; empowering and equipping the team to take the right technical decisions and prioritise; and the technical background in software development that lets the manager support and guide the team
- 08Wikipedia, King (company)founded in Stockholm in 2003, acquired by Activision Blizzard in 2016, part of Microsoft since 2023, the studios and the Candy Crush titles
- 09Levels.fyi, King software engineer pay in Greater Stockholmthe SEK 743K median package, the range from about SEK 593K, the highest report near SEK 920K, and that submissions record base only
- 10Levels.fyi, senior software engineer pay in Stockholmthe SEK 716K to 965K range for senior software engineers across Stockholm, for reference
Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.
Prep for a real King role
Practise your King interview, out loud.
Paste a real King 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. Calibrd is built in Stockholm, by a hiring manager who has run engineering hiring here, so this is a loop we know from the other side of the table.
Free to start · No card · Your resume stays yours, encrypted, remove it anytime