Ask HN: Best big companies to work for?
In the event that someone wants to take a break from the typical startup life (e.g. after a burnout or because of shifted priorities in life) and work for a big company, what would HN recommend for a senior software engineer (late 20s) with a very solid background developed while working like a horse in startups for the past few years (and MS in computer engineering)?
These points (in random order) might be important:
- Very very competitive salary and "deterministic" benefits (401k with good employer contributions, RSUs, cash bonuses, etc.)
- Challenging working environment where neat technical problems are still solved despite not being a startup, possibly with modern tools and technologies (e.g. not a "we use CVS as our SCM" shop)
- no more than 40-45 hours a week expected as per company culture
- Stable job (no serious failure possibility in the next 3 years or so for the company)
- Possibility of working from home (even just once or twice a week to break the routine)
- Main headquarters in SF bay area (where I'm located)
I'm of course expecting Google, Facebook, etc. But I'm curious to see what else might be there.
118 comments
[ 2.9 ms ] story [ 179 ms ] threadAll the engineering teams I've worked with are fairly forward thinking in both process and technology. Most teams use the hosted, enterprise GitHub for source control. There are a bunch of technical problems across the company spanning everything from researching photo/video manipulation, open source projects like Brackets, to a bunch of cool stuff going on as part of the Creative Cloud (or even analytics/big data in the Digital Marketing part of the company).
The company will definitely be around in 3 years and is on a good trajectory. A lot of teams have an unofficial work from home day every week, and while "main" HQ is in San Jose, a lot of fun stuff is going on in the SF office. In general I've found it to be a great culture in terms of work-life balance as well as encouraging volunteer activities.
Not only does it fit most of the criteria youve listed, Adobe technical leadership is becoming infused with alot of new blood since the acquisition of Day. Technologies like Apache Jackrabbit/Oak, Apache Sling, Apache Cordova/Phonegap are becoming integral pieces of Adobe's go to market on the DMS (Digital Marketing side - which is the lesser known enterprise offering side opposite the Creative Cloud/Creative Suite products).
It may be an big, "old" tech company, that gets a bit of grief for stale technologies like Flash, but IMO theyre moving in the right (and interesting) direction as quickly as their internal structures and market offerings allow.
So, on the bright side, there are no more insane hours, there's no begging for money, I'm doing a bluesky / "fun" project for a living, and for a big company a lot of it seems to be more fast paced like a startup. My coworkers are nice people, and my boss is like a real life Ron Swanson.
Downsides? We're not really supposed to telecommute though some managers allow it. There's a dress code, but it's tolerable. Lots and lots of meetings, and lots of lots of management. There can be a lot of communication issues between different departments. Almost everything has a well designed workflow, but they often break down due to those communication issues. As GE is a very large and political company, people without great social networking skills may need to work on them.
All in all I'm happy there, and it's a really nice change from burnout-inducing workloads, pagers constantly going off at 3:00 AM, and wondering whether any of us will have a job by the end of the day.
So they made me the offer on thursday, I responded on Friday afternoon, and they demanded an answer by Friday at 5pm. I ended up rejecting the offer but the whole experience left a bad taste in my mouth.
It's also much easier to negotiate a better deal if you have a competing offer from another firm. And doing extremely well on the interview process also helps, along with a strong track record or in-demand skill set (e.g. mobile development). This is generally applicable to the most tech companies, not just Google.
Disclaimer: I'm a hiring manager at Google.
And I speak from personal experience. As Erich stated, all the cool work is taken at Google. Blind allocation will likely land you on a team doing work unrelated to the standout work that got you noticed by Google in the first place.
If you don't mind trading away your life's passion for Google's admittedly fantastic perks, then it's a great career move. OTOH if you're finally making your mark in the world such that Google notices you, don't fix what isn't broken, avoid Google(1). My stint at Google could best be described as "Career Interrupted."
1. Exceptions: Acquihires and moonshots in your area of expertise. These are no-brainers and a great deal. Google perks plus compelling work? Sign me up. Sadly no longer an option for me because I got labelled as unmutual for leaving.
PS: I accidentally upvoted this ... hazard of using HN on a mobile phone :/
Obviously though I have my doubts.
I was invited over to their HQ to give a talk late last year and wow. An amazing company, every employee has a huge smile and nothing but great things to say, they have a really great culture, are a very wealthy company, and engineers are given a lot of freedom. Had I not just started working for myself, I would have taken them up on the full-time jobs they offered me!
EDIT: http://blogs.perl.org/users/booking_employee/2014/01/booking...
http://blogs.perl.org/users/bookingemployee/2012/03/truth-ab...
Just read the blog... what the hell?
Anyway to reply to @csswizardry while we have offices worldwide (including in SF) the only office where we're hiring developers/sysadmins is in Amsterdam, and very small sysadmin operations in Seattle/Singapore that mostly handle pager load outside of Amsterdam office hours.
If anyone's interested I'd be happy to field questions about it, my E-mail is listed in my profile.
Thanks for all the responses so far, definitely interesting names I wouldn't have considered otherwise!
- Very very competitive salary and "deterministic" benefits (401k with good employer contributions, RSUs, cash bonuses, etc.)
Total comp is high, but the bonuses are super deterministic. There's 2 cash bonuses, both based on formulas that are published. 401K is just a contribution, not a match, RSUs based on performance (4 year vesting for each issue). You also get discounts on Intel products. There's also a very nice "kudos" system where you can send people small cash awards for promoting company values or doing a good job.
- Challenging working environment where neat technical problems are still solved despite not being a startup, possibly with modern tools and technologies (e.g. not a "we use CVS as our SCM" shop)
Intel takes sand and turns it into computers, and they spend several billion dollars a year making that happen. There's a lot of tough technical problems all over the place, like how do you make drivers and software for a chip that doesn't exist yet?
- no more than 40-45 hours a week expected as per company culture
Depends on the group again. Some managers will push you to work more than 40 (all the time, not just crunch), but you have to let them control you.
- Stable job (no serious failure possibility in the next 3 years or so for the company)
The company is definitely stable. In the event that your particular group is restructured or given the axe, there's retraining opportunities to keep you in the company.
- Possibility of working from home (even just once or twice a week to break the routine)
Most are okay if you work from home once in a while. Consult your specific manager on their views of structured or regular work from home.
- Main headquarters in SF bay area (where I'm located)
Santa Clara or Folsom would be the nearest sites, but both of them are huge.
There's free tea and soda in addition to the coffee.
Generally, you would only need to be in the office if you have a meeting ( as long as you get your work done).
Depending on your team, you may or may not be expected to work over 40 hours a week. On my team, we are encouraged to work 40 hours with no overtime.Even if we need to stay in late for a bug fix, we would come in late or leave early the next day.
There are lots of interesting projects in state and local government. Great benefits, pay is usually competitive with a company (but no bonuses), and you usually get a defined benefit pension.
These organizations--governments, schools, and hospitals--aren't "tech companies". Their cultures are generally the opposite of what a person interested in technical challenges in software would want. They're places where "playing it safe" and "playing politics" are far more important than writing software.
I've had the privilege of working on some really amazing technical projects for a state government.
My startup was based in San Francisco. Even though Groupon has an office in the city, they mandated my entire team be in the Palo Alto office from day one.
The rest of the things you mention are spot on. Besides the commute issue I had no complaints.
I would differ with the "modern tooling" opinion though.
Lot's of investment/work in "BigData" (Hadoop, HBase, etc). Interesting scalability challenges at all levels. Great work/life culture.
If you get on the wrong team, you will have a tough time getting past the "group-think" established by the ranking veterans who refuse to innovate. However, that seems to only exist at the "team" level rather than the organizational level. I had to learn the appropriate place to take certain ideas.
A downside is that they don't seem to fire anyone which can lead to quite a bit of "bloat" at the lower end of the staffing spectrum. However, the higher up the technical ladder I climb the more brilliant people I meet.
The corporate red-tape is a never ending battle and my favorite managers @ the company thus far have been able to remove me from those situations and let me work on fun stuff.
The culture is a little too formal for me. The dress code is "business casual". I feel like a renegade for wearing a t-shirt to work. They have an odd reluctance to spend money on certain things and have no trouble dumping 100's of K into something else. We still use 4:3 monitors at work and I can't bring in a widescreen from home. It drives me up the wall.
Overall, the company will treat you well. You will receive a reasonable compensation. You will fight normal corprate red-tape related fights. The "unofficial technical leaders" are really smart people and drive the company in the right direction. A few people seem to take advantage of the "it is hard to get fired" here mantra, it shows.
This phrasing makes me chuckle. Why's there a presumption that "neat technical problems" are the sole preserve of startups? If I were to make a generalization at all, I'd say a successful company with a solid customer base has a lot more areas of technical challenges (both new products as well improvement and scaling of existing products) than a small startup, (especially when those small startups are in the consumer space where product features/design and customer support are far more important than sheer technical solutions).
I definitely confused "technical problems" solved by the company mission vs the feeling of excitement and freedom that a single developer gets solving a "technical problem" in a typical early stage startup.
During my time at Google, there was an engineer next to me working full-time on GCC, because found compilers most fun and technically challenging. On the open-source version, not a private branch or anything.
Very few startups would have the scale and stability to allow an employee to work on something that maybe delivers 5% faster code or 5% faster build times in a few year's time.