[feih] companies: misc tweaks
This commit is contained in:
Yangshun
parent
7b981a5f02
commit
bf495b9299
|
|
@ -9,31 +9,26 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**19th Jun 2025**:
|
||||
|
||||
> Attended Adobe system design, it was non frontend system design. I was asked to design LRU cache and design the classes and interfaces for a chess game.
|
||||
> Also had the hiring manager round, was asked to implement the flood fill algorithm. i.e. there is a m*n grid which has outlines of some shapes. If clicked inside any shape, then the shape should be flood filled. If clicked outside the shape, then the whole grid should be flood filled except the shapes.
|
||||
>
|
||||
> Had to implement the pseudo code only though.
|
||||
> Attended Adobe system design, it was non frontend system design. I was asked to design LRU cache and design the classes and interfaces for a chess game. Also had the hiring manager round, was asked to implement the flood fill algorithm. i.e. there is a m\*n grid which has outlines of some shapes. If clicked inside any shape, then the shape should be flood filled. If clicked outside the shape, then the whole grid should be flood filled except the shapes.
|
||||
>
|
||||
> Had to implement the pseudo code only though.
|
||||
|
||||
**16th Jun 2025**:
|
||||
|
||||
> Attended Adobe interview. In the language and web fundamentals round, a question similar to https://www.geeksforgeeks.org/problems/leaders-in-an-array-1587115620/1 was asked.
|
||||
>
|
||||
> Another question that was asked was the following: You are given an API getAllLinks(url) which returns all the links on the page. You have to write a function to return all the descendant links (i.e. child urls of child urls and so on) of the url. Edge cases were built on top of this: what if there are circular dependencies between pages? What if getAllLinks returns a promise? How can the async code be more efficient? Time complexity?
|
||||
>
|
||||
> Attended Adobe interview. In the language and web fundamentals round, a question similar to https://www.geeksforgeeks.org/problems/leaders-in-an-array-1587115620/1 was asked.
|
||||
>
|
||||
> Another question that was asked was the following: You are given an API getAllLinks(url) which returns all the links on the page. You have to write a function to return all the descendant links (i.e. child urls of child urls and so on) of the url. Edge cases were built on top of this: what if there are circular dependencies between pages? What if getAllLinks returns a promise? How can the async code be more efficient? Time complexity?
|
||||
>
|
||||
> One thing to note was that I had to handrun the code as the test cases were not setup and the interviewer actually typed out the test cases instead of copy pasting.
|
||||
|
||||
**26th Oct 2023**:
|
||||
|
||||
> I had my Adobe onsite last week for FE mid-level role. It was following a HackerRank + quick QnA with HM
|
||||
>
|
||||
> It was five rounds each consisting of 30min tech and 10min behavior 5min QnA
|
||||
> These were some technical questions asked
|
||||
>
|
||||
> LC medium - find total number of islands in a nested arr of 0 and 1
|
||||
> LC easy - covert Oct 1 23 to 10-01-23
|
||||
> UI - build an accordion using JS or react
|
||||
> create polyfill of .reduce
|
||||
>
|
||||
>
|
||||
> It was five rounds each consisting of 30min tech and 10min behavior 5min QnA These were some technical questions asked
|
||||
>
|
||||
> LC medium - find total number of islands in a nested arr of 0 and 1 LC easy - covert Oct 1 23 to 10-01-23 UI - build an accordion using JS or react create polyfill of .reduce
|
||||
>
|
||||
> It was on the easier side but only for one headcount so I didn't get an offer
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -33,19 +33,18 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**21st Mar 2025**:
|
||||
|
||||
> "Our frontend technical screens tend to be more practical than algorithmic"....
|
||||
> proceeds to drop a LC hard question during the screen FML
|
||||
>
|
||||
> "Our frontend technical screens tend to be more practical than algorithmic".... proceeds to drop a LC hard question during the screen FML
|
||||
>
|
||||
> Not my first rejection but actually wanted to work at Airbnb for a long time now so this one just hurts a bit more. I actually learned a good amount using GreatFrontEnd to prepare so I definitely did improve.
|
||||
|
||||
**12th Jul 2024**:
|
||||
|
||||
> Just got done, it was okay. They asked Backbone.js, but the 2nd part was slightly different from GreatFrontEnd. Threw me off quite a bit. Got the right output, but took up the whole time. Let's see! Not feeling super confident based of the interviewer's demeanor
|
||||
>
|
||||
> It was add on listener, but the event names are change:foo, change:bar, (which is fine).
|
||||
>
|
||||
> Just got done, it was okay. They asked Backbone.js, but the 2nd part was slightly different from GreatFrontEnd. Threw me off quite a bit. Got the right output, but took up the whole time. Let's see! Not feeling super confident based of the interviewer's demeanor
|
||||
>
|
||||
> It was add on listener, but the event names are change:foo, change:bar, (which is fine).
|
||||
>
|
||||
> There was additional on change which should be a global change listener that fires when any change is made
|
||||
>
|
||||
>
|
||||
> And the kicker was that when you call unset, you need to keep the listeners (soft delete the data), so that when you set the attribute again, all the global listeners and the attribute listeners before unset are fired
|
||||
|
||||
**19th Apr 2024**:
|
||||
|
|
@ -58,7 +57,6 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**13th Mar 2024**:
|
||||
|
||||
> Just got rejected from Airbnb. I do want to thank this forum / GreatFrontEnd for system design cause I got a strong yes from that on my system design. So the method works great. Unfortunately I didn’t do well on my experience interview out of all things lol.
|
||||
> I laid out full technical details process, results, issues, but that’s not enough. Oh well. It was nice to try.
|
||||
> Just got rejected from Airbnb. I do want to thank this forum / GreatFrontEnd for system design cause I got a strong yes from that on my system design. So the method works great. Unfortunately I didn’t do well on my experience interview out of all things lol. I laid out full technical details process, results, issues, but that’s not enough. Oh well. It was nice to try.
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -39,35 +39,26 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
**21st May 2025**:
|
||||
|
||||
> in final rounds with apple, this is what recruiter explained
|
||||
>
|
||||
> There will be 4 x 45 min interviews conducted virtually so can be on 1 day or split over 2. See below for focus areas.
|
||||
>
|
||||
> JavaScript: Coding (similar to tech screen)
|
||||
> Bug Hunt: Coding (working on existing code base)
|
||||
> Web Performance (Domain knowledge questions focused on Web Performance)
|
||||
> Product Thinking (Behavioral round focused on collaboration, balancing technical VS business needs and understanding user impact)
|
||||
>
|
||||
>
|
||||
> There will be 4 x 45 min interviews conducted virtually so can be on 1 day or split over 2. See below for focus areas.
|
||||
>
|
||||
> JavaScript: Coding (similar to tech screen) Bug Hunt: Coding (working on existing code base) Web Performance (Domain knowledge questions focused on Web Performance) Product Thinking (Behavioral round focused on collaboration, balancing technical VS business needs and understanding user impact)
|
||||
>
|
||||
> if anyone has tips for how to practice / prepare for "bug hunt" and "product thinking" feel free to comment. i believe "web performance" will be deep JS trivia likely covering a range of concepts that are usually surfaced in FE system design interviews
|
||||
|
||||
**2nd Dec 2024**:
|
||||
|
||||
> they have a big question bank, usually team by team case
|
||||
> yes they ask sys design, its a faang company so the bar is really high
|
||||
> also one of the lowest paying of the faangs lol
|
||||
> they have a big question bank, usually team by team case yes they ask sys design, its a faang company so the bar is really high also one of the lowest paying of the faangs lol
|
||||
|
||||
**14th Apr 2024**:
|
||||
|
||||
> Think it was 6 total rounds
|
||||
> All fundamentals
|
||||
> Vanilla js
|
||||
> 5 yoe
|
||||
>
|
||||
> (In response to what do you think helped you prep for: big tech, specifically apple is asking a lot of vanilla js questions, dom related questions?)
|
||||
> GreatFrontEnd UI questions all with vanilla js implementation
|
||||
> Think it was 6 total rounds All fundamentals Vanilla js 5 yoe
|
||||
>
|
||||
> (In response to what do you think helped you prep for: big tech, specifically apple is asking a lot of vanilla js questions, dom related questions?) GreatFrontEnd UI questions all with vanilla js implementation
|
||||
|
||||
**3rd Apr 2024**:
|
||||
|
||||
> I finished up my Apple Phone Screen. They don’t like to ask LC questions but rather asked my background and experience with 10 mins left for a super easy js question. I guess the process really depends on the team you are about to interview for. They care more about if you are a good fit for the position rather than if you are someone who can ace a LC question. Hope I can make it to the onsite.
|
||||
> I finished up my Apple Phone Screen. They don’t like to ask LC questions but rather asked my background and experience with 10 mins left for a super easy js question. I guess the process really depends on the team you are about to interview for. They care more about if you are a good fit for the position rather than if you are someone who can ace a LC question. Hope I can make it to the onsite.
|
||||
|
||||
**12th Mar 2024**:
|
||||
|
||||
|
|
|
|||
|
|
@ -3,36 +3,31 @@ title: Atlassian Front End Interview Questions
|
|||
sidebar_label: Atlassian interview questions
|
||||
---
|
||||
|
||||
:::info Latest version on GreatFrontEnd
|
||||
|
||||
Find the latest version of this page on [GreatFrontEnd's Atlassian Front End Interview Guide](https://www.greatfrontend.com/interviews/company/atlassian/questions-guides?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook).
|
||||
|
||||
:::
|
||||
|
||||
## 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 Atlassian.
|
||||
|
||||
**16th Jun 2025**:
|
||||
|
||||
> I haven’t done Atlassian yet. These are my notes based on recruiter chat:
|
||||
> The technical interview is a 60-minute video interview with two main parts:
|
||||
>
|
||||
> I haven’t done Atlassian yet. These are my notes based on recruiter chat: The technical interview is a 60-minute video interview with two main parts:
|
||||
>
|
||||
> First 10 minutes: Rapid-fire questions about modern JavaScript practices. Simple questions to test your basic understanding of JavaScript.
|
||||
>
|
||||
> Remaining 45 minutes: Front-end coding portion with 1-2 coding scenarios. Key details:
|
||||
> No React involved
|
||||
> Focus on vanilla JavaScript, HTML, and CSS
|
||||
> Solve the first question before moving to the second
|
||||
> Goal is to assess your coding skills
|
||||
>
|
||||
>
|
||||
> Remaining 45 minutes: Front-end coding portion with 1-2 coding scenarios. Key details: No React involved Focus on vanilla JavaScript, HTML, and CSS Solve the first question before moving to the second Goal is to assess your coding skills
|
||||
>
|
||||
> Option to do a redo interview within 24 hours if needed, and Atlassian will take the best result (best to just do it since it will do good than harm).
|
||||
|
||||
**13th Jun 2025**:
|
||||
|
||||
> Atlassian Karat Screen (unclear if these always ask the same questions):
|
||||
> -Analyze arrays (know push, pop, unshift from memory - no resources allowed)
|
||||
> Know Promise.any from memory (no resources allowed)
|
||||
> -Know Async Generators, await, yield, async for await loop, Promise.resolve (know from memory, no resources allowed)
|
||||
> (^ for those, you just have to be able to talk about them from memory, you don't have to write code with them from memory)
|
||||
>
|
||||
> Resources allowed:
|
||||
> -Build a custom search widget - only HTML and CSS. You can use resources here, brushing up on css, flexbox, etc is helpful here. This wasn't written but the requirements state you can't hardcode height or width so use EM or %
|
||||
> -JS/HTML - fetch todos from an API. Render 20 todos at a time. the dummy API call takes params to control how many you get. Brush up on fetch with no helper libraries, and like, creating/appending/removing dom elements. Again, pretty easy if you have time, but you don't have a lot of time, and if you (like me) haven't been writing vanilla JS and HTML like this much for years it's definitely helps speed things up to brush up on this
|
||||
> Atlassian Karat Screen (unclear if these always ask the same questions): -Analyze arrays (know push, pop, unshift from memory - no resources allowed) Know Promise.any from memory (no resources allowed) -Know Async Generators, await, yield, async for await loop, Promise.resolve (know from memory, no resources allowed) (^ for those, you just have to be able to talk about them from memory, you don't have to write code with them from memory)
|
||||
>
|
||||
> Resources allowed: -Build a custom search widget - only HTML and CSS. You can use resources here, brushing up on css, flexbox, etc is helpful here. This wasn't written but the requirements state you can't hardcode height or width so use EM or % -JS/HTML - fetch todos from an API. Render 20 todos at a time. the dummy API call takes params to control how many you get. Brush up on fetch with no helper libraries, and like, creating/appending/removing dom elements. Again, pretty easy if you have time, but you don't have a lot of time, and if you (like me) haven't been writing vanilla JS and HTML like this much for years it's definitely helps speed things up to brush up on this
|
||||
|
||||
**22nd May 2025**:
|
||||
|
||||
|
|
@ -45,25 +40,21 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
**16th Mar 2025**:
|
||||
|
||||
> Based out of BLR, got an offer from Atlassian for a front-end principal role (P60).
|
||||
>
|
||||
>
|
||||
> GreatFrontEnd has helped me a lot in practicing and getting over interview anxiety. Especially the RADIO framework for system design rounds (the more senior you get, more system design rounds start to matter).
|
||||
>
|
||||
>
|
||||
> Atlassian has a well documented interview process, that can be easily found with some basic searching on the internet. Your recruiter will help you a lot in setting expectations for the upcoming round.
|
||||
>
|
||||
>
|
||||
> I had 5 rounds:
|
||||
>
|
||||
> Round 1: code up a widget in React (browser coding round)
|
||||
> Round 2: code up a utility in JS
|
||||
> Round 3: system design round
|
||||
> Round 4: leadership craft round
|
||||
> Round 5: values and principles round
|
||||
>
|
||||
>
|
||||
> Round 1: code up a widget in React (browser coding round) Round 2: code up a utility in JS Round 3: system design round Round 4: leadership craft round Round 5: values and principles round
|
||||
>
|
||||
> Atlassian relies more on follow-up / scale up questions. Instead of focusing on specific solution to a specific problem, you have to expect interviewer to keep changing the requirements and keep making the problem more and more complex.
|
||||
>
|
||||
>
|
||||
> You would be able to solve the first problem in a round easily. But if your initial solution requires a major overhaul when the follow-up question tweaks the requirement, that 's a red flag for the interview feedback.
|
||||
>
|
||||
>
|
||||
> Practicing GreatFrontEnd helped me solidify ton of concepts, and helped me feel comfortable in my skin during interviews.
|
||||
>
|
||||
> Almost no company interviews candidates in an in-browser coding interview environment like GreatFrontEnd. So I used to practice setting up the problem with test cases locally in VSCode. Used Bun and Vite heavily, to avoid spending time configuring test runner, bundlers etc.
|
||||
>
|
||||
> Almost no company interviews candidates in an in-browser coding interview environment like GreatFrontEnd. So I used to practice setting up the problem with test cases locally in VSCode. Used Bun and Vite heavily, to avoid spending time configuring test runner, bundlers etc.
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -47,16 +47,17 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
**17th Nov 2024**:
|
||||
|
||||
> cant say too much because of NDA but this is how it went for TikTok entry level FE
|
||||
> 1: leetcodes, javascript fundamentals (covered in GFE 1 month study plan)
|
||||
> 2: UI component + follow up
|
||||
> 3: system design based on past project + javascript coding
|
||||
> and now awaiting 4th round w recruiter
|
||||
>
|
||||
> 1. leetcodes, javascript fundamentals (covered in GFE 1 month study plan)
|
||||
> 2. UI component + follow up
|
||||
> 3. system design based on past project + javascript coding and now awaiting 4th round w recruiter
|
||||
>
|
||||
> feedback for each round was fairly quick, received update the next morning
|
||||
|
||||
**12th Nov 2024**:
|
||||
|
||||
> i do bytedance/tiktok round 2 recently, unfortunately get rejected. the coding questions is quite overwhelming for me.
|
||||
> after experience & quiz questions, the interviewer directly give me 3 questions (all for ~30 mins), and i can choose the order.
|
||||
> i do bytedance/tiktok round 2 recently, unfortunately get rejected. the coding questions is quite overwhelming for me. after experience & quiz questions, the interviewer directly give me 3 questions (all for ~30 mins), and i can choose the order.
|
||||
>
|
||||
> 1. similar to Map Async Limit but has to be solution 4
|
||||
> 2. some compose middleware question (can't find anything similar)
|
||||
> 3. implement bind, but i can't handle the new keyword
|
||||
|
|
@ -67,8 +68,7 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**8th Aug 2024**:
|
||||
|
||||
> Had my first round tiktok frontend engineer interview. Not sure on the level but I told them I have 3 YOE so maybe 2-1?
|
||||
> Strange interview tbh. There was a huge language barrier and it was difficult to build rapport with the interviewer (my interview was at night so I had someone overseas). Very difficult to read. First 20 minutes was talking about past projects/experiences/challenges, then a React coding question, then a JS quiz question, and then an untagged tiktok LC med... I asked some good questions about the company imo but the interviewer could barely answer it. I tried my best but it was not a collaborative interview at all and more of a test so it was challenging for me. I think it was a lot for an hour and we ended up going over time
|
||||
> Had my first round tiktok frontend engineer interview. Not sure on the level but I told them I have 3 YOE so maybe 2-1? Strange interview tbh. There was a huge language barrier and it was difficult to build rapport with the interviewer (my interview was at night so I had someone overseas). Very difficult to read. First 20 minutes was talking about past projects/experiences/challenges, then a React coding question, then a JS quiz question, and then an untagged tiktok LC med... I asked some good questions about the company imo but the interviewer could barely answer it. I tried my best but it was not a collaborative interview at all and more of a test so it was challenging for me. I think it was a lot for an hour and we ended up going over time
|
||||
|
||||
**18th Jun 2024**:
|
||||
|
||||
|
|
|
|||
|
|
@ -45,7 +45,6 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**11th Feb 2024**:
|
||||
|
||||
> I did Dropbox two years ago. They loved testing Vanilla JS, no react
|
||||
> i had to build carousel with vanilla js and there's debugging round purely made of vanilla JS
|
||||
> I did Dropbox two years ago. They loved testing Vanilla JS, no react i had to build carousel with vanilla js and there's debugging round purely made of vanilla JS
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -82,34 +82,28 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
**5th Apr 2025**:
|
||||
|
||||
> Interview experience at Google L4 frontend role - Offer Accepted
|
||||
>
|
||||
> Round 1 DSA: question of finding all subsets in a deck of cards that pass a valid condition
|
||||
> Round 2 Frontend: Implement a color swatch. Also with a slider
|
||||
> Round 3 Googlyness: Behavior and resume
|
||||
> Round 4: DSA - File system API and streaming API with generators
|
||||
>
|
||||
> Team match round
|
||||
> HC review
|
||||
>
|
||||
> Offer
|
||||
>
|
||||
> 1. Round 1 DSA: question of finding all subsets in a deck of cards that pass a valid condition
|
||||
> 2. Round 2 Frontend: Implement a color swatch. Also with a slider
|
||||
> 3. Round 3 Googlyness: Behavior and resume
|
||||
> 4. Round 4: DSA - File system API and streaming API with generators
|
||||
>
|
||||
> Team match round, then HC review, Offer
|
||||
|
||||
**9th Mar 2025**:
|
||||
|
||||
> I have a google senior frontend engineer loop coming up. The recruiter shared material suggests 2 dsa + 1 frontend + 1 system design (guideline suggests it can be anything frontend or backend) + 1 behavioural.
|
||||
> I have a google senior frontend engineer loop coming up. The recruiter shared material suggests 2 dsa + 1 frontend + 1 system design (guideline suggests it can be anything frontend or backend) + 1 behavioural.
|
||||
|
||||
**20th Dec 2024**:
|
||||
|
||||
> Hello, folks!
|
||||
> Previously, I had an interview with Google for a Front-End role.
|
||||
> The problem I got was DSA-style, just like you guys mentioned, thanks to this channel, so I did prep for DSA.
|
||||
> Hello, folks! Previously, I had an interview with Google for a Front-End role. The problem I got was DSA-style, just like you guys mentioned, thanks to this channel, so I did prep for DSA.
|
||||
|
||||
**20th Dec 2024**:
|
||||
|
||||
> dsa is fair game throughout the entire google experience
|
||||
> easy, medium, hard, all fair game
|
||||
> DSA is fair game throughout the entire google experience easy, medium, hard, all fair game
|
||||
|
||||
**10th Nov 2024**:
|
||||
|
||||
> I interviewed a few years ago. At that time it was mostly DSA and 1 round involved frontend design with some coding HTML, CSS, JS. But I echo what others have said. Google's FE is DSA heavy.
|
||||
> I interviewed a few years ago. At that time it was mostly DSA and 1 round involved frontend design with some coding HTML, CSS, JS. But I echo what others have said. Google's FE is DSA heavy.
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -44,17 +44,15 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
**13th May 2025**:
|
||||
|
||||
> Linkedin technical screen experience for Senior FE role - 1 hr interview, lots of parts to this one:
|
||||
>
|
||||
> FE quiz questions - event delegation, closures, etc
|
||||
> Memoize I+II
|
||||
> Implement infinite scroll with data fetching/pagination - implementation is in plain JS, can optimize with throttle
|
||||
>
|
||||
> General thoughts - They're primarily testing for JS fundamentals, you gotta know your stuff real well to pass. I'm guessing they conduct interviews this way bc their FE codebase is written in Ember which not many ppl have experience with
|
||||
>
|
||||
> FE quiz questions - event delegation, closures, etc Memoize I+II Implement infinite scroll with data fetching/pagination - implementation is in plain JS, can optimize with throttle
|
||||
>
|
||||
> General thoughts - They're primarily testing for JS fundamentals, you gotta know your stuff real well to pass. I'm guessing they conduct interviews this way bc their FE codebase is written in Ember which not many ppl have experience with
|
||||
|
||||
> (How did you implement infinite scrolling? Did you use IntersectionObserver?)
|
||||
>
|
||||
>
|
||||
> I just used scroll events since they provided some boilerplate code for it, but IntersectionObserver would've been better to use had I been more familiar with the api. But I think the idea is generally the same where you check for a boundary being crossed, fetch more data and then take each item and append it to the parent container.
|
||||
>
|
||||
>
|
||||
> Honestly I fumbled on this one tho, I haven't spent as much time on vanilla JS implementations vs react so I was a lot less confident in general. Also I'm surprised they even wanted to interview me for a senior role consider I'm only at ~3 yoe lol.
|
||||
|
||||
**28th Jan 2025**:
|
||||
|
|
@ -64,14 +62,13 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
**5th Jan 2025**:
|
||||
|
||||
> LinkedIn US asked JS/web/html trivia questions and a Leetcode easy question for the phone screen round. Not sure about the onsite
|
||||
>
|
||||
>
|
||||
> Their systems design question was also not one I had seen before, and was difficult to understand. However in retro, asking more questions about "how it should work if the user does x, y, z" would have got me to design a better answer.
|
||||
>
|
||||
> I went back to try and solve it correctly. I was not really satisfied with any solution until reading white paper on the subject asked.
|
||||
>
|
||||
> I went back to try and solve it correctly. I was not really satisfied with any solution until reading white paper on the subject asked.
|
||||
|
||||
**5th Jan 2025**:
|
||||
|
||||
> Is it frontend or fullstack? They ask leetcode for fullstack. Merge intervals is one question
|
||||
> Study for tic tac toe and autocomplete questions
|
||||
> Is it frontend or fullstack? They ask leetcode for fullstack. Merge intervals is one question Study for tic tac toe and autocomplete questions
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -32,9 +32,7 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**18th Oct 2023**:
|
||||
|
||||
> I once had the [Digital Clock](https://www.greatfrontend.com/questions/user-interface/digital-clock/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook) question for Lyft interview 😦 but I had an onsite to be scheduled but they didn't have my level so it seemed futile
|
||||
> It was a technical phone interview, they were on the phone and I was live coding on something like a codepad
|
||||
> I think it was about an hour, 10 minutes of intro and 10 minutes of questions 🫠
|
||||
> I once had the [Digital Clock](https://www.greatfrontend.com/questions/user-interface/digital-clock/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook) question for Lyft interview 😦 but I had an onsite to be scheduled but they didn't have my level so it seemed futile It was a technical phone interview, they were on the phone and I was live coding on something like a codepad I think it was about an hour, 10 minutes of intro and 10 minutes of questions 🫠
|
||||
|
||||
**4th Mar 2023**:
|
||||
|
||||
|
|
|
|||
|
|
@ -3,24 +3,29 @@ title: Meta Front End Interview Questions
|
|||
sidebar_label: Meta interview questions
|
||||
---
|
||||
|
||||
:::info Latest version on GreatFrontEnd
|
||||
|
||||
Find more company guides on [GreatFrontEnd](https://www.greatfrontend.com/interviews/company?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook).
|
||||
|
||||
:::
|
||||
|
||||
## 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. 😢
|
||||
> 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.
|
||||
> 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.
|
||||
>
|
||||
> 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**:
|
||||
|
||||
|
|
@ -28,8 +33,6 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**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
|
||||
> 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)!
|
||||
|
|
|
|||
|
|
@ -44,14 +44,13 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**20th May 2025**:
|
||||
|
||||
> Honestly my interviews at Microsoft were much more chill than Amazon tbh. I do not mind the LP’s but the amount of dry runs they made me do was shocking. I even wrote assert statements before hand but turns out no execution allowed for Amazon.
|
||||
>
|
||||
> Honestly my interviews at Microsoft were much more chill than Amazon tbh. I do not mind the LP’s but the amount of dry runs they made me do was shocking. I even wrote assert statements before hand but turns out no execution allowed for Amazon.
|
||||
>
|
||||
> MSFT however, everything was smooth.
|
||||
|
||||
**8th May 2025**:
|
||||
|
||||
> I passed the Senior fe loop for a similar team to Microsoft (Copilot) last year. A team which was working on embedding copilot inside m365
|
||||
> Just a standard interview, system design was just catered to modularizing copilot so it can plug into any app
|
||||
> I passed the Senior fe loop for a similar team to Microsoft (Copilot) last year. A team which was working on embedding copilot inside m365 Just a standard interview, system design was just catered to modularizing copilot so it can plug into any app
|
||||
|
||||
**25th Apr 2025**:
|
||||
|
||||
|
|
@ -60,52 +59,31 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
**31st Jan 2025**:
|
||||
|
||||
> Hi! Just wanted to give a huge shoutout to GreatFrontEnd and say thanks for all the amazing work the team is doing! After leaving AWS a couple of months back, I was pretty nervous about the job market and didn’t know what to expect. But with GreatFrontEnd as my best friend (and, honestly, confidant lol) throughout the interview process, I was able to land interviews and offers at multiple companies for senior frontend/full stack roles.
|
||||
>
|
||||
> Thanks to you, I either got an offer or made it to the onsite stage at the following companies. In each one, I found some element of my prep from GreatFrontEnd extremely valuable:
|
||||
>
|
||||
> Vanta
|
||||
> Remitly
|
||||
> Coinbase
|
||||
> Microsoft
|
||||
> Lululemon
|
||||
> TikTok
|
||||
> Google
|
||||
>
|
||||
> One thing I did find a bit frustrating in system design rounds, though, was how most companies (Even Microsoft) focused on API design but skipped over more advanced frontend deep dives. I love the depth and deep-dives in the prep material—they really made me a better engineer—even if I didn’t always get to showcase it in interviews.
|
||||
>
|
||||
> So grateful for all the support and resources! 🙌
|
||||
> Following up on my earlier thread, I was responding to someone about my experience with Microsoft and thought I’d share it here for the community as well.
|
||||
>
|
||||
>
|
||||
> Thanks to you, I either got an offer or made it to the onsite stage at the following companies. In each one, I found some element of my prep from GreatFrontEnd extremely valuable: Vanta, Remitly, Coinbase, Microsoft, Lululemon, TikTok, Google
|
||||
>
|
||||
> One thing I did find a bit frustrating in system design rounds, though, was how most companies (Even Microsoft) focused on API design but skipped over more advanced frontend deep dives. I love the depth and deep-dives in the prep material—they really made me a better engineer—even if I didn’t always get to showcase it in interviews.
|
||||
>
|
||||
> So grateful for all the support and resources! 🙌 Following up on my earlier thread, I was responding to someone about my experience with Microsoft and thought I’d share it here for the community as well.
|
||||
>
|
||||
> I had two separate Microsoft onsites—both for Microsoft Teams and Senior Frontend positions—but they were very different.
|
||||
>
|
||||
> First onsite (I received an offer for this):
|
||||
> React-based interview – Very easy. It included a 30-minute behavioral round followed by a technical session. The question was more like an implementation of a basic to-do app (Add/Remove/Edit todos).
|
||||
> Algorithm round – LeetCode Easy/Medium. Another 30-minute behavioral session followed by coding.
|
||||
> Hiring manager round – Behavioral + System Design. This was more full-stack focused, but the interviewer gave me the option to deep dive into either frontend or backend, depending on my preference. However, the initial design needed to be full-stack. The task was to implement a part of Microsoft Teams itself. I really loved the discussion—it was very open-ended and adaptive.
|
||||
> JavaScript coding – I was asked to design an SDK in JavaScript, implementing features like throttling, retry strategies, etc. The focus was on defining contracts that others would need to adhere to. It felt more like a mix of system design and coding.
|
||||
>
|
||||
> Second onsite (No offer for this):
|
||||
> LeetCode Medium – A variation of the 3Sum problem.
|
||||
> LeetCode Hard - Still have PTSD from this 😄
|
||||
> LeetCode Medium – More of an implementation-focused merge sort problem.
|
||||
> System design + Hiring manager – Focused more on API design; the interviewer didn’t care about frontend deep dives at all.
|
||||
>
|
||||
>
|
||||
> First onsite (I received an offer for this): React-based interview – Very easy. It included a 30-minute behavioral round followed by a technical session. The question was more like an implementation of a basic to-do app (Add/Remove/Edit todos). Algorithm round – LeetCode Easy/Medium. Another 30-minute behavioral session followed by coding. Hiring manager round – Behavioral + System Design. This was more full-stack focused, but the interviewer gave me the option to deep dive into either frontend or backend, depending on my preference. However, the initial design needed to be full-stack. The task was to implement a part of Microsoft Teams itself. I really loved the discussion—it was very open-ended and adaptive. JavaScript coding – I was asked to design an SDK in JavaScript, implementing features like throttling, retry strategies, etc. The focus was on defining contracts that others would need to adhere to. It felt more like a mix of system design and coding.
|
||||
>
|
||||
> Second onsite (No offer for this): LeetCode Medium – A variation of the 3Sum problem. LeetCode Hard - Still have PTSD from this 😄 LeetCode Medium – More of an implementation-focused merge sort problem. System design + Hiring manager – Focused more on API design; the interviewer didn’t care about frontend deep dives at all.
|
||||
>
|
||||
> It’s very difficult to predict Microsoft interviews—they have no set format whatsoever. Really didn’t enjoy the second loop, but they didn’t seem to like me either—so I guess it’s even! 😅
|
||||
|
||||
**23rd Nov 2024**:
|
||||
|
||||
> Alright guys/gals I just had a frontend interview for a contract role at Microsoft. Overall it was challenging, but not overbearingly difficult.
|
||||
>
|
||||
> Alright guys/gals I just had a frontend interview for a contract role at Microsoft. Overall it was challenging, but not overbearingly difficult.
|
||||
>
|
||||
> The interview consisted of two 45 minute rounds. Interview One was a coding round in React with a senior dev. Second Interview was just a technical discussion with a principal engineer. More details about interview one:
|
||||
>
|
||||
> Implement the number/character pad using buttons (kind of like the old school flip phones) where 2 == abc, 3 == def, etc, and display the string that is being pressed. Example:
|
||||
> press 2 --> "a"
|
||||
> press 2 again --> "b"
|
||||
> press 2 after a 1 second delay --> "ba"
|
||||
> press 6 --> "bam"
|
||||
>
|
||||
>
|
||||
> Implement the number/character pad using buttons (kind of like the old school flip phones) where 2 == abc, 3 == def, etc, and display the string that is being pressed. Example: press 2 --> "a" press 2 again --> "b" press 2 after a 1 second delay --> "ba" press 6 --> "bam"
|
||||
>
|
||||
> As I said it was challenging. Honestly I don't think I'll get the contract position. I get nervous easily and trying to control my jitters was an issue in the beginning. Because of this I made a lot of silly mistakes that really slowed me down. Also, admittedly some of react skills are rusty in some parts. I'm not giving though. I think the silver lining of all this was once I got into my rhythm I was able to convey my thoughts more clearly and able to break down the problem further. Also I learned I'm not completely incompetent in react which helps 😄
|
||||
>
|
||||
> But yeah just wanted to share my experience. Hope it helps and if anyone can help me with the solution that be great!
|
||||
>
|
||||
> But yeah just wanted to share my experience. Hope it helps and if anyone can help me with the solution that be great!
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -3,23 +3,27 @@ title: Oracle Front End Interview Questions
|
|||
sidebar_label: Oracle interview questions
|
||||
---
|
||||
|
||||
:::info Latest version on GreatFrontEnd
|
||||
|
||||
Find more company guides on [GreatFrontEnd](https://www.greatfrontend.com/interviews/company?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook).
|
||||
|
||||
:::
|
||||
|
||||
## 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 Oracle.
|
||||
|
||||
**11th Jun 2025**:
|
||||
|
||||
> Interview experience for Oracle OCI India SDE-3 role
|
||||
> Round 1 (DSA) - Given a string "1+3-2", print the output "2". Handle all edge cases. No need to follow BODMAS rule
|
||||
> Round 2 (JavaScript) - Squash Object question on the GreatFrontend (https://www.greatfrontend.com/questions/javascript/squash-object?practice=practice&tab=coding)
|
||||
> Round 3 (DSA) - a. Similar elements between two array. arr1 = [1, 2, 2, 4, 5] arr2 = [3, 2, 4, 2] . The output should be [2, 2, 4]. b. Follow up on the same question by giving matrix instead of the two array.
|
||||
> Round 4 (System Design) - Design the frontend of Jira Board
|
||||
> Round 5 (System Design) - Design a backend system to block a bot request
|
||||
> Round 6 (Coding + System Design) - a. Debug a react app. (Functionality is missing from the App. Fix and make the functionality of the App work)
|
||||
> b. High level frontend architecture of the app that you are currently working
|
||||
> c. Design a backend system for URL shortener
|
||||
>
|
||||
>
|
||||
> And at least one behavioural question in each round.
|
||||
> Interview experience for Oracle OCI India SDE-3 role
|
||||
>
|
||||
> 1. Round 1 (DSA): Given a string "1+3-2", print the output "2". Handle all edge cases. No need to follow BODMAS rule
|
||||
> 1. Round 2 (JavaScript): Squash Object question on the GreatFrontend (https://www.greatfrontend.com/questions/javascript/squash-object?practice=practice&tab=coding)
|
||||
> 1. Round 3 (DSA): a. Similar elements between two array. arr1 = [1, 2, 2, 4, 5] arr2 = [3, 2, 4, 2] . The output should be [2, 2, 4]. b. Follow up on the same question by giving matrix instead of the two array.
|
||||
> 1. Round 4 (System Design): Design the frontend of Jira Board
|
||||
> 1. Round 5 (System Design): Design a backend system to block a bot request
|
||||
> 1. Round 6 (Coding + System Design): (a) Debug a react app. (Functionality is missing from the App. Fix and make the functionality of the App work), (b) High level frontend architecture of the app that you are currently working, (c) Design a backend system for URL shortener
|
||||
>
|
||||
> And at least one behavioural question in each round.
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -9,28 +9,27 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**21st Aug 2024**:
|
||||
|
||||
> I had a tree / graph traversal type problem for Palantir phone screen. More leetcode-y and less FE-specific. Uber was building a small app in the UI. React GreatFrontEnd problems were super helpful with clearing that round
|
||||
> I had a tree / graph traversal type problem for Palantir phone screen. More leetcode-y and less FE-specific. Uber was building a small app in the UI. React GreatFrontEnd problems were super helpful with clearing that round
|
||||
|
||||
**1st Jun 2024**:
|
||||
|
||||
> Search the server for Palantir. You’ll get a lot of tips here! Otherwise, I think this all depends on how prepared you already feel for leetcode and GreatFrontEnd questions. One week isn’t a lot of time, so I’d focus on your weakest topics and topics most likely to be asked
|
||||
> I mentioned leetcode because other people here who interviewed with Palantir said they had leetcode questions. Using the interview as just a practice is good too, if you really don’t wanna study leetcode, even just the questions posted on here.
|
||||
> Search the server for Palantir. You’ll get a lot of tips here! Otherwise, I think this all depends on how prepared you already feel for leetcode and GreatFrontEnd questions. One week isn’t a lot of time, so I’d focus on your weakest topics and topics most likely to be asked I mentioned leetcode because other people here who interviewed with Palantir said they had leetcode questions. Using the interview as just a practice is good too, if you really don’t wanna study leetcode, even just the questions posted on here.
|
||||
|
||||
**29th Mar 2024**:
|
||||
|
||||
> Hi for Palantir, it was a leetcode style question. I had to validate a graph and there were some additional questions about time and space complexity afterwards.
|
||||
> Hope this is not too late. The interviewer determined if it passed or not. There were no automatic tests.
|
||||
> Hi for Palantir, it was a leetcode style question. I had to validate a graph and there were some additional questions about time and space complexity afterwards. Hope this is not too late. The interviewer determined if it passed or not. There were no automatic tests.
|
||||
|
||||
**26th Mar 2024**:
|
||||
|
||||
> Just finished up a tech screen with Palantir. Pretty leetcode-y. Was asked to take a text and a query of two words, an integer k, and return the indicies of where the distance between the two words is `<= k`. Got a semi-optimal solution, but wasn't the most optimal (we went through the most optimal after). Was essentially just a text document (i.e. no test cases, I wrote the function signature, no ability to run the code). We'll see what happens 🤷♂️
|
||||
> Just finished up a tech screen with Palantir. Pretty leetcode-y. Was asked to take a text and a query of two words, an integer k, and return the indicies of where the distance between the two words is `<= k`. Got a semi-optimal solution, but wasn't the most optimal (we went through the most optimal after). Was essentially just a text document (i.e. no test cases, I wrote the function signature, no ability to run the code). We'll see what happens 🤷♂️
|
||||
|
||||
**25th Mar 2025**:
|
||||
|
||||
> I have one tomorrow with them for a full-stack role leaning frontend. Here's what the recruiter told me to expect for the interview process: - Technical Interview — Leetcode, DSA
|
||||
>
|
||||
> - 2 Interviews
|
||||
> - Web Dev
|
||||
> - Decomposition Interview (System Design)
|
||||
> - Hiring Manager Interview
|
||||
> - Web Dev
|
||||
> - Decomposition Interview (System Design)
|
||||
> - Hiring Manager Interview
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -3,32 +3,33 @@ title: Pinterest Front End Interview Questions
|
|||
sidebar_label: Pinterest interview questions
|
||||
---
|
||||
|
||||
:::info Latest version on GreatFrontEnd
|
||||
|
||||
Find more company guides on [GreatFrontEnd](https://www.greatfrontend.com/interviews/company?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook).
|
||||
|
||||
:::
|
||||
|
||||
## 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 Pinterest.
|
||||
|
||||
**3rd Apr 2024**:
|
||||
|
||||
> I tríed few months ago. I did the first round only for a release engineer position. The problem is called Can you win. And it is similar to that in Leetcode jump and jump II.
|
||||
> They are medium level problems. At least you can solve 2 in 20-30 mins. They recommend that.
|
||||
> I tríed few months ago. I did the first round only for a release engineer position. The problem is called Can you win. And it is similar to that in Leetcode jump and jump II. They are medium level problems. At least you can solve 2 in 20-30 mins. They recommend that.
|
||||
|
||||
**4th Feb 2024**:
|
||||
|
||||
> Last time I interviewed for a FE engineer role at Pinterest in 2019, it was 3 LC rounds. one required a trie data structure to solve a string DSA. "Given a stream of comments, detect inappropriate language". I would be interested to know if they do have a true FE track.
|
||||
> Just re-read this question. I thought you were asking about onsite. The question I got for phone screen was:
|
||||
>
|
||||
> Last time I interviewed for a FE engineer role at Pinterest in 2019, it was 3 LC rounds. one required a trie data structure to solve a string DSA. "Given a stream of comments, detect inappropriate language". I would be interested to know if they do have a true FE track. Just re-read this question. I thought you were asking about onsite. The question I got for phone screen was:
|
||||
>
|
||||
> Given an array of integers like [1,2,0,4,3] and a starting index, return true if you are able to get to a "0" value. Return false if you can't. Each value in the array is how many steps to the left or right you can move. You have to take that many steps exactly. If you are at the start or end of the array and you have movements left, you can wrap around to the opposite side.
|
||||
>
|
||||
> ex: same array, but startingIdx = 3. It returns true because you can go 1 step to the right, then 3 steps to the right starting at 0.
|
||||
>
|
||||
> So this is backtracking plus keeping track of which indexes you've finished evaluating. I've never seen this on LC. I think I spent 15 mins trying to voice out the solution. 15 minutes coding. Finished. 15 minutes of talking back and forth about Pinterest. Ended the interview 15 minutes early.
|
||||
> hilariously, i got the same question on the onsite and then there was a follow up question to this which was: you've used recursion to solve htis, but can you solve this without it? So instead of a (call) stack of nodes to process, use a queue,
|
||||
> Pinterest was the worst interview experience I've gone through for frontend. Position asked for React experience, didn't write a single line of JavaScript. Only Python for DSA. So it would be a breath of fresh air if they did create an FE track since 2019
|
||||
> Yup, passed the phone screen, went to onsite. Didn't get offer because I wasn't very good with string DSA at the time
|
||||
>
|
||||
> ex: same array, but startingIdx = 3. It returns true because you can go 1 step to the right, then 3 steps to the right starting at 0.
|
||||
>
|
||||
> So this is backtracking plus keeping track of which indexes you've finished evaluating. I've never seen this on LC. I think I spent 15 mins trying to voice out the solution. 15 minutes coding. Finished. 15 minutes of talking back and forth about Pinterest. Ended the interview 15 minutes early. hilariously, i got the same question on the onsite and then there was a follow up question to this which was: you've used recursion to solve htis, but can you solve this without it? So instead of a (call) stack of nodes to process, use a queue, Pinterest was the worst interview experience I've gone through for frontend. Position asked for React experience, didn't write a single line of JavaScript. Only Python for DSA. So it would be a breath of fresh air if they did create an FE track since 2019 Yup, passed the phone screen, went to onsite. Didn't get offer because I wasn't very good with string DSA at the time
|
||||
|
||||
**4th Feb 2024**:
|
||||
|
||||
> yes, afaik they have a FE track and a full stack track for interviews. thats what the recruiter alluded to because im teetering between FE and full stack and she mentioned that the interview might be different if i wanted to focus on full stack
|
||||
> yes, afaik they have a FE track and a full stack track for interviews. thats what the recruiter alluded to because im teetering between FE and full stack and she mentioned that the interview might be different if i wanted to focus on full stack
|
||||
|
||||
**12th Sep 2023**:
|
||||
|
||||
|
|
|
|||
|
|
@ -3,13 +3,19 @@ title: Reddit Front End Interview Questions
|
|||
sidebar_label: Reddit interview questions
|
||||
---
|
||||
|
||||
:::info Latest version on GreatFrontEnd
|
||||
|
||||
Find more company guides on [GreatFrontEnd](https://www.greatfrontend.com/interviews/company?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook).
|
||||
|
||||
:::
|
||||
|
||||
## 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 Reddit.
|
||||
|
||||
**14th May 2025**:
|
||||
|
||||
> Hi! You should prepare JavaScript fundamental and building UI problems with html, and JavaScript
|
||||
> You should prepare JavaScript fundamental and building UI problems with html, and JavaScript
|
||||
|
||||
**20th Feb 2025**:
|
||||
|
||||
|
|
@ -17,16 +23,12 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**27th Oct 2024**:
|
||||
|
||||
> Yes I just had Reddit interview.
|
||||
>
|
||||
> Phone screen - ask some generic questions like GET & POST, XSS, implement feed (just talk about it). 20 mins simple coding with arrays and filters.
|
||||
>
|
||||
> Onsite
|
||||
> coding: manipulating arrays
|
||||
> system design: design quiz like game app
|
||||
> UI frontend coding: form related
|
||||
> - hiring manager round
|
||||
>
|
||||
> I just had Reddit interview.
|
||||
>
|
||||
> - Phone screen - ask some generic questions like GET & POST, XSS, implement feed (just talk about it). 20 mins simple coding with arrays and filters.
|
||||
> - Onsite coding: manipulating arrays system design: design quiz like game app UI frontend coding: form related
|
||||
> - Hiring manager round
|
||||
>
|
||||
> Reddit focus on communication and collaboration. No reactjs, just prep for JavaScript and html.
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -3,6 +3,12 @@ title: Shopify Front End Interview Questions
|
|||
sidebar_label: Shopify interview questions
|
||||
---
|
||||
|
||||
:::info Latest version on GreatFrontEnd
|
||||
|
||||
Find more company guides on [GreatFrontEnd](https://www.greatfrontend.com/interviews/company?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook).
|
||||
|
||||
:::
|
||||
|
||||
## 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 Shopify.
|
||||
|
|
@ -22,7 +28,7 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
**13th Feb 2024**:
|
||||
|
||||
> Just wanted to say, I used your site for 1 month to prep for my interviews at Shopify, and I got the job! Staff level engineer.
|
||||
>
|
||||
>
|
||||
> Just saying thank you and honestly, no complaints. Loved the site, loved the system design questions. Everything was very, very useful.
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Twitter Front End Interview Questions
|
||||
title: X/Twitter Front End Interview Questions
|
||||
sidebar_label: Twitter interview questions
|
||||
---
|
||||
|
||||
|
|
@ -32,7 +32,6 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**6th Nov 2024**:
|
||||
|
||||
> I had one last month for their product web engineer role. They don't have recruiters at xai. It's the engineers in the team that filter resumes, call candidates.The first round was a short 15 mnts google meets call, the engineer went over what they are building - they are basically upgrading a legacy app built by twitter engineers years ago into react and looking for someone who has both react as well as react native skills.
|
||||
> Received a rejection after the initial chat.
|
||||
> I had one last month for their product web engineer role. They don't have recruiters at xai. It's the engineers in the team that filter resumes, call candidates.The first round was a short 15 mnts google meets call, the engineer went over what they are building - they are basically upgrading a legacy app built by twitter engineers years ago into react and looking for someone who has both react as well as react native skills. Received a rejection after the initial chat.
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -27,19 +27,16 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**3rd Jun 2025**:
|
||||
|
||||
> I was asked a reactjs based question although I majorly prepared for dsa and JS type questions based on the questions asked previously. What I've learned and observed about Uber's FE process is that they can ask pretty random questions.
|
||||
> I guess recruiters are not in sync with the interviewers. Or it feels like it is more up to the interviewers on what they ask. I watched some YT videos of people on their uber interview experience and literally to each one of them dsa was asked.
|
||||
> I was asked a reactjs based question although I majorly prepared for dsa and JS type questions based on the questions asked previously. What I've learned and observed about Uber's FE process is that they can ask pretty random questions. I guess recruiters are not in sync with the interviewers. Or it feels like it is more up to the interviewers on what they ask. I watched some YT videos of people on their uber interview experience and literally to each one of them dsa was asked.
|
||||
|
||||
**7th May 2025**:
|
||||
**7th May 2025**:
|
||||
|
||||
> Just gave BPS round of Uber and gotta say, Uber has quality problems!
|
||||
> I thought it would be DSA as the recruiter had mentioned. But I guess you can’t trust recruiters nowadays.
|
||||
> Question was “create a utility in JS to send data in batches with a timeout. So, as soon as a batch size is reached, send the data right away and start the timeout. If timeout happens before batch is filled, send the batch as it is and start the timer again.”
|
||||
> Also, I asked the interviewer for what to prepare for DSA round and he said array, trees, graphs, traversals, but he also mentioned that Uber is trying to get away from DSA for frontend roles and keep it frontend focused and slowly they are doing it.
|
||||
> Just gave BPS round of Uber and gotta say, Uber has quality problems! I thought it would be DSA as the recruiter had mentioned. But I guess you can’t trust recruiters nowadays. Question was “create a utility in JS to send data in batches with a timeout. So, as soon as a batch size is reached, send the data right away and start the timeout. If timeout happens before batch is filled, send the batch as it is and start the timer again.” Also, I asked the interviewer for what to prepare for DSA round and he said array, trees, graphs, traversals, but he also mentioned that Uber is trying to get away from DSA for frontend roles and keep it frontend focused and slowly they are doing it.
|
||||
|
||||
**5th May 2025**:
|
||||
|
||||
> Ik someone who gave Uber's SDE II web interview, in short prepare everything, there were 5 rounds -
|
||||
> Ik someone who gave Uber's SDE II web interview, in short prepare everything, there were 5 rounds -
|
||||
>
|
||||
> 1. DSA - leetcode styled and js based
|
||||
> 2. Web Fundamentals - HTML, CSS, JS, APIs, Internet
|
||||
> 3. Frontend System Design
|
||||
|
|
@ -48,12 +45,10 @@ These tips were shared by [GreatFrontEnd](https://www.greatfrontend.com/?utm_sou
|
|||
|
||||
**19th Jan 2025**:
|
||||
|
||||
> For Uber FE SDE2 check mapAsyncLimit question.
|
||||
> Since you're interviewing for their Bengaluru office, prepare behavioral well and do google calender system design
|
||||
> For Uber FE SDE2 check mapAsyncLimit question. Since you're interviewing for their Bengaluru office, prepare behavioral well and do google calender system design
|
||||
|
||||
**6th Dec 2024**:
|
||||
|
||||
> I've my uber onsite coming up. First 2 rounds are leetcode styled coding and System design.
|
||||
> abt me: 7 YOE
|
||||
> I've my uber onsite coming up. First 2 rounds are leetcode styled coding and System design. abt me: 7 YOE
|
||||
|
||||
For more insider tips, visit [GreatFrontEnd](https://www.greatfrontend.com/?utm_source=frontendinterviewhandbook&utm_medium=referral&gnrs=frontendinterviewhandbook)!
|
||||
|
|
|
|||
|
|
@ -49,9 +49,9 @@ module.exports = {
|
|||
'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',
|
||||
'companies/atlassian-front-end-interview-questions',
|
||||
'companies/uber-front-end-interview-questions',
|
||||
'companies/apple-front-end-interview-questions',
|
||||
'companies/dropbox-front-end-interview-questions',
|
||||
'companies/linkedin-front-end-interview-questions',
|
||||
'companies/lyft-front-end-interview-questions',
|
||||
|
|
|
|||
Loading…
Reference in New Issue