- asked ahout some mirrors in a room. was writing lots of if elif statements and interviewer said i dont have to write down all the mirror logics and just finish the other logics. i wrote other logic for other cases and interviewer said this would work
- was asked about writing a function that tells who was chosen from a list with ids and weights and keeping the probability proportional to the weight. came up with non optimal solution. solution required prefix sum and binary search.
- bombed it hard. could not understand the question. interviewer put one input and the output. trying to get the interviewer elaborate took most of the time. interviewer said my approach could work and wanted me to expand on it. wrong approach wasted rest of the time until interviewer told me to go with other approach. at this time, it was over. I finally understood the question few minutes after interview was over. it was a simple dfs that I could have solved in few minutes. sorta pissed on this one.
- googlegness i think I did well. the interviewed agreed with my answers.
i did not hear from the recruiters back, but
i think its going to be no hire since I bombed the 3rd round very hard.
things I learned through this process.
- learn to clarify really well. I was given just an input and output.
- abandon the approach and start from the scratch if it doesnt work after 10 minutes.
- learn to identify data structures to use on vague wordings. the real questions aren't like what's on leetcode problems.