I don't want to work for a big company

One of the cardinal rules of software development is to ask your market what their pain points are, but come up with the solutions on your own. That's because your users understand their problems, but they aren't aware of the different ways you can solve those problems.<p>For lack of a better word, I'm going to call this the <i>over-association fallacy</i>. The over-association fallacy is when you think "I must have X, Y is one way to get X, therefore I must have Y."<p>This post is a classical example of the over-association fallacy. What the author really wants is the freedom to experiment, and he concludes that you can't have this in a big company.<p>However, there are plenty of big companies that give you that freedom, and plenty of small companies that don't. The smallest company I ever worked for had 4 people, but the CEO was an extreme micromanager who layered huge amounts of work on his employees and was terrified of innovation. In contrast, I had a huge amount of freedom to play around at a giant bank, because I automated all my work and my manager only cared about the quality of work (not how many hours I spent.) The result of this playing around helped me learn a lot and save the company millions of dollars.<p>So keep in mind what you really want. Don't avoid big companies, avoid places that don't let you learn anything.

One thing I've noticed about large organizations is that they pay more. Pay is set in a structured way with regular pay rises, so you can just sit tight and watch it rise.<p>Additionally, you can move around without leaving the company. Why is that important? Check the graph from the long term unemployment article[1]. Personally, I like to move every 2 years, so that's kind of important.<p>I'm going to write about something of personal interest now. Downvote away. It's a bit UK specific.<p>Something I've noticed, looking at the people I graduated with 8 years ago, is that the ones who have done well went to work for large companies. They did a grad scheme, stayed in the role after it had finished, and just sat tight, maybe moving a couple of times within the company.<p>They earn a multiple of those that didn't - the PHDs, sure that's expected, but also much more than the freelancers and those who have hopped between small programming houses. Certainly more than people who did something fashionable, like fashion, the arts, or teaching English abroad.<p>The funny thing is that those left behind don't have an opportunity to get on that gravy train now. Grad programs are for recent graduates. Experienced hires from companies the recruiter has heard of get first place.<p>Another effect (an this is UK specific) has been in mortgages. Since 2008, you need to save maybe 70k dollars in order to get one. That's a full years pay for a software engineer. 4 if you count tax. But rents are double or triple mortgage interest, so unless you already have one, you won't save that.<p>So we have this widening wealth gap between those who got onto, and stayed in, a graduate program 2008, and the rest. It will really be quite something in future.<p>The BBC did some analysis where they collected data about the population (wealth, cultural signifier), and clustered it. They found 7 distinct clusters, and decided to invent a new 'social class', called 'emergent service workers'. This turned out to mean 'young people who graduated since 2008'. I suspect they will be a generation of lifetime renters, doing similar jobs for a little less money than their peers 2 years older (starting salary has a compounded effect, and is suppressed by maybe 1/4 right now).<p>I don't really see this in the press. As usual, they don't notice things.<p>We live as ever in interesting times.<p>[1]<a href="http://cdn.theatlantic.com/static/mt/assets/business/LongTermUnemploymentChurn.png" rel="nofollow">http://cdn.theatlantic.com/static/mt/assets/business/LongTer...</a> [2] www.bbc.co.uk/labuk/experiments/class

The vast vast majority of interesting technical work is done in large organizations, or at least organizations that have enough people that you're not "picking your clients". Small companies that have genuinely interesting work are sadly the exception rather than the rule. Many of those small organizations support themselves with DARPA R&#38;D contracts or the like.<p>If you really care about interesting work and colleagues, there never a cut and dried answer about small vs large organizations. Ever.

I dunno about "better chances of getting to the top" in a big company.<p>In a company with 10,000 employees and 5 C-level employees, not everybody gets a shot at a C-level position.<p>In a small company you might just get a position with high responsibility (if little status) that will get you ready for a high responsibility position with more status elsewhere.<p>I once worked at a web design shop where three salespeople who dressed normally, a few goth designers and programmers, and me who dressed "business goth" at the time. (I got along really well with everybody.) The production people got out their anger against the world by designing web sites with black backgrounds for everything. They would have put black text on a black background if it would have gotten past QA.<p>I've been contracting with many big corporations and I've found many where the people are a delight to work with -- I'd imagine these people are happy.<p>Remember also that big organizations are divided into smaller units which are further subdivided. These can have radically different cultures.<p>A major University I know of has many IT cultures.<p>The central IT organization is a disaster, although I know many people who've found comfortable places in it. If you try to get something done by going through official channels this has a 25-40% chance of working.<p>If you have a large rolodex of people you know there, however, you can guess who might know who to call to fix the problem, and eventually find that person, naming by name all of the people who helped you find them.<p>Then I get off the phone and I'm like "damn... I got this guy to change the firewall settings for the campus and how does he know who I am?"<p>I was dealing with another major IT organization and tried to compress the schedule using the same technique. Well, he called his boss, and his boss called my boss, and we got it done.<p>There are so many companies out there with so many parts that there's very possibly some position you could stand to do.

Tangent - Can someone please explain to me what medium is? It seems like it's the new svbtl, but I'm not quite sure if it's a collection of individual blogs, a curated selection of posts or an open community platform.<p>Their home pages (<a href="https://medium.com" rel="nofollow">https://medium.com</a>) states "Sharing ideas and experiences moves humanity forward" which sounds really nice, but still tells me absolutely nothing about what the platform actually is/does.

