projekt202 logo

projekt202 Interview Questions
& Process

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

Based on 21 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
42.9% Positive experience

Which role are you interviewing for?

10 roles · 21 reports

Candidate interview experiences

First-hand accounts from people who interviewed at projekt202.

Showing 4 of 21
projekt202 logo
projekt202

Experience Strategist

Design

Mid Average Negative experience No offer 7 rounds
Interview process
Recruiter call Phone screen Presentation Background check Offer
Interview formats
Behavioral Presentation Case

I had 7 interview rounds. First, a 30-minute chat with the recruiter. Then, a 30-minute 'craft interview' with the hiring manager, where I submitted a deck with work samples that they didn't review or discuss. Next, a 45-minute meeting with the GM, followed by a 45-minute meeting with the VP of Research and Strategy. After that, I did a 1-hour case presentation with some team members. Then, a 1-hour meeting with another manager. Finally, a 45-minute session with my potential peers. The whole thing started before Christmas. The final interviews were on February 1st. I didn't hear back for over a week, and then I was told hiring urgency was pushed out by 3-4 weeks, but that I was a top candidate. I followed up again after 3 weeks and got the same response. It's frustrating to have spent so much time prepping and interviewing only to get minimal follow-up. I would have preferred a clear 'no' for closure rather than this limbo, especially given the time investment. It felt like they were hoping I'd just give up instead of being upfront.

Confirmed questions2 questions
  • Can you tell me about your past work experience?
  • We have a case study for you that relates to the job and your background.
projekt202 logo
projekt202

Experience Designer

Design

Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Panel Presentation Offer
Interview formats
Behavioral Technical Presentation Other

The interview process was really thorough, which I liked because they want to be sure you've got the skills you say you do. You should definitely come ready. The first interview was with a Senior Director. We talked about my portfolio, design in general, the company, and the role. Then, there was a 2 hour panel interview. It involved a deep dive into my past projects, a lot of questions, and also a 20-30 minute design challenge. Be ready to present your work clearly and answer many questions. For the design challenge, they're looking to see your thought process and how you can quickly make a plan for a new solution and then explain your reasoning.

Confirmed questions2 questions
  • What makes you want to work for a consultancy rather than a product company or in-house?
  • Why do you want to join a consultancy instead of a product company/in-house?
projekt202 logo
projekt202

Software Engineer

Engineering

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

I spoke with the recruiter after getting referred by someone who works there. They had to reschedule the interview a few times and didn't seem very engaged during our conversations. The recruiter mentioned that my skills weren't a good fit for the project. Later, the employee who referred me was asked about whether they knew any smart people from their home country, Germany. This seems to be the reason the recruiter was dismissive and kept rescheduling. However, it worked out for the best because I wouldn't want to work for a company that's not inclusive and judges candidates based on their origin.

Confirmed questions1 question
  • Could you describe the most recent project you were involved in?
projekt202 logo
projekt202

Director of IT Systems

Engineering

Director Average Negative experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The interview process was simple and not overwhelming. After a lot of multi-day, all-day interviews elsewhere, interviewing with p202 was a welcome change. I first met with HR to discuss the role and assess fit, then interviewed with my potential manager, and finally had a technical interview with my peers, the people who would report to me, and my boss's boss. It was great that my direct reports were involved in the interview process. It shows a lot about the company culture when the people who will report to you get a say in whether you're a good fit.

Confirmed questions2 questions
  • If you get this job, what's your plan for training us on new systems and processes?
  • What's your level of familiarity with ISO standards or other security standards?

projekt202 Interview Questions

Quoted word for word from projekt202 interview reports.

Can you explain how React operates and how it interacts with the DOM?

Read reports

Why do you want to join a consultancy instead of a product company/in-house?

Read report

What's your level of familiarity with ISO standards or other security standards?

Read report

Formats, difficulty and experience

Across all 21 projekt202 interview reports.

Interview formats

Behavioral 44.2%
Technical 27.9%
Presentation 11.6%
Coding 9.3%
Other 4.7%

Interview difficulty

Easy 33.3%
Average 57.1%
Difficult 9.5%

Candidate experience

Positive 42.9%
Negative 52.4%
Neutral 4.8%

Reports by job function

Design 8
Engineering 7
Sales 2
HR 1
Analytics 1
Research 1