Ask HN: Would you work for a company if you do not use their product?
I'm curious if other folks have considered this: I see a lot of career/job opportunities that look interesting/exciting, but I have not seriously considered them because I don't use/believe in the product they are developing.
One example could be Facebook; I don't have an account (I never have), and generally don't believe in their product. That said, I'm sure it's a great place to work, and would be a great opportunity.
How do you folks reconcile that?
10 comments
[ 3.1 ms ] story [ 37.3 ms ] threadWhile having a belief in the company you're working for and what they're doing is valuable, I don't think you need to be a 'user' of a company's services or products to work somewhere.
Perhaps that's not what you're asking, or perhaps you're only looking to work at consumer-facing public web service companies?
Currently, I'm trying as hard as I can to get a hold of the most difficult projects I can find in the workplace. If that means working on a technically challenging product that I kinda-sorta believe in, then so be it. My goal is to get my technical chops up. I suspect that as time and my experience progresses, the actual product will mean more to me.
On the other hand, I've taken one job with a company whose "product" I found counterproductive to society. I got so depressed I could barely work, and was drummed out in 6 months.
It's almost never worth it.
I work for a company that builds machinery that costs close to $1M. I'm not likely to ever use one of them (but I wholeheartedly believe in the product: medical instrumentation).
If you only look for jobs where you would have used the end product, you're likely to spend a lot of time unemployed.
For example, many of the big name financial companies have a higher premium because of the service and knowledge of the financial experts (or at least perceived knowledge).
There are many financial firms that offer less expensive options but have less customer service, etc... So I expect many Morgan Stanley and Fidelity financial analysts to have a portfolio from a different company.
Yet, I derived motivation and pleasure from the technical challenges and the creative atmosphere created by the crazy geeks I have the privilege to work with. Besides, the rather short development cycles with hardly any maintaining after release make for fun projects: Code and forget.
Something else to consider: If you don't like their product, you may be able to help them to turn the product into something you can enjoy as well, and with this they may be able to open up to new audiences. Sometimes, the naysayers can actually be useful, or so I like to believe.