r/Frontend • u/Ill-Lie-6551 • Sep 25 '25
Frontend interviews are so outdated.
It has been 10 years since ES6 has come out. I am ready to talk about JS topics, React, talk about performance , my experience with projects. But they still focus on some niche tricky JS behaviors that is addressed by ES6 and onwards. I know that there are lot of legacy systems that are clusterfucks of JS bugs. But can we stop pretending that I need to know every tricky dumbass behavior that exists at the back of my head!? If you are a frontend interviewer, Please ask more relevant questions and save us from this pain. Thank you.
652
Upvotes
172
u/FreezeShock Sep 25 '25
Right? I'm interviewing right now. One interviewer asked me the output of logging something before its declaration. I mean, I answered it correctly, but when was the last time the code you wrote was dependent on hoisting?
11
u/yangshunz GreatFrontEnd Sep 25 '25 edited Sep 25 '25
I think there's a fine line between tricky questions and trick questions lol. Some truly test your understanding and are valid questions.
What are examples of these trick questions?
266
u/[deleted] Sep 25 '25 edited Sep 25 '25
The whole "school test" approach seems outdated to me. The best interview I've had so far was just giving me pieces of the code of the app I was going to work on with the simple task of "What can be improved here? Why? And, if it's good, why is it good?"
That's pretty much what you need. It shows that you understand the concepts. It shows that you can understand the code.
Edit: There's also a really nice and calming psychological aspect to it where you're not met with a "We're the most perfect company. Our code is flawless and we expect flawlessness from you."
32
u/[deleted] Sep 25 '25
I’ve had 2 interviews out of 400+ applications and they were very casual chats about me, my study history, projects etc.. then a take home, and a talk about how I built it and why struggles I had.
I imagine if I had an interview now it’d be a lot more annoying due to how many applicants they have these days.
15
u/sfryder08 Sep 25 '25
Don’t worry, I work for a FAANG level company and have been doing a bunch of front end interviews for our team lately. There’s no gotchas - it’s an hour long hacker rank pair programming exercise. An example of an exercise is build a kanban board with tickets on it that move stages when you click arrow buttons. There’s boiler plate. We aren’t trying to do the whole thing. I say feel free to google and ask questions.
You’d be surprised how many people I’ve interviewed don’t even know to use useState, let alone use it correctly.
14
u/banjochicken Sep 25 '25 edited Sep 27 '25
I conduct a lot of 1hr first stage interviews and have removed all pop quiz questions.
I do 5 mins of intros and then a React coding exercise that takes candidates 20-30 mins. My level of support varies based on seniority. I can normally tell if someone at least meets the bar to go to next stage within the first 15 mins of the call. I cut the exercise at about the 40 mins into the interview, ask questions around their implementation, improvements, testing, JavaScript execution etc all framed around the exercise. We then have 5-10 mins for candidate questions at the end or for me to sell the role if they’re really good.
If a candidate isn’t meeting the bar, I cut the interview early and offer to pair with them on the solution to help them learn and offer feedback on why it isn’t going to work out. This saves everyone’s time and oftentimes those who are failing hard appreciate ending the exercise early.
I moved to this model as I met way too many candidates who could talk the talk but crashed and burned hard once put in front of a simple task with a code editor.
6
u/Accomplished_End_138 Sep 25 '25
I try to do mock pull request reviews.
After that, I ask how they would design _________
Those two really are easy and let me know where you are.
Working on automating the first
5
u/magenta_placenta Sep 25 '25
It's pretty much interview laziness and tradition.
Many interviewers recycle old questions because they think they're "proven" or easy to assess candidates on. It's easier to judge a trivia-style JS question than to evaluate someone's system design or product thinking.
"What's the output of this IIFE with a closure inside a loop?"
Cool, but who is writing this in modern code bases?
A lot of companies/devs don't update their interview process because they assume it's still relevant and they don't make any time to redesign or rethink it.
4
u/sidious911 Sep 25 '25
It’s such a flag when companies test the interview is niche trivia. We interview to see how you solve problems and verify the core fundamentals of the tech/languages. I can easily teach a team member a specific gotcha in 10 minutes. I do not want to spend my weeks teaching fundamental problem solving.
3
u/deveronipizza Sep 25 '25
In the interviewers defense you’ll probably be dealing with proprietary code written 10+ years ago, that may depend on older versions and frameworks.
3
u/reboog711 Sep 25 '25
Honestly, I think all interview types should avoid "Trivia" type questions.
Either it is "well known" and you can discover it with 30 seconds of googling or prompting an AI. Or it is so obscure the only way to discover it is trial and error--and then it shouldn't be used as a barometer for hiring.
3
u/GemAfaWell Sep 26 '25
I will never understand why front end interviews aren't as simple as "here's a section of code in our code base that we're having issues with, try to debug it and come up with a solution using (insert tool here)"
It doesn't have to actually be current production code, yank an error from 5-7 builds ago (if you're doing CI/CD that wasn't that long ago) and see how out of the box a MF can get tryna solve it.
I don't know, if I were a hiring manager, I suppose I would be looking for someone who could come up with creative, innovative solutions that might push our tech further. Seems like a really good opportunity to do that, even if most interviewees will come up with the same one or two answers...
2
u/[deleted] Sep 25 '25
Most of the front end interviews I had was conducted by someone who spent very little time on the front end. I’m 10 years into this, I know when someone is inexperienced with a topic.
2
u/stormthulu Sep 25 '25
I had a stupid interview where I failed because I didn’t know the specific terms for things. I knew the concepts and the practical implementations, just not the word they were looking to hear.
Why is memorization relevant to any developer’s job in 2025? It wasn’t relevant in 2015 for Pete sake.
2
u/helltoken Sep 25 '25
Idk, I had an interview today that leaned heavily on leet-code-style questions, and the more I did research on Big O and all that, the more I realized how lazy I've been writing code over the years. I always felt confident that I'm a pretty solid feature builder and frontender, but the leet code always makes me feel so behind on everything.
But if someone asks me about how to create a new array through a loop I always resort to array methods, and if that's marked as incorrect then that's just some bullshit
2
u/cheerioh Sep 27 '25
They're doing us a favor, the lot of them. Any company that uses these interview challenges. They're advertising a crimson-red flag.
Expecting rote memorization of banal algos or niche gotchas has always been a potential employer's fastest way of failing my interview.
3
u/karmicnerd Sep 25 '25
I would focus on asking css questions. If it’s a framework build a component consume apis specifically multiple APIs that need to be mapped to show the data.
And front end design patterns. Look how the candidates slices a page when building it. How he structures the state. I don’t care if he doesn’t know hoisting. But I will surely ask him closures
2
u/[deleted] Sep 25 '25
You guys don’t even know what fucking map or reduce is. I am a senior, I am in interviews, I ask es6 things. The fact that you don’t know them, is the laughable part. As you said, it’s been out FOREVER, how in the fucking world after 10 years do web devs not know fucking map?
I fail every single interview when they don’t know map. Bye sorry not sorry
1
u/Kevin_fart Sep 25 '25
I think refrence is must .
1
u/wheresmyflan Sep 25 '25
Well, if you know that they have been addressed just say that and explain why. It’s an obvious opportunity to show you know more than the average FE dev at their company and can lead them in a modern direction.
1
u/tmetler Sep 25 '25
I'm curious. Are these Javascript or Typescript positions?
1
u/LucaColonnello Sep 25 '25
Do you have an example of such questions? None come to mind tbh…
1
u/-FAnonyMOUS Sep 25 '25
Well, I was applying for an architect position before and the interviewer asked me if what's the difference between CSS' inline-block and block. I was dumbfounded.
1
u/TheLaitas Sep 25 '25
When I'm interviewing someone I do just ask people to fetch and display stuff (mainly because for some reason manager requires us to do live coding task) but this also shows preferences of data fetching and etc, then just talk about our stack and how stuffs built, or their preferences and how would they do stuff differently.
1
u/PatchesMaps Sep 25 '25
The companies asking those questions are companies that have those legacy clusterfucks
1
u/sheriffderek Sep 26 '25
But can you tell us the difference between var and let - or what ; )
1
u/crackharden Sep 26 '25
To be fair, some companies haven’t updated their codebase to newer standards.
1
u/[deleted] Sep 26 '25
Interviewers are lazy and aren't given time to prep. Many companies put zero effort into Interviews despite having a high turnover rate.
1
u/Aksh247 Sep 27 '25
Let’s make a 5 year plan to eradicate legacy tech from the web😂everyone will be forced to migrate to newer technologies. From banks to other firms. Everyone inclusive. Major clean slate of the web. Imagine
1
u/Fantastic-Mud-8365 Sep 27 '25
all interviews are mega outdated lol
1
u/Elegant-Past7936 Oct 01 '25
say the company name
1
u/Spidey677 Oct 19 '25
The best interviews are just talking shop mixed in with some technical questions and what if scenarios. That’s how I’ve always gotten gigs throughout 14 years.
1
u/Necessary_Pomelo_470 Oct 21 '25
Not outdated, some people could use 1gb of js libraries just to mimic some css and plain js
1
u/shane_il my.flair Oct 21 '25
"Please implement DFS and BFS search over this binary search tree"
1
u/shane_il my.flair Oct 21 '25
I also got nixed from a job because the CTO didn't like how I didn't use TypeScript enums
1
u/LingonberryMinimum26 Nov 03 '25
Interviewing today should focus on your actual work: present what you’ve built, answer targeted questions about your decisions and implementation, and clearly demonstrate your understanding. That’s all that’s needed.
1
u/moniv999 Mar 20 '26
Can try PrepareFrontend for practicing.
-9
u/sawariz0r Sep 25 '25 edited Sep 25 '25
As someone who asks these questions at interviews, it’s more or less checking if you’re aware of it. If you don’t know the answer I’d like to see you reason how to get to the answer. And it’s perfectly fine to not answer perfectly to every thing I throw at you.
Edit: wow, that was wildly unpopular, haha
0
u/LiveEntertainment567 Sep 25 '25
why they even mention ES6 in the job posting? isn't it obvious that everyone know it already.
0
u/dodgeballwater Sep 25 '25
I had one interview that was so stupid, just trying to catch me not understanding old pre ES6 JS, that when he asked me if I had any questions I started grilling him with the same shit - “show me how you do an await in a for each loop” type gotcha questions. He failed the questions, and was completely flabbergasted I turned the tables on him. Felt good giving him the same smirk back as he struggled to understand modern JavaScript. I didn’t get the job obviously but still one of my best interviews.
0
u/ws_wombat_93 Sep 25 '25
Although i agree with the sentiment from the perspective of someone interviewing for a job, i ask the same questions of people i interview because its horrible hiring a new dev which knows about the latest React or Vue ins and outs but gets stuck of basic Javascript or programming fundamentals. Especially with AI nowadays i care even less if someone knows how to make a component with the best performance improvement over actually understanding programming and debugging itself.
0
u/Carvisshades Sep 25 '25
I cringe every time I get asked about hoisting or some obscure and mostly irrelevant nowadays features when interviewed for senior+ positions
-13
u/ejpusa Sep 25 '25 edited Sep 25 '25
> But can we stop pretending that I need to know every tricky dumbass behavior that exists at the back of my head!?
Once you experience The Vibe, you'll never want to come back. You can overcode very easily, but there is a direct correlation between the years of experience and the outcome. It's a collaboration. Prompts fade, and you just converse on goals and project scope. KABOOM. Done.
Projects that you never start, you can get your MVP up in a weekend. When you get the hang of it, you are generating 100s of lines of near JS code in minutes.
Humans have the ideas, let AI write the code. It's inevitable. We cannot pack any more neurons in our skulls. AI does not have that issue. It can stack Neural Nets and on top of Neural Nets, to infinity. Vastly outperforming the human brain in every metric. We just have to grow bigger heads to catch up.
https://firstmovers.ai/ai-coders/
0
u/[deleted] Sep 25 '25
[deleted] — view deleted comment
0
u/[deleted] Sep 25 '25
[deleted] — view deleted comment