Petuum logo

Petuum Software Engineer Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

1.9 Rounds average
Average Typical difficulty
8.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Petuum.

Showing 3 of 12
Petuum logo
Petuum

Software Engineer, Backend

Engineering · more than a year ago

Mid Average Positive experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Coding Behavioral

The interview involved a technical problem about network transfer speeds for large data amounts (copying 100 GB at 1 GB/s). It also covered C++ knowledge, API experience, and some behavior questions.

Confirmed questions3 questions
  • Can you explain move semantics in C++?
  • What is the purpose and usage of unique_ptr?
  • How does shared_ptr work and when would you use it?
Petuum logo
Petuum

Software Engineer

Engineering

Mid Average Negative experience No offer 3 rounds
Interview process
Take home Phone screen Onsite
Interview formats
Coding Technical

Worst experience ever. Passed the coding challenge and phone interview. The recruiter requested an onsite interview. I sent my schedule over. 3 weeks after, I was told they would not move forward with me. The recruiter never replied my emails. I had other interviews in the same period, and it was really hard for me to manage my schedule since they NEVER replied my email. I guess they prefer local candidates. If they find local fits, they would cancel your interview. To me, the company seems to be too cheap. I know pay is low. I like what Dr. Xing does, and this is the only reason I applied for Petuum. However, very disappointed. Will never consider the company. Eric is a good researcher, but definitely not a good CEO.

Confirmed questions1 question
  • Questions about algorithms and data structures
Petuum logo
Petuum

Software Engineer

Engineering

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Coding Technical

The interview process was very unprofessional and disorganized. It took a very long time to hear back after the initial email. I could tell early on that it wouldn't work out for either side, but that doesn't excuse the lack of professionalism. A friend recommended not applying here because they had a similar experience, but I applied anyway.

Confirmed questions1 question
  • Were you asked standard "google"-like coding questions, maybe on the easier side?

Petuum Software Engineer Interview Questions

Quoted word for word from Petuum interview reports.

Could you write the K-means clustering algorithm for a given matrix of [document, features] in a LeetCode style?

Read reports

Can you explain the implementation details of Deep Learning, specifically dimension computation and their functionality?

Read report

What are your thoughts on overfitting in Machine Learning?

Read report

Can you implement the 'add two numbers' problem from LeetCode?

Read report

Tell me about the implementation details and theory behind Deep Learning.

Read report

Formats, difficulty and experience

Across all 12 Petuum interview reports.

Interview formats

Coding 40%
Technical 32%
Behavioral 24%
System Design 4%

Interview difficulty

Easy 8.3%
Average 83.3%
Difficult 8.3%

Candidate experience

Positive 8.3%
Negative 41.7%
Neutral 50%