4 ms·
>Cramming may get a candidate a job. But they won’t succeed at the job if they don’t have the skills and experience needed. This is a fallacy, you'll encounter
by dogma1138 10y ago
>Cramming may get a candidate a job. But they won’t succeed at the job if they don’t have the skills and experience needed.
This is a fallacy, you'll encounter things that you are not "qualified" to do on the job all the time, not to mention that if you are applying for an engineering job, or any other job that effectively requires you to solve problems; then learning new things, performing studies and research and finding a solution to the problem is your job description.
If the role is such that a candidate can have 100% of the experience and knowledge needed to perform that role during it's entire lifetime than that role is effectively the burger flipping of the tech world.
This role is also the easiest to automate since apparently all the answers and knowledge needed to fulfil are known.
- zzbzq 10y agoThat objection could be seen as compatible with the original thesis in the title, though. Equate the need to work with unexpected things on the job, with improvising a job interview. In both cases, you need to expand beyond your knowledge, but you also need a baseline of knowledge and ability to even get started.
- geofft 10y agoAt a job interview you're typically not allowed to use the web and also typically expected to answer a question within seconds instead of within days, so the environment is very different from working with unexpected things on the job. You could design an interview process where neither of these were true, but I think it's pretty hard and comes with its own downsides.
- icedchai 10y agoI have done live coding exercises with candidates, allowing them to use the web, etc. This is actually even more enlightening... you should see some of the things people google, copy-and-paste, etc.
- khedoros1 10y agoUsing a mountain or pile of stuff as a metaphor (and ignoring its potential lopsidedness for now): At the base, you've got some knowledge that might be kind of dusty, but that you can reacquaint yourself with quickly. Then you've got a mass of experience, layered on top of that knowledge, that further colors how you'll approach problems, the solutions you'll choose, etc. You can reach further from there by doing a little research, and put another layer of experience on the pile you already have. If the job doesn't require any reach, it's "burger flipping". If the job requires more reach than you can get, even from the top of your experience-pile, and building the pile up to extend your reach enough to achieve the goal will take more time than you have, then you're unqualified for the job. So, you want something in the happy middle: not trivial for you, but not out of your grasp. Your reach should be small, compared to your experience, unless you're just starting out.