I applied online. The process took 4 weeks. I interviewed at Orum.io in Oct 2023
Interview
Spoke with a recruiter and then a manager of some sort. The 2nd interview with a manager was not technical at all and felt like a complete waste of time. Was near identical to the recruiter interview. Was sent a github link to a challenge. (implement basic API). Was bored so I went above and beyond on this challenge... CI, docker, testing, etc... Got a generic rejection email. I wasted time on the challenge and never even spoke to someone technical lmao. Do not waste your time doing the technical take-home for Orum unless you have nothing better to do. See other reviews here who stated the same thing... Lastly, the interview process moved slow as molasses.
Interview questions [1]
Question 1
Talk with recruiter Talk with a manager Takehome basic API design
I applied online. The process took 3 weeks. I interviewed at Orum.io (New York, NY) in Aug 2023
Interview
A typical screening call first with their external headhunter. They were very slow and bad with follow-up. Next, I met with an Engineering leader for about an hour. He seemed nice enough. He didn't make much of an impression as far as his technical chops went. After meeting with the Eng leader, I did a take-home assessment for them. It was a relatively easy API design project where they provided me with an SQLite database and some silly barebones project scaffold. The project was meant to measure your SQL ability and API design experience. It was pointless; a call talking through a systems design would have made more sense. Follow the system design by writing some SQL together on a call, and it would have been enough. Don't bother with the assessment, though. Honestly, they aren't going to learn much from that little exercise and they drag their feet getting back to you. The recruiter tells you they WON'T BE PROVIDING FEEDBACK, which means they are either lazy or can't defend any decision they made. They have no respect for the candidate's time. Don't ask for an assessment if you don't want to provide feedback. It makes the "company" look unprofessional. Regardless, I'd suggest you pass on this company unless you're just starting your career as an engineer. There seems to be a ton of "leadership" and only a few ICs and the product doesn't have a clear direction.
Interview questions [1]
Question 1
Why do you want to work for them, and to do a silly API design project with either Go or Typescript and a little SQLite database.
There are 5 rounds of interviews total, 1 behavior 2 technical and 2 manager interview. One technical interview was a take home proj and the other was a work simulation. Both are take homes.