7 ms·
In my short career of ~10 years I've yet to use any of those the algorithms they ask about in these interviews. I've gone from full stack on php, to java backen
by dastx 6y ago
In my short career of ~10 years I've yet to use any of those the algorithms they ask about in these interviews. I've gone from full stack on php, to java backends,to devops engineering, and never have I ever had to use any of these algorithms. I got a decent score at university where we learned it, but it's ridiculous to be asked about something I'll never use. Even if I knew the theory, and was able to ace it, it would be rare for me to use it, because it's all available in libraries, and they definitely will have done a better job than I will do.
"It's not about the solution, it's about how you get to the solution" you say, I say there's better ways of figuring out if you have problem solving skills.
For sure, there are jobs that require such theory, but many do not. And if it's not required, managers need to realise they're potentially missing out on good talent.
- nullsense 6y agoThey're not optimizing for knowing the theory or problem solving ability. They're optimizing for how far are you willing to go to jump through this here hoop of ours?
- lliamander 6y agoAlgorithms are often treated as a trivia challenge, which is the complete wrong way to use them. What you really want to know is whether a person can translate a set of requirements into working code. Algorithms are useful because they reduce the possibility that the candidate failed in the coding test because of poorly specified requirements. "Problem solving" ability is a different beast altogether.