Crunchtime logo

Crunchtime Software Engineer Interview Questions
& Process

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

Based on 9 interview experiences · FREE TO READ

3.9 Rounds average
Average Typical difficulty
11.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Crunchtime.

Showing 3 of 9
Crunchtime logo
Crunchtime

Software Engineer

Engineering · a year ago

Senior Easy Negative experience No offer 7 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical Coding

So I was reached out to by a recruiter from CrunchTime who was super nice and walked me through their interview process. It sounded like quite a bit, 7 interviews in total. The first chat was with the hiring manager, and it was basically just a conversation, and I think it went pretty well. I got good vibes and positive feedback throughout. After that, I had a technical interview with two developers. They hit me with some standard coding questions. But then, the very next day, they told me they’d found someone who was a better fit and wouldn't be moving forward, which was a bummer after all the good feedback. Honestly, I can't really recommend interviewing with them. It seems like they might not be great at evaluating senior folks or maybe aren't upfront about their feedback.

Confirmed questions2 questions
  • Can you code a solution to identify a Palindrome?
  • Can you code a solution to get the first n Fibonacci numbers?
Crunchtime logo
Crunchtime

Software Engineer

Engineering · more than a year ago

Staff Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Behavioral Technical Coding

Started with a Zoom call with the recruiter, which was pretty standard. Then I had an interview with the hiring manager, who is a VP. This was more of a traditional HR-style Q&A, not really a deep conversation. The next part was a technical interview that was supposed to be an hour long, but I finished the coding exercises and questions in about 30 minutes. The interviewer seemed disengaged and not really into it. They asked me to code Fibonacci and Palindrome, along with some questions about time complexity. I think I did well on most of the questions. A few days later, the recruiter contacted me to let me know they weren't moving forward. My advice would be to have interviewers who are actually enthusiastic about conducting the technical interviews, rather than seeing it as a burden. Also, I find the 'write the Fibonacci sequence' type of question to be a bit old-fashioned and not the best way to evaluate candidates. The recruiter was really good about keeping me in the loop and providing updates, though, which was appreciated.

Confirmed questions1 question
  • What feedback would your current manager give about you?
Crunchtime logo
Crunchtime

Software Engineer

Engineering · more than a year ago

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

The hiring process took some time due to the new HR system, but overall it was a positive experience. It involved a couple of phone screening interviews, followed by an in-person interview where they reviewed my background and some technical skills, and everything went smoothly.

Confirmed questions1 question
  • Given a specific scenario or a new environment, describe how you would develop a solution.

Crunchtime Software Engineer Interview Questions

Quoted word for word from Crunchtime interview reports.

Can you code a solution to get the first n Fibonacci numbers?

Read reports

Can you explain the difference between an abstract class and an interface, and in what scenarios would you choose one over the other in Java?

Read reports

Can you describe a system design using event-driven architecture?

Read report

Formats, difficulty and experience

Across all 9 Crunchtime interview reports.

Interview formats

Behavioral 35%
Technical 30%
Coding 25%
System Design 10%

Interview difficulty

Easy 22.2%
Average 77.8%
Difficult 0%

Candidate experience

Negative 88.9%
Positive 11.1%