Prometheum logo

Prometheum Interview Questions
& Process

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

Based on 8 interview experiences · FREE TO READ

2.5 Rounds average
Easy Typical difficulty
62.5% Positive experience

Which role are you interviewing for?

6 roles · 8 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Prometheum.

Showing 4 of 8
Prometheum logo
Prometheum

Product Manager

Product · a year ago

Senior Easy Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Other

Got an email saying I was shortlisted and asked for my availability. I replied with some times, but then got a call the next day at an inconvenient time and missed it. I rescheduled with the recruiter, but they called me two hours early. They only asked two questions and then said they'd pass my resume along. It's been over a week with no response. The whole process felt disorganized.

Confirmed questions2 questions
  • Can you tell me why you are considering leaving your current company?
  • What are your salary expectations?
Prometheum logo
Prometheum

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Phone screen Technical screen Recruiter call
Interview formats
Technical Coding

Three technical rounds in total: a technical phone call, a technical round, and an HR round. Each took about 30 minutes. The technical questions were easy to average difficulty. The whole process, including onboarding, took 2 weeks and it was easy and fast.

Confirmed questions2 questions
  • Basic SQL questions
  • Python coding questions
Prometheum logo
Prometheum

Backend Engineer

Engineering

Entry Easy Positive experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Behavioral

The first stage was a recorded interview where I answered basic Node.js internal questions, like explaining the Event Loop, and the Observer pattern. The next round didn't go well, as the interviewer seemed to confuse me with someone else. He told the recruiter I knew little TypeScript, even though he never asked me about it. He also claimed I had mostly frontend experience, which is strange given my resume and our brief chat about starting in frontend. He said I had no relational database experience, but he only asked a yes/no question about it. I feel there was a disconnect between what he asked and what he reported. Despite not getting the job, I stand by my integrity, as evidenced by my contributions on Stack Overflow.

Confirmed questions4 questions
  • Can you describe the Event Loop?
  • Could you explain the Observer Pattern?
  • Have you worked with relational databases?
Prometheum logo
Prometheum

Executive Assistant

Operations

Executive Easy Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Other

Applied with no referral. Application was shortlisted, which apparently means they want to interview you. Had a first interview with the recruiter and Ben. They said they wanted a second interview, but didn't schedule it for a week. When I followed up, they disqualified me. That's how it goes with small startups I guess.

Confirmed questions3 questions
  • Why are you interested in Prometheum?
  • Describe how you would manage a chaotic individual.
  • What is your spirit animal?

Prometheum Interview Questions

Quoted word for word from Prometheum interview reports.

Formats, difficulty and experience

Across all 8 Prometheum interview reports.

Interview formats

Behavioral 41.2%
Technical 29.4%
Other 17.6%
Coding 5.9%
Case 5.9%

Interview difficulty

Easy 62.5%
Average 37.5%
Difficult 0%

Candidate experience

Negative 37.5%
Positive 62.5%

Reports by job function

Product 3
Engineering 3
Operations 1
HR 1