We're a web development company in a 'company town' where everyone seems to work for a single Fortune 50 company. You think it'd be easy to hire developers away when you offer good pay and benefits, 4.5 day work weeks, flexible hours, casual dress code, and we buy you whatever hardware you want.<p>We don't get a single qualified applicant. We use Ruby and Javascript, it's a ~ 25 person company so you can make a difference, you can work on iOS or Android stuff. If you only know a different programming language, we'll still hire you and let you learn if you can prove you're competent.<p>We're not silicon valley or a 'cool' city, but we're near a few state universities. I guess people would rather sit in a cube, in a suit, while they work on legacy internal apps in VB and .Net for a cold, dark corporation and wait 20 minutes each morning in line at the security gate just to get on the damn property.

I have worked as a software developer for a very large company (Ericsson) for nine years, and for smaller companies (Tilgin, Symsoft) for eleven years, and I too prefer small companies.<p>The biggest difference for me is the impact ypou have. In a small company, your own contribution is a much larger part of the total output, and that is very satisfying. Frequently it also means faster turn-around time - what you do gets deployed much quicker.

Sorry to break it to the OP, but <i>most</i> companies are shit. Big or small doesn't matter <i>that</i> much because all people (under the right conditions) have parasitic tendencies and power makes it worse. Good companies are easily less than 10 percent, and startups are no better.<p>What makes startups seem great is the survivor bias. The shitty ones with MBA-style management and closed allocation tend to faceplant. The good ones grow and become less good gradually.<p>Also, many of the big-company perks mentioned in the OP don't exist.<p>Big companies actually don't provide better benefits than startups. Banks, for just one example, have pretty shitty health insurance due to misguided shareholder activism and cost-cutting. Also, it takes <i>forever</i> to move up in large companies. The upshot of that, though, is that you'll never have a 25-year-old manager-favorite ladyboy hipster douche barking orders at you (which I have seen demolish a startup or two).<p>Finally, large companies are not great at long-term projects. Those tend to be cut first when there are cuts, and in most companies, continuous cutting is now in favor over press-making layoffs. The best people in large companies (excluding companies with a real research presence, and those aren't paying salaries that would impress anyone on HN) want to work on immediate P&#38;L stuff, not long-term efforts that lack job security and short-term promotability.<p>There is exactly one reason to work for big companies, and it can be substantial: <i>lateral mobility</i>. Your compensation won't go up fast, but if you can move to more interesting work under a manager the ability to protect, it can be a pretty damn good deal, because with a good manager it doesn't matter that you're in a mediocre company. You'll get to learn a lot (even if you won't have a major impact) and your work will be interesting enough (much more interesting than what most of these startups do) to provide jumping off points into credible side projects and, possibly, startups. It can be a great way to get a 5-year stint (there are plenty of HR Boomer-o-saurs who are still stuck up about "job hoppers") and a lot of time to learn.<p>The problem is that most companies make it a lot harder to move internally than they advertise. They have ridiculous "headcount" issues and it's almost impossible to move in most firms without a top-20% performance record... but impossible to <i>get</i> a top-20% review unless your manager sees you as having staying power. So you have to play dishonest political games, in most companies, to get the one big-company benefit (lateral mobility) that actually matters.<p>In fact, most companies are so fucked up on the matter of internal mobility that the only genuine time at which transfer's possible is shortly after a promotion, but managers rarely promote people who seem to have any interest in mobility.

"But being in school is not something I truly want. I love creating, innovating, pushing myself with real-world challenges and projects, and the amount of satisfaction you get from pushing something out there is tremendous."<p>I've seen this type of sentiment before - it's quite common for people who don't go through school.<p>University level education (quality ones) give the student exactly the same feeling that the author is describing as enjoying. The only difference is that the pace of learning and achievement is far higher then it is in the real world in which you are subject to daily demands for return on investment and stability.<p>I've been through both University level education and real world work - I'd take University any day of the week. University provides an environment in which experimentation and play is encouraged - I have yet to find a work environment that does the same, even among small start-ups.

I'm a consultant that mainly works with big companies, the main thing big companies have in common is that they are big.<p>Seriously there's so much variation in how they go about things that it makes no sense to say big is bad and small is better. It all depends on the individual case. I've seen a lot of dysfunctional companies of all sizes.

&#62; In my opinion, the larger the company and the higher the hierarchy, the harder it is to innovate and experiment with something different for that next project.<p>In my experience this just simply isn't true. Both large and small companies can put up reasons why you can't innovate or experiment.<p>For small companies there is always a deadline or budget that gets in the way.<p>The size of a company has no real bearing on what they allow their employees to do.<p>The only difference I've seen is with well run and poorly run companies.<p>In my experience these are evenly distributed between big and small companies.<p>Or put another way, your manager will determine 90% of your happiness at your job.

IMHO, the divide (at least in the US) is not between big and small but between public and private. In a private corp you get a chance to find an awesome work environment no matter the size and in a public, it appears, even if it had not been bad before, it's going to become worse.<p>PS. I am not saying that <i>all</i> private companies are awesome. Some are exceptionally bad e.g. Lucas Arts used to be pretty horrible. I am not saying that <i>all</i> public companies are horrible either - Apple seems to be all right.

"sales dude extrodinaire" I will be using that phrase a lot.