Team Selection Q&A and Videos

I recently joined Meta as a junior engineer and my hope is to be able to try out several domains (guessing realistically 2) to see where my interest lies. I’m not on an AI team currently, but given the rise of AI, I hope to be able to explore that area.

However, I understand that switching teams will disrupt my productivity and growth as a junior engineer. I’m wondering:

• When should I approach changing teams/domain? More specifically, is it better to change teams after being promoted to mid-level?
• How should I approach changing teams?

I am a mid level engineer from a small startup and have recently secured a senior FAANG engineering position. Given this I am expecting to have some challenges when transitioning both from startup to FAANG and also from a mid level to a senior position.

Given the above my questions are:

• How can I ensure I find a good manager and team during team match to help me succeed? Particularly, what questions should I ask during team match to achieve this?
• Given the quite situational nature and the focus more so on making the transition easier rather than growing, I assume that my focus should be on finding a team with less pressure. Perhaps an internal team?

Would be good to get some thoughts on this.

In taro there are tons of great resources for Job Switches, like:

• As Alex explained  Job Switching has some caveats
• As , it is a red flag for recruiters when you switch jobs within 12-14 months.

I understand the point, but what if I choose the wrong company? It's well-known that not all companies can offer the opportunities that we wanted initially. In this case, should I stay longer even if I know that I won't grow there due to factors such as the company structure or lack of opportunity?

I have a goal of reaching senior levels in my career, but to achieve this, I need to gain expertise in certain areas, like

• Strong domain knowledge to make an impact on the product side,
• connections and collaboration
• software craftsmanship.

Currently, my role does not offer me an opportunity to gain experience in the first two areas. As the product is well-regulated and the entire engineering team works on-site, it is difficult for me to connect and collaborate remotely.

On the other hand, this is making me lose my confidence and my ability to make an impact, even though I have gained hard skills and knowledge from my previous experiences in software craftsmanship part.

I am seeking advice on what to do next, should I even care about those red flags in my particular case if I switch the job?

I am a senior software engineer at FAANG (not Meta), and have found myself in a difficult career dilemma.

I joined the company as a junior and made progress to senior in the same team (say A). The nature of the work was very unique. It was heavily focused on technical analysis of software as opposed to writing one yourself. A significant portion of it was cross functional collaboration across different orgs, probably the reason why I was able to get promoted fairly quickly. The coding part was maybe 30% (you were welcome to pursue more if you have the time). The culture overall was nice with good work life balance. Manager mostly supported things I wanted to pursue. Later, I switched teams (say B) and moved to the one with more focus on development of the software. I loved the technology, projects. However, the expectations were crazy high. I ended up getting a low performer rating, a year after I was promoted to senior in my previous team. The side effects were no bonus, refreshers, salary hike.

I have been working hard since then to manage the expectations. However, I have come to the conclusion that it is impossible to exceed them and thereby pursue a career growth and the next title without throwing your life at work. I can get “meets expectation” for foreseeable future. We are also thinking of expanding our family next year.

I discussed with my previous manager who is willing to take me back. The work there has a high visibility, impact for the next year. I could build strong soft skills - leadership, driving things through others, collaboration there; but, not so much as to actually writing software.

My options -

1. Stick through in my current team for few years because it lets me stay closer to software development and open up opportunities in the future for development roles. But that means financial stress, an impact on family goals. Added anxiety.
2. Go back to previous team. Get that job stability, pursue family goals; but, might get rusted on software development skills. Maybe if I find some ways to keep honing them (also software design skills) then maybe there is that.
3. Looking externally. This is my last resort; but, given the market conditions it does not look pretty. I also like my company in general and would hate to leave. Also not sure of the dynamics of going through pregnancy shortly after joining a new company.

What is the correct mindset I should have? How should I navigate this situation in short and long run.

Hello, I've seen the term "maintenance projects" (basically, projects where you do bug fixing most of the time) and green field projects (projects where you write code from scratch).

I've been told that the maintenance projects are generally the ones that you want to avoid since you won't learn much.

I didn't see this view against software projects on TARO, like to divide the projects in to these categories from a high level view and I was wondering if you guys can tell me more about this business view of the software projects.

Are there other categories besides maintenance and greenfield? How can I avoid maintenance ones or recognize them?

For the record, I’m not personally interested in game development - I’m just quite curious.

Everyone hears the following complaints across the gaming industry in general:

• Crunch time

• Lower TCs

I find this quite curious, because I imagine there’s a lot of technical complexity in building games and the numerous tools and engines needed to make them. 

Games are interdisciplinary, combining art, music, sound design, acting, writing, and game design, to create interactive entertainment software - so I would imagine this presents a unique world of challenges that make it just as complex as “regular” software. 

Plus, MMOs and games like Fortnite or Counter-Strike have to deal with all the technical complexity of ensuring a good player experience while having millions of players (clients) playing concurrently.

