Meta Career Development Videos, Forum, and Q&A

Hi, I have a question about answering these prompts for Meta referral

1. How well do you know this person's professional skills within their area of expertise? (Never worked together, just by reputation, worked occasionally, very well)
2. Why do you think your referral should be hired?

How important are they? What are they looking for?

Direction: Strategy formulation and road mapping are key, along with influencing and collaborating with other teams. How I could promote proactive inclusion of ideas on other teams’ roadmaps and engaging with leadership to drive product decisions. It’s also important to consult with managers to identify tasks that create the most impact, whether they are big or small. Engaging in strategic and road mapping discussions can be highly beneficial.

How to seek manager or TL’s support on project unblocking or career growth?

What topics I should talk in 1:1s with my manager/TL?

How to build the connections with leaderships?

How to build your reputation in new area?

How to use better story telling?

How to better align on the organizational goals?

How to define the priority and work on your projects?

How to setup clear expectations for yourself and your team?

How to identify my gap to next level?

How to narrow my gap to next level?

The Hack language is indeed associated with PHP but it's not exactly a new version of PHP. Instead, Hack is a programming language developed by Meta (formerly Facebook) that operates within the same ecosystem as PHP and is designed to interoperate with PHP code. Hack extends PHP by adding additional features such as static typing, type inference, generics, nullable types, and async programming, among others.

Hack aims to maintain the fast development cycle of PHP while offering the added reliability of static typing, enhancing both performance and safety. It was developed to address some of the shortcomings and challenges of working with large PHP codebases, especially in a fast-paced development environment. Hack and PHP codes can coexist, allowing developers to gradually migrate PHP codebases to Hack, providing a smooth transition pathway without requiring a full rewrite. Meta originally developed Hack to run on the HipHop Virtual Machine (HHVM), which is used to execute both Hack and PHP code, significantly improving execution times compared to the standard PHP interpreter.

Meta recruiters request references of people you have worked with before who are current employees of Meta before submitting feedback file to review committee.

My question is what & how much impact does providing these references have on your application, candidacy and the ultimate outcome of the interview process.

Does it hurt your chances to not be able to provide these one or more of these references?

What sort of documentations should we have for our 1 on 1s? Is there a video on having a 1 on 1 doc?

My previous manager at Workday told me to discuss
Wins, What I am focusing on, Blockers, Personal Development, Action steps

and created a shared google doc for us, but it seemed kind of status-reporty. Is there another recommended format for our 1 on 1?

Background:

Our team inherited a set of products which are full of spaghetti code and bad design. We are currently building a high visibility and high impact project based on the backend of this system.

Although the main project UI goes on-track, some critical backend design flaws will hinder product performance and reliability within a couple of months - maybe close to or right after official product launch, which will turn our whole effort into a joke since we have executives' eyes on it.

My progress this year so far: (besides my roadmap item commitment)

• 1. Identified a system hotspot, finished analysis & design, and convinced our EM to rewrite this module (currently 95% finished by a junior engineer.)
• 2. Rewrote 1 foundation module to eliminate legacy design flaw (ended up with less code, less complexity, same performance, more system reliability.)
• 3. Design and rewrite another foundation backend module to address legacy design flaw & unblock development of the next milestone
• 4. Leading on technical design and discussion of a re-architecture for the overall backend end to end flow. (simplify design, improve performance)

NOTE:
- I tried to delegate 2 & 3, but no other engineers can do them after a few try since it's too tightly coupled with the rest of the system.
- our team lead is championing for all these work, which is how we are able to make room for them

Benefit of these work:

• accelerate other engineers' work in the system
• cut clean with the legacy system design flaw, improve product reliability and performance
• ensure our team's win on the high visibility project that built on top of this backend
• easier oncall for the short run or long run

My questions:

• In terms of performance review, my manager thinks this is better engineering work, while I think is closely tied to the success of our main project. What kind of evidence do I need to convince him? (My EM is not very technical)
• From his tone, I sense he thinks better engineering work in considered "lower priority contribution". Is this true? How do I communicate the importance of code/design quality with him?
• I'm trying to reach the staff level promo, does this initiative demonstrate any trait for the next level? (I'm not doing it for promo, but my EM's neglect on this makes me pretty frustrated because refactoring and rewrite is such tedious and painful work... I want to make it count)

Thank you!

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?

Hi all, I'm currently working on GenAI server infra at Meta as an IC5. I'm interested in the space and have had a long standing interest to dig deeper into ML. At a high level, I'm considering the following:

1. Positioned well for E6 scope and exploring interest in people management (M1)
2. Taking an online masters program to brush up on math, ML foundation skills. This can better validate my interests. Alternatively, I can lean into online resources like Cousera, deeplearning.ai
3. Recruit internally as an E5 to a relevant team. Generally internal mobility empowers people to explore and learn new things. However, it helps to have relevant experience.

For online masters programs, I've heard of great things from Georgia Tech, with a ~$7k online program. Alternative options include UT and Stanford, and the latter is ~$60k. Rahul made a great video about his , but this would rather be a part time commitment, and I already have many YOE at Meta for my resume.

I'd also love to hear your general thoughts on navigating career moves into an area with existing, highly talented pool.

Hello everyone,

I joined Meta a couple of months ago as an IC5, coming from a predominantly Java background. Recently, I've started working with the PHP codebase, which is somewhat new to me. I've noticed that my diffs tend to undergo several rounds of revisions, which not only delays their integration but also consumes more engineering time than I'd like.

A fellow engineer pointed out that my diffs are often too lengthy, leading to extensive feedback and additional iterations. I'm actively looking for ways to streamline my review process and improve the quality of my submissions.

Here’s what I’m considering to reduce the review cycles and improve my coding approach:

1. Reducing the Size of Diffs
2. Pre-Review Checks: -- Any suggestions here would be great

I would greatly appreciate any advice on:

• Strategies or tools that could help in catching potential issues early.
• Best practices for structuring PHP code and managing larger changes in a PHP environment.
• Any insights on transitioning from Java to PHP, particularly with regard to common pitfalls or key differences I should be aware of.

Thanks in advance for your help! I'm eager to learn from your experiences and improve my contributions to our projects.

What is the Rotational Software Engineer Program?

How is it different from a regular SWE role?

Is it like being a contractor hired through a staffing company?

Are there levels to it (E4/E5, etc) or is it just one level?

Is there a good chance to become a fulltime employee afterwards and is this a good way to join Meta?

Is it a decent career move to join such a program if you are already a senior in another company or will you be considered a noob if you join a role like this?

I recently started a side project that could have an org level impact soon within this year. The feedback for the prototype is pretty good and I got a green-light to put more bandwidth in it.

I used to think once I get the good work done, promotion should come naturally. But both my manager and skip manager are telling me to leave proper documentation and communication as evidence for promotion - docs like PRD, roadmap planning, status update etc.

I usually do communications pretty well, so their feedback make me wonder if I missing something for a staff level promotion.

• What kind of evidence is being valued in a staff promo packet? Any differences between senior and staff promo packet?
• What do I need to highlight and keep track of if I'm creating scope outside of daily work?
• What kind of data I should keep track of to quantify the impact? How do you usually learn about finding the matrix to track?

Thanks!

My brother is very worried about getting a return offer at Meta - he'll be interning there this summer. He reviewed the videos on , but is still confused on who he would assign to review diffs/vouch for his performance other than his EM.