Career Advice About Microsoft

Every time, when my manager asked me to do some changes to the repository that is totally new to me. I became scared.

I prefer to do research by myself first. But I got lost in the new repo by reading file by file, and don't get the clarity.

So I ask the repository owner to provide documentation, mostly they don't maintain documentation, and even if they do, it is not updated or it involves a lot of detailed feature-wise documentation, which is usually not relevant to my requirement.

Then, I call the POC of that repo, but I couldn't figure out what is the right question to ask in the first call. Over time, I ping him asking questions whenever I face hurdles while achieving the requirements.

Sometimes, I put a debugger or logs to understand the flow of code.

The above processes took a lot of my time.

What is your suggestion to get clarity in the new repo such that I can complete my requirements in less time?

My team owns a really wide set of features spanning across multiple repos and programming languages (C++, React, Angular). On top of that, each person works on pretty different areas (telemetry/data, UI components, client side api, etc.). We have a v1 of the app being maintained and a v2 currently being developed with some people working on v1 and some working on v2. It's impossible to know all the context behind every pull request.

How can I give quality code reviews? At most I can only provide feedback to simple code logic and really well written PR descriptions. Should I be trying to private message the developer for each PR to understand more, or is this just something that comes with time?

I've been debating this though for a while. Is it worth it to go for a principal role (61 -> 62 -> 63 -> 64) or just go and build something your own

I am good at coding, and I am able to deliver features to prod. However, when it comes to technical writing, like writing software design document, coming up with state transition diagram, block diagram, I am struggling with it a lot. I am not from computer science background, so I am not well versed in coming up flow chart, sequence diagram and state transition diagram. How to improve on these areas? Because of this, I am finding it difficult to communicate my idea to principal engineers/ architects. How can I improve on this?

I was watching this recorded session . In that series, Alex mentioned picking a tech stack and sticking to it.

In that case, I work in C# and .net tech stack, however, if I switch companies, and the other company uses Java and its relevant framework, how can I gain expertise in that stack?

Should I look for jobs that use the tech stack that I am strong with?
Or learn and master the tech stack that companies use?

Hello! I would appreciate some career guidance tips in transitioning to a new role. To give some context about me, I am currently L62 at Microsoft with 7 YOE and have recently received an offer for E5 at Meta. It is a level+1 for me. From what I have gathered, the expectations for E5 are going to be high involving scope/ambiguity resolution, delivering under tight deadline, etc. Also given the stack-ranking nature of evaluation, might need to compete with my new colleagues, who are currently working at senior level.

I feel I'm an average+ engineer and doing WFH for the last 3 years made me working in silos. My current team does not punish teammates without active participation. Being introvert by nature and someone who is afraid of public-speaking, I got used to the comfort zone of inactive participation. My misconception about focusing solely on technical skills to grow in career has made my career progress slower and I am painfully realizing it lately. To add to that, job security is important for me as I'm a visa holder.

Given this context, I am considering whether to take E5 Meta offer. On one end, I can take this as a growth opportunity and improve my technical and soft-skills. I am definitely looking forward for ways to increase participation, influence team and being a strong engineer. I wonder if I should improve my current soft-skills in my current-role and then move or if I could simultaneously improve them on my new job.

On the other end, I wonder if I could survive in an environment like Meta and deal with stress/burnouts and whether the lack of improved soft-skills would make me unsuccessful in my new role.

Appreciate your thoughts!!

At Microsoft, basic criteria for promotion is to deliver at next level consistently. Example: At L62, i need to work and deliver at L63s work level standards.

I had a career discussion with my new manager during my one-on-one meeting. I did ask him if he is ready to put me up for promotion to senior software engineer. He said he will gather feedback and get back to me next week. In the following one-on-one discussion, he brought up a few points as feedback.

1. I have to do independent projects: (I have already delivered three independent projects right from design to shipping to prod. My old manager knows about this and he had given me the highest rating).
2. I have to mentor juniors: (I have already mentored two juniors in my team).
3. He pointed out saying that I took more time to lock my recent design: ( We took over a project from another team, and the design had many open-ended loose strings. I took the initiative to fill those gaps apart from designing my module.) From this discussion, I feel like my new manager is either less informed or he lacks knowledge of the previous impact that I delivered.

