DEV Community

Discussion on: What’s your favorite JS interview question?

Collapse
 
ky1e_s profile image
Kyle Stephens • Edited

Solid approach.

Remember, interviewing is a two-way street. It's just as much about you assessing a prospective employer/boss as it is them assessing you.

If an interviewer tries to "catch you out" with some arbitrary, illegible code or tries to belittle you because you don't know answers to some esoteric problem then it says more about them and their approaches to work than it does about your knowledge/abilities.

Collapse
 
niorad profile image
Antonio Radovcic

Most def, it's more a conversation-starter, without a "right" answer. If they can argue their claim, perfect.

I think I could argue why React should always be used, sometimes be used, and never be used :-)

Thread Thread
 
ky1e_s profile image
Kyle Stephens

Absolutely. Evidence about ways of thinking/approaching a problem are much more revealing about a candidate than their ability to interpret obtuse code like a compiler.