
Last year, I spent 6 months preparing for front-end interviews and landed offers from several FAANG+ companies. I wanted to share what I did, and the steps I took that helped me get there.
How I prepared for interviews
Like everyone else, I started with Leetcode. Still, I quickly realized that as great as Leetcode is for great general software engineering, it isn’t exactly applicable for front-end engineering interviews, as they tend to focus more on domain-specific questions.
So, I decided to scour the internet and quickly realized how tedious and difficult the process was for preparing for front-end interviews. I spent weeks just scouting the internet to find the correct resources to study for interviews. While good resources were available for the front end, I struggled to find anything that simplified the study process and showcased questions that were actually asked at companies.
Eventually, I created a large spreadsheet that listed the most frequently asked questions tagged by companies. The spreadsheet had over 5 tabs and hundreds of questions collected.
Here’s what that looked like: https://i.imgur.com/hOlZ8n3.png
Realizing I am probably not alone in my frustration with interview preparation, I started posting YouTube videos, teaching what I have learned to others, and simultaneously building a website called FrontendLead to help other engineers prepare for front-end interviews. Any link I share from my site in this post will be completely free to read and view and do not require any signup.
This entire post can also be found in an in-depth handbook for free here.
What I recommend to others while preparing for interviews
1. Get your fundamentals solid first. Refresh your data structures and algorithms.
There are plenty of free resources online; I published one for free to help you get started.
2. Start practicing front-end trivia questions
Meta and other top companies would love to test you on your foundational JavaScript knowledge.
You may get questions like:
- HTML concepts, for example: Explain the purpose of semantic HTML tags and their importance.
- CSS concepts, for example: What is the box model in CSS, and how does it work?
- For example, javascript concepts (arguably the most asked): Explain the concept of closures in JavaScript.
- Frame work-related questions, such as react, for example: How does React virtual DOM work, and why is it important?
Again, I published a free guide to share some of the most commonly asked trivia questions; you can find it here.
3. Javascript coding questions
These are the questions you will encounter the most, so you should spend the majority of your time preparing for them.
Expect questions like:
- Build a promise
- Flatten an array
- Build a debounce / throttle function
I aggregated the top 75 questions coding questions you might see during interviews here.
I want to call out something very important because I am also guilty of this mistake. Knowing the question may just be 25% of what you need to pass the interview. You might think you know the solution, but it may not be the most optimal solution and may fail certain tests.
I highly recommend solving each coding question with the code editor provided inside FrontendLead. Each problem comes with integrated unit tests and an official solution, so you can ensure you are learning the correct solution.
4. App design questions
Personal favorite type of question. There are many more real-world-related questions, and they will ask you to use the framework or vanilla JS to build a small app.
Such as:
- Build a todo list
- Debug a problem in their code
- Fetch images and render it
You can find a full list of questions to expect here.
5. React JS interview questions
Some companies may just focus on asking you more react-specific questions, so it’s a good idea to prepare yourself there, too. I keep an updated list of 300+ React interview questions with answers.
Expect things like:
- What is the difference between a real dom and a virtual dom?
- Talk to me about hooks, tell me some of the popular ones, and why you would use one over the other.
- Talk to me about the life cycle of a react component.
Again, the free article I created for this can be found here.
6. Frontend System Design
Unlike general system design interviews, front-end system design rounds will primarily focus on the UI/UX, so you do not need to speak much about the backend architecture, except discussing the expected API response you would like to see from the server and perhaps some basic napkin math of QPS you might be delivering there.
It is important to discuss various trade-offs in front-end implementation design. Why would you choose React over Vanilla JS? Why would you choose server-side rendering vs. client-side vs. hybrid? What protocol would you choose to communicate with the server, and why? How would you measure performance and optimize it?
You may encounter questions like
- Build a news feed
- Build an e-commerce platform
- Build a star rating component
I created a free 40-minute video on front-end system design fundamentals, which can be found here.
7. Behavioral Questions
Most engineers tend to brush this one off. I am guilty of this myself, but believe it or not, behavioral rounds can make or break your interview, so it’s best to prep for them.
Expect questions like:
- Share an occasion when you had to act on challenging feedback
- Tell us about a time when you had a conflict with a co-worker
- Walk me through your resume
You can find a more detailed free guide here.
When should you begin interviewing
I recommend you begin applying to companies you don’t care about 4 weeks before you are ready to start interviewing with companies you care about.
Why? This will help you break the ice with interviews and, perhaps, give you some confidence when you are ready to interview for companies you care about.
How to set yourself up for success
Try to schedule the onsite interviews with the companies you care about within the same 2-week window period. Why? Because if you pass the rounds, you can get offers around the same time and use each offer as leverage to negotiate other offers.
You can find my free salary negotiation guide here, including some mistakes to avoid.
Bonus tips
- Try not to burn yourself out while studying. It would be ideal if you could prepare for 3–4 months, as that gives you enough time to cover and digest all the material you learned.
- During interview day, spend 30 minutes reviewing all your study material in the morning, but then take some time to meditate and gather your thoughts before your interviews.
- Be yourself, don’t be a robot. People want to see authenticity and no BS. If you truly don’t know something, just say it. They will eventually catch on if you try to BS your way through the interview.
- Once you have a working solution during coding rounds, ask the interviewer if you can write some tests to test your code. I don’t mean actual unit tests, but perhaps you call your function or code with various arguments to see if it covers various edge cases.
- Research the company you are interviewing for and show excitement towards the company.
And that’s it, folks. I hope this can be helpful to others. Feel free to check out frontendlead.com if it may be helpful during your interview prep.