I am actually upset and demotivated. How can I handle this situation? How to move forward with my new manager regarding career discussion?

He keeps assigning me projects where the visibility is low and it has made me immensely frustrated. I'm looking for a new job but in the interim any suggestions how to deal with my manager? This has been happening for quite sometime now. I talked to him about it last year and then he moved me to a development project which I did pretty well but after it was over he again assigned me low priority projects/tasks which are very tedious to do and not so rewarding.

I'm not sure talking to him will help me in anyway because he is aware of my interests but he keeps doing this and acts like this is the best he can do.

Some of my work involves coding in an old AngularJS codebase that has a lot of issues. Most files are 5-6k lines long, many of the functions are on v3() while v1 and v2 are left in there creating technical debt. We've already moved on to a rewrite of the application in React, leaving the AngularJS code a mess that no-one cares about.

How should I approach work that is assigned to me in this codebase? Get it done as fast as possible so I can get back to my "real meaningful work" in the React codebase, probably adding on more technical debt in the process? Take my time and try to make the most even if the code is worse and I might be learning anti-patterns? The AngularJS codebase will be deprecated and migrated away from in a year anyways so developers don't really care about refactoring or improving the code quality. I've been trying my best to essentially avoid work in the AngularJS codebase, but unfortunately I can't ignore it since 200 million+ users rely on it and oftentimes on-call issues crop up in it.

I have 15 years of experience in the tech industry. I joined meta as an E6 engineer in July, following 7 years at Amazon and over 6 years at Microsoft. Afte joining, I quickly initiated and led small projects, progressing to a major project. I utilized my experience to guide and support other engineers, contributing to their professional growth. Our team has another E6 tech lead with deep domain knowledge and currently, he is the face of the team. We maintain a positive and respectful relationship, trusting each other.

However, I observed that our engineering manager (EM) was not effectively providing direction, hindering team productivity. Recognizing this gap, I collaborated with other tech lead to create a project tracking sheet, enabling us to monitor initiatives with timelines and ownership. This significantly improved our team's efficiency and motivation, leading to the successful completion of a major project.

Now, here's the exciting part – my skip reached out and surprised me with an offer for the EM role! While I'm honored, I'm grappling with doubts about whether I have the necessary skills for success. Despite enjoying mentoring others in technical discussions, I'm concerned about potentially losing touch with the hands-on tech work that I love.

On the bright side, my tech lead partner is supportive and believes I should take on the EM role, offering full support. However, I'm contemplating whether I should explore the possibility of a Tech Lead Manager role to strike a balance between leadership and hands-on technical involvement.

I'm at a crossroads and would love to hear your thoughts and advice based on your experiences.  One side me want to try EM path but one side says why take this hassle and stick with what you know better i.e tech. Also, I treat myself as avg communicator. I feel, I am good at empathy, task breakdown and mentoring skills.

I live in orange county, CA. I have about 30 years of tech experience where I was a software engineer for most of these 30 years. I also had couple of jobs as manager leading a team of software engineers. For last 5 years, I have been working as a senior software support engineer for a local company here in Orange County, CA.

So I would rather be software engineer than be in a support role where I just do mindless support of enterprise software. And its not very challenging either. So when I started working for this company, 5 years ago, I started to teach myself angular and typescript. Worked on a project and deployed it live on the website and learnt a lot. And really enjoyed programming.

But then 1 year ago, I started applying for actual jobs in angular programming and got zero response. Zero emails from the companies. Zero interviews from the companies. That was very scary. So a friend who works at Microsoft, advised to prepare and apply for SWE job at Microsoft. She mentioned that MS would not care about lack of my latest/greatest experience. If I pass the coding interview, I have a good chance event to get an entry level SWE job which is better than what I am doing these days.

Another reason I would like to work at MS, is that all my 30 years I have worked for midsize companies. I would like to work at MS because I will be surrounded by really smart engineers and people.

I am lucky to have a job, Pay the bills and have health insurance for me and my family. A year ago I started the interview prep, leet code, algoexpert etc. But then for some reason for last 4 months, its really hard for me to study. May be its my age. May be I get very tired after all day of work, and just watch mindless TV and eat sugary snacks and waste my time and health away.

When I used to work on my angular skill sets I was really energized. I had small tasks already in my queue. I could easily get in the flow when programming.

