
Scribd Inc. Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 24 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Scribd Inc..
Software Engineer
I went through a few rounds of interviews, including chats with the hiring manager and some technical assessments like an architecture review. They gave me some prep materials beforehand, which was nice. I was upfront about my salary expectations, which matched what they advertised, and that's why I applied. Everyone seemed friendly, but also a bit unenthusiastic, like the job had drained them. After what I thought was the last interview, I didn't hear back as quickly as before, so I figured I wasn't getting an offer. I got an offer from another company, and then that same afternoon, Scribd reached out to schedule a call. They said they were still discussing an offer, and I let them know my timeline and the other offer I had. They said they couldn't match it because of my interview performance and location (which wasn't mentioned as affecting pay in the listing). The recruiter tried to convince me Scribd would be a better place to work, so I asked them to let me know their offer since I was still interested. After that, the recruiter ghosted me completely, with no rejection notice. Months later, she accidentally messaged me on LinkedIn about the same role.
- Can you discuss a project you were involved in?
Software Engineer
The hiring process was about a month long, with significant delays between stages and no communication. I was informed that the position was already filled after the process concluded. It started with a standard recruiter call, followed by a productive hiring manager call where we discussed my technical background. There was a two-week communication blackout, then I was contacted to schedule a technical round, apparently due to stakeholders being on vacation. The technical round involved coding, where I was asked four algorithm questions of varying difficulty. Two days after that, I received an email stating the role had been filled.
- Four algorithm problems, ranging from easy to hard, focused on arrays and maps.
Software Engineer
This was seriously the best interview process I've ever gone through. The recruiter was super quick with getting back to me and setting up the next steps. It started with a chat with the recruiter about the company, then a technical video call, and finally an onsite where I had a few technical interviews and a behavioral one.
- Did they ask you some standard algorithmic questions?
- Did they ask about projects you'd done?
- Did they ask some typical behavioral questions?
Scribd Inc. Software Engineer Interview Questions
Quoted word for word from Scribd Inc. interview reports.
“Write code to check if a string of parentheses is valid.”
Read reports →“How do you calculate the number of ways to climb n stairs if you can take 1, 2, or 3 steps at a time?”
Read reports →“Can you flip a linked-list?”
Read reports →“When the submit button is clicked, can you validate the input using the Luhn algorithm to confirm it's a legitimate credit card number?”
Read reports →“How would you visually signal to the user whether the number they entered is valid or not?”
Read report →“How would you create a postcard using letters found in a magazine?”
Read report →“Is it possible to ensure that the user interface adapts seamlessly to screen rotations on both Android phones and tablets?”
Read report →“Could you build a basic application that features a single screen? This screen would include a text input field specifically for numbers and a button to submit the input.”
Read report →“How do you create a sprint?”
Read report →Formats, difficulty and experience
Across all 24 Scribd Inc. interview reports.