I don't want to work for a big company
medium.comOne 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.
For lack of a better word, I'm going to call this the over-association fallacy. The over-association fallacy is when you think "I must have X, Y is one way to get X, therefore I must have Y."
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.
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.
So keep in mind what you really want. Don't avoid big companies, avoid places that don't let you learn anything.
Yes, I love this realization.
People don't know what they want, but they sure as hell know what they don't want. I think this ties both to businesses (specifically startups and what they focus their efforts on) as well as employees and entrepreneurs themselves.
To quote Henry Ford: "If I had asked people what they wanted, they would have said a faster horse."
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.
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.
I'm going to write about something of personal interest now. Downvote away. It's a bit UK specific.
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.
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.
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.
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.
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.
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).
I don't really see this in the press. As usual, they don't notice things.
We live as ever in interesting times.
[1]http://cdn.theatlantic.com/static/mt/assets/business/LongTer... [2] www.bbc.co.uk/labuk/experiments/class
> The funny thing is that those left behind don't have an opportunity to get on that gravy train now.
For what is worth, I noticed that also (not in the UK, but somewhere else in Europe). My ex-wife, a psychology major, managed to get hired into a big oil company doing procurement work (yes, they were that desperate at hiring people) around 2005-2006. Of course, in the meantime she has gathered a ton of experience and she'd have no problems whatsoever of picking another similar job at another big company.
For comparison, looking at kids aged 22 to 24 who have just graduated it seems like they're, well, fucked. Nobody will hire them in a big company for lack of work experience and they can't get any experience because nobody wants to hire them.
> " looking at kids aged 22 to 24 who have just graduated it seems like they're, well, fucked. Nobody will hire them in a big company for lack of work experience and they can't get any experience because nobody wants to hire them."
IMO this makes a strong case for working with small companies. Big companies are relatively risk averse and will look for external validation of the candidate - certifications, degrees, impressive prior experience, etc.
It's much easier for a young person lacking experience today to approach a small business and successfully pitch them on an internship or some contract work. A large corporation is too hamstrung by HR, by policy, and by its own approval chain, to take advantage of things like this.
Speaking of which, if anyone is reading this from the UK, and has an ~ 18 year old who doesn't want to go to university, BAE are recruiting heavily for apprenticeships. They are very serious about providing a 'university alternative'. I suggest taking a look.
London is city of finance. There are only few good technology companies that happened there. A few years majority of good people went to investment banking and starting a company was perceived as reckless. Probably a lot of programming places was kind of outsourcing places, not creating long term product.
Would you relate your situation to the Silicon Valley, where majority of new tech companies have been created? How would you compare situation of your friends to situation of people who joined Google 15 years ago, or Facebook 8 years ago?
I would bet that in UK ratio of revenue of big companies to small companies is much higher than in Silicon Valley.
You make good points, I certainly wouldn't extend this to America, or even other parts of Europe.
It is true that a lot of London money is made in finance, but we also have some giant engineering companies and subsidiaries, such as Rolls Royce, BAE. Sony, Huawei, IBM, Siemens, and others have large research presences in the suburbs, because engineers are cheaper here than in America, but we have more aggressive IP laws than China or India.
If you want a big company to get lost in as an engineer or project manager, there is no lack of them.
Working at a startup, hoping for an IPO, is a high risk high reward gamble. People choose to do it because it gives them agency over their work and futures in a way that being part of a big machine does not, but most fail, and we should be aware when we take a risk what that risk is, hence my post.
Taking advantage of London's competitive advantage in finance, a lot of financial startups have won really big, setting up major energy trading exchanges and brokerages, though you wouldn't hear of them outside the industry.
I'm more cynical about the current wave of London web startups.
Would I suggest a young Londoner goes to work at a startup? This city has a bit of an unpaid internships culture, and I fear they would get the same experience as at a larger company, for less CV impact and no money. Get into computer security at KPMG, you'll get rich.
Around 2010, 2009 I noticed some articles come out that observed that in general, people who graduate in a recession have lesser lifelong earnings than people who graduate in a boom.
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&D contracts or the like.
If you really care about interesting work and colleagues, there never a cut and dried answer about small vs large organizations. Ever.
I do agree with you on the fact that the most interesting technical work is indeed done in large organizations, but it has (at least in my own experience) always been the case that the companies strive to get lots of clients instead of trying to choose the ones where they think they could do something awesome with. You know?
I suppose I came out a bit aggressive on the fact that it's about small vs. large organizations only, but this was just my own personal opinion based on (only) a few years of experience in the field.
I'm not ruling out large organizations, and large organizations can also be all up for the new and interesting stuff, but that's not the case in the bureaucracy companies (which I'm ruling out) where everyone is stuck to the standard in-house CMS, programming language, or framework.
There's always exceptions to every rule. I agree with that.
> The vast vast majority of interesting technical work is done in large organizations
So is the vast majority of boring technical work.
Small companies have a lot of work. A lot of work doesn't actually mean good work.
Unless you are simply looking to undergo a form of endurance training.
I agree, it seems that smaller companies as for more work for less. Usually, in my experience, they need something to outfast, but don't care if its made correctly since they just need to look good to sell the business.
I dunno about "better chances of getting to the top" in a big company.
In a company with 10,000 employees and 5 C-level employees, not everybody gets a shot at a C-level position.
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.
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.
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.
Remember also that big organizations are divided into smaller units which are further subdivided. These can have radically different cultures.
A major University I know of has many IT cultures.
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.
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.
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?"
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.
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.
Their home pages (https://medium.com) 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.
I consider Medium a new way of writing articles with some insight, instead of tutorials and online findings. I'm thinking of using it for the sole purpose of getting my opinions out in the open.
Medium only comes with a simple editor with minimal formatting options and you can push your posts into "Collections", by either yourself or by other people. With that you can create lists of articles about things that are related to each other.
I only just got into it, so I can't really say what the main focus is, but that's what I think.
How about first link from Google when asked your question? ;) http://gizmodo.com/5935016/what-is-medium
Even that link concedes - "There's really nothing new about Medium."
I'm really not trying to hate on Medium - it looks really clean, but I'm just trying to figure out it's placement in the content publishing space.
I see it as just being a brand.
Some of the old magazine publishers are exploiting their brands by having stables of people throwing up whatever topical crap pops into their brain, never mind quality or accuracy, so there is clearly some market for topical writing (seems to me the tendency for articles to occasionally get huge attention drives posting lots of articles).
If Medium can build a brand around having decent recent articles, more power to them (I see svbtle as the same thing, with different ideas about curation).
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.
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.
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.
It's a risk reward thing. I'm one of those company town people. You put up with a certain amount of nonsense in a big company, but you get stability, career path, great benefits, etc.
Small companies aren't nirvana, and if there are few small companies, you're taking a big risk that you're stepping into an organization where the owner's dumb nephew will be made an SVP over you. In the valley, you jump ship. In the "company town", you need to uproot and move.
I saw this attitude quite a bit at the large defense contractor I used to work for. As in your case, I'm in an area without much of a small-company tech culture[1]. Additionally, this area saw a big telecom surge during the dot-com bubble. A number of people left for telecoms large and small during that period, then got burned on the bubble pop and came back humbled. This reinforces the culture of staying put and dealing with whatever crap the company descides to put them through.
Defense contractors are a bit of an oddity, though. Its a quasi-government job, overall the most stable private sector employment, and has excellent benefits. Someone starting at my former employer out of undergrad today does have a reasonable chance of retiring from there. It seems like the workforce is slowly distilling down to those for whom such old-style employment is highly desirable.
[1] Its slowly changing, but it seems to be mostly B2B services, marketing and advertising shops.
Just an idea: qualified applicants could preffer to work for themself.
What town are you talking about?
Midland, MI
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.
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.
I recently blogged about what I look for when considering where to work: http://henrikwarne.com/2013/03/26/what-do-programmers-want/
The three main criteria are "the product is software", "great colleagues" and "challenging problems". Small/large is not on the list, but maybe I should have added "having a high impact".
Sorry to break it to the OP, but most companies are shit. Big or small doesn't matter that 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.
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.
Also, many of the big-company perks mentioned in the OP don't exist.
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 forever 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).
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&L stuff, not long-term efforts that lack job security and short-term promotability.
There is exactly one reason to work for big companies, and it can be substantial: lateral mobility. 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.
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 get 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.
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.
> 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 get 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.
>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.
This was the driving reason I left my prior employer. I had no internal mobility without some sort of advocate, despite the large number of open reqs. At the end I got hit by the political double whammy of not having any support for a lateral transfer from my manager[1] and being on the 800lb gorilla project that was trying to draw people in from elsewhere at the time I was trying to leave. The company got away with shit like this, though, because most people thought that was just the way it was at large companies, and small companies were too risky and flaky.
[1] I even got labelled "disloyal" in the heat of the moment for expressing the desire once.
What you experienced is typical. It's harder to get a new job within a company than to get an external promotion into another one.
Here's probably more than you care to read on this topic. I just finished it this morning: http://michaelochurch.wordpress.com/2013/04/16/gervais-macle...
The short version, as pertains to what you experience, is that companies have (since Enron made it fashionable) included performance reviews in the transfer packet as a way of enabling managerial extortion (for the sake of project expediency, although it's unclear that it achieves that) and passive firing, reducing lawsuit risk. The passive-firing infrastructure is supposed to be there to make low-performers look objectively unwanted (lawsuit issues) but the headcount limitations and transfer blocks actually end up getting used against high-perfomers that their managers want to keep captive. Google (which has Enron-style performance reviews) has a well-documented problem with this.
My own recent-ish exeprience on this may be of interest - I was made redundant (worked in City) in 2008. I kept job hunting like a demon, and went through three jobs in 18 mths, going from unemployed to 100K - but each time I moved companies, and I think I did not spend less than 4 out of 5 lunch hours glued to phones hunting down leads.
Not sure if thats of interest
In small company, while you don't have internal mobility across teams it's much easier to work on different projects, since cost of switching between projects is not so expensive as in big company. There are no formal management rules, so you don't have to play politics to achieve this.
Even in companies with "open allocation" you are not given completely free choice where to work, because you first need to gain credibility. It's faster to achieve level of credibility, required full freedom on what to work inn smaller company with open allocation than in big corporation, even ones, which are pretending to have open allocation.
In small company, while you don't have internal mobility across teams it's much easier to work on different projects, since cost of switching between projects is not so expensive as in big company. There are no formal management rules, so you don't have to play politics to achieve this.
It depends. Small companies can go to shit quickly. I've seen it happen at under 10 people.
Even in companies with "open allocation" you are not given completely free choice where to work, because you first need to gain credibility. It's faster to achieve level of credibility, required full freedom on what to work inn smaller company with open allocation than in big corporation, even ones, which are pretending to have open allocation.
That goes against open allocation, because the whole idea is that you have the right to work for the company directly without needing a "credible" person to sanction it. Open allocation probably requires that projects have some degree of sanction, but that should be based on project merits as much as possible. And if people aren't free to move form one sanctioned project to another, then it's not open allocation.
> ladyboy
This doesn't mean what you think it means. Or at least I hope it doesn't.
Synonym for "golden child" or managerial favorite, and yes, I know that it originally meant a male prostitute dressed to look feminine. I'm not the first to use it in that way.
"Golden child" doesn't have enough bite and Ancient Greek references get old.
It definitely still means a transsexual prostitute. I can't find any mention at all of this managerial definition anywhere.
I'm not disputing that it is used that way in certain circles, but it isn't common. Also, ladyboy is often used as a term of hatred and abuse against transsexual people, so if you keep using it like that eventually you're going to be in a situation where you come across like some old guy casually talking about "niggers in the woodpile" and that would be bad. (I'm not saying it's equivalent, just that it could land you in equivalently hot water. You know what I mean.)
I didn't know that it was a term of abuse. I won't use it, then.
I guess we need another emasculating/biting term for male managerial favorites. "Protege, in the Ancient Greek sense of the word" is a lot of words, but it's the best alternative I can come up with.
Perhaps a re-contextualisation of the phrase "Teacher's Pet" could be sufficiently infantilising?
Desk ornament.
Shame, cos I could have sworn he was talking of my direct experiences
"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."
I've seen this type of sentiment before - it's quite common for people who don't go through school.
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.
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.
Experimentation in a very narrow manner. A university is where you explore new algorithms using Fortran on an old Sun machine. However, if you are just interested in a new programming paradigm, want to write an ORM in Haskell, or design a new IoC container university is not for you. As someone with a masters degree in CS I can assure you.
Might be true for Computer Science, but what does computer science have to do with tech/innovation? ;)
Engineering programs are a great example - most provide opportunities for students to join projects outside of the core curriculum to build something cool (sun powered cars, robot competitions, etc). Even the Arts programs offer opportunities to do exciting things (and especially fine arts).
My comment was to dispute the notion that school isn't an environment where someone can push the boundaries - on the contrary, it's the very place that boundaries SHOULD be pushed (both personal and other).
> However, if you are just interested in a new programming paradigm, want to write an ORM in Haskell, or design a new IoC container university is not for you. As someone with a masters degree in CS I can assure you.
As someone with a masters degree in CS I can counter-assure that University is faaaaar more open to experimentation and delving into new things than a company.
I'm a consultant that mainly works with big companies, the main thing big companies have in common is that they are big.
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.
> 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.
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.
For small companies there is always a deadline or budget that gets in the way.
The size of a company has no real bearing on what they allow their employees to do.
The only difference I've seen is with well run and poorly run companies.
In my experience these are evenly distributed between big and small companies.
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.
PS. I am not saying that all private companies are awesome. Some are exceptionally bad e.g. Lucas Arts used to be pretty horrible. I am not saying that all public companies are horrible either - Apple seems to be all right.
"sales dude extrodinaire" I will be using that phrase a lot.