Orum logo

Orum Interview Questions
& Process

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

Based on 65 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
76.9% Positive experience

Which role are you interviewing for?

18 roles · 65 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Orum.

Showing 4 of 65
Orum logo
Orum

Account Executive

Sales · more than a year ago

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

I was contacted by Orum’s recruiting team regarding a fully remote Enterprise Account Executive position. The interview process involved an initial screening call, followed by two meetings with the Director of Sales, and then a meeting with the VP of Sales. The final stage was a mock interview with the CEO. Throughout this entire process, I had confirmed that the role was fully remote. However, after completing all stages, the recruiter informed me that the hiring team was now looking for candidates based in either NY or SF. If this is indeed the situation, I feel it was misleading and unfair to reach out for a remote position and then change the requirements at the very end. I also never received direct feedback from the sales team, which was quite disappointing. I would not recommend this experience.

Confirmed questions1 question
  • Describe a professional challenge you faced and how you successfully navigated it.
Orum logo
Orum

Software Engineer

Engineering · more than a year ago

Senior Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

The interview process generally followed the standard steps for software engineering roles. The initial recruiter call was more in-depth than usual, but it was essentially a discussion about my past work. The assessments and technical rounds weren't focused on LeetCode-style problems but were more practical and collaborative. They were challenging due to their unique nature but better than abstract brain teasers. The whole process wrapped up in under two weeks because we were trying to work around holiday schedules and needed to finish quickly.

Confirmed questions5 questions
  • What is your experience with our specific stack, and Node.js in particular?
  • Can you share an example of dealing with competing priorities?
  • How do you approach situations with a high degree of ambiguity?
Orum logo
Orum

Product Manager

Product · more than a year ago

Mid Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Take home Presentation
Interview formats
Behavioral Presentation

So there was a 30 minute phone screen, then a 1 hour HR manager screen, followed by a 1 hour screen with the hiring manager who's also a product lead. After that, there was a 1 hour panel interview with a current PM and an Engineer. The final stage was a take home assignment, which was really practical and focused on the core product. Instead of a hypothetical exercise, it asked to solve real user problems with solutions within the product itself. This was great for learning the product and customers while showing off my problem-solving and product skills. The assignment was time-intensive and challenging, but I had two weeks and could get a planning session beforehand. The HR team at Orum was super responsive with feedback and updates throughout.

Confirmed questions3 questions
  • What is your general approach to product management?
  • Can you share an instance where you had to make a difficult prioritization or tradeoff decision?
  • Describe a product or feature that you consider your proudest achievement.
Orum logo
Orum

Customer Success Manager

Sales · more than a year ago

Mid Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Presentation

This was one of the most refreshing interview processes I've gone through. I completed all four interviews in about a week. Every single one was a Zoom meeting, which I actually really enjoyed. It's nice being able to interview with someone "face to face." The process felt very well-structured, and many parts felt more conversational than super serious or intimidating, which is how many interviews can feel. Because of that, I felt more relaxed during the process. I had been through dozens of interviews over the prior nine months and would honestly say this was probably my favorite.

Confirmed questions3 questions
  • What unique contributions can you make?
  • How do your previous experiences align with the requirements of this role?
  • Based on your understanding, what attracts you to our company?

Orum Interview Questions

Quoted word for word from Orum interview reports.

Could you explain the Node.js event loop and its concurrency model?

Read reports

Hypothetically, if you were to be an animal, which one would you choose to be and why?

Read report

What's your spirit animal and what's the reason behind it?

Read report

Can you explain how to join multiple tables and then sort the results?

Read report

Formats, difficulty and experience

Across all 65 Orum interview reports.

Interview formats

Behavioral 43.1%
Technical 27.7%
Presentation 13.9%
Coding 5.8%
Other 5.1%

Interview difficulty

Easy 10.8%
Average 61.5%
Difficult 27.7%

Candidate experience

Positive 76.9%
Neutral 7.7%
Negative 15.4%

Reports by job function

Sales 29
Engineering 17
Operations 7
HR 5
Design 2
Marketing 2