3 ms·
Keep in mind that, because the number of programmers is increasing, the majority of them are fresh out of school or close to it. Algorithms interviews are large
by dahart 10y ago
Keep in mind that, because the number of programmers is increasing, the majority of them are fresh out of school or close to it. Algorithms interviews are largely designed for interviewing people who don't have much experience, so they're skewed toward testing what people learned in school.
If after 2 CTO roles you interview for a job and they ask you to write a linked list algorithm, then would you want to work there? I mean you might, but that alone should at least beg the question. If they're not asking you how you'd manage a team of smart but stubborn coders or structure their company's software architecture and services to be more reliable, then they certainly aren't paying much attention to you or what your strengths and experience are. Or they simply don't know how to hire an experienced person, which signals that they don't know what to do with an experienced person once hired.
Also, it would take the vast majority of great coders at least a half hour to code a linked-list from scratch in C and get it right, depending on what you're doing.
So don't worry.
- FLUX-YOU 10y ago>Keep in mind that, because the number of programmers is increasing, the majority of them are fresh out of school or close to it. But the number of unfilled positions is also increasing, so we are not closing the gap, right? So the gap is widening, but the requirements to get a position are also going up. That just makes no sense to continue for a long period of time.
- dahart 10y agoIf the number of unfilled positions is increasing, that would tend to lower the requirements, not raise them. If the number of filled positions is growing at the same rate as the number of unfilled positions, that would be evidence that the requirements are staying roughly the same on average. (Except I'm sure there some small amount of average improvement and widespread knowledge increase every year that everyone benefits from.) In any case, it still makes sense for companies to come up with interview strategies for inexperienced devs, and the article at the top is once such way. It doesn't mean companies will interview experienced devs the same way, and in my experience, they don't. (EDIT I had written some other junk based on me misreading your comment, apologies if you had to spend any time on that.)