4 ms·
If the test doesn't reflect the job you'll be doing then it's not a good test of whether or not you'll be able to do the job. If you're applying for a role that
by onion2k 7y ago
If the test doesn't reflect the job you'll be doing then it's not a good test of whether or not you'll be able to do the job. If you're applying for a role that expects you to know an application then looking in the help is cheating. If using the help is acceptable in the job then it's not.
It's also worth noting that people don't like "proxy tests" for the skills they'll need to use on the job. If the test only tangentially assesses a skill then it's going to be influenced by other skills or flaws and won't give an interviewer a good idea of how good you are at something. This is why people complain about whiteboard exercises in developer hiring. Unless remembering and explaining an algorithm on a board is something you'll actually be doing in the role then it's not a good test - it sort of assesses how good you are at explaining an algorithm, but it really assesses memory, presentation skills, etc. Someone with brilliant whiteboard skills isn't necessarily a good developer, so hiring them on because you were impressed by how well they explained something in front of a board feels wrong, especially to people who aren't good at the tangential stuff.
In the case of the suggested hiring test in the article, it doesn't test someone's job skills. It tests how well they look for help, but it also tests how well someone copes in unfamiliar applications, or with esoteric UIs (in the case of Blender), or if they've actually used the app that's being used as a proxy. None of those things are necessarily a good assessment of whether the person can do the role they're applying for, so the test fails.
- disintegore 7y agoIf you are required to demonstrate that you can create pivot tables, and you not only know what they are and how they work but also figured out how to do it in a brand new software suite within 10 minutes under stressful conditions, you have succeeded. Committing obscure UX patterns to memory is far less important than your ability to understand concepts and find ways to apply them. I understand a manager may prefer to supply someone with Microsoft Office 2001 Alpha Deluxe Edition (& Knuckles) and see them hit the ground sprinting but the time spent looking for such a person might be greater than what it would take for a motivated person to reach that level.
- dangerface 7y ago> If you're applying for a role that expects you to know an application then looking in the help is cheating. If you discourage your employees from learning you are going to have a lot of dumb employees. Even the developers who made excel do not know how to do everything that excel can do.
- onion2k 7y agoSome businesses need to hire people to do a job using an application in a very standardized way from day 1, there is no expectation that the person doing it will learn anything in the role, and when the software changes training is provided. The employer is in complete control of what is done and how the software is used. Figuring something out yourself is considered a bad thing because it's not the standardized way of doing the thing. Please don't go through life imagining every job is like a developer job. We get far more freedom, creativity, and responsibility than a lot of other workers.
- hvidgaard 7y agoThat is all well and good for those types of jobs. But no one can remember how to use all of Excel, and they should be able to search for help and understand that help.
- dangerface 7y agoI get your point there is a lot of dumb work that employers give to dumb employees. However if you want a dumb job done consistently in a standardised way with no mistakes you want automation not a humans. Ultimately the competition who allows people to improve will improve themselves and the job until it's no longer necessary.
- croon 7y agoThis really nailed it on at least one particular job I was interviewing for. I'm freelance and really happy with it, but was referred by a friend to a (at least regionally highly regarded) company, so I thought I'd go. I was first presented with a IQ test-looking set of pictures where you choose what comes next in the sequence. Seeing as I love puzzles, I scored great on it, but also aware that it doesn't really say anything about my skills on the job. They were very positive and wanted to move forward. So I got a take-home test in Java. There wasn't a time estimate, but it was fairly convoluted, and it was meant to show what you would turn in, had it been my task, meaning I wanted build configs, testing, deployment, etc. The problem was that I hadn't worked with Java for a decade, nor did the position have any connection to Java. I didn't even have a jdk installed at the time, but made an effort at setting it all up, figuring out maven or gradle, making my classes and data models, getting a skeleton set up, and after three hours figured I wasn't even half way done. I wasn't interested enough in the job, would have gotten a pay cut, and had a 3 month old at home I was much more keen to hang out with on my free time, so I reported what I had done and that I was unlikely to do more. They stated that they would set up a meeting with the CTO, but never heard back. I wish they had done a (sort of) exit interview or just sent out a minimal effort feedback questionnaire. It would be one of the first one I'd actually like to fill out. I don't think I'm top tier in my field or region, or that I would've gotten/taken the job anyways, but they really put me off for the wrong reasons. And I bet this is more common than it has any right to be.