Take-Two logo

Take-Two Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 7 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
42.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Take-Two.

Showing 3 of 7
Take-Two logo
Take-Two

Software Engineer

Engineering · nearly a year ago

Entry Average Positive experience No offer 2 rounds
Interview process
Technical screen Take home
Interview formats
Technical Coding

Did a first technical assessment with a bunch of MCQs on C/C++, DSA, and DP, plus LeetCode medium problems. Then there was a take-home assessment where I had to build functions for an existing game, covering concepts like thread-safe programming.

Confirmed questions1 question
  • Could you tell me about structures in C++?
Take-Two logo
Take-Two

Software Engineer

Engineering · a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Presentation Technical screen
Interview formats
Presentation Technical

To kick things off, they wanted me to put together a presentation. I'd never had to do that for a technical interview before. The pay for this role is also really low. After I presented my stuff, they asked me questions related to what I'd put in my presentation.

Confirmed questions2 questions
  • Can you elaborate on your previous experiences?
  • What are the best practices concerning CICD?
Take-Two logo
Take-Two

Tableau Developer

Analytics · more than a year ago

Mid Easy Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical

The interview process seemed a bit disorganized. I went through 5 interviews, and in the end, they suggested I might be a better fit for a different open position. After that, I was ghosted. Everything moved fast and people were super responsive until my 4th interview. After that, it took about 2-3 weeks for anyone to respond, and I got a random text from the recruiter asking if I was still available because the last interviewer was back from vacation. No one had communicated that the interviewer was on vacation, so I figured I wasn't moving forward. The 5th interview was set up, and it went well. They mentioned I might be a better fit for the Data Analyst role if I was interested, but then it was radio silence again. It's been about a month since I heard back, even after sending 2 follow-up emails to both the recruiter and the HR contact. I really thought working here would be interesting since I love video games, but this whole process would make me hesitant to accept an offer if I ever got one.

Confirmed questions1 question
  • Questions about yourself and some basic Tableau specific questions were asked by people on different teams you'd be working with.

Take-Two Software Engineer Interview Questions

Quoted word for word from Take-Two interview reports.

When comparing access times, which of these data structures is faster?

Read reports

Can you explain the difference between an array and a linked list?

Read reports

Describe the memory structure for arrays and linked lists.

Read reports

What technical questions did you have about my tech stack?

Read report

Can you tell me about any recent projects you've worked on that are relevant to this position?

Read report

Formats, difficulty and experience

Across all 7 Take-Two interview reports.

Interview formats

Technical 46.7%
Coding 26.7%
Behavioral 20%
Presentation 6.7%

Interview difficulty

Easy 28.6%
Average 71.4%
Difficult 0%

Candidate experience

Positive 42.9%
Negative 28.6%
Neutral 28.6%