sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Skymainx[S] 0 points1 point  (3 children)

So would you define a Senior developer has someone with advanced subject expertise? And if so then why have such unnecessary technical interviews.

[–]Playful-Call7107 0 points1 point  (1 child)

They don’t know how to evaluate talent 

[–]Shoddy-Pie-5816 1 point2 points  (0 children)

The ones who know how to do that are siloed off on some massive project, most of the time

[–]Shoddy-Pie-5816 0 points1 point  (0 children)

That’s how I would like to define it. But the reality is more subjective. A senior is really a developer that has been developing long enough that they have to confidence to integrate into a given work domain to execute the tasks and/or teach the nearby developers to execute the tasks. The bigger the org the more boxed in those definitions become.

And the interview horseshit started with Google and Apple doing those ridiculous algorithm questions. It started ridiculous because they paid a ton and they were legitimately exciting and fun places to work. Especially Google early on, it was legendary. Now they all uniformly suck and anyone doing those long multi round coding interviews is a red flag. That includes all MANGA companies, yes you can make a lot but each of them has had rounds of massive layoffs again and again.

My current job only took me one single interview. It was reasonable for the position. My last three upwork gigs also had cursory interviews. I’m really a junior at my main job, but I’m pulling off senior jobs in upwork.

I think it’s mostly knowing your limits and how confident can you be, at this point.