DoiT logo

DoiT Interview Questions
& Process

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

Based on 265 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
90.9% Positive experience

Which role are you interviewing for?

30 roles · 265 reports

Candidate interview experiences

First-hand accounts from people who interviewed at DoiT.

Showing 4 of 265
DoiT logo
DoiT

Business Development Representative

Sales · nearly a year ago

Entry Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Presentation Phone screen
Interview formats
Presentation Behavioral Technical

Had 4 rounds of interviews. Started with HR, then talked to a current BDR teammate, followed by the head of sales, and finally the BDR manager. There was an exercise where I had to pick out three companies that fit the Ideal Customer Profile (ICP) that I would cold outreach to. I then had to explain my choices to the head of sales using a short slide presentation, just a couple of slides. The last round with the BDR manager involved a mock cold call for a general persona, not a specific individual. The camera was off during the exercise. I got strong feedback but unfortunately no offer.

Confirmed questions1 question
  • If you weren't given a call list, how would you go about identifying people to contact?
DoiT logo
DoiT

Senior Backend Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding Behavioral

So I had a screening call with Oscar, which was pretty standard and seemed to go well. After that, I had a technical interview with two engineering leads that lasted about 1.5 hours. It was mostly a discussion about topics from the job description, some code analysis, and a quick exercise. The technical part was okay, though one of the senior engineers was sometimes tough to follow, possibly due to his English or when we delved into unexpected topics where questions weren't clear (even the other engineer seemed confused at times). The interview ended abruptly because they had another meeting immediately after, so the last 30 minutes felt rushed, and I barely got to ask any questions. The worst part is I never heard back after that. It's been a week with no feedback, I emailed Oscar, and another week has gone by with complete silence. Basically, don't bother, the interview process was disorganized and you'll get ghosted.

Confirmed questions4 questions
  • Can you compare and contrast ClickHouse and Postgres?
  • Tell me about your experience with Kubernetes.
  • What are your thoughts on Go (programming language)?
DoiT logo
DoiT

Senior Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Behavioral Technical Coding

The interview started with a call with Oscar where I was given details about the recruitment process and told I'd get feedback after each stage. This was followed by a technical interview focusing on my experience, Go principles, channels, and goroutines. Unexpectedly, I was then asked to do a live coding task using a text editor, as Oscar hadn't mentioned this beforehand and I didn't have an IDE available. There were no questions about design patterns or architecture. The interviewers were quite introverted, which contrasted with my open personality. I also observed some communication issues when one interviewer tried to explain a task, suggesting they could improve how they ask questions. Furthermore, I didn't receive the promised feedback, even after reaching out separately, leaving me with mixed feelings.

Confirmed questions1 question
  • What data structure allows setting values with O(1) complexity?
DoiT logo
DoiT

Account Executive

Sales · a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Panel Background check
Interview formats
Behavioral Technical Presentation

My interview process with DoiT was a really great and interesting experience. Over about four weeks, I got to talk with a few team members, and each talk made me more interested in the company and its vibe. Right from the start, the Senior Recruiter was super open and helpful, making sure communication was clear and I felt supported. The process had a good structure and included three more parts: an interview with the Hiring Manager, a Panel Interview, and then a final chat with the Chief Revenue Officer (CRO). Every conversation felt important, was well-paced, and showed how DoiT is all about teamwork and its people. I'm thankful for the whole thing and everyone who made it so easy and welcoming.

Confirmed questions2 questions
  • Could you walk me through a typical structured discovery call, detailing each step?
  • Describe the entire process of a structured discovery call.

DoiT Interview Questions

Quoted word for word from DoiT interview reports.

How does the Linux kernel's mechanism for separating system resources facilitate containerization and enable features like Kubernetes resource requests and limits?

Read reports

Can you write code for get, set, and setAll functions that operate in O(1) time?

Read reports

How would you debug packet loss between an EC2 and an RDS instance?

Read reports

Can you detail the entire process of resolving an A record to its corresponding IP address?

Read reports

What are potential reasons for GKE cluster level autoscaling to have issues with scaling down effectively?

Read report

What does a 502 error in Looker signify, and how would you resolve it?

Read report

Could you explain what a cold start is in the context of AWS Lambda functions?

Read report

In Google Workspace, where would you look to find initial email errors or misconfigured settings for a company?

Read report

Could you explain the functionality and predicted output of the provided code snippet involving chained promises?

Read report

Formats, difficulty and experience

Across all 265 DoiT interview reports.

Interview formats

Behavioral 45.5%
Technical 30.2%
Presentation 14.3%
Case 3.9%
Coding 2.6%

Interview difficulty

Easy 9.4%
Average 70.6%
Difficult 20%

Candidate experience

Positive 90.9%
Negative 6.8%
Neutral 2.3%

Reports by job function

Sales 116
Engineering 91
Operations 19
Product 11
Finance 9
HR 7