4 ms·
I think it varies by company, but at mine the questions are very much domain based for senior people. The focus is greater on algorithms for new grads. The que
by dhjsnana83 8y ago
I think it varies by company, but at mine the questions are very much domain based for senior people. The focus is greater on algorithms for new grads.
The questions being asked aren't extremely challenging, they can be trained for. Willingness to learn new things (even if useless) and put in the effort to pass interviews is a positive signal imo.
On that note, it seems like HN has assumed the only work that exists is writing CRUD apps and not worrying about performance. There are many roles where you do need to have a strong understanding of performance and algorithms, and those are the difference between a smooth rollout and crashes in the middle of the night.
- akra 8y agoWhat aspect of performance though? Even that means a variety of different things to different people and it isn't just algorithms. I've met people who are bad at typical CS algorithms yet know their language of choice very well and write low-allocation high performance tight code that "does less". Or people that are used to handling concurrent code which sadly is still somewhat of a rare skill. Only the algorithms are touched on in typical CS courses; most aspects of performance tuning come from experience and persistence spending hours trying to get more performance and less resource usage out of an application.