Impact Analytics logo

Impact Analytics Software Engineer Interview Questions
& Process

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

Based on 22 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

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

Showing 3 of 22
Impact Analytics logo
Impact Analytics

Software Engineer Intern

Engineering · nearly a year ago

Intern Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The interview started with an HR screening to check my background and how I communicate. Then, I had a technical round focusing on core concepts, my projects, and problem-solving skills. The last round was a mix of technical and managerial discussion where they wanted to know how I'd handle real-world situations, teamwork, and my responsibilities. It all went pretty smoothly.

Confirmed questions1 question
  • Can you explain what Redux is and describe the process of state management in a large-scale application?
Impact Analytics logo
Impact Analytics

Software Engineer

Engineering · more than a year ago

Entry Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

The interview was really helpful and gave me good insights. It made things clearer about what they're looking for and boosted my confidence and readiness. I'm keen to use what I learned and am looking forward to what comes next.

Confirmed questions4 questions
  • The interview provided valuable insights and was highly beneficial.
  • It clarified key concepts and expectations, enhancing my confidence and preparedness.
  • I'm eager to apply the knowledge gained.
Impact Analytics logo
Impact Analytics

Senior Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Take home Technical screen Phone screen
Interview formats
Coding Technical Behavioral

So I usually don't post about interviews, but this one was super bad, like exceptionally horrible. I've done over 100 interviews and gotten tons of rejections, but this experience needs a special mention. They typically have 6-7 interview rounds, and they really don't care about your time. Plus, they're super rude and disrespectful. For this role, I had two interview rounds: one was a problem-solving DSA round, and the other was about concepts and projects. There was also a take-home assignment, which was just a simple DP problem. The second round, the one with projects and concepts, had to be rescheduled because the interviewer couldn't make it. I had to wait in the meeting room for about 15-20 minutes with zero heads-up from HR, and HR was totally unreachable. It eventually got rescheduled for the next day. When I started explaining my projects during that round, the interviewer kept cutting me off every 5 seconds, which was incredibly annoying and frustrating. He had this dismissive attitude and seemed more interested in shaming me for not knowing or having worked on certain things. He kept saying stuff like 'how come you don't know this?' or 'you're saying big words' whenever I mentioned any cloud tech. Even though I stayed polite and professional, this guy was a complete jerk and just kept humiliating me the whole time. I honestly feel bad for the poor folks working under him. Hope they have the strength to deal with him. It really says a lot about the company culture and how they treat their people. Definitely watch out for companies like this. Oh, and this isn't my first time interviewing with them. I applied for the same role about 9-10 months ago. They set up rounds without ever discussing salary expectations. After the first round and doing their assignment, when they wanted to schedule the next round, I pushed them to discuss expectations first. They couldn't even match my salary back then, so I backed out. Seems like they have a thing for wasting people's time. Seriously, the arrogance! Scheduling technical rounds without even having basic talks about salary and experience, like candidates don't matter at all. Honestly, avoid these toxic workplaces.

Confirmed questions5 questions
  • What's the solution to the Angry Cows problem?
  • Can you explain some cloud-related concepts?
  • Tell me about Python concepts.

Impact Analytics Software Engineer Interview Questions

Quoted word for word from Impact Analytics interview reports.

What is the difference between the `let` and `const` keywords in JavaScript?

Read reports

Given the object `var object = { name: 'John', details: { id: 308, address: { city: ['Bangalore'] } } }`, what is the expected output array?

Read reports

What's the difference between synchronous and asynchronous execution in Python?

Read report

Explain the difference between deep copy and shallow copy.

Read report

How would you mathematically derive the time complexity of an algorithm?

Read report

How would you ensure a Python program utilizes all available physical CPU cores?

Read report

Formats, difficulty and experience

Across all 22 Impact Analytics interview reports.

Interview formats

Technical 33.3%
Coding 30%
Behavioral 28.3%
System Design 8.3%

Interview difficulty

Easy 9.1%
Average 77.3%
Difficult 13.6%

Candidate experience

Neutral 27.3%
Negative 22.7%
Positive 50%