2K logo

Candidate-reported interview insights

2K Software Engineer interviews, decoded.

Explore commonly reported questions, interview rounds, difficulty, duration, and candidate experiences for the Software Engineer role at 2K.

3.5 rating Video Game Publishing

Interview overview

Difficulty

Average

Average rounds

2.7

Average duration

~44 days

Difficulty and candidate experience

Interview difficulty

easy9.1%
average59.1%
difficult31.8%

Candidate experience

negative31.8%
neutral27.3%
positive40.9%

Candidate-reported interview process

Did a coding test on hackerrank, then a take home test where I had to complete a small c++ game. After that, there was a short 10 min HR phone screen. Then, a 1-hour interview with the program coordinator which was conversational and not technical. The response times between interviews and for the final decision were way too long and very taxing.

We did a long take-home assignment to check your technical skills and creativity. It had different parts and was pretty open-ended. After the assignment, there was a quick personal interview. We didn't get any feedback on the assignment.

So the interview process kicks off with a HackerRank C++ assessment, then there's a take home C++ assessment, and finally a technical interview. The C++ part includes a few small questions touching on theory, followed by two bigger questions.

Common 2K Software Engineer interview questions

A focused selection of the most detailed candidate-submitted questions.

  1. 1

    Why do you want to leave your current position?

  2. 2

    Describe a time you solved a difficult problem

  3. 3

    Write a program to shuffle a deck of cards.

  4. 4

    Write a solution for a programming puzzle.

Interview question formats

Coding35.3%
Technical35.3%
Behavioral27.5%
Case2%

Ready to prepare for 2K?

Practice technical, system design, and behavioral questions with Zitlee.

Interview information is based on candidate reports and may not represent the current official hiring process of 2K.