Apollo.io | Frontend Engineer | Wastage of time, apply at your own risk!!

apollo.io logo
apollo.io
Frontend Engineer5 years
July 25, 20255 reads

Summary

I interviewed at Apollo.io for a Frontend Engineer role, which included live coding, app creation, debugging, and behavioral rounds. Despite feeling positive about my performance, I was rejected with the stated reason 'Lack of AI mindset', which I found to be an uncommunicated and frustrating excuse.

Full Experience

Interviewed at Apollo.io in July 2025. I have applied via referral. The whole process took 3 weeks. And it was a waste of time (read to know more).

Round 1: Live Coding Round on CODERBYTE

2 Simple JS based problem solving questions on string manipulation, pretty easy and doable with basic problem solving. Cleared the next round.

Round 2: App Creation Round

Need to set up an interview repo locally before the interview. Was asked to build a TodoMVC application in React,Javascript and CSS. You are free to use any external help except AI tools. Focus is on functionality first with a viewable styling. Was able to build it with all the functionalities required and decent styling. The interviewer was satisfied.

Round 3: Debugging Round

Was given a podcast player and list of 12 bugs which were there in code and needed to be fixed in order. The interviewer was helpful, I was able to get 10/12 in due time and the interviewer seemed satisfied with my approach. The application was in Redux which I wasn't familiar with, but managed to understand it, having knowledge of similar state management libraries.

Round 3: Behavioural Round

Was with a engineering manager who asked me about

Most challenging project? How do you manage a conflict with a team member? Why Apollo? What do you look for in a company before joining? Any time when you suggested some change and there was a resistance to it? How do you use AI in your current workflow? How much productivity improvement have you seen using AI? What are your thoughts on the future of AI in development?

I thought it went well. I touched upon all the aspects of what I have worked upon so far.

Verdict - REJECTED

Got a rejection mail after 1 week with the reason for rejection being "Lack of AI mindset" (yeah I am not making this up). I honestly don't know what they mean by that, because I clearly told in the Behavioral round how I am using to improve my productivity right now and willingness to adopt the AI ways of working at Apollo.io. If AI experience was such a must have, they should have told this beforehand, seems to me a made up excuse. So beware of this company and interview at your own risk.

YOE - 5, TC - 48LPA

Interview Questions (10)

Q1
Build TodoMVC Application
Other

Build a TodoMVC application using React, Javascript, and CSS. The focus is on functionality first, with decent styling. External help is allowed except for AI tools.

Q2
Debug Podcast Player Application
Other

Given a podcast player application, identify and fix a list of 12 bugs in order. The application was built using Redux.

Q3
Most Challenging Project
Behavioral

Describe your most challenging project.

Q4
Managing Conflict with Team Member
Behavioral

How do you manage a conflict with a team member?

Q5
Why Apollo.io?
Behavioral

Why are you interested in joining Apollo.io?

Q6
What do you look for in a company?
Behavioral

What do you look for in a company before joining?

Q7
Suggesting Change and Resistance
Behavioral

Describe a time when you suggested a change, and there was resistance to it?

Q8
Using AI in Current Workflow
Behavioral

How do you use AI in your current workflow?

Q9
Productivity Improvement with AI
Behavioral

How much productivity improvement have you seen using AI?

Q10
Future of AI in Development
Behavioral

What are your thoughts on the future of AI in development?

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!