Each of your articles is a great pleasure to read. You are one of the first who talks about struggles of self taught programmers.
Major part are trying to hide the fact they don't have a degree.
Regarding the interviews and technical tests you are absolutely right. Usually they are so much disconnected with the real work.
However usually this is the way companies hire and test candidates. May I ask what is your strategy to overcome those barriers? Do you search only the specific type companies or you have a way to hack this "matrix"?
Sorry that I'm replying to this so late. Somehow I missed this last year...
As to your (awesome, very thoughtful) questions, I can only offer this: The best "strategy" is to try, whenever possible, to only "search" from a position of strength. Meaning, don't start that Next Great Job Search on the day that you quit (or are fired!) from your current job. When you really need a new job, it transfers any "power" you might've had to your next (potential) employer.
I'm not ignorant to the challenges we can all face when we really need a job. If you find yourself in a real "bind", it can be nearly impossible to assert any kinda control over the situation. You're at their mercy.
During those few times when I've been truly "between gigs", I'll freely admit that I frequently end up jumping through the same hoops that I rail against. But when I have a job? And I might like a different job? A "different" job? Well... that makes things sooooooo much easier. Cuz when I have a decent job (even one that I'd possibly like to get out of), it becomes infinitely easier to 1) recognize the "hoops" for what they are, and then 2) tell them, confidently, that "No, I won't be doing that."
Do I miss out on some potential opportunities this way? Of course I do. But I can sleep hella-well at night knowing that those so-called opportunities are prob not any opportunities that I really wanted that badly anyway.
After spending a lot of my personal time and energy on recruitment processes I had to review my strategy as well.
Now I do tech challenge only if it will be useful for writing an article afterwards. It changed my perception. In any case was I accepted or rejected this way I am not wasting my time.
In addition I started to reject any long recruitment processes, because it's really a waste of time.
Adam,
Each of your articles is a great pleasure to read. You are one of the first who talks about struggles of self taught programmers.
Major part are trying to hide the fact they don't have a degree.
Regarding the interviews and technical tests you are absolutely right. Usually they are so much disconnected with the real work.
However usually this is the way companies hire and test candidates. May I ask what is your strategy to overcome those barriers? Do you search only the specific type companies or you have a way to hack this "matrix"?
Sorry that I'm replying to this so late. Somehow I missed this last year...
As to your (awesome, very thoughtful) questions, I can only offer this: The best "strategy" is to try, whenever possible, to only "search" from a position of strength. Meaning, don't start that Next Great Job Search on the day that you quit (or are fired!) from your current job. When you really need a new job, it transfers any "power" you might've had to your next (potential) employer.
I'm not ignorant to the challenges we can all face when we really need a job. If you find yourself in a real "bind", it can be nearly impossible to assert any kinda control over the situation. You're at their mercy.
During those few times when I've been truly "between gigs", I'll freely admit that I frequently end up jumping through the same hoops that I rail against. But when I have a job? And I might like a different job? A "different" job? Well... that makes things sooooooo much easier. Cuz when I have a decent job (even one that I'd possibly like to get out of), it becomes infinitely easier to 1) recognize the "hoops" for what they are, and then 2) tell them, confidently, that "No, I won't be doing that."
Do I miss out on some potential opportunities this way? Of course I do. But I can sleep hella-well at night knowing that those so-called opportunities are prob not any opportunities that I really wanted that badly anyway.
Thank for the detailed response.
After spending a lot of my personal time and energy on recruitment processes I had to review my strategy as well.
Now I do tech challenge only if it will be useful for writing an article afterwards. It changed my perception. In any case was I accepted or rejected this way I am not wasting my time.
In addition I started to reject any long recruitment processes, because it's really a waste of time.
Sooooo well said!