|
|
|
|
|
|
by raverbashing
3547 days ago
|
|
|
Yes, the test itself is fine, however the issues I've seen: - Hidden tests/metrics that also get evaluated - Companies with an exaggerated sense of self-importance and unrealistic expectation of results This is a test, you don't have the feedback that you have on a company (code reviews/talking to a colleague/better understanding of the conditions/real data tests/etc). Don't expect me to guess your conditions. Also, I can't cover all points in the time you give me, I'm focusing on making the thing work, other stuff is secondary. |
|
|
I enjoy solving hard problems as much as any other engineer, or I wouldn't be in this field. But if you want to judge me on code quality, expressiveness, architecture, and test coverage, in addition to performance and correctness, you should really give me enough time to review, refactor and test my code to cover all of those criteria. You know, time that any responsible engineer would spend on any piece of code they write before sending it off to production.
If the position does actually involve writing production-ready solutions to hard algorithms problems within ridiculous time limits like 1 hour, let me know beforehand so I have the chance disqualify myself from it, and we can both avoid wasting any more time with each other.