I’m taking Meta ABCS and wanted to share my notes from the first class. These are just surface level things of the great things this program offers so go apply for the next application opening!

---

Technical Interview Approach

1. Understand and Plan
2. Execute and code
3. Review and Test

Understand and Plan

1. Something many people don’t do is create test cases. Creating test cases show the interviewer that you understand the problem.
2. Make 2-3 test cases. You need a variety of test cases that are a mix of simple, complex, edge, and other ones that would stretch your algorithm.
3. Designing an algorithm is the hardest step but a crucial one.

Execute and code

1. Coding should be the easiest step. If coding is not the easiest step, you need more practice to get more fluent.
2. Run through the code and work through the mistakes. Use the test cases that you made to test the code.

Review and Test

1. Run the code 🙂
2. Take one or two test cases and manually test them through the code.
3. If you know your space/time complexity, mention it. If you don’t, probably keep quiet.

---

Tackling Imposter Syndrome

Some Tips from ABCS Facilitator

• “Interviews are less of getting the correct answer, it’s convincing the interviewer that you have the correct answer.” – Meta ABCS Facilitator
• There are usually 1-2 questions or 1 harder question. The interviewer looks for signals. Those signals can be good or bad, but in general, the interviewer is looking to catch as many signals as they can.
  • If you don’t complete 2 questions, it doesn’t always mean you did bad.
  • In my personal case, I was not able to complete my questions, but I tried my best to demonstrate that I can be a good problem solver.
• Use a timer when practicing later on when practicing. Designing the algorithm is the hardest part so with time and practice, it gets easier and will get quicker.
• Don’t rely on trying to solve as many problems wishing to see a similar one during the technical interview. Instead, try to see patterns for the multiple problems that you solve.
• On Leetcode, sort problems by “tags” and do around 20 problems for each topic and a mix of easy-medium difficulties. It will help you recognize patterns of multiple problems of similar approaches that could benefit your technical interview skills.

Have a good mindset going into a technical interview. Don’t be nervous. Nervousness can cause these “bad signals” during an interview:

• Going silent for fear of asking “stupid” questions
• Trying a solution approach that you can’t get working vs a brute force approach that you’re comfortable with
• Give up
• Withdraw from an interview because of low confidence

Some more tips:

• Understand the process.
• Simulate the process: Mock Interviews
• Set realistic expectations and goals, and celebrate your progress on the journey.
• Slow and steady wins the race: 2-3 problems a week
• Treat yourself when you reach milestones: treat for every 10 problems completed
• Don’t compare yourself to others