Show HN: Form I send all recruiters to
e.l1t3.com
e.l1t3.com
Two comments:
1) This is obnoxious in the sense that it's placing a bar that other candidates don't, and it's lacking context I'd prefer to provide over a phone call. For instance, equity at our company is typically quite different than equity at other companies. Not all equity is created equal, and our cap table is very clean.
2) For the right candidate, I'd still make a best effort to fill it out despite the aforementioned comment.
To me the most broken part of recruiting is the third-party recruiting process, and yet, we still use them, because they do occasionally bring in great candidates we would otherwise miss.
This idea started as a joke, and more people liked it so I made it standalone :)
The negative is because they can be a motivation to fire an employee just before they become worth something, e.g. in the most infamous case: https://en.wikipedia.org/wiki/Brian_Reid_(computer_scientist...
I do 99% of my recruiting with a hand-written email from an email I find on linkedin, github, or a personal webpage.
Obviously this form could use improvement. For example, without knowing the percentage of shares outstanding and stock classes, having a number of options is meaningless. But it is more in the right direction than not.
Coding positions might be a whole different ballgame, though. I probably wouldn't have much patience for coding tests with a recruiter which undoubtedly makes the process harder for all 3 parties.
Given the following code snippet what is it's output:
//IMAGE OF CODE
A) 1
B) 2
C) false
D) null
These are stupid questions IMHO, in fact the last test I had to take like this I could have typed up each code example and run the code in the time I was given on each question. Test me on my problem solving but don't ask me to boot up an interpreter in my head that skill is NEVER needed in your day to day life as a coder. (I also take issue with tests that ask about boilerplate or stuff handled by the IDE/environment). We live in a world where a massive amount of information (I'd argue even more so when you look at just programming) is just a google away. Don't ask me to memorize docs that I can lookup in seconds, it's just not a skill that's really needed. I prefer "learn as you go" over "memorize this book". Now when it comes to programming concepts I might budge a little but not much.
And a good recruiter might find it a bit pretentious. I'd rather take the spam than risk my career.
i.e. does the compensation and perks come before technologies and management?
I think it is better than just not responding to recruiter email or mark it as spam. There is always a chance.