After reading a few of your posts in the past, I've thought about applying up where you are now (I'm an EE doing nothing EE related in my day job). I'm not sure I want to live in Madison, though.
[1] Took me two years, but I did it
I don't make nearly as much as my SF counterparts (midwest US), however factoring in for my insanely good health benefits and the ability to walk to work makes this almost too good.
Health insurance combined with a bureaucratic system that makes work oddly relaxing is a little too much to leave right now. I'm 26 with better benefits than my father had when he retired.
Our mobile development environment is a locked down internal Windows XP laptop that doesn't let anything in or out, so we had to write our own tools to package code to leave the laptop.
We wrote a simple little "chat" client in Node, but before sending the code off, it was packaged into a .jpg, and unpacked on the other side (my development macbook). This is how we've been dealing with code for over a year now.
Shit pay, 0 resources basically. Can't wait to leave.
Pay was good, resourcing was terrible, but the problem sets were really interesting and overcoming the technical challenges to get work done kept it interesting.
each team is essentially autonomous, and they pick the tools they wish to use.
yes, there is lots of paperwork, e.g. getting anything deployed requires multiple people from across the firm to agree, but it's mostly automated and doesn't take more a few hours of background time, and it's understandable: the amount of money the firm would lose if something went drastically wrong is eye boggling.
the problems are challenging and interesting, I get to experiment with extremely high end equipment that isn't available for general purchase, and the hours are good (as is the pay).
(though I admit there are parts of the organisation that don't have this freedom: you have to be careful when interviewing)
This will lead to a maintenance problem shortly. I worked in similar environments. Technically clueless managers think that they only have to throw requirements over the wall and let the developers figure out how to implement them. When someone leaves the team the replacement needs to become acquainted with totally unfamiliar code, libraries and tools.
I do not get any benefit such as daily perks which make me not to leave my job...
Recently, I applied for Google Designer Job and when I get a job there, I swear that I will write a blog post for Hacker News about the working environment of Accenture...
I can't just ditch them. I love the team and I will see this product through until production, then I'm asking for 40k/year on top of my current pay or I'm leaving.
Once the project's out, then he will have leverage in the form of a track record. Now his managers can say "look at what this guy's done for us, do you honestly want to let him go?"
1. Research-y projects. Big companies have the resources to place long-term high-risk bets on research projects that will probably fail. Some startups have a single such high-risk bet, but you can't just decide to work on whatever crazy idea you come up with because the company can't really absorb your salary for years if the bet doesn't pay off.
2. Really broad scope. One cool thing about working at a startup was that I could do whatever I wanted as long it was relevant to the startup. In fact, that was the biggest reason I went with a startup just out of school; I would have been some tiny cog on a giant team at a big company (that's not inevitable, but that's what the offers I personally had entailed). But I now have enough credibility that I can go off and do whatever I want at a big company. Since the big company has a much larger scope than a startup, there are many more things I can work on.
3. Resources. At the startup, I could take 100 machines to run an experiment and it wasn't a big deal. If I wanted to use 1000 machines I'd have to get people to ok it because I'd be eat into resources that were necessary for the company's operation. Now, if there's something I'm curious about, I can run a map reduce across the entire internet.
4. Relaxed environment. The vast majority of my team is married with kids, so the office is deserted by 5pm. There are a couple of folks I've seen stay late for a week or two to hit some deadline, but that's like one or two weeks out of the year. The startup was one of the most relaxed startups I've ever seen, but there were still month long crunches of 50+ hours/wk as some emergency came up. In principle, a startup could be as relaxed as a big company, but that's extraordinarily rare. At the big company, one of the most respected people in the office casually remarked to me that he's been at negative available vacation for all but his first two weeks at the company (and he's been here for seven years). At the startup, the most respected people all lost vacation every year because pushed up against the vacation cap.
5. This should really be like 25 or something, since it's not in the same league as the others, but I'm making a lot more money than I was at the startup.
Don't get me wrong -- there are a lot of advantages to being at a startup, and I'm glad I spent a good chunk of my career at one. I'm just saying that there's a lot I'd have to give up to go back to a startup, and the things on that list don't even make the top 30.