If you want to find the hiring manager at Meta, the first question is which kind of Meta role you’re looking at. For a lot of software engineering hiring, Meta interviews you for a level first and matches you to a team later. For most other roles, you’re interviewing for one team from the start. The search, and the moment when outreach helps, is different for each.
Meta reported 78,865 employees at the end of 2025, up 6% year over year, with the company attributing the growth mainly to technical hiring, especially in AI. That’s a big company, but far smaller than Google, Microsoft or Amazon, and a focused search can get you to the right handful of managers.
Two hiring paths at Meta
Team-specific roles. Most product design, data science, research, sales, marketing, partnerships, and many specialized engineering roles are posted for a defined team. The posting describes the product area, and the hiring manager exists from the moment the req opens. Meta’s careers site notes that your recruiter will share more about the role and the hiring team on the initial call.
Generalist software engineering roles. These postings read broadly: “Software Engineer, Product” or “Software Engineer, Infrastructure,” with many locations and little team detail. Candidates interview for a level and track (product versus systems, for example). The team comes later.
How “later” works has changed. For years, Meta was known for a six-week engineering Bootcamp in which new hires sampled teams before choosing one. Candidate guides and prep firms, including IGotAnOffer, now describe team matching happening before the offer for many engineering hires: after you pass the interviews, you talk with several hiring managers from teams with open headcount at your level, and the offer comes once a match is made. Bootcamp still exists as onboarding. The specifics vary by level and org, so confirm the current process with your recruiter.
How to find the hiring manager at Meta for a team-specific role
This is the more traditional search.
- Read the posting for the product area. Meta postings usually name it: Instagram, WhatsApp, Facebook, Messenger, Reality Labs, Meta AI, Ads, Integrity, Infrastructure. Some are more specific, such as Instagram Reels or WhatsApp Business.
- Note level and location. Menlo Park, New York, Seattle/Bellevue, London, and Singapore host different teams. Combine location with product area.
- Search LinkedIn for current Meta employees with manager titles (“Engineering Manager,” “Data Science Manager,” “Product Design Manager,” “Director”) in that area and location.
- Check for public work. Meta’s engineering blog (engineering.fb.com) and Meta AI research publish named authors. Conference talks at engineering and ML venues are common, too.
- Shortlist two or three. Message the best match first.
Finding hiring managers for generalist engineering roles
There’s no single owner to find here, and that’s fine. Your goal is different: identify the managers of the two or three teams you’d most want to land on, and build some relationship with them before or during team matching.
- Pick product areas you actually care about. “Anything at Meta” is a weak position in a matching conversation.
- Find engineering managers in those areas using the same search above.
- Reach out with a specific interest in their team, not a request to bypass interviews.
Here’s what that looks like in practice, using a made-up example. An infrastructure engineer who wants to work on storage would search LinkedIn for “Engineering Manager Meta Infrastructure Menlo Park,” read Meta’s engineering blog for recent storage and data infrastructure posts, note the named authors, and cross-check which of them manage teams. Twenty minutes of that usually produces three or four plausible managers, which is enough.
Then, when you reach team matching, tell your recruiter which teams interest you and that you’ve already spoken with someone there. Recruiters work from the list of teams with open headcount, but a manager who already knows you is much more likely to want the match.
Google runs a similar post-approval team match. How to find the hiring manager at Google covers that version in more detail.
A worked example for a team-specific role
Now the other path. Take a hypothetical posting: “Product Designer, WhatsApp Business,” based in London.
The product area is explicit: WhatsApp, business messaging. The level reads as senior IC. The likely hiring manager is a product design manager on WhatsApp Business, or a design director one level up.
A LinkedIn search for “Product Design Manager WhatsApp London” narrows things quickly. Meta designers also publish case studies and talk at design conferences, so a search for recent WhatsApp Business design talks or write-ups adds context. If one manager has spoken about business messaging tools in the last year, that’s the person to message first.
Here the hiring manager exists before you apply, so the timing logic is simple: reach out within a few days of applying, mention the role and that you’ve applied, and reference one specific thing about the product your work relates to.
Why outreach is worth it at Meta
The general math holds here: Ashby’s Talent Trends Report, covering more than 100 million applications, found that the average hire took more than 300 applications in 2025. Referred candidates passed initial screens 52% of the time versus 35% overall. Meta isn’t in Ashby’s data set, but a high-profile employer posting broadly scoped engineering roles sits firmly in the high-volume category.
Meta also adds a structural reason. In team matching, the decision is two-sided: you have to want the team, and the manager has to want you. A cold match call is a 30- to 60-minute first impression. A match call with a manager you’ve already talked to is a second conversation. That difference is easy to underestimate.
What to say to a Meta manager
Meta’s culture prizes impact and speed. Your message should show both.
Structure:
- The role you’re applying for, plus the job ID if there is one.
- One specific reference to their team’s work: an engineering blog post, a launch, a paper.
- One quantified result from your own work that maps to their area.
- A small, specific ask.
Example, written for illustration:
Hi [name], I’m interviewing for a Software Engineer, Product role and I’m hoping to match with a team working on creator tools. Your team’s engineering blog post on [topic] was the clearest explanation I’ve read of [problem]. At [company] I led a ranking change for our creator feed that lifted weekly creator retention about 8%. Would you be open to a short chat about what your team is focused on?
Notice what’s missing: no request to skip interviews, no paragraph about loving Instagram.
Use Meta’s own prep resources as research
Meta’s careers site publishes prep material for candidates, including guides for the initial technical screen and the full loop, and a Career Profile where candidates can see upcoming interviews and role-specific prep. Meta also says your recruiter will tell you more about the role and the hiring team on the first call.
Use that first recruiter call as a research step. Ask:
- Is this role hired into a specific team, or is there team matching after the interviews?
- If there’s matching, which orgs are hiring at my level right now?
- How long does it usually take between final interviews and an offer?
The answers tell you whether you’re looking for one hiring manager or several, and how much time you have to build relationships before matching starts.
If a Meta manager replies
A first conversation with a Meta manager is closest to a lightweight team-match call. Prepare the same way:
- A two-minute summary of your strongest project, with the impact in numbers.
- A clear reason you’re interested in their team’s product area.
- Questions about what the team is building this half, how it measures impact, how it splits product and infrastructure work, and what makes engineers successful there.
Meta’s performance culture emphasizes measurable impact, so managers tend to listen for whether you naturally talk in outcomes. “We launched X” is weaker than “We launched X and it moved Y by Z.”
If the manager doesn’t reply, follow up once after a week with something new. If they say they don’t have headcount at your level, ask which teams in the org do. That’s one of the most useful questions you can ask, because open headcount at Meta shifts by level and by half.
Common mistakes
Treating every Meta posting like it has one owner. For generalist engineering roles, it usually doesn’t. Searching for “the” hiring manager wastes time.
Waiting until team matching to start. By then you’re in a queue of candidates with the recruiter’s list of open teams. Relationships take longer than a week to build.
Ignoring the level. A manager hiring at one level may have no headcount at yours. Ask, and don’t take it personally.
Messaging executives about specific reqs. At 78,000 people, VPs aren’t tracking individual openings. First-line managers and directors are.
The bottom line
At Meta, the hiring manager either owns the req from the start (team-specific roles) or shows up during team matching (many generalist engineering roles). For the first, find the hiring manager at Meta in the product area and reach out before or right after you apply. For the second, find the two or three teams you’d most want, get to know their managers early, and tell your recruiter when matching starts.
Doing that research for every posting is slow. angld.AI speeds it up: paste a Meta job posting, and it identifies the likely decision maker, researches their public work, and drafts a personalized outreach message in about 60 seconds.
