ID Analytics logo

ID Analytics Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

4 Rounds average
Average Typical difficulty
54.5% Positive experience

Which role are you interviewing for?

5 roles · 12 reports

Candidate interview experiences

First-hand accounts from people who interviewed at ID Analytics.

Showing 4 of 12
ID Analytics logo
ID Analytics

Data Scientist

Analytics · more than a year ago

Entry Difficult Positive experience Accept offer 7 rounds
Interview process
Take home Phone screen Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral

The interview process was quite thorough, with several stages. It began with a data challenge to assess skills in data cleaning and preprocessing using Python or R. This was followed by a 45-60 minute phone screen with a Data Scientist, covering past data science projects, basic statistics, and software engineering and ML fundamentals, all at a moderate difficulty focused on core knowledge. The next step was another 45-60 minute phone screen with a Sr. Data Scientist, delving deeper into machine learning algorithms and their constraints. Subsequently, there were four 45-60 minute panel interviews onsite at ID's San Diego office with team members, focusing heavily on technical aspects like ML, programming, stats, math, and MapReduce, plus a non-technical one-on-one with the hiring manager during lunch. The interviews were collaborative discussions, not interrogations, with helpful hints provided when needed. Overall, the experience was positive, with all interviewers being respectful and friendly.

Confirmed questions8 questions
  • Could you explain the kNN (k nearest neighbor) algorithm and its complexity?
  • Can you describe your past experience in data science?
  • What are some fundamental statistical concepts you know?
ID Analytics logo
ID Analytics

Software Engineer

Engineering · more than a year ago

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

I had a first easy phone screen with the recruiter. They asked questions to check my fit and skills for the job. It went well, so the recruiter set up a call with an engineering director. The next phone screen was mainly technical questions and some experience questions. The technical questions covered basic data structures and OOP. A few days later, the recruiter told me I passed and would have another technical phone screen with a manager. This person had a very strong accent, and I could barely understand anything. I asked them to repeat or slow down, but even then, I couldn't grasp what they were saying. For the questions I did understand, they weren't difficult, similar to the previous screen. The interviewer got upset because I kept asking them to repeat. I got an email a few days later saying I didn't pass.

Confirmed questions3 questions
  • Can you explain what abstraction is and its purpose?
  • What are some basic data structures?
  • What are Object-Oriented Programming concepts?
ID Analytics logo
ID Analytics

Engineer

Engineering · more than a year ago

Entry Average Neutral experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Technical Behavioral

HR reached out first, they seemed uninterested and asked about my background then read 2 technical questions. The next week, a very professional and technical person contacted me and asked a lot of technical questions. About two weeks after that, I was invited on-site to meet the team. They asked some probing questions, mostly to see if I’d be a good fit. It felt a bit disorganized overall, but it was alright.

Confirmed questions2 questions
  • There are three light switches in your basement, all off. Each switch controls one of three bulbs upstairs. You can flip any switch, but you only get to go upstairs once to check the bulbs. How do you figure out which switch goes to which bulb?
  • Can you describe a time you had to work with a difficult coworker and tell me about it?
ID Analytics logo
ID Analytics

Business Analyst

Analytics

Executive Difficult Positive experience Accept offer 1 round
Interview process
Presentation
Interview formats
Case Presentation

People were friendly and mostly organized. The biggest stress was preparing for the case study. You are given a data file to analyze about goods sold in a fictional store, both online and in person and need to discuss your findings. The data file itself isn't too hard, but the panel evaluating your presentation includes director and VP level people, about a dozen or so sitting in.

Confirmed questions1 question
  • Regarding the fictional company used in the case study, what is your primary recommendation and the reasoning behind it?

ID Analytics Interview Questions

Quoted word for word from ID Analytics interview reports.

What is the difference between an abstract class and an Interface?

Read report

Can you explain the difference between StringBuilder and String?

Read report

Can you devise a recursive algorithm for merging two lists of lists, specifically prepending the first element of each sublist in the second list to every sublist in the first?

Read report

What is the most efficient algorithm for finding a 5-10 digit string?

Read report

Could you explain the kNN (k nearest neighbor) algorithm and its complexity?

Read report

Formats, difficulty and experience

Across all 12 ID Analytics interview reports.

Interview formats

Technical 34.4%
Behavioral 31.2%
Coding 18.8%
Presentation 12.5%
Case 3.1%

Interview difficulty

Easy 16.7%
Average 41.7%
Difficult 41.7%

Candidate experience

Positive 54.5%
Neutral 36.4%
Negative 9.1%

Reports by job function

Engineering 6
Analytics 5
Operations 1