Live data from Hacker News

Why should I start my career at Microsoft, rather than a startup?

blog.derrickko.com

21–24 of 24 posts

Re: Why should I start my career at Microsoft, rather than a startup?

#21
I did not start my career at Microsoft, but I worked there for quite a while, alongside many who did. As far as I am concerned, the primary upshot of working there is that it's decent resume material. But beware- after 5 years of being there, it starts being a resume killer. Seattle companies are wary of developers too indoctrinated in Microsoft's ways. I would not recommend staying there for more than 3 years.

Furthermore, I am very (very) thankful that I did not start my career at Microsoft, but rather at small startups. The primary drawbacks I see for starting at Microsoft are:

* You do not really learn from your mistakes- there are sooo many code reviews, design reviews, test reviews, etc that it's essentially waterfall planning and you have very little chance to experiment and fail. Which I think is critical for starting out. You're surrounded by very experienced people, but at first what you really need to do is to learn on your own (in a production environment).

* There is a certain lack of energy on many teams at Microsoft (not all, but a large majority). You're young, you have nothing to lose, may as well learn what it feels like to work on a small team and crank out features like your company is going to go bankrupt in 3 months.

* At Microsoft, you learn to code. At smaller companies, you learn everything. A bit of customer support, business models, ux design, etc. A small company gives you a great broad base of experience from which you can build on in any direction. Microsoft for the most part, is more of a specialist (one person who just works on installers, one person just working on build system, etc).

Re: Why should I start my career at Microsoft, rather than a startup?

#22
post #14

Earlier quoted context omitted.

as a side note -- I have several friends who work at both Microsoft and Amazon as I live here in Seattle. My Microsoft friends are A LOT happier -- they have a much more balanced schedule, are not expected to be available on a moments notice and feel much more relaxed at their job. The friends I know at Amazon are very rarely off at a normal time, have a lot more pressure from the higher ups and have to regularly tak…

From what I hear it is almost entirely based on your team. If you are on a team that is working on a product that is forward facing or requires constant uptime (AWS, eCommerce platform.. etc) then you can expect to share responsibility for critical bugs or catastrophic failure. Kindle dev- not so much. As far as I know, this isn't as bad as everyone tends to think. I kind of accept it along with the engineering cultu…

Sorry, I don't mean to sound super discouraging about Amazon -- I think it can be a great fit for right out of college if you're looking for some great experience in a fast paced environment. They do have a very high burnout rate though, as many people leave around the two year mark. One of my friends has had three different managers in the past year (one fired, two quit).

I think as my specific social circle is reaching the twilight of our 20s, those environments are less and less appealing for a lot of us but a few wouldn't trade it for the world.

Re: Why should I start my career at Microsoft, rather than a startup?

#23
I spent most of my career at Microsoft. 14 years, in fact. I had a great run there, and there was a lot of good, and plenty of bad, like anything. I just up and left one day, so take that for what it's worth.

But I did spend a lot of time hiring, coaching, and observing junior engineers of all stripes.

At junior levels, I don't think it's about MS v Startup as much as "Big Company v Startup". As Steve Blank says, startups aren't minified big companies, they are a different species.

On balance, I still believe a bigger company is a better place for a first job than a startup. This is not a rule, but a preference.

My main reason for this is that the number one goal of a new engineer is learning to be a better engineer. On balance, this happens faster when you're in the presence of more senior folks to mentor and challenge you.

If you're doing a startup with a bunch of folks with similar experience levels, you'll learn plenty but you'll also bake in some bad habits.

A corallary, as noted here, is that a larger company pays you and let you focus on your core job role, versus "wearing many hats", which is great for someone who's got some things down pat, and not so great for n00bs.

This is a vast generalization and frankly there are some caveats here with MS in particular (and maybe others, n=1) that might get in the way, but in general I think structure is good until you're really equipped to make a run.

My first job was at a startup and I came to this conclusion when I left there 1996, and nothing in between has changed my mind.

Re: Why should I start my career at Microsoft, rather than a startup?

#24
post #17

There are many reasons to start your career at Microsoft. Microsoft is an excellent company to start your career at if you have a limited educational background and little which distinguishes yourself, but you are willing to put in the work to overcome this. Salary and pay for graduates from tier 1 schools is higher across the board for new graduates. But with 1-2 years at Microsoft, many recruiters and businessmen w…

Couldn't agree with you more. Microsoft is an excellent launchpad. Your points are on point with most of the 20-somethings or 30-somethings I work with. Can't wait to see what we're all doing in 10 years.
Post reply on HN