4 ms·

I went through the same thing. All the problems you mention could also happen at a startup, but it is less likely, it really comes down to the people. My advi

I went through the same thing. All the problems you mention could also happen at a startup, but it is less likely, it really comes down to the people. My advice is when you interview with companies, ask a lot of questions and if something doesn't feel right to you ... keep poking and poking until you get a clearer picture about the questions you have. Trust your gut and if you don't feel all the way good about it, then don't join. What I've learned in my career is that those little things you overlook at the start of that shiny new gig have a way of growing into massive problems. Over all things, try to find a place where you really really care about the work, where you're excited to go to work in the morning, or something close to that. And if things go sour, don't waste time trying to 'fix' things, cut the cord and move on. Staying will only make you resentful and tarnish your image/reputation as the quality of your work suffers. I'll leave you with a quote that has come to summarize my world view these days. "Life is too short not to do something that matters" --- Hugh Mcleod Good luck.

kpennell 14y ago
Excellent post. Gotta trust your gut. Gotta trust your gut.
miql 14y ago
Can anyone recommend a resource or list of good questions to ask in addition to or similar to what's posted here? Thanks a lot for this.
- trustfundbaby 14y ago
  It really comes down to you and the things you care about. - For example, I'm a night owl so a company like github that doesn't care about hours appeals to me greatly, http://zachholman.com/posts/how-github-works-hours/ http://zachholman.com/posts/how-github-works-hours/, I'll ask about their attendance policy, how late is late? How much do they frown on lateness. More importantly how does the guy supervising you feel about it. - I hate forced pair programming, so that's the first thing I ask. if they pair program even 40-50% of the time, I'm out. - I don't like companies that scrimp on developer tools, so I ask about the equipment they get for developers. What the budget is for each dev? How often they replace the equipment? Do they pay for developer conferences or books or their employees have to take PTO and pay their way? - I don't like walled gardens, where devs can't influence product design, you know ... just-code-this-spec devs ... So I'll ask things like, what was the last feature a developer suggested that made it into production? This one usually stumps the fakers, you know the people who try to recruit rockstars and turn them into code monkeys? - I ask Devs when they get time to catch up on HN and read blogs, or play around with new technology and from their responses I can usually tell if doing that stuff at work is frowned upon (No bueno) or encouraged. - I also ask what sideprojects they're working on. just like that. If the dev looks shocked, I run. If they say something like ... "I have so many ideas and after mentioning them to x they usually become product features" ... that warms my heart. If they say something like, "I have some stuff I'm working on, but I'm still trying to see how to get it in front of people", then I'll dig deeper. Just ask about everything and take time to actually interview the company, on the things that matter to you. I have a prepared list of questions in evernote that I add questions to and delete stuff from as they pop in my head reading HN or just hanging out, one list for the devs, another for the managers and another for the higher ups (if I get a chance to talk to them). I have cultivated it over 2 years and it really helps me get a feel for how I'm going to get along with my potential employers, whenever I sit down to talk to anybody.

kpennell 14y ago

Excellent post. Gotta trust your gut. Gotta trust your gut.

miql 14y ago

Can anyone recommend a resource or list of good questions to ask in addition to or similar to what's posted here? Thanks a lot for this.

trustfundbaby 14y ago
It really comes down to you and the things you care about. - For example, I'm a night owl so a company like github that doesn't care about hours appeals to me greatly, http://zachholman.com/posts/how-github-works-hours/ http://zachholman.com/posts/how-github-works-hours/, I'll ask about their attendance policy, how late is late? How much do they frown on lateness. More importantly how does the guy supervising you feel about it. - I hate forced pair programming, so that's the first thing I ask. if they pair program even 40-50% of the time, I'm out. - I don't like companies that scrimp on developer tools, so I ask about the equipment they get for developers. What the budget is for each dev? How often they replace the equipment? Do they pay for developer conferences or books or their employees have to take PTO and pay their way? - I don't like walled gardens, where devs can't influence product design, you know ... just-code-this-spec devs ... So I'll ask things like, what was the last feature a developer suggested that made it into production? This one usually stumps the fakers, you know the people who try to recruit rockstars and turn them into code monkeys? - I ask Devs when they get time to catch up on HN and read blogs, or play around with new technology and from their responses I can usually tell if doing that stuff at work is frowned upon (No bueno) or encouraged. - I also ask what sideprojects they're working on. just like that. If the dev looks shocked, I run. If they say something like ... "I have so many ideas and after mentioning them to x they usually become product features" ... that warms my heart. If they say something like, "I have some stuff I'm working on, but I'm still trying to see how to get it in front of people", then I'll dig deeper. Just ask about everything and take time to actually interview the company, on the things that matter to you. I have a prepared list of questions in evernote that I add questions to and delete stuff from as they pop in my head reading HN or just hanging out, one list for the devs, another for the managers and another for the higher ups (if I get a chance to talk to them). I have cultivated it over 2 years and it really helps me get a feel for how I'm going to get along with my potential employers, whenever I sit down to talk to anybody.