But My highest priority right now is to get a job at Microsoft as a SWE so that I have job part taken care of. Then after that I could work on side projects so that is why I am focused on interview prep but that is not dopaminergic for me. If I work on interview Prep and work on a side project, that could be distracting and not very focused effort (I think)

I feel depressed about my career. Some of my friends are directors, VPs, CIOs for medium to large companies. Here I am still angling for mediocre DEV jobs.

Any how, here at Taro, I would like to meet, interact with engineers, and really find my passion back.

I would really like to join a mastermind here at Taro, where I could hangout with engineers where we could have a conference all once or twice a month, motivate each other, etc.

Thanks for reading..

What’s the best way to learn really good front end engineering? Specifically what frameworks / languages are useful, design patterns, and some projects to get hands dirty?

my motivation for learning front end is to build products that people would actually use :)

What is the average promotion timeline from an entry-level engineer (SDE I) to mid-level engineer (SDE II)? What is considered great?

What is considered a fast promotion? How do you convince others of impact and take on more meaningful projects?

Hi,

I have recently received an E5 offer from RL team as part of the dev-infra org working on developer tooling infra such as debugger, code editor. I have received this offer after a long 2 month wait in TeamMatching. Given the long wait time in team-matching, the recommendation in general is to accept the first offer regardless of your preference and then do an internal hop later.

I have a safe and secure job at Msft L62 right now(about to be promoted in the next quarter), working in developer tooling as well.

Team structure: The team is comprised of 4 sub teams with each sub-team focusing on a vertical and containing 6-8 members. My manager has 25 reportees under him and we have a tech-lead who is overseeing the whole product.

1. Any advice/gotchas in general about work-culture, leadership for the org?

2. Being an infra role, I wanted to know if there would be enough scope for me to succeed in this role ?

3. I see there is less diversity in my immediate team, except me all the other team mates, tech-lead, skip manager are Asian, my manager is Indian. P.S I am not against any race, but wanted to get some perspective if I would be isolated and if I could an impact and survive there.

4. I see that some of my peers are L6 at Amazon and I wonder if it would be difficult to compete with them and have decent job security. P.S: I am on H1B visa

Thanks!!

YOE:9

Hi Taro Community,

I’ve encountered an interesting situation at my company, where I was the sole member in India until recently. In March, we hired an internal manager in India, whom I now report to. In our latest 1:1, he mentioned that I wouldn’t be assigned direct coding tasks possibly until September or October. For now, my work involves renaming elements within the codebase, and while I understand the rationale behind these changes, I’m missing out on more substantive coding work.

Given this context, I’m seeking advice on how to proactively engage with and understand our codebase. Without being assigned direct coding tasks, what are some effective ways to delve deeper into the code, learn its intricacies, and prepare myself for future assignments?

• Should I take the initiative to review and study different parts of the codebase independently?
• Could I propose small, self-initiated coding projects to demonstrate my understanding and initiative?
• How can I use this time effectively to ensure that when coding tasks are assigned, I’m fully up to speed and ready to contribute meaningfully?

Any tips or shared experiences on how to navigate this period would be highly appreciated.

Thank you for your help.

Based on Rahul's answer here, he mentions that you should move to a location where your team is based :

I am interested in moving to Seattle if I get an offer from one of the FAANG companies. I would like to know what are the teams in those companies that have a center of focus in the greater Seattle area?

There are so many design patterns available. I read through all the design patterns and sometimes I feel like more than one design patterns work well for the logic I am coding. Example: I am trying to eliminate multiple if-else and switch statements as it is not scalable. I see the "Chain of responsibility pattern", and "strategy pattern". Both work well for my logic. How can I make a decision of choosing one of the designs for this?

During code review: People share their opinion on using a design pattern, and I sometimes struggle to convince my reviewers of the pattern that I have used in code.

I am open to getting feedback and analyzing different design patterns suggested by reviewers. However, in some situations, I feel more than one design pattern fits for the logic and there is no right or wrong approach.

How to handle this kind of situation?

At my current level, my skip level manager expects me to help my team members grow. I have couple of SDE 1s and SDE IIs in my team who are doing good. I am not sure if I can schedule one on one with them to understand their career goals and volunteer to be their technical & career mentor?

Will it look bad if I volunteer myself to be their career mentor? Or should I just mentor people who reach out to me?