From 6ef102e5fb662a3075e37dcabe9fa23001952796 Mon Sep 17 00:00:00 2001 From: Zhou Yuhang <54398705+xquisite0@users.noreply.github.com> Date: Mon, 23 Jun 2025 16:54:32 +0800 Subject: [PATCH] [feih] companies/meta: add GFE user experiences (#509) --- .../meta-front-end-interview-questions.md | 35 +++++++++++++++++++ contents/introduction.md | 2 +- website/sidebars.js | 1 + 3 files changed, 37 insertions(+), 1 deletion(-) create mode 100644 contents/companies/meta-front-end-interview-questions.md diff --git a/contents/companies/meta-front-end-interview-questions.md b/contents/companies/meta-front-end-interview-questions.md new file mode 100644 index 000000000..23395fbfb --- /dev/null +++ b/contents/companies/meta-front-end-interview-questions.md @@ -0,0 +1,35 @@ +--- +title: Meta Front End Interview Questions +sidebar_label: Meta interview questions +--- + +## Insider tips from the GreatFrontEnd community + +These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook) users who have completed interviews with Meta. + +**22nd May 2025**: + +> 17.5 mins to solve per question. and there are 2 questions in a 40 mins round. +> Meta asks variants. 😢 + +**31st Jan 2025**: + +> I did meta last year. It was 2 leetcodes for frontend positions. + +**7th Jan 2025**: + +> No, every company has preselected questions in a question bank. Google will delete leaked questions, Meta does not. +> +> If you do the top 100/250 of Meta leetcode questions, you have a really good chance at getting one of the questions during the interview. + +**11th May 2024**: + +> Appreciate the response! I interviewed with Meta and was caught off guard with Emitter Pattern & Classnames fn when I expected DSA 😦 + +**23rd Apr 2024**: + +> Hi, if you are in the front end pipeline, the questions will be focused on front end. For me, I am interviewing for IC 4/5. I have gone through a phone screen and the onsite was 4 rounds: 2 coding, 1 BQ and 1 system design. The coding is similar to the type of js questions on GreatFrontEnd and for system design, I used the RADIO framework to approach it. +> If you are interviewing for IC6 and above, I think you will need to go through one more design round but one less coding +> The next step is team matching. It could take a while, so it depends + +For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)! diff --git a/contents/introduction.md b/contents/introduction.md index c50b3b4cf..aa56ec330 100644 --- a/contents/introduction.md +++ b/contents/introduction.md @@ -120,7 +120,7 @@ _Legend: ✅: Asked, ❌: Not asked, ⚠️: No data_ | [**Atlassian**](./companies/atlassian-front-end-interview-questions.md) | ❌ | ❌ | ✅ | ✅ | ✅ | | [**ByteDance/TikTok**](./companies/bytedance-tiktok-front-end-interview-questions.md) | ✅ | ✅ | ✅ | ✅ | ❌ | | [**Dropbox**](./companies/dropbox-front-end-interview-questions.md) | ❌ | ⚠️ | ✅ | ✅ | ✅ | -| **Facebook/Meta** | ✅ | ❌ | ✅ | ❌ | ✅ | +| [**Facebook/Meta**](./companies/meta-front-end-interview-questions.md) | ✅ | ❌ | ✅ | ❌ | ✅ | | **Flipkart** | ⚠️ | ✅ | ⚠️ | ⚠️ | ⚠️ | | [**Google**](./companies/google-front-end-interview-questions.md) | ✅ | ✅ | ✅ | ✅ | ✅ | | [**LinkedIn**](./companies/linkedin-front-end-interview-questions.md) | ✅ | ⚠️ | ✅ | ✅ | ⚠️ | diff --git a/website/sidebars.js b/website/sidebars.js index f48cb812c..f4ccd2525 100755 --- a/website/sidebars.js +++ b/website/sidebars.js @@ -46,6 +46,7 @@ module.exports = { 'companies/amazon-front-end-interview-questions', 'companies/google-front-end-interview-questions', 'companies/microsoft-front-end-interview-questions', + 'companies/meta-front-end-interview-questions', 'companies/airbnb-front-end-interview-questions', 'companies/bytedance-tiktok-front-end-interview-questions', 'companies/apple-front-end-interview-questions',