In fact, Gergely Orosz has on the subject that I found fascinating.

Yet, game developers typically complain of lots of crunch time and being underpaid - and, subjectively, the game dev industry is less “prestigious” than SWE.

Also, I’ve almost always seen devs listed as “game programmer” or “UI programmer” in the credits, as if their primary job is to just write code (and not build good, complex software at scale).

What might be the reason for the differences between game development and regular software engineering?

Some context, last July after getting laid off I started searching for new work with a particular focus on FAANG.

I garner traction with a few companies but am elated when hear from a FAANG head hunter.

I passed the first interview. Scheduled the second and it wasn’t until the confirmation email of the second interview that I saw “Contract”. I was greatly disheartened though I figured I might as well go through the interview process and decide after I’ve lined up all my options. And after talking to the hiring manager I was promised a chance to convert the contract is up.

It was a hard decision, but ultimately I passed up on a well paying senior role at smaller company to take a stab at FAANG.

And I loved it. The engineers I work with are brilliant, the products impacting orders of magnitude more clients than I ever have before and I'm learning.

However, after shipping our first project, the hiring manager that brought me on board switched teams. The projects I've been reassigned to have been largely tech debt and non technical. I have had no direct manager for 4 months with no new one stepping in in the foreseeable future. While conversion is supposedly still on the table, there is no one tracking my contributions and there is a new stipulation of “if the market permits” tacked on top, meaning they have an excuse to prolong the contract rather than give a chance to convert.

The cherry on top of all this is, recruiters from this company have reached out multiple times over the past two weeks but pull out after I inform them that I'm currently contracting for them. This is due to the understandable “external” vs “internal” hiring conflicts.

So I guess the question is, should I quit and open up the chance to once again start applying externally? Or would it make more sense to stick around and try for the mythical conversion or even just maintain and study for the inevitable interviewing at the end of the contract? Maybe try being overemployed?

I have tried asking the stand in managers, but they have much bigger fish to fry than the ambitions of a contractor so I would really appreciate some opinions on how I might navigate this period of contracting.

Thanks for the read and your time,

E

I recently joined Meta, with over a decade of experience in software product development from various companies.

Currently, I'm working as a system generalist, but I have a growing interest in transitioning into a machine learning engineer role by next year.

This interest stems from both a desire to explore that sector and the recognition of the high demand for ML skills. I'm eager to invest the necessary effort to learn and adapt.

Could anyone share insights on the feasibility of this transition within Meta? Additionally, what specific skill set should I focus on developing to align with the expectations for a machine learning engineer role here at Meta?

Your guidance and advice would be greatly appreciated.

I'm feeling very undervalued at my current position. I've been working on my service the longest and therefore was the one that onboarded most of my team. In 2023 my manager and tech lead have largely been too busy to help. For instance, I only have 1-1s one every 2-3 weeks.

The new members we got on our team were new to the company and one in particular has relatively poor communication skills, so I have had to spend a lot of time onboarding them.

Unfortunately, in my performance reviews the main emphasis is on the work that I am delivering and there is not much emphasis on the impact I've had through the rest of the team. But the couple of months I tried focusing more on my work, I noticed the culture on the team degrading.

The hardest part for me has been that I have found my manager very unhelpful in helping me with my career and other frustrations. There have been multiple times where instead of helping I've felt as if he's blamed me. I have expressed this to them, but they have not changed.

Now I'm in late stages of interviews with 3 companies. I estimate the pay increase would be between 10-25% if I receive an offer.

Our team also just changed significantly, we swapped a mid-level engineer with a senior-engineer and got a new manager. They will be reporting to my previous manager so that manager will still be around.

I'm optimistic that the new manager and teammate will upgrade my situation but given the more than a year of frustration without improvement I'm still leaning towards leaving. Though I am having second thoughts as well.

I'd love to get any advice on how to handle my situation. Thanks so much!

I was wondering if you need to be part of a specific type of environment in order to make quick jumps in your career? Like to get promoted to senior level in 2 years.

I was asking because from my experience, there seems to be an invisible social hierarchy in every work place. Other people in the team may not allow me to make these jumps since this kind of anomaly will break the social hierarchy:

