Senior Frontend Engineer Interview Questions

1,548 senior frontend engineer interview questions shared by candidates

Difference between callbacks and promises. What would happen if you resolve promise twice? General questions about React: what is it, what is reconciliation, Virtual DOM etc. Would Next.js be a good fit for application like GMail?
avatar

Senior Frontend Engineer

Interviewed at FINN

4
Sep 7, 2022

Difference between callbacks and promises. What would happen if you resolve promise twice? General questions about React: what is it, what is reconciliation, Virtual DOM etc. Would Next.js be a good fit for application like GMail?

1. Given binary matrix write algorithm to find rectangle with largest area. e.g. [ [1,0,0,0] [0,1,1,1] [0,1,1,1] [0,0,0,0] 2. Analog to MS paint where you click a point, and all connected areas are auto filled with a color, you're given a matrix/grid with random number in it, so write a function that takes as parameters: canvas (matrix), x/y coordinates, and the color number to replace with. e.g. coordinates: 1,3, newColor:3 [[0,1,1,2,0,1] [1,0,2,2,1,1] [1,0,2,2,2,0]] so all adjacent 2's should be replaced with 3 3. Design front-end for an online chess game 4. Manager interview, just conversation about the interview process and about your background
avatar

Senior Software Engineer - Frontend

Interviewed at Microsoft

4
May 7, 2022

1. Given binary matrix write algorithm to find rectangle with largest area. e.g. [ [1,0,0,0] [0,1,1,1] [0,1,1,1] [0,0,0,0] 2. Analog to MS paint where you click a point, and all connected areas are auto filled with a color, you're given a matrix/grid with random number in it, so write a function that takes as parameters: canvas (matrix), x/y coordinates, and the color number to replace with. e.g. coordinates: 1,3, newColor:3 [[0,1,1,2,0,1] [1,0,2,2,1,1] [1,0,2,2,2,0]] so all adjacent 2's should be replaced with 3 3. Design front-end for an online chess game 4. Manager interview, just conversation about the interview process and about your background

Round 2 - Architecture - 1 hour - The Frontend team lead took this round. Problem 1 - He started sharing his screen and told me about their platform and the projects they would pick up next. He showed me their UI to write Scala code for a pipeline and asked me to convert that flow to a No/Low code solution. He was continuously using jargon that someone who has already worked with their products knows - such as gems. I had to explicitly ask him to slow down and explain the flow in detail, but he constantly failed to do so. He was talking like I was a member of the team and knew everything about their product. He failed to explain his thoughts clearly and was constantly lacking communication skills. I created wireframes despite lacking context and did my best to give him a solution. He also accepted the solution. Problem 2 - Then he showed me their search component which had an icon that was trailing the text you write in that input. This icon had a jitter and delay as it was moving along with the text. He asked me how I would build and improve this component. I gave him a solution that removed this jitteriness that it had previously. He was skeptical about the solution although my solution was 100% right, I checked that post the interview as well. Problem 3 - Next up, he asked me how I would add a hashtag autocomplete in the same search input. I gave him the solution and he accepted it. He then started talking about a scrolling issue in the same, but he failed to explain what the problem was. We ended the round here. It felt more like a consultancy call instead of an interview where I was solving their product's problems and planning for new features. Result - Moved to the next round.
avatar

Senior Frontend Engineer

Interviewed at Prophecy

3.7
Oct 10, 2024

Round 2 - Architecture - 1 hour - The Frontend team lead took this round. Problem 1 - He started sharing his screen and told me about their platform and the projects they would pick up next. He showed me their UI to write Scala code for a pipeline and asked me to convert that flow to a No/Low code solution. He was continuously using jargon that someone who has already worked with their products knows - such as gems. I had to explicitly ask him to slow down and explain the flow in detail, but he constantly failed to do so. He was talking like I was a member of the team and knew everything about their product. He failed to explain his thoughts clearly and was constantly lacking communication skills. I created wireframes despite lacking context and did my best to give him a solution. He also accepted the solution. Problem 2 - Then he showed me their search component which had an icon that was trailing the text you write in that input. This icon had a jitter and delay as it was moving along with the text. He asked me how I would build and improve this component. I gave him a solution that removed this jitteriness that it had previously. He was skeptical about the solution although my solution was 100% right, I checked that post the interview as well. Problem 3 - Next up, he asked me how I would add a hashtag autocomplete in the same search input. I gave him the solution and he accepted it. He then started talking about a scrolling issue in the same, but he failed to explain what the problem was. We ended the round here. It felt more like a consultancy call instead of an interview where I was solving their product's problems and planning for new features. Result - Moved to the next round.

Questions like: - How was your input/output in the discovery level of a new product or new feature? - As a Front-end, an OKR converted to a feature to be implemented based on what do you measure the impact of this feature to the business.
avatar

Senior Frontend Engineer

Interviewed at Flix

4.1
May 18, 2024

Questions like: - How was your input/output in the discovery level of a new product or new feature? - As a Front-end, an OKR converted to a feature to be implemented based on what do you measure the impact of this feature to the business.

Viewing 991 - 1000 interview questions

Glassdoor has 1,548 interview questions and reports from Senior frontend engineer interviews. Prepare for your interview. Get hired. Love your job.