Treasure Data logo

Treasure Data Interview Questions
& Process

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

Based on 37 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
67.6% Positive experience

Which role are you interviewing for?

21 roles · 37 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Treasure Data.

Showing 4 of 37
Treasure Data logo
Treasure Data

Test Engineer

Engineering · a year ago

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

The interview process was pretty good. Mostly, they asked about my previous work experience. There were also some scenario-based and logical questions. It consisted of two main parts: a general discussion and a technical evaluation. They wanted to know about the automation tools I've used and my approach to code maintenance.

Confirmed questions5 questions
  • Can you tell me about your work experience?
  • What would you do in this specific scenario?
  • Can you answer some logical questions?
Treasure Data logo
Treasure Data

Staff Site Reliability Engineer

Engineering · more than a year ago

Staff Difficult Neutral experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen Technical screen
Interview formats
Behavioral Technical Coding

Went through a phone screening with a recruiter for 30 minutes, then spoke with the hiring manager for 30 minutes. After that, had a 45-minute behavioral questions session with some SREs, then a 45-minute systems questions session with SREs, and finally a 45-minute software(?) questions session with SREs. I'm sure there would have been more rounds but didn't progress. Each of these steps happened on different days. The first two felt like warm-ups, and the last three were the main part. It was unfortunate that the main parts were on different days and also not clear what focus each interview would have, even though I was told there would be systems, software, and behavior. Since the order wasn't known, it was a guessing game for those three days. The interview experience got progressively worse. I did like the talk with the hiring manager though, felt like they asked the right questions to see if I'd be a good fit. The behavioral questions stage was enjoyable too, felt genuine and made sense. The systems questions stage was okay. The software(?) questions stage felt a bit like an interrogation, just trying to confirm specific knowledge on certain protocols and concepts, and it felt like they were trying to find what I was missing rather than what I had. They said it was open-ended but it didn't feel that way too much.

Confirmed questions3 questions
  • Mostly about networking protocol related concepts, somewhat in-depth.
  • A few questions regarding SRE concepts.
  • A few questions regarding file handling (in terms of kernel and userspace using a programming language) and bash scripting.
Treasure Data logo
Treasure Data

Account Executive

Sales

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

Recruiter reached out on LinkedIn, and we had a first call with talent acquisition that went great. They set up a second interview with the hiring manager, which I thought was fantastic. He told me I was exactly what they were looking for and that I'd move to the next round after one last person. I started to worry when he didn't reply to my thank you email. After three emails and reaching out to the recruiter, they said I didn't align with the role. I'm shocked they haven't given me a clear answer and have been deceptive throughout the process. The recruiter offered to help me find other roles, but I don't see myself going through this again.

Confirmed questions2 questions
  • In which US state or region do you reside?
  • Can you describe your approach to prospecting and provide evidence of its success?
Treasure Data logo
Treasure Data

Customer Success Manager

Sales

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral

I got to the last stage of interviews and had a pretty good experience during the process. Most of my talks were with the director and head of the department, and they were both great, thoughtful, easy to talk to, and people I would have been excited to work with. The problem was the follow-up. After the final round, I never heard back from the recruiter. It's been over two months, so I'm guessing they didn't go forward, but not closing the loop after a final interview feels unprofessional and pretty disrespectful of a candidate's time. What made it more frustrating is that I was upfront early on that I didn't think my background was as technical as what they might be looking for. Even so, I was encouraged to continue through the process and made it all the way to the end. After that, getting completely ghosted by the recruiter was disappointing and left a bad impression of the overall experience.

Confirmed questions1 question
  • Can you answer an SQL question?

Treasure Data Interview Questions

Quoted word for word from Treasure Data interview reports.

Explain the differences between column-oriented and relational data stores.

Read reports

What's the difference between synchronous and asynchronous programming in Javascript, and how do you apply them?

Read reports

Would you rather complete all of your work or be completely accurate?

Read report

Formats, difficulty and experience

Across all 37 Treasure Data interview reports.

Interview formats

Behavioral 44.3%
Technical 30%
Coding 10%
Presentation 7.1%
System Design 2.9%

Interview difficulty

Easy 10.8%
Average 73%
Difficult 16.2%

Candidate experience

Neutral 10.8%
Positive 67.6%
Negative 21.6%

Reports by job function

Engineering 14
Sales 9
Design 5
HR 3
Marketing 3
Operations 1