
Schrödinger Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 19 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Schrödinger.
Software Engineer
The recruitment process at Schrödinger has 3 rounds. It starts with an online assessment which took 1.5 hours and was offline. This OA had three questions. The first two were basic observation questions that were easy to medium in difficulty (like LeetCode problems), and most people with good problem-solving skills could solve them quickly. The third question was a medium-level tree problem that required a small but important observation, which made it difficult for many.
- Given an integer array arr, we split arr into some number of chunks (i.e., partitions), and individually sort each chunk. After concatenating them, the result should equal the sorted array. Return the largest number of chunks we can make to sort the array. Example 1: Input: arr = [5,4,3,2,1] Output: 1
Software Engineer
It was a 4 stage process. Started with a recruiter call, then two video interviews where I had to solve coding problems using an online platform. The problems were easy at first but got progressively harder. The last round was a full day, about 7 hours, and involved six 1 on 1 interviews and a social hour with some engineers. The 1 on 1s were pretty standard and I felt good about them. The social hour was a bit weird, the engineers were mostly focused on their own work and I had to really try to keep the conversation going.
- What is the longest path problem in a Directed Acyclic Graph (DAG)?
- Can you explain or solve the 2-Sum problem?
Software Engineer
Applied online, then a recruiter reached out. Had one phone screen, followed by five technical interviews. There was also a lunch with the entire team, which was a bit much. The team itself was great though. They got back to me in two days saying I was a strong candidate but needed more time to decide since they were still interviewing others. A week later, they called to say they chose someone else, and it was a close call. I felt I did well in all the interviews, but I guess they really wanted someone with strong Java and SQL experience, which I didn't have.
- Tell me about OOPS design.
- How would you approach algorithms?
- What about data structures?
Schrödinger Software Engineer Interview Questions
Quoted word for word from Schrödinger interview reports.
“What's the difference between virtual and pure virtual functions?”
Read reports →“Given an integer array arr, we split arr into some number of chunks (i.e., partitions), and individually sort each chunk. After concatenating them, the result should equal the sorted array. Return the largest number of chunks we can make to sort the array. Example 1: Input: arr = [5,4,3,2,1] Output: 1”
Read reports →“Could you build a string parser in python to represent molecules?”
Read reports →“Describe the purpose of the @Transactional annotation.”
Read reports →“What is the longest path problem in a Directed Acyclic Graph (DAG)?”
Read report →“Can you determine if a given string exists within an array of strings?”
Read report →“What exactly is an abstract class?”
Read report →“What are the differences between RabbitMQ and Kafka?”
Read report →“What are the isolation levels of a database transaction?”
Read report →Formats, difficulty and experience
Across all 19 Schrödinger interview reports.