Coding questions was easy for me due to this being a solution architect position and I am a SWE that grind leetcode for fun. I probably didn't get an offer due to my lack of past solution architect experiences, behavior, and overly high compensation level for this position. Recruiter was bad though.
The recruiter asked me how I could survive financially when I wasn't working.
Sell me your current product
Present MongoDB to us in a mock customer setting.
Not difficult, per se, but unexpected: one interviewer asked me to name several different sorting algorithms and rank them by their computational complexity. Unexpected because I've never had such a discussion with a customer, no matter how technical; the question would have been more appropriate for an engineer being hired into their kernel group but the interviewers didn't seem to know the difference.
Give us a demo of Atlas
can you tell things about indexes?
What is the most successful thing you have done in your work?
How does Stable Diffusion use CLIP?
How would you solve a problem with a chatbot model where it thinks it can write a book but is making no actual progress on writing that book and instead just tells users that it's working on it?
Viewing 1661 - 1670 interview questions