I like this. That is exactly how I feel and it's great to read/hear about it outside of my head. :-)
After reading your comment, I ought to clarify a few things:
(1) I have in fact been unemployed for several months, mostly because I needed the break and have decided that I should be more careful about where I choose to work next to avoid going through the same nightmare again. Even so, I'm not in a hurry to get a paycheck and am willing to take the time for finding a good match. But I'm aware that many employers look upon this rather negatively and will be rather "curious" about what happened.
(2) The "bureaucracy" aspect I was whining about was not so much dysfunctional relationships as it was pure cluelessness and red tape. Think 6-month wait times for a 15-minute procurement job, or crappy tools that were "standardized" in the company based on some sales pitch delivered at the VP level. I'd imagine it's this type of situation that is more easily avoidable at a startup.
I have a vague hunch of what you mean by "VC darling" and am taking all mentions of high-profile backers with a grain of salt, but I'm curious about what you consider "Real Technology" -- in what ways are the technical challenges, from usability to scalability, of a social media "joke" startup substantially different from those of a business that you'd take seriously?
Don't worry about missing any boats. If you like a job take it, if not, don't. If you want to start a business, start it, and focus on making money rather than chasing techcrunch headlines and VCs.
If you're evaluating work at a startup, look at it like you're your agent:
1) What's the comp package? Equity, unless very significant, is basically a deferred bonus that you can't count on. Don't overrate it.
2) What skills will you get to develop? It's usually not worth taking a lower salary for X,000 shares of "i don't know". But it can absolutely be worth taking a lower salary now in exchange for higher skills later.
Also, when a candidate does speak negatively about their current employer, you're left with two possibilities: it's really that bad, or they're not a good employee. As a candidate, you don't really want to raise that possibility in anyone's mind.
(1) Don't take jobs where the company isn't willing to
tell you what you'll be working on. That usually means
you're going to be allocated to the least desirable
projects.
I passed on a job at Google precisely because of this fear. I wonder if they've since changed that practice.However, you do get to talk to 4-5 hiring managers based on your skillset and their interests, and you get to rate them based on the group you want to join.
I've done that and it's worked out pretty good for me.
(Btw, this is all in the public - Stephen Levy's In The Plex is a pretty good resource)
If you have a fairly impartial interviewer, he's most likely trying to hire competent people - he doesn't have any other sort of incentive except to not hire stupid people.
However, if you're a hiring manager, you're under pressure to produce software and fill open recs. So, if you have an open position, the natural thing to do would be to hire a mediocre person cause hey, he's better than nothing, and we got a hole we need to fill for our next project.
As for my personal experience, I'm a bit of an outlier. I'm older (mid thirties), know a couple dozen people who already work here (know which groups to avoid), and my friend who I've worked for before personally recommended me to his current team (I know I'm landing in a good position).
Any other specific questions?
If you work at Google, keep your head down for 12-18 months. Don't pay attention to big-company politics and (unlike me) stay the fuck away from eng-misc. Work hard and (unless you're on a good project) figure out what transfer opportunities will be available, and which ones will be good. At the 18-month point, try for a promotion. It makes it easier to transfer. If you don't get the promo, you can still transfer; it's just somewhat harder. If your performance ratings are still at "Meets Expectations" you should have a good story as to why. In that case, you need to find that middle ground of (a) making it obvious that your manager's appraisal of you is boneheadedly wrong, (b) without throwing him under the bus.
The objective sign of a decent manager is whether his or her reports get promoted. Good managers (at Google) get their reports promoted and bad managers don't. It's that simple. Look into this when you're evaluating transfer opportunities. If you find that a group has a lot of really good people stuck at SWE 3, stay away from it, even if the work sounds interesting. The truth about Google is that no one will consider you qualified to do anything actually interesting (i.e. you won't be considered a Real Googler) until you climb that ladder a bit, so your first few years should be focused on making Staff SWE. (The Real Googler line is somewhere between Senior and Staff.)
Piaw Na wrote some excellent material on the promotion process at Google: http://piaw.blogspot.com/2010/08/tips-for-noogler-engineers....
Do you have any less specific questions that I could answer without getting canned?
Instead, you are looking for good co-workers, good management, a comfortable work environment, and a compelling or at least interesting-enough business. You are not looking for a company that merely subscribes to your pet programming philosophy.
If they don't use a bug tracker? If they don't use version control? If they edit the code on the live servers to make changes/add features?
(I've seen all these things)
I agree it depends a little on the specific project but a lot of these kinds of best practice stuff are more than just pet programming philosophies. If you are used to or function best in a place with a certain level of professionalism than working somewhere with some cowboys who just wing it or somewhere were the every piece of work is in a feature branch with a corresponding user story, conforms to a style guide and has proper tests is probably not a good fit.
Where a team falls on this spectrum is part of the company culture.
These are all practices that in a larger team, or with a larger user base, or with higher requirements, would be untenable. But they work for us, for now.
I learned my lesson though, retroactively adding proper deployment practices is pretty easy, adding tests later is freaking impossible. It's harder to do later when the code isn't fresh in your head (or you didn't even write it) and it takes a lot of time to write tests for legacy code and getting approval to take that much time away is near impossible. Now I pay the 5% tax to do things right and develop features 2-3 times faster long term. (Those numbers are based on pulling some numbers from my work logs and time sheets a while ago, they are very rough and small sample size on a project where there was legacy code with no tests and new code with tests).
To go back to my point though, it's not some rabid devotion to some pet philosophy that would make me think seriously about starting a new job somewhere where they don't test. It's because I've done both and I like my job so much more when I don't have to deal with the bullshit that comes from years or even just months of developer laziness (often my laziness). I can spend more time concentrating on creative problem solving and actual features and less on debugging fragile code.
In my job I deal with a fair amount of legacy code, and definitely find anecdotally that I work several times faster on new code, but that's because the legacy code is crap and the new code is clean and brilliant (just like all code written by yours truly). (Of course, the fact that the code is new and is being edited by the original author are the primary drivers, but I think my code quality is slightly better than my predecessors'.) Once the code is well-written, I don't think that adding tests would significantly improve my productivity. Having a test suite would give me confidence and save me time doing manual testing (no need to test features I haven't touched and am not worried about), but don't see it having a major impact on my development productivity per se.
"Once the code is well-written, I don't think that adding tests would significantly improve my productivity"
Yeah, if you never touch that code again then it would not, I agree. I don't have many modules or classes that never change though. I suppose there might be other types of programming where that's not the case.
When I ask a question in a job interview, it’s because I want to learn something about the company, because I want to know whether its corporate culture and its philosophy of how to run a software shop are in sync with how I want to work. If significant questions get the “it depends” answer, I take it as a sign that either the place is so chaotic that it doesn’t have a corporate culture, or that I won’t know what culture I will work in until I find out who my manager is.
One of the key signals I use to judge someone's intelligence is their willingness to say "It depends." Because that demonstrates their comfort with ambiguity, their ability to see distinctions in circumstances, and their confidence in being able to make sense of unfamiliar surroundings. All of these are absolutely essential in doing high-level creative work, where there's no roadmap of best practices because nobody's done it before.
It's great that you ask the question, but if you're looking for a specific answer, you're doing it wrong. You should then be able to drill down into "Depends on what?", and then if you can have a sensible conversation based on that, you've probably found someone worth working with.
Or, you know, it means "it depends". Because sometimes, it depends on the circumstance. As they say, the exceptions make the rule.
The larger point here is that if you go into an interview prepared to dump on a company because they're not absolutists about your particular favorite development philosophy, you shouldn't be surprised if you don't get the job. And nearly every company is going to have something that they're letting slack in order to keep the lights on.
So maybe not having unit testing is a deal-breaker for you. If so, fine. Don't work for companies that don't unit test. But I hope your list of deal-breakers is short.
So personally? I say find employers who subscribe to your pet programming philosophy, but don't be willing to rule out someone who doesn't.
But I agree whole-heartedly that some jobs are just painful. Sometimes they start out great, and the company changes, and then they are painful. Sometimes its the other way around, and sometimes they are all great or all painful.
So lets step past the 'burnout' part, the damaged goods part if you will, and talk about who you are. Try to come up with times where you felt really great about your job, could be a task completed, feedback received, or even just the amount of light in the office. Let those memories inform you about what you really value (as opposed to things you think you should value). Now armed with knowledge about what you value, think about ways to interview companies which would help you know if those things are likely to be there.
I joke sometimes that people often spend a lot of time interrogating a potential boyfriend/girlfriend but don't invest the same energy in interrogating a potential company. While it is true that as a job seeker you are in the 'inferior' position to the job offerer, but both of you want exactly the same thing, a happy, productive employee. That occurs when you love your job and knowing what it takes for you to love your job and being up front with that with your potential employer will pay big dividends.
Regarding "On job interviews, don't discuss the negative experiences or the bad employer. At all. Bad job experiences are too common to deserve the "silent shame" stigma, but nonetheless, a job interview is just not the place for that. Keep the conversation positive and focused on the future." . I see this very often when I interview people and when it happens I usually stop the interview not too long afterwards.
I'm not saying I want to dwell on the negative, but if someone in an interview asks me "Why did you leave Company X?", honestly answering that I left because "Company X is badly managed" would be a lot easier on me than making up some bullshit reason, which is what I'm forced to do because everyone is so afraid to speak or hear anything negative.
I've been asked point-blank for critiques of past employers before. What is the best response?
Instead try being a bit more concrete: "I didn't like BigCo because of <specific, observable and especially non-judgemental facts go here>. Some people like that, but that's just not what I enjoy. I'm curious to hear if you feel I'll run into the same problem working for you."
If a candidate said that, I'd be more convinced that:
1. The candidate is willing to leave the BigCo world behind.
2. The candidate has realistic expectations of what a startup will be like.
I probably won't say it in the way I wrote the post, since I think it will be open to misinterpretation that might close some doors unnecessarily. But I will definitely bring up my expectations as a matter of concern.
Indeed, a fine line to walk.
Imagine yourself on a date with someone you barely know, and listening to that other person go on a long rant about his or her ex. Does that make you more or less likely to want a second date?
If they still look upset, might as well leave right now. They have no sense of ethics, and they sure won't keep promises they made you.
@HN I've been a hiring manage for years. Take the advice about what to avoid with a grain of salt, and be sure to read some of the other excellent comments in this thread.
You're not "damaged" because you had a terrible job. This is as common as dirt. Don't take it personally and don't let it affect you emotionally. Almost everyone has had one. If you can afford to take two months off to do recover, do so. If not, then find a job that will allow you to work 9-to-5 and recover on your own time.
On work hours: most startups will have occasional spikes, but well-managed ones will try to keep a 40-45 hour per week average. When people are working 70 hours per week, the quality of work deteriorates quickly. It's a really short-sighted strategy. There are a lot of startups that push people to work 70 hours, but most of those are going to crash and burn.
Also, what happens to most people as they get older is that they have mostly negative work experiences, because most companies are badly managed, and they learn things to avoid. People learn things with experience like, "Working 70 hours per week for months on end doesn't actually work out well." IMO, that's what the 20s, for the smartest people, are actually about: watching people in power fuck up so you know what not to do when you're in charge. Eventually, you'll be in a position to do things properly. It might take a while.
Some things to avoid, going forward: (1) Don't take jobs where the company isn't willing to tell you what you'll be working on. That usually means you're going to be allocated to the least desirable projects. (2) Stay away from the VC darlings, which have (as of 2012, mid-bubble) been infested in MBA culture and are companies in which you're likely to get some insultingly low (~0.01% equity) "profit sharing" offer while making 60 percent of market salary. (3) Don't take an offer just because it's "a startup". Most of these hot startups won't exist in 5 years. Evaluate the job based on the people you'll be working with and the type of work you'll get, not the size of the company. (4) Don't think you're desperate or that your negative experience makes you less qualified for the types of jobs you actually want. Negative experiences are very common, and it gets easier to recover from them as you get older. (5) On job interviews, don't discuss the negative experiences or the bad employer. At all. Bad job experiences are too common to deserve the "silent shame" stigma, but nonetheless, a job interview is just not the place for that. Keep the conversation positive and focused on the future.
For the record, I don't think it actually matters what size of company you work for. There are groups within large companies doing amazing things, and there are awful startups. "Bureaucracy", in the toxic (rather than mildly annoying) sense, is about power dynamics and I've seen dysfunctional relationships in small companies and much as large. In 2006, it was pretty clear that startups were the place to go if you wanted to learn a lot quickly, because we were coming off a bust, startups were undervalued by labor as much as investors, and there were a lot of challenging technical problems in small companies. I don't think that's as true now as it was then. In Real Technology, yes, that's still true; but most of these VC darlings in "social media" are a joke and you won't learn much in them.
What seems to be a trend, in 2012, is that a lot of large companies are developing small and mostly-autonomous groups that I think of as akin to "honors colleges" in order to get a level of talent that would otherwise go exclusively to academia, finance, and startups. Right now, I think the VC startup scene is played out and these honors colleges are a better avenue.