Yapstone logo

Yapstone Software Engineer Interview Questions
& Process

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

Based on 21 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
47.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Yapstone.

Showing 3 of 21
Yapstone logo
Yapstone

Software Engineer

Engineering

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

I applied online and after a phone screen, I was invited for an onsite interview. I was kinda hesitant to take a day off for it because of the reviews I saw on glassdoor, they looked fake with tons of 1 and 5 stars but hardly any in between. I probably should have just skipped it. The onsite itself had 4 interviews, some were okay, others were pretty bad. The first one was a SQL design and query interview, which I think went fine. The second interviewer asked about random, obscure design patterns. I mentioned I knew and used singletons and MVC but couldn't name others off the top of my head. The third interview was the only one that felt like a real "problem solving" interview where I wrote code, and that went well. The last interviewer seemed lost and was using the same question sheet as the second guy. This sheet had basic questions on Java (like access modifiers) and SQL (like indexes). They gave me a rock as a thank you gift when I left, I was more excited about getting lunch after the whole ordeal.

Confirmed questions3 questions
  • Questions about Java, SQL, and design patterns
  • One coding challenge during the phone screen
  • One coding challenge during the onsite interview
Yapstone logo
Yapstone

Senior Software Engineer

Engineering

Senior Easy Negative experience No offer 3 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Coding

I cleared an online test and then got a call for a face-to-face interview. The first 3 rounds went well and I was feeling positive about it, but then I encountered an interviewer who seemed immature. They were very impatient, which was surprising given their position in top management. They asked very specific, bookish questions about obscure parts of Java that are not commonly used, expecting answers likely found online. I have extensive experience (9+ years) in e-commerce and order management, having worked with a leading OMS product. Although I don't have direct experience with payment systems, I understand their application in the order lifecycle. It would have made more sense not to shortlist me if they saw my resume. The interviewer lacked the maturity to see how my commerce background could offer insights for their payment system's product development, especially as they aim to enter the e-commerce and retail market. I was initially very interested in the company, but this experience changed my mind. After the interview, I did more research and found reviews mentioning that many hires in high positions came from Western Union, and I suspect this interviewer was one of them. It was amusing to read reviews calling some employees 'minions from Western Union'. I'm actually glad I didn't end up joining Yapstone, especially in such an environment. I believe it's crucial for interviewers to also 'sell' the company to the candidate, just as the candidate tries to impress the interviewer.

Confirmed questions3 questions
  • Can you explain how to do SSL Configuration using Java?
  • What's your approach to debugging a Java code that's stuck in a Deadlock?
  • Could you tell me what is Enumeration in Java?
Yapstone logo
Yapstone

Software Engineer

Engineering

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Technical screen Panel
Interview formats
Behavioral Technical

Applied through LinkedIn and got a recruiter call. Then had a phone interview. After that, I interviewed with the hiring manager in person. Then I had more interviews over two separate days with several people, including a product manager and a director. The early interviews covered my background, my grasp of the development lifecycle and Agile, and tested my technical knowledge in Java, SQL, and Linux. The later interviews were with more senior folks.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Yapstone Software Engineer Interview Questions

Quoted word for word from Yapstone interview reports.

How would you remove all elements from a linked list that are greater than a specified value?

Read reports

Given an array of integers, how can you find pairs whose difference matches a particular value?

Read reports

How would you find a duplicate number from a given set of numbers?

Read reports

How would you implement ajax calls so that they update a view in the order they were called?

Read report

Formats, difficulty and experience

Across all 21 Yapstone interview reports.

Interview formats

Technical 37.7%
Coding 30.2%
Behavioral 20.8%
System Design 9.4%
Presentation 1.9%

Interview difficulty

Easy 28.6%
Average 66.7%
Difficult 4.8%

Candidate experience

Negative 26.3%
Positive 47.4%
Neutral 26.3%