• There is project specific information, in absence of really god wikis you have to rely on the peers in the team to provide you such information (like how are specific parts in a service working, or how is an obscure internal tool working etc). From what I see, often times they will provide small chunks of information, as much as you need to do your task, but small enough such that they still have the information and you depend on them (probably a measure to prevent others from replacing them).
• Envy might appear between other senior folks if you progress quicker than them and might start to backstab you (For example, you need some information from them about a piece of code they wrote in order to progress, but they might do the knowledge transfer in such a way that it looks like they told you what you need to know, but in reality you got nothing; or might tell you to go debug to figure out how is something working, and you can spend days debugging modules when it would've been an 1 hour stretch if they simply told you or there was any wiki).
• Manager might not want to give you extra money and compensate at your true value.
• If you work too much, or too hard there's going to be problems withe the peers, because you increase the bar and kind of force them to work harder too.

I was asking these things, because I was wondering if I got anything wrong about these fast jumps or in general that I have a broken view about work. My first professional experience was an internship at a big tech and when got there the seniors told me that I have the same knowledge as a senior engineer, but best they could do was another internship next year (still in college).

I've raised this concern to manager in almost every 1-1 once even in front of Director of Eng that I'm interested in more roles and responsibilities. Cuz I was not a fresher even when I joined the current company at entry level and now that I've done decent work too at current company.

But manager fails to give me a path/timeline of when will I be entrusted with some impactful work.

He criticises in public, and has a favourite too who uses this to influence the manager against others.

Manager also wants every small thing to be done his way and he presents the whole thing as learning opportunity for me.

If junior engineers are not supposed to do anything on their own then why are they even hired as engineers?

Should I look for new opportunities? Or how can I take away most from the current situation?

I received a verbal offer from Meta for the Android role and I'm in a team matching phase. Recently team matching has been a lot of struggle and could take weeks or maybe months. Last year a lot of hiring managers posted on LinkedIn about hiring for roles and I did exchange a conversation with them. Is it wise to ask the hiring manager on LinkedIn about open roles in their org and then telling my recruiter about it or I should go with a team that the recruiter helps me to connect with?

I've received a verbal offer from Meta for the Android role and I'm in a team matching phase right now. I've a couple questions:

• My recruiter mentioned that team matching is taking a lot of time these days and suggested me to take a team that's available and later could think of changing the team. What should I do here wait for the right team or take a team that's hiring right now?
• Does anyone have any recommendations for teams at Meta which are layoff proof, has interesting and promising projects coming up and a good mobile engineering foundation?

I switched jobs ~4 months ago and switched teams (not voluntarily) after ~1 month. My eventual goal is to (voluntarily) internally transfer into the AI org once I'm eligible.

During a 1:1 with my skip manager, I mentioned that my current team didn’t have much opportunity for impact. He floated a meaty project in a different org and asked if I was interested. Previous question . Let’s call this option 1. Afterward, I spoke to my direct manager, who presented opportunities in the other team that he directly manages. Let’s call this option 2.

Now I'm trying to decide between these options.

Pros of option 1:

• More technically interesting
• Platform/infra play that will eventually integrate with every single product => project has large scope

Cons of option 1:

• Not sure whom I'll work with
• Not sure how much support I'd get. (Good thing if lots of scope; bad thing if I'm flailing alone)
• Org structure tbd: although my skip asked if I want to work on this, he’s loaning engineers to another org to fund the initiative.
• Uncertainty re: how well defined the work is

Pros of option 2:

• I know there are things that I can start working on tomorrow that are time-sensitive and needed for an upcoming product launch.
• My EM manages this team and is responsible for the overall delivery. He seems to care more about this new project/team than my current team.
  • It sounds like my EM would rather that I work on option 2 than option 1
• Product surface is high-visibility and therefore affords opportunity for impact

Cons of option 2:

• I'm less interested in product / user-facing work, even though it's high-visibility

With all this in mind, does anyone have advice on which option I should pick or things to keep in mind?

Thanks for reading this far!

I switched jobs a few months ago. Recently, I shared with my skip during our quarterly 1:1 that I'm not feeling much of a long-term vision or impact in my current team. He hinted at a potential opportunity to work on a new project crucial for an upcoming product launch.

I'm eager for growth but hesitant about switching teams again, considering it would be my third move in a short time. Also, the details of what we'll build, how it'll integrate with other products, etc are still uncertain, as is the org structure for the new project's ownership. This raises concerns about stability. However, I'm inclined to embrace the opportunity, especially after reading about embracing ambiguity for growth from Alex's LinkedIn post.

My ultimate goal is to transition to a different org, but I know I need to demonstrate impact first. Any advice on navigating this situation would be greatly appreciated.

Hi everyone,

I hope this message finds you well. I'm currently an SDE-II at Amazon and have developed a keen interest in advancing my career towards AI, specifically in Vision and Autonomous Systems.

I am reaching out to seek advice on how to approach this transition within Amazon. I value my current role and team, but I'm eager to align my career with my growing interest in AI technologies.

Could anyone share their experiences or advice on how to discuss this career aspiration with my manager and skip level? Additionally, I would be grateful for any guidance on mentorship programs, internal channels, or resources that were instrumental in your career transitions within Amazon, particularly into AI-focused roles.

Any insights or recommendations on how to navigate this path would be immensely appreciated. Thank you for your time and help!

One of the questions I have is product manager same as the project manager (TPM)? It means a bit hazy between companies and has always puzzled me when looking at a job opening.

Another question was around what are the natural progressions for each of these titles in the career?