PredictSpring logo

PredictSpring Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at PredictSpring.

Showing 3 of 5
PredictSpring logo
PredictSpring

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Take home Presentation
Interview formats
Coding Technical

Had an interview with the VP of Engineering, followed by a 2-day assignment focused on Java and Apache Solr. They didn't provide proper input data or software for the task. Even though I completed the assignment and found bugs in the code with the latest versions, it felt like a waste of time. I'd advise against applying.

Confirmed questions3 questions
  • Can you tell me about SQL Apache Solr setup?
  • What about debugging configurations?
  • Are there any coding tasks involved?
PredictSpring logo
PredictSpring

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Presentation Offer
Interview formats
Technical Coding Behavioral Presentation

Applied online and had a 20-minute phone call with the Director of Engineering for a quick screen. He discussed company goals and job needs, and asked about my background and availability. This led to an on-site interview. During the on-site, I did a JS coding exercise, allowed to use any JS framework. The goal was to spend the day with engineers and get a feel for the company. I met senior engineers and we talked about the exercise. My code was reviewed at the end of the day, with discussions on improvements. The DOE then extended an offer. The day after the interview, I had a meeting with CEO Nitin to go over his expectations, company projects, work-life balance, and culture. It was a good interview overall.

Confirmed questions1 question
  • JS Coding Exercise
PredictSpring logo
PredictSpring

Software Engineer

Engineering

Staff Average Negative experience No offer 5 rounds
Interview process
Phone screen Take home Phone screen Phone screen Onsite
Interview formats
Technical Coding System Design

The entire process took over a month. After two phone screens, they gave me a take-home project to design and implement an API server, estimating 10-12 hours but realistically taking 20-30 hours. I completed it with docs and a working server. Then, they wanted me to talk to the CEO and VP of Engineering, which led to two more phone screens. Finally, they said they'd fly me to the Bay Area for the final round, but a week later, they canceled due to changes and said the position was unavailable. It felt like a waste of time as they seemed not to want to hire from the start.

Confirmed questions1 question
  • Design and implement an entire E-Commerce Checkout API server

PredictSpring Software Engineer 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

Could you build a web application that satisfies all the stated requirements?

Read report

Formats, difficulty and experience

Across all 5 PredictSpring interview reports.

Interview formats

Technical 46.2%
Coding 23.1%
Presentation 15.4%
Behavioral 7.7%
System Design 7.7%

Interview difficulty

Easy 0%
Average 100%
Difficult 0%

Candidate experience

Negative 60%
Positive 40%