Profile picture

Interviewing Q&A and Videos

About Interviewing

Entry-Level Software Engineer [SDE 1] at Amazon profile pic
Entry-Level Software Engineer [SDE 1] at AmazonPosted December 9, 2024

My Meta Interview Experience (Mid-Level [E4] | USA | Reject After Follow Up)

Preparation: Standard top 100 LC problems + Infra System Design Problems + Behavioral problems (STAR)

Interviews

Meta phone screen: Asked two questions directly from the top 50 LC tagged (Array Sum and Tree BFS categories). Aced both questions and was notified the next day that I had moved on to onsite. Onsite prep: This would be my first system design interview and I didn't want to mess it up. I booked multiple mocks and though they weren't cheap, I was satisfied with the overall quality, feedback, and accurate grading. Meta onsite 1 (coding): This round tripped me up and I was disappointed given how much I had prepared 🙁 First question: (got optimal runtime, but not optimal space) Second question: Multiple binary searches on an array (did not get the optimal solution, couldn't find a question to tag) Immediately after the round, I realized my mistakes on both questions but couldn't go back and change it 🙁 Meta onsite 2 (behavioral): No surprise questions and I answered them to the best of my capacity stressing my ability to work with other people specifically Meta onsite 3 (system design): The question is similar to I had trouble understanding the interviewer and threw all my system design knowledge out there. There wasn't much discussion but I did mention concepts such as inverted index, sharding, replication, hot partitions, cache invalidations Meta onsite 4 (coding) This was my strongest performance and I was proud of myself after this round. I solved both questions optimally

  • Question 1: (LC Hard)
  • Question 2: Surprisingly (given my other rounds) I received a call the next day saying that they wanted to give me a follow-up coding round Meta onsite 5 (follow-up coding) I fumbled this round, which was especially heartbreaking. The questions were related to Palindrome (LC Hard) and Grid DFS Same day I was notified that I was rejected 🙁 Eye-opening experience overall and I know I have much more work to pass next time around. Total time: ~1.5 months
1.5K Views
5 Comments

Learn About Interviewing

Interviewing is an essential skill for every software engineer. The tech industry has one of the highest rates of job switching, so learning how to get good at interviewing can elevate your career. Your ability to transition between roles and companies depends on how well you perform during the interview. Taro offers resources for helping you to excel in software engineering interviews. We provide insights on effective preparation strategies and guide you on how to master the interview.
Interviews are a test for you to demonstrate your problem solving and technical skills. The ability to navigate complex challenges during an interview shows how prepared you are to take on the demands of being a software engineer.
Interviews also assess cultural fit and communication skills. This is important because you’ll be working in collaborative work environments where you need to talk to your team and other teams to execute well on your projects. Having great communication skills means you are able to effectively outline a broader vision of your project, dig into the technical details of your project, and communicate any potential issues to your stakeholders.
It’s crucial to thoroughly research the company to get valuable insights and make a good first impression. You can filter our Q&A by company to see whether there are any relevant conversations about the company to help with your interview. You can also check Blind and Reddit to understand what people are saying about the company. Use our Taro Networking feature to reach out to people in a company to get an insider perspective of the company. The company page should include information about their values and culture. Make sure that you align with these values. You should get a sense of the company’s financial reports to understand their products from a revenue point of view.
You should have a solid foundation in data structures and algorithms to show your experience and problem solving capabilities. Pick a programming language that you are proficient in, and use it for the technical portion of the interview. Leetcode is recommended as the best tool to practice for data structures and algorithms type of interviews. The provide a large set of problems with a code editor for you to solve the problems, and they have test cases and performance profiles so you can evaluate your solution. it’s also recommended to prepare through mock interviews.
The above strategies, along with diving more into Taro interviewing resources, can help you effectively prepare for an interview at a tech company.
Show more