I applied through a recruiter. The process took 2 months. I interviewed at Playlist in Jul 2025
Interview
I had a very disappointing experience with Playlist’s hiring process.
Over the course of nearly two months, I went through six separate interviews, each lasting around one hour. I invested a significant amount of time and effort into the process, prepared thoroughly for every stage, and maintained consistent communication throughout.
However, after all of that, I never received any final feedback or closure. Since August of last year, I have had no response whatsoever from the company.
I understand that hiring priorities can change, positions can close, and candidates may not always be selected — that is completely normal. What is not acceptable is putting candidates through an extensive and time-consuming interview process and then simply disappearing without any follow-up.
A simple update, rejection email, or acknowledgment would have demonstrated basic professionalism and respect for the candidate’s time.
Unfortunately, this experience left me with the impression that the company’s recruitment process lacks organization, transparency, and consideration for candidates.
I applied online. I interviewed at Playlist (Bengaluru) in Jul 2025
Interview
Round 1 – Hiring Manager Screen
General technical discussion covering backend fundamentals: benefits and use cases of Kafka, microservices architecture, CAP theorem, and some high‑level questions around my past experience.
Round 2 – DSA (Codility)
Data structures and algorithms round on Codility: implement the classic “Count Number of Islands” problem using graph/DFS/BFS techniques.
Round 3 – Low-Level Design (Codility)
LLD exercise on Codility: design a Parking Lot system, including entities, relationships, and core operations like parking, un‑parking, slot allocation, and capacity handling.
Round 4 – Technical Design Document Review (Codility)
Given a design document for a ProductCatalogService in an e‑commerce application where users were complaining about slow image load times. The task was to review the existing design, which already introduced a CDN, and propose further performance optimizations (caching strategy, image formats, pre‑processing, etc.).
Round 5 – Code Review (Codility)
Code review exercise for an OrderMessageProcessor. I had to identify issues and suggest optimizations around readability, performance, error handling, and edge cases.
Round 6 – Cultural Fit with VP
Behavioral round focused on cultural fit:
Discussed one project I am particularly proud of.
Deep dive into my recent project and impact.
“Why Mindbody?” and “Why should Mindbody hire you given that the tech stack is new for you?” – assessing learning mindset, adaptability, and motivation.
The Process:
- 8 total interview rounds: initial screening, technical test, interview with engineering manager, and panel interviews
- Process took 2 months from start to finish
- Very time-intensive with significant preparation required for each stage
The Good:
- Recruiter was responsive and communicative throughout the process
- Interview process was well-organized with clear timelines initially
- Team seemed engaged during interviews
Areas for Improvement:
- After 8 interview rounds and extensive candidate time investment, no specific feedback was provided in the rejection
- This felt inconsistent with the transparent communication style established earlier in the process
- Company policy apparently prevents detailed feedback, which makes it difficult for candidates to understand how to improve after such a substantial commitment
Interview questions [1]
Question 1
Fix the bugs in a DFS algorithm
Perform a code review
Review a technical document
Design a parking lot system