2 ms·
The stated goal is to design the model which is most ideal for me. The real goal - meaning, the one which decides if I will be hired - is to design the model w
by eesmith 8y ago
The stated goal is to design the model which is most ideal for me.
The real goal - meaning, the one which decides if I will be hired - is to design the model which is most different from others.
Since I want the job, shouldn't I disregard the instructions and instead create crazy looking calculators which aren't ideal for me but which are different enough to stand out, and thus get me hired?
As a test designer, aren't you making a bias toward hiring people who are good at gaming the system? Is that really good for the company?
Going back to my examples, which you did not address, would your team hire the "C++ programmer" who implemented the sorting challenge by using the Python/C API to write a Python program? Because that's certainly thinking outside the box. But it doesn't tell you if the programmer would be a good C++ hire.
> If you develop COBOL look for a developer that can do COBOL but hates it and would love to switch elsewhere.
What? If you want to hire a COBOL developer with the expectation of working for 20+ years at a bank, why would you want that developer to hate that job? Do you have any evidence that they will be "more efficient" at it? Why wouldn't they do the bare minimum need to do a satisfactory job, while looking for a new job on the side. And when that happens you'll need to retrain your new employee.
It seems like money down the drain.