
Yubi Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 60 interview experiences · FREE TO READ
Which role are you interviewing for?
20 roles · 60 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Yubi.
Engineering Manager
The interview process felt overly lengthy and procedural, with a mechanical approach that lacked agility and offered little in terms of meaningful insights or engagement. It was a bit too long and by the book, not very flexible and didn't really give much useful info or feel engaging.
- Questions about coding and data structures
- Questions on fundamental engineering management
Software Engineer
There were 4 rounds in total. The first two were technical rounds, which were quite straightforward. The first technical round focused on DSA, Java, and Spring Boot. The second technical round covered HLD, LLD, and some puzzles, although the interviewer wasn't very clear. Then, there was a Hiring Manager round which was more of an informal chat and went well. The last round was with HR, which felt odd because they seemed to think I was laid off and decided not to move forward. It felt like a way to reject me because of salary expectations. I was looking for a 35% raise, but they were only offering up to 20%. After that call, they just ghosted me. The recruiter didn't answer my calls or emails, which was unprofessional, especially after asking for my salary slips, PAN card, and appraisal letter.
- Design of an IPL Ticketing System, along with DSA Questions, and discussion about your Projects.
Software Engineer
The first round was a technical interview focusing on Data Structures and Algorithms. They also asked a lot about databases, and a couple of questions on Java Spring Boot. One question was about why you'd pick Java over C++.
- Can you explain normalization in detail with an example?
- What is the Spring Boot @Configuration annotation?
- Solve this server nodes coding question.
Director QA
I reached out to the recruiter on LinkedIn for the Director QA role since my profile was a good match. The recruiter asked for my details via email and said they'd set up a call with the hiring manager in a few days. When I didn't hear back after those days, I followed up, but got no response. I waited a few more days and followed up again because I was really interested, and the recruiter curtly replied that they needed until the next day EOD. I never heard back from them, even after two weeks. So, I eventually emailed the recruiter to say I assumed my profile wasn't selected since I hadn't heard back in two weeks, thanked them for their time, and ended the conversation. I found the lack of professionalism concerning, especially since it was a direct message for a senior role. If this is how they treat senior candidates, I don't think it reflects well on the company culture.
No confirmed questions were included in this interview report.
Yubi Interview Questions
Quoted word for word from Yubi interview reports.
“Find the count of triplets that sum up to a given range.”
Read reports →“Find a pair in an array that sums up to a given number.”
Read reports →“Can you find strings from a list that can be formed using random letters from another input string?”
Read reports →“Can you rearrange a given linked list?”
Read reports →“What is the difference between an interface and a class?”
Read report →“Could you design a generic LRU cache?”
Read report →“How would you design the database for an Instagram-like news feed?”
Read report →“Can you implement a Data-Table component in React?”
Read report →“Could you explain the concept of the Event Loop in JavaScript?”
Read report →Formats, difficulty and experience
Across all 60 Yubi interview reports.