My only advice to people at BigCo is to make sure you have a good reason for doing whatever it is you're doing. Your boss telling you to do something is not always a good reason to do it.
And make sure you have some kind of metrics that show your work is important. If you're told to do something that you don't think is important, make sure you have metrics showing that your work is more important and do that.
I just started recently and was considering leaving for a startup, but have decided to stay and see if it gets better (I have only been at BigCo for few months). Mainly I feel like I'm not really needed, and it's a long existing and complex system so I can't propose some project of my own that easily. Many changes require multiple teams input etc. Feels slow.
Thanks for the advice, I will definitely keep it in mind.
I would either build credibility at your local team first (seems slow given the setup you describe) or find another group that is more dynamic. Look for energetic team leads that run impactful projects, talk to them (face to face) and ask what would it take to join their team. My 2c. Good luck
I understand the initial project you're assigned may not seem terribly important. But that's because you're new and you don't really know how things work yet, so they can't assign you anything really complicated. Do the initial not-quite-busywork successfully, and more important and interesting work will come along.
It took me around two years in to start feeling comfortable setting direction and priorities at a team-wide level. Of course, I was making my opinion heard long before that, but it was just that, an opinion.
At only a few months in you're still an unproven quantity. Don't expect to be getting the most important projects just yet. Take whatever you are given and knock it out of the park.
I like my team and manager, I just don't think they have a lot of time for me or time to think about what I'm assigned and whether it's worth doing. Lots of new ppl on the team recently. It's also possible that I'm just not asking enough questions. I think it is a bit of both.
If it turns out your manager was right (which is likely given you've only been there a few months), you'll at least get more context to understand why. You can use that context next time
I'm also not a very social person, and randomly chatting with people around the company for project ideas is something that I'm seemingly incapable of doing.
Will this cause me to fail at my job? How do I learn to be more proactive with these kinds of things?
But (to use my example) "efficiency" is relative. It requires a good mental model of what fits into what and how. So, to solve for that, you'd focus on absorption, and taking-in as much of the environment you can in as much detail as you can - oh, and focus on the most insignificant things the most. (The idea is to stretch your attention span and make it grow.) Endeavor to absorb at the same rate on day 100 that you do on day 1 (ie, replicating the way you react when things are new/interesting). Not perfectly achievable (I don't think), but that's the approach I've used to get my brain going in the right direction.
As for sociability, that's something that needs to be practiced in its own right to get stronger, like attention span. A bit like learning to use a new tool, you can't immediately be fast at it without some initial purpose-less practice. (Always fun to bootstrap those kinds of things...)
If necessary (but only as a last resort) spend an hour each day increasing test coverage. That is just something you can do that will probably also yield further ideas.
Second, if you're at google, get a mentor. They probably have an internal tool for that, maybe even something hr-like.
"The nail that sticks out gets hammered down."
Unless it's a coat hook. The lesson I think is if you're going to stick out, be useful.
Its curious how these companies claim they are totally different or even unique but just turn out to be the very same.
>>I wasn't promoted when I figured I deserved it
This is again one of those large company political things. Year long promotion packet building, lobbying your work with promotion committees, getting a willing boss, and doing other routine political ground work to set you up for one.
Another big thing in these companies, every one joining has to go through a very arduous interviewing process, preparation for which can last weeks to months. So you have rockstars full in all teams, or at-least they like of themselves that way.
Ultimately regardless whatever people might say about surrounding yourself with smart people, its never generally a great idea to surround yourself with smart competitors in a pyramid hierarchy.
If a smaller company has a toxic culture or you have a toxic manager you may have no choice but to leave.
Bad managers are everywhere!
Honestly, I don't care enough about getting promoted to go through that whole rigmarole, nor would I quit a job over having to deal with that in order to get promoted.
Of course, that's also probably why I don't work at a FAANG and never will.
Of course, that's also probably why I don't work at a FAANG and never will.
I don't think you should let that stop you. I work at Google and don't care about promotion. I expect that I will get it sooner or later but really don't care if I do or not. I get paid enough to live a decent life already so I prefer having the freedom to do what I think matters as opposed to what's good for my career since sadly those don't align as much as they should.
then again, i hate office politics and i cannot see myself getting to close to this kind of big-company.
I'm guessing you don't know how the process works? I'd like to give a summary so you have more context. Apologies if that's incorrect.
Your promotion is decided by a promotion committee, who likely do not know you or what you do. This is done in an attempt to make promotions fair and objective across the company.
That being the case, you need a promotion packet to describe what you've done to people who are basically strangers.
Don't get me wrong, the process has many issues but I don't think it's fair to assess them without understanding their purposes and I don't think anyone I've seen who complains about it has been able to come up with something better.
In my career experience, that has more to do with understanding what really needs to be done, and what brings value to the company.
I'm sure I've made some junior engineers feel that way after they tried to pull me into a long argument about brace styles, or after they wanted to refactor years of working code to use their favorite framework.
Were you on a 4 year vest schedule for your stock grant at Google? If so, did you leave some money on the table?
I left for a more senior position at a smaller, less prestigious software company, though I've moved again since. Right now I'm working remotely from Toronto for a Silicon Valley start-up.
Ultimately, I wish I had approached working for Google a bit differently. I thought it was sort of an overgrown startup, and you were supposed to look for something that needed doing and do it. No. Google is a large highly structured company with a distinctly process-oriented culture. It's a place where you do what you are told. That famous proverb about Japanese nails absolutely applies. I eventually figured that out, but by then it was too late.