InfoObjects logo

InfoObjects Interview Questions
& Process

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

Based on 47 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
70.2% Positive experience

Which role are you interviewing for?

11 roles · 47 reports

Candidate interview experiences

First-hand accounts from people who interviewed at InfoObjects.

Showing 4 of 47
InfoObjects logo
InfoObjects

Fullstack Developer

Engineering · a year ago

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

The interview process was well-organized. The technical questions and problem-solving tasks were relevant and challenging. However, I got rejected despite answering all questions and solving the problems. The feedback was unclear and the evaluation criteria seemed misaligned with the selection process. Management should consider providing detailed feedback.

Confirmed questions4 questions
  • Can you explain the Virtual DOM concept?
  • How can the Virtual DOM be optimized?
  • Describe the use of useMemo.
InfoObjects logo
InfoObjects

Business Development Head

Sales · a year ago

Executive Average Negative experience No offer 2 rounds
Interview process
Recruiter call Presentation Offer
Interview formats
Behavioral Presentation

They reached out to me first with a PDF that has job description. I said I'm interested and had the first meeting with the HR. He explained me what's expected, asked about my background etc. and then we scheduled a meeting with the CEO. It was a 45 minutes, very nice experience. He explained to me everything about the company, was very clear about the expectations, goals and everything else. I asked my questions and he said I'd get the feedback if I'm selected and the next steps. After couple days, I got a message from the HR that said the CEO was very positive about my first interview. He enjoyed meeting me and is interested in taking next steps to find out if I'm the right man for the job. After that I couldn't get any feedback, when i asked HR about the situation, he told me the first interviews with the other candidates should finish first and some other similar stuff like that. After 24 days, I got a message from HR saying "At the moment the CEO is preparing an offer for another candidate. So to be transparent, it looks like he is moving on."

Confirmed questions1 question
  • Can you tell me about your background?
InfoObjects logo
InfoObjects

Software Engineer

Engineering · more than a year ago

Entry Difficult Positive experience No offer 5 rounds
Interview process
Take home Technical screen Recruiter call Phone screen Technical screen Technical screen
Interview formats
Technical Coding Behavioral

The interview was good. It involved questions from DBMS, mainly OOPs, and major questions from academic projects. The process had 5 rounds. First was an online assessment, followed by a written pen and paper test. If shortlisted, there were 3 rounds of interviews. The first was basic, testing knowledge of fundamental concepts and speaking confidence. The second was a technical interview focusing on projects and hard knowledge in computer science core subjects. The third round was even harder, related to the specific field, with extensive questions about APIs.

Confirmed questions1 question
  • Could you explain the principles of Object-Oriented Programming and the distinction between abstraction and interfaces?
InfoObjects logo
InfoObjects

Data Scientist

Analytics · more than a year ago

Mid Difficult Positive experience Accept offer 4 rounds
Interview process
Technical screen Group Technical screen Technical screen
Interview formats
Coding Group Technical Coding

It's a 4-round process. First is a coding test, problems are easy-medium, with an hour time limit. You need to solve any 2 out of 3 questions. Then there's a GD, which is an elimination round. You'll need to discuss a given topic. The trick to clear is to grab chances to speak. After that, there are two technical interviews. For these, prepare at least one project. There will be two coding problems. Try to interact with the interviewer and be confident. Ask questions whenever necessary.

Confirmed questions2 questions
  • Can you introduce yourself?
  • Solve the two-sum coding problem.

InfoObjects Interview Questions

Quoted word for word from InfoObjects interview reports.

What distinguishes the 'type keys' command from the 'type' command?

Read reports

What is the difference between Spring and Spring Boot?

Read report

Given a customer object with a 'name' attribute, how would you identify customers with duplicate names at least once using Java streams?

Read report

Formats, difficulty and experience

Across all 47 InfoObjects interview reports.

Interview formats

Technical 43.3%
Coding 30.8%
Behavioral 17.5%
Group 7.5%
Presentation 0.8%

Interview difficulty

Easy 17%
Average 63.8%
Difficult 19.1%

Candidate experience

Positive 70.2%
Negative 14.9%
Neutral 14.9%

Reports by job function

Engineering 40
Analytics 4
Sales 1
Other 1
HR 1