How I get Promoted Every Year At Microsoft (as a Software Engineer)
Vložit
- čas přidán 25. 06. 2024
- I've been at Microsoft for 2 years and I've been promoted twice, how do I get promoted every year? Watch this video to find out
Chapters:
0:00 - Intro
0:14 - Level systems
1:34 - Responsibility
3:06 - Accountability
4:34 - Dependability
6:36 - Be humble, thank often
8:13 - The ultimate tip
Discord: / discord
LinkedIn: / jasonlevigoodison
Instagram: / jasongoodison
Github: github.com/JasonLeviGoodison
**DISCLAIMER**:
Tech Inturn was prepared or accomplished by Jason Goodison in his personal capacity. The opinions expressed in this video are the author's own and do not necessarily reflect the views of Microsoft, Waterloo, or its affiliates.
Keywords:
software engineer,software engineering,how to be a good software engineer,how to get promoted,how to get promoted software engineer,how to get promoted as a software engineer,how to get promoted engineer,engineer promotions,software engineering promotions - Věda a technologie
I want to thank Jason publically for taking time out of his day today to get me a promotion :)
😂
This was the best tip, I didn’t realise it was a technique
Yes, the Bill I was referring to was Gates
Update 2022: I got a third promo in a row using this advice
Good advice here. I've done all of these things naturally since the start of my career and my standing with a company has always been solid. Some caveats though:
1. Be curious and take ownership: Be careful not to spread yourself thin. Make sure you've already delivered on your promises before taking on new tasks.
2. Being indispensible because you're an expert with ignored/boring parts of the system: Can be a double edged sword because you can end up tying yourself down to a position, maintaining that part of the system. It could be a career killer too (e.g., testing all the time and not taking on design tasks) -- doing something that, although necessary, wouldn't impress your next employer; deciding to leave too soon and p!ss off your manager because no once can pick up your torch.
As a new employee, I look for "necessary gruntwork" to establish a position on the team; it's usually a good way to learn about a system without being a team liability. I try to become an expert, even though I don't plan to work with that part of the system forever. And most importantly, I write notes that can be read as a guide for how to do the job -- that reduces friction when you go to ask your manager for more interesting tasks and put the new guy where you were.
3. Helping others: basically, be a good samariton. If you know a task assigned to your coworker is just 8 hours of mindless clerical work, offer to help. This is a HUGE and easy way to build rapport. I did this for a more senior dev and he now does not hesitate to help me out when I'm in a pickle. He'd even ask me to try to do some work for him, end up walking me through it, and then letting me have the credit.
Some good caveats here! Thank you for sharing :)
dude you are a real gem, no BS gold level advices for real life situations. Thanks so much!
Thanks Jason... I'm in 2nd year doing computer science. I'm right now doing my internship and I'm sure I'm going to nail it.
Yeah you are! Keep me updated!
Great video! being at aws, this is very in-line with a lot of the leadership principals we follow. I wish I knew this earlier in my career. Fantastic tips and outlook.
Thank you!
Excellent advice in this video, incredibly useful.
Good tips, we all know these things already at the back of our minds but it's always good to have an explicit reminder to help realign your work mindset!
Thank you for these advice especially the last one. Golden.
Thanks for the eye opening video! You really word your thoughts in a way that's very easy to understand!
Really appreciate it :) thanks for commenting
Hey Jason, thanks so much for sharing your knowledge and making these videos. I'm going into uni this fall and these videos inspire me and teach me things I probably won't learn at school. Thanks again and keep up the good work!
Glad you enjoyed them! Let me know what you want to see, too!
Hey man! This was great episode. ❤️💯
Thanks 😊 glad you liked it
Thank you soooo much! 🙏 Those are really really good advice!
Thank you!
Thanks Jason, for sharing new tips.
you are very mature in the subject of teamworking! you obvsly deserve all the promotions you get👍
Hi Jason, this is really good information. Thank you for sharing.
Thanks jason for all the guidance
It really motivated me
Glad it helped!
Man !!! that was amazing last tip was kind of becoming powerful you know like some kind of mc in your team .... love it jason surely gonna like ,follow ,& join discord
(btw i am a subscriber from when you touched 10 k) ..^_^
I'm a fan of your content ! Keep it up helps a lot
Thank you, Jason. It was helpful.
Fire episode 🔥 Advice was great, real inspiring for me as an aspiring SWE!
Appreciate it! I put a lot of work into this advice :)
Congratulations bro, wish you all the best 🤩
Thank you 🙌
Thanks a lot about this content it's very useful
❤
Congrats! 🎉🎉
I've watched a lot of youtube videos on promotions, and I have to say, this one is really powerful. I'll be using these tips and hopefully I can get a promotion!
very rational advices here, cheers from France.
Great Advice! I'm going to apply these in my current job 🔥👩🏻💻👩🏻💻
Thank you!!
Regarding the last one, it's a double-edged sword. You never want to end up a "Brent" where you're the nexus of too much. That's an opportunity for burnout and will lower your team's overall efficiency because you've made yourself a bottleneck. If you do make yourself indispensable, keep the bus factor low and *document* what you know or what you did. Posting stuff to Slack, an internal blog, or your bugtracker isn't enough either: it should be searchable prose in a wiki or on a site built with a site generator like MkDocs, Sphinx, or Hugo, and encourage others to contribute to it and keep it up to date too.
Yeah, agreed! As someone with domain expertise, you should always be trying to disseminate the info to the rest of the team (the "what if you get hit by a bus" factor). But its still good to be a domain expert in some areas and you'll find people will always default to you to ask questions
I am just starting my journey of job hunting and my ultimate goal is Microsoft! I love your series about Microsoft! Thanks
Amazing video
Dependability, i really learned an interesting thing. thanks
I can relate to this. These are really important skills to have other than coding.
awesome Jason, ty
You are absolutely right
I have been working as backend engineer for 4 months now and I keep thanking my co-worker everyday in public and you are right
They are more likely to help me if I am in the situation
Thanks Jason, stumbled onto your channel when looking for programming info, glad I did, you give a lot of useful information, and I like seeing the journey of how you got to where you are. Thanks again..
Being indispensable is my favourite tip. But I practice publicly thanking people more.
I never say, "It's not my fault". I say, "I told you so..." [follow the chain of emails (and other documentation)]. Then I usually say, "Just get of the way as I fix this" [I saw it coming and prepared the solution... I was just waiting until it failed so I could implement said solution]. (That's one of the ways I wrote the online permit system.)
To be fair, your videos are quite helpful and I'm grateful you've created them. Props. I would point out on the subject of making yourself indispensable, it can backfire: You may end up tied to it forever and be too valuable to promote because they want you to keep working on it because you've done so well. It's the inverse Peter Principle. Once you get a reputation for maintaining something, you may never advance in your career until you get another job and quit the one you are tied down to.
Love your content bro, keep it up! Quick question if you do see this, I’m a second year software engineer major in university and my dream work place is Microsoft, and I wanted some tips on places I should be applying to internship for. Thank you if you do see and respond to this!
Good content, thank you!
In my opinion, you, as an employee, have to be respectful and supportive as well. These two things really help and people want to communicate with you. For example, I morally supported (comforted candidly speaking) my teammate when she had some issues in her PR. She was grateful.
P.S. I’ve smashed that like button. What sub would you like? A meatball one? 😂
Great video.. thanks
I made notes during this video. I'm doing my internship at Microsoft, and I hope it'll help me to get a full-time job :)
Loved this! so true....
I'm currently interning at MS in Dublin. Gotta take notes. 😂
These are some big brain tips
I really enjoyed this video Jason! I'm not even in university yet, so sorry if this is a bit of a stupid question. Your description of your job and what you must do to succeed at it gave me the impression that in order to succeed as a software engineer you need to dedicate nearly all of your free time to the job. Do you still have a social life outside of work? Is the sacrifice of other aspects of your life worth the money and success in the career?
Hey! I'm really sorry to give that impression cause it's not like that at all. Generally speaking, I stop work at 4:30pm every day and don't think about it for the rest of the day. Every few weeks you may have an incident outside of work hours that you could help with, but it definitely isn't a daily or even weekly thing
Great tips! I’m actually going to be working at microsoft next summer for an internship! Maybe I’ll see you around haha :)
Awesome! Send me a message on teams when you join :)
@@JasonGoodison 100% will do.
Great advice! I will be starting at Microsoft next year as a university hire!
Awesome! Congrats! Send me a message on Teams when you start!
Hi @Jason Goodison awesome video , I applied for Microsoft 2023 summer internship, do you have any guidance on that? How do I reach out to you on Teams.
Just having a go getter attitude is great IMO.
Agreed!
3:28 This is actually a really important core principle from the book that has become the gold standard in mastering personal relationships, How To Win Friends and Influence People.
"Say about yourself all the derogatory things you know the other person is thinking or wants to say or intends to say - and say them before that person has a chance to say them. The chances are a hundred to one that a generous, forgiving attitude will be taken and your mistakes will be minimized. [...] There is a certain degree of satisfaction in having the courage to admit one’s errors. It not only clears the air of guilt and defensiveness, but often helps solve the problem created by the error. Any fool can try to defend his or her mistakes - and most fools do - but it raises one above the herd and gives one a feeling of nobility and exultation to admit one’s mistakes. Remember the old proverb: 'By fighting you never get enough, but by yielding you get more than you expected.' "
I read this book! Learned a lot of life lessons from it
@@JasonGoodison It's one of very few books I think everyone can immediately benefit in their personal lives from reading, and it's a book I often refer and go back to when I need tips for how to best handle dispute situations, how to affect change in people, and how to leave a good impressions on people.
Love the channel by the way! Your CS Degree abridged video was tops, keep up the great content!
I actually had a situation as described in the second advise once
I screwed up, although it wasn't entirely my responsibility, said it was mine and I was immediately defented by the others
Hi there, Jason
Hi there.
I'm 33 years old now, I have been working as Java Software Developer 10 years ago, then I moved into Cisco Enterprise Computer Network Engineering, after that I worked as a VMware Data Center Consultant.
But, now I would like to back to Software Engineering role, I feel my passion is in the software development world. How should I do the transition?
Hmm probably warrants more than 1 comment on CZcams. Can you reach out to me on LinkedIn or Instagram?
Do international student get an internship in the US while studying Cs Co-op in Waterloo and do they have to stay in the US for that given time period or can they do their internship from Canada itself
Think it depends on the company. Many are doing remote work due to covid, so interns are staying in Canada. All I can say is when I was in Waterloo, international students did internships in America and they moved to America to do them
@@JasonGoodison Ohk👍Thanks for the help mate
Hey jason
Just a quick question about accountability. What if the team doesn’t say that it was teams fault. (In this case I am assuming the scenario where it actually was a fault of 2-3 members of the team)
Then can we conclude that the team is toxic
I mean … everything in this video really assumes you are on a properly functioning team with competent management.
If you’re on a toxic team there’s really nothing you can do to grow in your role and you should be looking to switch jobs ASAP.
9:52 that's all that will happen, coworkers will think that, but not managers. I've seen people like that leave because of realizing that their efforts have been for nothing (after a decade!), or people like that just being let go because no one besides coworkers know how indispensable they are, and they don't want to admit that to management either, because they are afraid that it would look as if they are not that good at their job as their managers think.
Can't wait to apply these tips in my new and first ever software development role.
Hey man not gonna lie I skipped to the last tip, but I agree with everything you said about that.
Good to know! I've been tryng to make the content more engaging so people dont feel the need to skip. Check out some of the newer vids and let me know what you think!
whatta G!
The last tip is definitely the most important.
One example is that I work on a team that is responsible for an old DLL API application that nobody know much about.
I took it on when we had to make changes to it and now I'm the only developer on the team that knows how to work with it.
I've created documentation explaining how to compile it, but nobody has any interest so it was an easy win.
thank you Bruh
This video is gibberish but I appreciate the effort.
hello jason, i had requested for the portfolio templates on your hired for tech site, but haven't got the template, if you would be kind enough to send me those templates that would be awesome, cheers ✌
I wonder where will you get promoted after CEO
Supreme ruler of tech?
How I get Promoted Every Year: I went to MIT, The End
I have to admit: if its your goal to be promoted every year, then this is the right way to do it, well networking might be good too but that's more like kissing ones ass instead of being valuable.
But if not, don't try to follow it ad absurdum.
I wouldn't work on weekends and I don't care what happens.
For me that's an unbroken rule and if that means I will wait 2 years for my promotion, im fine.
But if you wanna be the one who does junior to senior in 4 years, Jason's way is the one to gi
New sub, sup
Oh, Bill definitely helped you.
you studied computer science or computer engineering or sth else in university?
Computer science!
The word you're looking for is mindfuck.
as the last advice i really expected follow and subscribe xD
Mindset shift 😉
Good video, I just don't get why youtubers add 2:14 in their video, does not make the video funny just distracts from the content.
"A mindset"
Hello
hello there
I don't like the advice about being on-call, at least not in the long-term. There is more to life than working and being on-call is a fast track to burnout.
You can always earn more money. But you can never earn more time.
Works at microsoft : "I don't know anyone named Bill".
Hmmmm......!!!
single every year
Real men wear 'medium' t-shirts
why algoexperts ads are made with pornstars xD x) X)
He's cute tho
Great points but I don't agree with the details on some. Might be your team's culture, but I don't think you should have to work weekends/on call in a 40hr/wk job, especially at big tech like Microsoft, to be considered -dependable-. Also, while it could make you difficult for removal, holding knowledge of the inner-workings of a "poorly" understood area of software, does NOT make you indispensable. In fact, I'm surprised Microsoft lets teams leave themselves susceptible to such inherent risk by failing to spread the necessary technical knowledge of a product or service via documentation and distribution. Anyway, it's obvious you are young, early career, and inflated video title, but this recipe you sell overall just isn't going to hold mid or late stage in a software or any kind of career in general. Wish you the best of luck.
I agree with some of what you're saying but I think there might just be a misunderstanding for some of them:
The dependable one I don't think its a requirement but as I said a few times "it'll be easier". Also I was confused by your wording it sounded like you said you shouldn't have to work weekends when you are on-call? When you are on-call you have to work whenever the phone rings. If you don't then absolutely you will be seen as undependable, that isn't an opinion. Not sure if thats what you intended with your comment.
On the poorly understood area of code thing: you're right that you shouldn't have a system where only 1 person is knowledgable. We often have meetings where we discuss how we can better diseminate the information amongst the team for our service. But I work on Windows and Windows is a different beast. There are certain people that have so much context after having worked on this product and specifically one part of it for over 30 years that its "easier said than done". We do want them to train everyone else in there field (and we have meetings for that too), but they will always be the expert in it.
Thanks for your comment
Bill gates: ...
lol works for Microsoft, doesn’t know any Bills. That was clever.