Related Posts
McKinsey & Company I am entering in the interview rounds with McKinsey and wondering if anyone had tips, online course advices or materials to share!
Also would anyone be interested or knows anyone to do a coaching session that has already worked in Mckinsey? Thanks! McKinsey & Company @
More Posts
Does BofA give broadband reimbursement?
Bowl Leader
Hi! Excited we have a space finally :)
Conversation Starter
Mentor
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
I really feel for you here. This was me, me, me and yep me 🙋🏼♀️
THIS really scared me the biggest part of applying for a new job until now. I blacked out with a panic attack after a technical on site interview 6 years ago, and this was a huge confidence knock for me applying for new jobs. Feeling like I’ll be “caught out” impostor syndrome mode kicks in. Fight or flight mode, or faint in my scenario!
I had a technical interview 2 weeks ago, first one since that dreaded day and passed to the next stage. I went through leet code questions for my prep. Doesn’t have to many. I filtered the top 150 interview questions and done maybe 20-30 odd of them. I may have not got the solutions for them all but if I reviewed the solutions I would make sure I 100% understand how it was done before I move on. Data structures used, time complexity and space complexity. Also, I bought a udemy course on algorithms and data structures as refresher. Helps huge with time and space complexity questions. Whatever language you are most comfortable with. Don’t try learn a new language. Stick to what you’re most familiar with. Crack the coding interview book is great too for information from interview prep. I read mostly the theory and reading sections for what to expect in the interviews etc.
Technical interviews are much less whiteboard and more pair programming these days remotely I find, which made it feel less intimidating for me. But I assure you that it a much more supportive and encouraging environment. My interviewers were nothing but nice and the main thing is not about solving the problem 100% but how you effectively communicate. So thought process etc. They want to see how you effectively collaborate. It’s not code the problem 100% and say nothing. They help you along the way if you keep talking - the only way they can help if you are stuck is to understand your thought process. The single worst thing you can do is get stuck and say nothing. That’s where candidates fall at the hurdle. I was basically thinking out loud and that helped the interviewer or myself guide me to the solution in the end. I wouldn’t consider myself the greatest problem solver in the world but by god I can talk lol
Also a bit cliche but mindset is everything. For this interview I took out the raw emotion and fear for failure/humiliation aside and just said I’ll do my best. Sometimes just got to fight the fear and do it anyway. But if I can do it you certainly can do it too! Good luck 😊
Wow, thank you for sharing your experience and for the tips. I'm trying to see the technical interviews from a different angle. Hopefully I can find a mindset that works better.
Practice coding out loud. Most interviews are looking to understand how you solve problems and your thoughts process and how you work collaboratively. So you’ll need to speak every process your doing as your working to solve the problem. I am alors preparing for a tech interviews and I ABSOLUTELY HATE leetcode style code questions. But as I’ve been practicing them and understanding what I’m doing I’m finding myself less nervous and more excited. Remember that you are going into the interview just simply talking to another human and working through a coding problem with them, like pairing, that’s how I think about it. Best of luck to you!!! You will crush whatever interviews you get!!!!