Ask HN: Is it possible to fight back against the “big 4” hiring fads?
This post got me triggered https://news.ycombinator.com/item?id=12348756 as I've experienced the same feelings of worthlessness and inadequacy after terrible interview experiences. I also know a lot of people who have either: quit tech or moved overseas, unfortunately this stupid fad of "algorithmic" puzzles has gotten out of control and it's spreading like wildfire, because everyone wants to be like Google/Facebook/Amazon.
I can understand why some complex algorithm competency might be required at some of these companies but this alpha nerd "dick-measuring contest" needs to stop.
I am angry for the OP of the post above and for my own experiences as well as for many other fellow developers who have been through the same.
I think it's time we fight back as a collective and tell the "big 4" and the big 4 wannabes to go screw themselves, however I feel powerless, frustrated and angry. We can't continue to be complacent, enough is enough I say, let's do something about this.It has gotten out of hand. I refuse to accept this as the status quo.
26 comments
[ 3.4 ms ] story [ 68.3 ms ] threadSecond, remember that interviewing is both way lane. It's not only a way for employer to assess candidate, it's a way for a candidate to assess the potential employer. Treat it as such.
This may be a cliché, but if all I got asked in the interview was some random puzzles and nobody was interested in the work I had done in the past, I would probably avoid such company. They don't seem to hire based on competency, so I'm likely the first one with the ability to develop and deploy a well-designed system (completely different thing from algorithms). I don't like to struggle with making each and every step. The same stands if they require specific education.
And the last thing, in current landscape there's plenty of jobs in IT and only so many competent programmers, sysadmins, netadmins, or DB operators. It's the employers who struggle with finding good candidates, not the other way around.
I don't know, maybe it was Microsoft. I haven't put much thought about what is "the big four". To me, they all fall into the same bucket: big, computers, mostly US.
[1] https://en.wikipedia.org/wiki/Big_Four
1. Apple 2. Alphabet 3. Microsoft 4. Berkshire Hathaway 5. Exxon Mobile 6. Amazon 7. Facebook
If we're going by impact on tech, opportunities for software development, etc., it could potentially be different.
http://dogsofthedow.com/largest-companies-by-market-cap.htm
Career Capital Theory-
Research shows that the traits that lead people to love their work are general, and can be found in many different career paths. They include things like autonomy, a sense of impact and mastery, creativity, and respect and recognition for your abilities. Once you recognize that these traits have little to do with following a pre-existing passion, and can be cultivated in many different fields, you can safely abandon the myth that there's a single right job waiting out there for you.
On this subject, Steve Martin's advice is solid > http://lifehacker.com/5947649/steve-martins-advice-for-build...
People that don't give a shit stagnate.
It helps to have Models. Who are the benchmark leaders in your field? How did they get there? What exactly made-up their mythical 10,000 hours of practice?
Hold yourself up to the standard. Emulate the formula, add your own ingredients. You'll know it's working if you feel stretched professionally.
Josh Kaufman has a brilliant take on acquiring new skills quickly > https://www.youtube.com/watch?v=CsGihiSE6sM
I'm inclined to agree with the OP. Not every employer is going to be Google/Facebook/etc, so they shouldn't try to hire like they are already.
I've realized that most companies are similar and opportunities don't just fall into your lap. Want a low growth job fixing bugs for 10 years? You can probably get that at Google (or pretty much anywhere). Want a job where you can develop the next big feature in Android? You can probably make that happen, too.
If you want the latter, don't just sit there, fall into a routine, and fix bugs all day thinking that one day a VP will knock on your door asking you to be a Software Architect. Don't become complacent.
See this advice a lot, are there any tips on this? make more to-do list? set goals?(how to know if goal is too high instead of myself being too lazy? etc)
My main point is, you don't need to work for a big N company to achieve your goals (unless your goal is to simply work for a big N company). The sooner I realized that, the sooner I was able to start working on my actual goals where the actions are vastly different than those of "getting into big N."
e.g. I want to design software, but not necessarily at Google makes it a lot easier to achieve than saying it must be at Google. :)
Overall, I think the process is just kind of silly, and I'm sure whoever comes up with a better way will be able to make some good money as well.