DEV Community

loading...

Discussion on: Rejected by Facebook

Collapse
bytebodger profile image
Adam Nathaniel Davis Author • Edited

This really illustrates the downside of wanting/expecting feedback - because even when you do get feedback, it can often be bad, useless, or comically inaccurate. There are a lotta things that I know I'm "weak" in. And if one of those so-called weaknesses were called out in the feedback, I'd truly just shrug and move on. But I've had interviews before where, after being eliminated, they told me that I was "weak" in some area - some area that is literally one of my strongest skills. And like you, I laughed out loud.

Unfortunately, I usually know why someone has tried to paint one of my strongest skills as being "weak": Because they have some litmus test in that area with which I wasn't familiar. And when I didn't have that litmus test in my back pocket, they wrote me off as being "weak" in that area.

A great example of this happened the other day during a different interview (not for FB). I was coding stuff with one of their devs and I wrote a looped set of asynchronous Axios calls to fetch a series of data. The interviewer pointed out that my approach would've probably been better if I'd used Promise.all. And he was right. I admitted that I knew about Promise.all but I just haven't made myself familiar-enough with it and I need to brush up on it.

In this particular incident, the guy seemed cool and I don't think he treated it as any kinda disqualifying factor. This was probably helped by the fact that he seemed to like the rest of my solution. But in other situations, with other evaluators, not only would you be eliminated, but they'd also mark you down as being "weak" with asynchronous calls, or even, "weak" with JavaScript overall.

Forem Open with the Forem app