Try this experiment. When you get to ask questions in the interview, instead of being nice and asking tings like "what's your data science stack" or "how important is testing here" give them a whiteboard. Give your future boss a whiteboard. But do it only if you don't care about getting an offer.
Senior Developers Are Getting Rejected for Jobs
381–384 of 384 posts
Re: Senior Developers Are Getting Rejected for Jobs
#382Earlier quoted context omitted.
You're missing the forest for the trees here. In these larger companies, senior engineers tend not to work directly with code that much anymore, they're usually working on higher level problems like system design or management. These require different skill sets such as leadership and social skills that take years to develop; the ability to google quickly for a function name isn't really valued as much. If you're wor…
> you shouldn't discount these engineers over minor details like this. Then they should apply for a job where their skills are relevant. If you're applying for a job where you're writing code (like all of the ones I described), you'd better be able to code. Edit: and we let you Google whatever you need in the interview. If you can't figure out how to clone an array (an implementation detail of the interview question)…
> If you're applying for a job where you're writing code (like all of the ones I described), you'd better be able to code.
That's fair. No sense in bringing in architecture astronauts who can't translate their dreams to reality.
> we let you Google whatever you need in the interview
Right, rejecting someone who can't Google things properly is the correct choice. That's a skill that's useful at all levels.
Re: Senior Developers Are Getting Rejected for Jobs
#383Earlier quoted context omitted.
Yeah that's fair. Im just frustrated with how low-bandwidth those things are. I definitely get a bit of a sense of how a person thinks by watching them do those CS 201-style problems, which isn't nothing.
If the CS 201-style problems annoy you, then... stop doing them? I don't ask algorithm questions, and I wouldn't even dream of asking brain teasers. I ask questions like "Here's a pile of text that claims to be CSV, let's explore how you'd generate an HTML report out of it", and branch out from there depending on how the interview goes. I've got all sorts of directions I can go from there, from screwing up the input…
A little late but I wanna be clear that I don't ask them! I ask questions similar to you. My comments here largely come from my experience doing the interview problems. But yeah, i've tried to "be the change," so to speak.
Re: Senior Developers Are Getting Rejected for Jobs
#384Earlier quoted context omitted.
I call shenanigans on this comment. Weeding out folks for not knowing how to sleep in a particular language or array syntax in another is not warranted. I think the response that Scala doesn't have arrays is totally legitimate. You should have asked them what was the project/problem they were most proud of and suss out the details of that. Moreover, keep in mind that for some orgs a Senior dev is actually someone tha…
In all of the above cases, the candidate had no fundamental knowledge of their chosen language. All of the jobs I was hiring for were for positions that involved writing code. None of these were roles that involved more thought leadership than coding. I should have been more clear about the JavaScript issue: there is no sleep command. The candidate didn't know how callbacks worked. In JavaScript. Callbacks in JavaScr…
just give fizzbuzz and call it a day. It sounded like you were asking about array to someone who doesn't use them and penalizing them.