Crunchbase logo

Crunchbase Interview Questions
& Process

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

Based on 72 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
44.4% Positive experience

Which role are you interviewing for?

30 roles · 72 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Crunchbase.

Showing 4 of 72
Crunchbase logo
Crunchbase

Customer Success Manager

Sales · a year ago

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

It was a multi-step process over several weeks with different interview stages. I completed three rounds and was really looking forward to hearing back, but unfortunately, I never did. Each interview was eye-opening, and I really liked the company and its vibe. The people I met were super into their jobs, making me want to join even more. It seemed like they were all about new ideas and helping employees grow, which is important to me. It felt like a fantastic chance for development, both personally and career-wise. Even though there was no follow-up, I'm still hoping to work with them someday.

Confirmed questions1 question
  • Can you describe your current cross-functional collaboration with other internal departments?
Crunchbase logo
Crunchbase

MLOps Engineer

Engineering · more than a year ago

Staff Easy Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding Technical

The interview process felt like another LeetCode grind, which I usually skip, but I did this one for fun since the pay was decent. I got close on both my solutions but ran out of time. They gave me two LeetCode medium problems, one in Python and one in a specific Postgres SQL variant, not standard SQL. Each problem only had about 15 minutes, which is wild. Honestly, it felt like they either don't know what they're doing or are intentionally messing with the hiring process, maybe due to recent layoffs.

Confirmed questions2 questions
  • Questions about Python
  • Questions about SQL
Crunchbase logo
Crunchbase

Product Manager

Product · more than a year ago

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

So first I had a chat with the recruiter, just to get the basics about the company and the role, and they asked about my background as it relates to the job. Then came a take-home assignment that was about a past product I managed, which was cool because it wasn't one of those super long, vague PM take-homes that take forever. This one was more realistic, maybe 3-4 hours. After they looked at that, I talked to the hiring manager for about 30 minutes. We went deeper into the role, my experience, and Product at CB overall, plus their strategy and growth. The next part was a series of chats with people I'd work with from other teams, all 30 minutes each with different leads. Everyone was on time, nice, and kept it interesting. The recruiter actually did a great job setting me up with info beforehand so I knew what to expect for those.

Confirmed questions3 questions
  • Can you describe how you collaborate with different teams to make sure your product is successful?
  • Tell me about a past product experience you were in charge of as a PM.
  • What are your thoughts on the company's strategy and growth plan?
Crunchbase logo
Crunchbase

Sales Development Representative

Sales · more than a year ago

Entry Average Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Phone screen Technical screen Group
Interview formats
Behavioral Technical Case Presentation

So, first, my resume got screened out with over 200 applicants, but I managed to connect with the recruiter and the SDR lead, which got me a phone screening. Then, they had me write out a sales cadence on how I'd reach out to a prospect. I got positive feedback on that and was told the next step was to chat with the Senior SDR Lead. The interview with him involved going over my accomplishments, KPIs, and tech stack, and I had to answer two STAR questions. I finished by asking if he had any reservations about me, and he said no, even suggesting I was qualified for their senior SDR team. We then set up a next step to meet the team, and I felt the interview went really well. I followed up on LinkedIn since I didn't get his email, making it personal while waiting for the recruiter to send his professional contact. Later, I got a generic email saying they needed a more experienced Enterprise/senior SDR, which totally came out of nowhere, especially since the Senior SDR Lead himself hinted I was a good fit for a senior role and that it was remote. Honestly, sales leaders should be more transparent during interviews. I checked his LinkedIn, and wasn't impressed that he only hit 91% of his pipeline quota, while I'm hitting 110% of mine. Talk to me when you're hitting 120%-130% and have your own territory.

Confirmed questions2 questions
  • Could you share an instance where you experienced failure and subsequently rectified a situation?
  • Describe a time you failed and how you fixed it.

Crunchbase Interview Questions

Quoted word for word from Crunchbase interview reports.

Can you write Python code to flatten a nested JSON object that includes different data types like basic values, lists, and dictionaries?

Read reports

Can you explain the criteria for selecting news headlines?

Read reports

Can you solve a problem similar to the Valid Parentheses problem?

Read reports

What KPIs or success metrics would you use to measure this?

Read report

Could you write an article of approximately 500 words or more that explains how to write the ideal sales email, specifically highlighting how Crunchbase can enhance the sales outreach process? Additionally, please create a content calendar that includes social media copy for promoting this article across Crunchbase's LinkedIn, Twitter, and Instagram profiles. Finally, include your planning notes (such as an outline, research, and sources) below your final draft to offer reviewers insight into your thought process.

Read report

What are your thoughts on the company's strategy and growth plan?

Read report

Based on the SWOT analysis, what is your recommended feature or product roadmap?

Read report

Formats, difficulty and experience

Across all 72 Crunchbase interview reports.

Interview formats

Behavioral 42.3%
Technical 24.4%
Presentation 10.9%
Coding 10.3%
Other 7.1%

Interview difficulty

Easy 23.6%
Average 59.7%
Difficult 16.7%

Candidate experience

Positive 44.4%
Negative 37.5%
Neutral 18.1%

Reports by job function

Sales 26
Engineering 15
HR 10
Analytics 7
Marketing 7
Product 3