PredictSpring logo

PredictSpring Interview Questions
& Process

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

Based on 18 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
50% Positive experience

Which role are you interviewing for?

9 roles · 18 reports

Candidate interview experiences

First-hand accounts from people who interviewed at PredictSpring.

Showing 4 of 18
PredictSpring logo
PredictSpring

Customer Success

Sales · more than a year ago

Mid Average Neutral experience Decline offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical

The whole thing took forever with a bunch of rounds that felt like they were just repeating stuff. I guess they do that to make you really commit, so you'll just take whatever they offer at the end of all that. Honestly, it's not a super professional company, and a lot of other people have said the same. They don't seem to take responsibility for decisions, the job isn't what they post online, the pay is bad compared to the market, and you get different answers from different people during the interviews. Their business is small, and there's not much room to grow. Definitely a lot of red flags, so make sure you ask about the role, pay, location, and what success looks like right at the start (first round) to save yourself some trouble later.

Confirmed questions3 questions
  • How do you manage customer success?
  • How do you manage revenue?
  • How do you manage profitability?
PredictSpring logo
PredictSpring

Android Software Engineer

Engineering

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call Phone screen
Interview formats
Technical Behavioral

The interview process was unclear and disappointing. I received an email from an engineer to have a video call and discuss the role. The interview lasted longer than expected, which I took as a good sign. The interviewer said I'd hear back in two days, but it's been a week and after two emails, I still haven't received a response. While the interview itself was good and the people seem smart, they need to improve their recruiting process if they plan to hire more people. I thought it would be a good experience, but it seems other reviews were accurate. Don't apply if you don't want to waste your time. I'm not sure why they waste their time unless they're not busy.

Confirmed questions1 question
  • Can you tell me about Android basics and your project details?
PredictSpring logo
PredictSpring

Visual Designer

Design

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Onsite Offer
Interview formats
Behavioral Presentation

I applied and then I interviewed with the CEO. It was about an hour long, and he was a really great guy. He talked about what they expect from the role, the company culture, and went over my resume, portfolio, and past work. After that, he said I could move on to the next step, which was an onsite project with the team. I spent an afternoon doing the project and then the team reviewed it. It was a good experience because I got to meet everyone and learn more about the product. A few days later, they called me with the results. The whole thing was pretty straightforward and a good interview experience.

Confirmed questions1 question
  • What draws you to PredictSpring?
PredictSpring logo
PredictSpring

Customer Success Manager

Sales

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Presentation Offer
Interview formats
Technical Presentation Case

The whole process took 2 months, which is a long time. This startup seems to lack direction and has many red flags, evident in their interview process. The first round was with a senior manager, followed by a technical assessment. The third round involved meeting a director, and the fourth round was with the CEO. The final stage required creating a case study. The CEO round was particularly unorganized; they didn't mention it would be technical, and the CEO seemed unsure about the role and the company's direction. The case study, which took five days to complete, was ultimately not presented because they had already chosen someone else. They also criticized the system architecture slide, implying an expectation of deep infrastructure knowledge, which is unreasonable. While it offered some practice, the process is lengthy and often misleading, leading to a significant time investment with no guaranteed outcome. Based on my experience and others', it's likely to waste your time.

Confirmed questions1 question
  • Were there any API oriented questions that might be challenging if not prepared?

PredictSpring Interview Questions

Quoted word for word from PredictSpring interview reports.

Can you explain the difference between a Map and an ArrayList?

Read reports

Design and implement an entire E-Commerce Checkout API server

Read reports

What is the maximum number of customer accounts I can manage?

Read reports

Formats, difficulty and experience

Across all 18 PredictSpring interview reports.

Interview formats

Behavioral 31%
Technical 31%
Presentation 19%
Coding 9.5%
Case 4.8%

Interview difficulty

Easy 5.6%
Average 77.8%
Difficult 16.7%

Candidate experience

Positive 50%
Negative 38.9%
Neutral 11.1%

Reports by job function

Engineering 7
Sales 4
Operations 3
Design 2
Other 1
Product 1