I've got my first interviews lined up with Meta and LinkedIn in December. I can probably push it to January but the dilemma remains the same.
How do I effectively prepare for those interviews?
Background : 2 years of SWE experience and Electrical Engineering background.
I am pursuing my master's from Georgia Tech part time and working a full time job. I barely get 4-5 hours for myself a week and I use those to either play football with friends or watch a show with my family.
I didn't expect to get such interviews in the first place. The recruiters had reached out to me.
After Thanksgivings and up until January first week, I have the semester break. So I can prepare them effectively for around 6 weeks with my job and no master's going on then.
I am not well versed with any topic to solve a question but I remember some of the concepts from my undergrad algorithms course and the weak interview prep I had done 3 years ago.
A good thing here is that I am pursuing a graduate level algorithms course this semester but again it's purely theoretical/psuedocode based. It helps building intuition with DP, Graphs and Divide N Conquer problems. On paper I can solve those questions but may fumble with the implementation.
I'm thinking of picking questions from the frequently asked Meta/LinkedIn problems list on leetcode and preparing for the Interviews solely based on this. I don't know if any other problem set would help me now.
I'm only giving this interview because I don't want to miss out on this opportunity. I've always dreamt of such an opportunity and now it's finally coming true. I wouldn't be sad if I didn't clear the interview but just disappointed in myself if I don't give my best in the limited time available.
Please do let me know if there is anything I can do to game the system and somehow perform well.
When do you finish your part-time masters at Georgia Tech? Doing the masters, working full-time, and doing interview prep is too much. For the next round of interviews, I'd strongly recommend that you compartmentalize, perhaps taking a semester off from the program.
I think the best bet is to (1) solve all the questions tagged with Meta on Leetcode, and (2) do some mock interviews. It's hard to create shortcuts for interview prep, unfortunately.
I also don't recommend applying for just one company: instead, apply for many so you can do 5+ interviews in a short period. You'll find that you naturally get significantly better between the first and last interview.
This Meta seems opportunistic, so it's great to pursue it, but I'd calibrate your expectations (sounds like you're doing this)
This is something I got out of the blue. I didn't expect to get scouted by recruiters. Especially from Big Tech.
I just started the program this semester. Will graduate in 2-3 years.
This is honestly to get an experience of what the interviews are like. People pay for mock interviews and it just seems stupid of me to let go of such a chance.
I want to know how my interview preparation should ideally be looking after these interviews. There's more to the picture than just the code, the setup, the approach to solving and an idea of what I really need to work on.
I've been thinking of doing competitive coding on code forces, so would that help me post the interview to focus on word problems instead of just straightforward leetcode questions.
Basically there's a lot to learn from the interview for me and I don't want to embarrass myself without any efforts.
I'm thinking of picking questions from the frequently asked Meta/LinkedIn problems list on leetcode and preparing for the Interviews solely based on this.
This is a solid approach. I would start with breadth to make sure you are covering all of your bases. In the past, I've used Grokking The Coding Interview because it categorizes different technical questions into patterns. It can be easier to solve coding questions if you can compartmentalize the type of question into one of the patterns.
I would recommend grinding hard during your 6 weeks, having goals in mind for how many questions you want to solve. Also, I would keep a journal to reflect on your solutions to see what you missed or what kind of question gives you trouble the most.
It helps building intuition with DP, Graphs and Divide N Conquer problems. On paper I can solve those questions but may fumble with the implementation.
I would make sure that you run your code. With pseudocode, it's possible that you could have a misunderstanding of programming language syntax, and you don't want to discover that during the interview.
I would also make sure to time yourself when you are going through a question.
I'm not sure if Meta makes you code on the computer, but I would try to mimic your interviewing environment as much as possible. If you are coding on a computer for the technical interview, make sure you code on a online IDE. If you are coding on a whiteboard for the technical interview, make sure you can use dry erase markers to write out your solution on a whiteboard.
I am a bit confused about what you mean by white eraser and whiteboard. I thought that the whiteboard round means you have to do this on Google docs or some online drawing tool like excalidraw.
Am I supposed to have an actual whiteboard lying around?
I've been practicing in excalidraw for a while for the sole purpose of whiteboard rounds.
Thanks for reminding me that I need to compartmentalize the questions into patterns. I was literally thinking of solving just the questions with the highest frequency and not caring about the wide variety of problems that I should have an idea about.