Data science interview tips (product and technical interviews)

Key Takeaways

during technical interviews always communicate that is number one like literally just talk through everything that you're doing even if you're saying i'm just gonna think about this now this is i'm just thinking out loud like say stuff like that and make sure that you repeat the question the way that you understand it to the interviewer multiple times to make sure that you're on the right track because with these questions especially if you're nervous it's very easy to stray off track like we're not exactly answering a question that's being presented and you might be answering something that's like slightly off but if you're not communicating with your interviewer then the interviewer doesn't know that you're doing something wrong until much later and that by that time a lot of time probably has passed so that's not good for you another thing is don't try to find the most optimal solution for something um always try just to put a solution that works first and then be like hey i think i can optimize this even further and then talk through like the optimization process and start doing these optimizations yeah like if you think too much and be like what is the most optimal solution i can put on here then most likely you're just gonna like get nervous really confuse yourself so yeah just get something down on paper first and for non-technical interviews maybe like product or business sense interviews check out consulting interviews that's an excellent structure to follow the way the step-by-step process is very very good and also be very logical about what you're doing so if someone asks you a question like hey like there's something that went wrong in this feature and we're trying to figure out how to solve it for example that's a pretty common question for a product interview don't like think very thoroughly about it like don't just start rambling like be like okay to diagnose this problem we first will consider like this step and then from here if this step shows a certain result then it means you know this thing and if it doesn't then we will do the next step and then you just kind of go on from there like be very very structured in your thinking and not just like ramble on for technical interviews you should also be very careful about that like don't just like start typing stuff and be like oh my god like i feel really awkward just you know maybe maybe the interviewer things i don't understand and just like start typing things never never never do that think through exactly what it is that you're going to do write down the steps in english and then start writing stuff down trust me like it will save you so much more effort and so much more time to figure it out the first time like understand the logic as opposed to start typing stuff or stop writing stuff and then trying to figure that out then horse correcting is only necessary you know afterwards like you don't want to do that as your number one choice like you want to try to do things like properly the first time don't be afraid to take time to think about things it's totally fine to be like i need to i'm just thinking through this right now or like give me a moment um anything like that