
Scribd Inc. Data Scientist Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Scribd Inc..
Data Scientist
It was good, they asked python and sql coding questions. Also some basic questions about expected value and hypothesis testing. Many ML questions came up, some theory and some about a project I did. Overall it was a good and relaxed experience, seems like a cool place.
- What's the expected value of a dice roll?
- What's the expected value of a game where you can roll two dice?
Data Scientist
The interview process was pretty standard: I had a call with the hiring manager, then a call with a recruiter, followed by two technical phone screens. What wasn't standard was that every person I interacted with during the process was a white male – the recruiter, the hiring manager, two data scientists for the first tech screen, and two for the second tech screen. I thought this was weird, so I asked around in my network about the diversity on the Scribd data science team and found out it's like 95% white males. This is pretty unacceptable for a company of their size, especially since I think they have over 15 data scientists. I ended up taking another job because I'm a minority and I wouldn't want to work on a team with such little balance. The recruiter was nice, but he took forever to respond.
- Can you tell me about your background?
- What about Scribd interests you?
- SQL knowledge check.
Data Scientist
Scribd's hiring process needs a lot of work. Even though it only had 3 rounds, the whole thing took over 3 months from start to end. Every update was late by 2 weeks or more. Seriously, this was the first role I applied to in my latest job search and literally the last one to get back, by which point I'd already moved on. I found the questions very odd as well. Prior to my recruiter call I was asked to submit a written response to a bunch of behavioral questions, and then during the call the same questions were asked--so what's the point of the written response? For the technical call and on-site, many questions had nothing to do with data science; in fact, the interviewers themselves said the questions "do not reflect the work they actually do". So again, what is the point of asking these questions? It took them 4 weeks to get back to me about the on-site, and only after I sent them a follow-up email. The recruiter told me the position had been filled, except she named me the wrong position! Once I corrected her, she apologized for the confusion and said they were still sorting out my position, but I just withdrew my application. Honestly, after witnessing such unprofessionalism, if anything I felt like I had dodged a bullet.
- What makes you interested in Scribd?
- Can you perform string manipulation on DNA sequences?
- How would you reformat lists into a table and output to a txt or csv file?
Scribd Inc. Data Scientist Interview Questions
Quoted word for word from Scribd Inc. interview reports.
“Describe gradient descent.”
Read reports →“What is Bayes Theorem?”
Read reports →“What's the expected value of a dice roll?”
Read reports →“What's the expected value of a game where you can roll two dice?”
Read reports →“Can you perform string manipulation on DNA sequences?”
Read report →“How do Monte Carlo methods work?”
Read report →“How would you reformat lists into a table and output to a txt or csv file?”
Read report →“Can you explain conditional probability?”
Read report →“Do you have any general Python coding questions?”
Read report →Formats, difficulty and experience
Across all 7 Scribd Inc. interview reports.