Skip to contentSkip to footer

Senior Frontend Engineer Interview Questions

Salaries
Interviews

1,542 senior frontend engineer interview questions shared by candidates

Generic technical questions with the EM which were fair. The problem is more the technical task – the two people running the interview had zero empathy and no way of making the session a comfortable experience. Asked specific questions about cases with promises and such while in total silence, which led to pressure and very slow response on my side. Gotta admit I was missing some of the bits, and that's on me, but I highly disagree with such an approach – letting people use google is not gonna make people more comfortable – and testing devs on one specific argument is never gonna tell you anything about their seniority.
avatar

Senior Frontend Engineer

Interviewed at Photobox

3.6★
Sep 2, 2022

Generic technical questions with the EM which were fair. The problem is more the technical task – the two people running the interview had zero empathy and no way of making the session a comfortable experience. Asked specific questions about cases with promises and such while in total silence, which led to pressure and very slow response on my side. Gotta admit I was missing some of the bits, and that's on me, but I highly disagree with such an approach – letting people use google is not gonna make people more comfortable – and testing devs on one specific argument is never gonna tell you anything about their seniority.

1. Given a set of wireless routers that are interconnected, write an algorithm that finds the longest distance between these routers 2. Was supposed to be a system design interview, but this was the interviewer who arrived late and had no idea what he was supposed to interview for. 3. Design algorithm to instruct a robot how to go through a maze 4. Implement an auto-complete // trie implementation 5. Behavioral questions
avatar

Senior Software Engineer (FrontEnd)

Interviewed at Google

4.4★
May 7, 2022

1. Given a set of wireless routers that are interconnected, write an algorithm that finds the longest distance between these routers 2. Was supposed to be a system design interview, but this was the interviewer who arrived late and had no idea what he was supposed to interview for. 3. Design algorithm to instruct a robot how to go through a maze 4. Implement an auto-complete // trie implementation 5. Behavioral questions

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.6★
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.

Viewing 881 - 890 interview questions

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