4 ms·
But when you're interviewing at a company, pretty much all you have to go on is what the company says. Yeah, you can talk to other engineers and observe them,
by nostrademons 16y ago
But when you're interviewing at a company, pretty much all you have to go on is what the company says. Yeah, you can talk to other engineers and observe them, and I've tried to do that each time I interview, but no employee is going to badmouth his employer at work and the 5 minutes you get on your way in and out of the interview isn't going to show you much.
So at offer-time, there are very few concrete facts that you know for sure about the company. One is your compensation package. Another is the product that you'll be working on. A third are the investors backing the company.
Not much to go on. The OP is asking prospective employees to consider the intangibles when making their decision. And yes, ultimately the intangibles are more important to job satisfaction. But they don't know the intangibles yet - they know what the OP says the intangibles will be. And every other company that they interview with says the same thing. They can be forgiven for discounting a few promises from a wild-eyed entrepreneur and making decisions based on the facts they have in hand, right?
FWIW, I applied to Google and ended up accepting their offer mostly because I asked around, several of my friends knew Google employees, and virtually nobody had anything bad to say about the company. Even people who were no longer there thought it was generally a nice place, it just wasn't right for them at their particular stage in their career. That's the kind of word-of-mouth that can make or break hiring for a startup. If you want people to join you for your intangibles, make sure that they hear it from your employees, not from you.
- strlen 16y ago> If you want people to join you for your intangibles, make sure that they hear it from your employees, not from you. In a sense yes, it's hit or miss. I agree with you that knowing people who work in a place is very important, as you're going to get a far more fair picture out of them (e.g., they're more likely to give a truthful picture of the hours worked, legacy technologies used, etc...). Generally, it's also a lot easier to get an interview (for a core position) if you're going through a referral rather than by sending out your resume or responding to a recruiter. You can also judge the quality of the team and interesting-ness of their work by talking to the engineers, discussing the projects they work on and if there's open source work, reading their code. Yes, it's hard to get a complete picture of the intangibles, but it's still a bad idea to base the entire decision solely on a single number.