3 ms·
The advice I always give to a new college grad is try and get a job at one of the big tech companies. The work and the mission may not be exciting, but there i
by jedberg 9y ago
The advice I always give to a new college grad is try and get a job at one of the big tech companies.
The work and the mission may not be exciting, but there is huge room for growth and often the large companies have programs especially designed for career growth for new college grads.
But don’t get stuck. The job will comfortable. After a few years it’s time to move on. Maybe you’ve found a few folks to cofound with, or maybe you just have a good lead on a much bigger role. But the only way to really advance is to leave — most big companies have artificial limits on salary growth and promotions. You can always go back later.
- s73ver_ 9y agoNot to mention, you'll be paid enough that you can easily pay off your loans, and you can hopefully put a good sized chunk away so you'll be more able to weather the startup paying less.
- eradicatethots 9y agoIt sounds very stressful to work at a major company
- arthurjj 9y agoEh. Having worked at a Defense Company, a unicorn and then a Big 5 tech company I can honestly say the work life balance is probably the best at the the Big 5. At Defense companies you're both clearly a cost center and a cog in an unfathomably large machine. Imagine a combination of Kafkaesque and Chtulhu. At a Unicorn. You learn a lot but only because you work insane hours. Also you're paid under market wages because your job is sexy.
- oakswood 9y agoVery much agree here. I've done the same to a lesser extent (defense contractor, maybe a Big 15, failed startup, and then freelancing). Freelancing is pretty good in terms of work-life balance as well, although it can feel like an endless pursuit of finding projects (interviewing, selling yourself, etc)
- kbart 9y agoI've found the opposite to be true. In a big company you usually have a strict role and responsibilities, know what and when to do, there are established procedures for basically everything and if something unexpected happens, you know whom to call. In small, young (startup) companies you are forced to be jack-of-all-trades, take responsibilities depending on situation and there's nobody around to give an advice. Sure, it might be fun to be that-guy-who-keeps-everything-running when everything works fine, but when production server stops, you have no idea what has happened and nobody to call, all the fun ends very fast. Both ways have their cons and pros and my advice would be to try both, to see which one suits you best.