Senior Software Engineer Interview Experience - Bengaluru, India
Process
Interviewers reached out to me. There was a screening round for half an hour with the recruiter. The first round was coding, and the next round was system design.
- Expression evaluation DSA question.
- Rejected in the system design round.
Questions
Design a system for a live comment section on YouTube. There was an in-depth discussion on all aspects of the design. It was a pretty intense round. They asked me to mail the final HLD, back-of-the-envelope calculations, and any assumptions I took.
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the Apollo.io Senior Software Engineer role in Bengaluru, Karnataka.
Success Rate
Apollo.io's interview process for their Senior Software Engineer roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Apollo.io's Senior Software Engineer interview process in Bengaluru, Karnataka.
Apollo.io Work Experiences
- 5.0Fast-paced Learning, Scalable ArchitectureSenior Software Engineer • Current EmployeeBengaluru, Karnataka, IndiaFebruary 18, 2025Pros: Great learning experience, good exposure on highly scalable architecture.Cons: It's a fast-paced environment; you should have the ability to learn quickly.
- 1.0Not a healthy place to workSenior Software Engineer • Current EmployeeBengaluru, Karnataka, IndiaJune 18, 2025Pros: No pros, some might say WFH.Cons: No WLB Negligible (2-3%) Hikes in Appraisals Mostly mundane maintenance work
- 2.0Great peers, bad work-life balanceSenior Software Engineer • Current EmployeeBengaluru, Karnataka, IndiaJune 25, 2025Pros: - Awesome peers with great qualities to learn from. - Good pay. - Interesting challenges to solve.Cons: Every other week, something new becomes a P0, tossing out all the work done till then. There's no clear path ahead for the product, and we're just trying to keep up with the competition. Work-life balance is quite bad, and any feedback to improve it is tossed out. The requirement of staying online from 8-11 PM for syncing up with other timezones doesn't make sense if the company is remote-first and trying to promote an async communications culture.
Apollo.io Interview Questions
