Qubole logo

Qubole Interview Questions
& Process

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

Based on 47 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
55.3% Positive experience

Which role are you interviewing for?

16 roles · 47 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Qubole.

Showing 4 of 47
Qubole logo
Qubole

Sales Director

Sales · more than a year ago

Director Average Positive experience Accept offer 7 rounds
Interview process
Recruiter call Phone screen Presentation Onsite Offer
Interview formats
Behavioral Technical Presentation Other

The interview process spanned 3 weeks and had 7 rounds in total. It started with a quick HR screen, then a chat with the hiring manager. There were a few more chats with the hiring manager to check for specific traits using some mock exercises. After getting the green light from the hiring manager, I had several onsite rounds where I met most of the team I'd be working with. This was a good chance to see if I'd fit in. They were looking for specific qualities like how quickly I could learn and how responsive I am. Everyone was really supportive and seemed genuinely invested in my success, making for a great experience overall.

Confirmed questions5 questions
  • Can you describe your previous sales experience?
  • What is the largest deal you have closed?
  • What is the biggest deal you have lost?
Qubole logo
Qubole

Software Engineer

Engineering

Mid Difficult Negative experience No offer 1 round
Interview process
Phone screen
Interview formats
Coding Technical

The usual scheduling stuff happened. Then, during the phone interview, the interviewer was nice and calm. They even went over the time limit waiting for me to finish the problem. But their expectations are way too high. It's unreasonable to expect a candidate to solve both a Leetcode medium and a hard problem in just 45 minutes. The questions were also designed in a way that providing hints would be almost impossible to answer unless you've already solved the exact problem on Leetcode. If you can solve a Leetcode medium and hard problem in 45 minutes on a phone call without having seen it before, you should be interviewing at top companies like Google or Facebook. I really think they need to adjust their expectations.

Confirmed questions1 question
  • A Leetcode medium and hard problem with a high number of dislikes.
Qubole logo
Qubole

QA Engineer

Engineering

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Phone screen Technical screen Presentation Background check
Interview formats
Technical Coding Presentation

Got an email from the recruiter on Feb 20th. Replied expressing interest, and a week later got a Hackerrank test. They mentioned they're hiring fast. I finished and submitted the test the next day. No response for 3 days, so I emailed. 7 days after that, they said they'd check feedback. Turns out the role was filled. 20 days later, the same recruiter emailed again asking if I was still interested. I said yes, but heard nothing. 75 days later, another email from the same recruiter. Again, I said yes. Then I had a ~60 min Zoom call (Round -1) with a tech person, which felt good. Got feedback within an hour saying they're hiring aggressively and want to move fast. Another ~60 min Zoom call with a different tech person, also felt great. The next day, they asked for another Zoom call with someone else before the on-site. This felt like progress. The first two calls were about problem-solving. The third call focused on my current project's architecture and test frameworks, lasting ~80-85 mins. Felt good about it. That same day, the recruiter emailed saying they decided not to move forward. I asked for reasons, given how well discussions went, but got no response. I'm unsure if they hired someone local or if I wasn't a fit. The recruiters are unclear about the process. It seems offers can be rescinded for local candidates or those with lower salary expectations. My advice: take this seriously. Bad reviews are piling up. Be transparent with candidates, give reasons for rejection (profile mismatch, performance, or hiring someone else), and respect their time.

Confirmed questions1 question
  • Design a backend test framework for a given product architecture.
Qubole logo
Qubole

Security Engineer

Engineering

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check
Interview formats
Coding Technical Behavioral

I was first contacted by a recruiter and the whole thing took about a month. It started with two phone calls with HR, just talking about the role and my background. Then, I had to complete an online challenge which involved coding, shell scripting, and some logic problems. Once I passed that, they invited me to the company for an on-site interview. I heard back about the results about a week later.

Confirmed questions5 questions
  • Can you tell me about your resume?
  • What do you know about securing cloud infrastructure?
  • How do you secure docker containers?

Qubole Interview Questions

Quoted word for word from Qubole interview reports.

What is the fuzzy score for two strings based on matching characters?

Read reports

What's the approach for finding the maximum matching parenthesis in a string?

Read reports

What is the next lexicographical sequence after a given sequence?

Read report

What algorithm does Python use for sorting, and could you explain how it functions?

Read report

Can you write Python code to handle two character streams, one adding to the front and the other to the back, and determine if the formed word or subset is a valid English word, printing "Yes" or "No" accordingly? Previously found words shouldn't be counted.

Read report

Formats, difficulty and experience

Across all 47 Qubole interview reports.

Interview formats

Technical 32.8%
Behavioral 26.1%
Coding 25.2%
Presentation 6.7%
System Design 6.7%

Interview difficulty

Easy 12.8%
Average 70.2%
Difficult 17%

Candidate experience

Neutral 14.9%
Positive 55.3%
Negative 29.8%

Reports by job function

Engineering 34
Sales 7
Marketing 2
Other 1
Analytics 1
HR 1