Team Selection Q&A and Videos

Hi everyone, I have about 0 experience with machine learning and I'm thinking of ways to significantly increase my value in the future. My ideal plan is to get promoted to E5 in < 1 year and then change domains to ML (or ML Infra and work closely with ML engineers). I have almost 0 experience with ML directly, but I think they make much more money in the long run? I'm currently a backend software engineer.

Basically I want to know if it's worth investing my time & effort this or if it would be better to just eventually go for engineering management in the domain that I am already familiar with.

Does specialization matter? I have a bunch of friends working in Big Tech, and some of them at my level started growing in 1 specific area. For example, one of them started going deep into machine learning. Do you need to make that decision when you’re a mid-level/senior engineer and what’s the criteria?

Adding on to this, I see a lot of noise in the market about various degrees and certifications to help you with specializations. Things like web3, ML, or other hot topics. This, combined with what I see my peers doing, makes me feel like this is a worthwhile or even the optimal thing to do.

As a counter-example, I have a friend who chose to specialize in ML and they’re job hopping a lot as they haven't been able to find good ML work at any of their recent companies.

I asked this question on chatGPT, nothing proper not found. I need your help guys, currently I am interviewing with some companies which their Glassdoor reviews are really low and there are pretty bad reviews in terms of culture and engineering. Just wondering what is important things can I ask them to get know more about that, or is there any technique that bring this kind topics during the interview?

I've had 5+ friends leave Meta or quit software engineering altogether after E6. Either the responsibilities and stress were too much or what they were being asked to work on wasn't really aligned with their core interests. Business needs are always changing, so it can be a common occurrence to take a lot of ownership over a project you don't have personal interest in.

It's important to be adaptable, but I think intrinsic motivation can be hard to sustain if the people, project, or priorities are in flux.

For the older crowd, what really typifies career longevity in a software engineering?

Given this industry, switching is always somewhere in my mind. How can I figure out if it makes sense to pursue that or stay? When it comes to staying, how do I know if my current team is conducive to my overall growth and goals going forward?

What sorts of reasons make people leave big tech? I recently received an offer from a tech start-up is super interested in my candidacy and they're moving what they can to try to match compensation. The move includes a promotion. It also seems like I'd have access to career growth and learning due to people there wanting to work with me to help me succeed.

However, no matter what they do, they won't be able to match the compensation I'd receive within a few years, assuming I grow into a senior engineer role and stay at a big tech company. I see driven, career-focused individuals moving out of FAANG-like companies to start-ups and non-FAANG companies, so I'm curious: what drives people to do so? When is this the right career move?

I have often found platform teams to be quite "tech-heavy" rather than being driven solely by business. On the other hand, it is easier to convey impact for product teams for the metrics that the org cares about much more.

If I am trying to move from Mid Level to Senior Level i.e. Senior Software Engineer to Tech Lead level in my org, what kind of teams should I target?

Does choosing a certain one help you in fast-tracking your career growth?

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'm moving forward to team matching at Meta for E4 and wanted to ask the community if they had any suggestions for teams with the strongest potential for growth, especially for the New York office.

The recruiter gave me the following survey. I stated I'd be more of a "Product - Generalist" role. Would also be curious to learn more about "Systems - Generalist" as I did the System Design interview as well.

In general from what I've seen, there's a decent amount of opportunity in Instagram, Whatsapp, and Reality Labs (from product announcements and earnings calls). I've also been told to avoid monetization as it's difficult to make an impact there.

Would appreciate any advice or suggestions! Also would appreciate tips on what questions to ask Hiring Managers to assess how they grow E4s.

What is your role? (select the one that applies)

• Systems - Generalist
• Product - Generalist

What type of work motivates you the most? (select all that apply)

• Infra: Scaling challenges
• UX: Building user experiences
• Growth: Top of line impact
• Integrity: Ensuring platform safety
• Social Impact: Progressing positive change on key social issues

Who do you want to build products for? (select all that apply)

• Consumers: External, individual users of the Meta family of apps
• Businesses: External business account users of Meta family of products
• Meta Employees: Users of internal tools
• Developers: Internal and external engineers using Meta developer products and APIs

Please select which Meta Pillar(s) you’d be interested in joining? (select all that apply)

• Family of Apps: Enable optimized enforcement and support of account integrity to foster safe and meaningful communities.
• Monetization: Empower people and businesses to succeed in the global economy
• Gen AI: bring the transformative potential of generative AI to people and businesses
• Reality Labs: build tools that help people feel connected anytime, anywhere

How would you rank your preference in terms of products? (feel free to use numbers)

• Facebook App
• Monetization
• Privacy
• Messenger
• Instagram
• WhatsApp
• Reality Labs (AR/VR)

I'm looking into a team switch, and I was wondering what I could ask to figure out if the team works for me. My priority is to find a team with good growth opportunities, so I can make the jump to L5 (senior). I know in Taro that it's suggested that you talk to engineers, but talking to engineers has been tricky from my experience with Target's team-switching culture. Questions that I can ask to just the engineering manager would be great!

I have been in the team matching process with Meta for the last 3 weeks. I have talked to 4 teams and 2 of them did not proceed futher. The other 2 teams are something I would rank in the top of the 4 but I am not completely satisfied with the role at these teams. How long do you think is it good to slow down the team matching for so as to explore other team matching calls? Or would it be a bad move as I can miss out the current available opportunities?

If I go ahead with any of the teams that don't completely align with my interests, how easy is it to switch internally after I join a team?

Hi All,

Would love to get some advice on how to ask highly pointed questions during a 30 minute conversation with a hiring manager to get the maximum info out of him regarding the team culture and the product.

Regarding my preferences...

I would love to stick fully on the Backend stack. I have experience working with Python, NodeJS, Typescript and a bit of Java, I have experience working with Infra and databases as well. I get excited working with data at scale but do not have stellar industry experience with it such that I can start being impactful on day 1.

Since this will be my first time at a big tech, I want to optimize for a decent to moderate enough ramp up time, good wlb and not being super heavy with oncall at least for my first team.

Once I get used to the pace, I'll jump around to start optimizing for impact, visibility and scope.

Here is what I have in mind for my Hiring Manager meetings but feel free to add/subtract from this.

1. Basics, what is the product/org
2. What is the team size and team structure (how many E5s, E4s etc) and tech stack.
3. What is the code velocity like on average for an E5.
4. Give me a brief idea about what the first project you have in mind for me, if not tell me about a project an E5 is currently working on.