
Dandy (NY) Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 28 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Dandy (NY).
Software Engineer
The interview process at Dandy is excellent and well-crafted. It reflects their core value of moving at Speed. They conduct interviews quickly and make decisions promptly. It was a refreshing experience without unnecessary delays. While quick, the process is deliberate and not careless. There are several interviews, including a coding challenge where passing all unit tests is crucial, a data modeling and systems architecture discussion, a deep dive into past projects, and a review of previous employment, focusing on reasons for hiring, accomplishments, areas for improvement, and reasons for leaving. Dandy maintains a high hiring bar, which worked out well for me.
- Thinking about your past roles, can you share for each: the reason you were hired, your key accomplishments, aspects you could have improved, and why you departed?
Software Engineer
The interview process was pretty disorganized. The people interviewing me seemed totally disengaged, like they had more important things to do. It really made me wonder about the company culture. Honestly, based on how it went, I wouldn't want to work there.
- Can you design a denture delivery system using distributed manufacturing?
Software Engineer
It started with a recruiter call, then an online assessment, and finally a virtual onsite. The recruiter was really helpful and the interviewers were all nice. The onsite was spread over two days and had four interviews. The coding part for front end was okay, asking to make an algorithm for data manipulation. System design was about APIs and data models. The last two interviews were more about behavior. It was actually one of the better interview processes I've gone through.
- Can you elaborate on a previous technical project you were involved in that required significant collaboration across different teams?
- Walk me through the algorithm you developed for manipulating data during the front-end coding challenge.
- Could you describe your thought process for designing APIs and data models?
Dandy (NY) Software Engineer Interview Questions
Quoted word for word from Dandy (NY) interview reports.
“Given a hashmap of orders and dental-fitting attributes, identify the most common attribute pairs to set as default and return the original hashmap excluding these default values.”
Read reports →“Taking an object of current inventory and a set of default options, can you return an object in a different structure with the default options taken out?”
Read reports →“Can you implement flatmap yourself?”
Read reports →“Can you build your own version of flatmap?”
Read reports →“For a given hashmap/dict containing orders and dental-fitting attributes, could you return the most common attribute pairs as the default option, along with the original hashmap excluding the default values?”
Read report →“How would you take a JSON object representing preferences and a list of similar objects, and then remove the preferences that are common to both?”
Read report →“Given several time blocks for different offices, what are all the available 30-minute appointment slots?”
Read report →“Can you design a denture delivery system using distributed manufacturing?”
Read report →“Could you design a data model to store fillings?”
Read report →Formats, difficulty and experience
Across all 28 Dandy (NY) interview reports.