I'd say that about mirrors my experience as well. Is this really that common? Here I was thinking that I'm just an idiot.
I'd say that about mirrors my experience as well. Is this really that common? Here I was thinking that I'm just an idiot.
The gist of your comment might be correct, but I think we shouldn't perpetuate the mindset that mid-40s or even 50s is "so old."
In almost all knowledge-worker professions, age and experience is acknowledged as an asset. I think software companies are just starting to realize that, as the "move fast and break things" companies are now weighed down under technical debt and imposing hiring freezes on recent grads and junior engineers.
I feel like I'm in my prime in terms of experience and productivity, and though I may not want to work 70+ hour weeks or chug beers at the office anymore, I'm a considerably better engineer than I was 20 years ago. I think many of us intuitively know that, and we shouldn't let ourselves become victim to self-defeating SV groupthink.
> but it's those damn algorithm questions I just can't get past
I was under the impression there was a minimum bar on the algorithms that applies regardless of seniority and whether you pass the interview as a junior/senior/staff/etc. was mostly dependent on communication, system design interview, etc.
What are the expectations, in an interview for this level?
[0]: http://blog.interviewing.io/after-a-lot-more-data-technical-...
[1]: http://blog.alinelerner.com/people-cant-gauge-their-own-inte...
My reading of that is that out of all the people he knows, there are four that could plausibly "fail" 20 interviews in a row, not that 25% of (engineers?) he knows would do so.
Sounds about right. I can pass "take home quiz" style interviews at nearly 100%, but put me in front of a whiteboard and everything goes blank. Not sure why people insist on doing that.