Skipped the screener and went straight to the 2nd round.

2nd Round: RM/PM/OPS

The 2nd round was with someone in the actual role. It was scenario/behavioral based and quite friendly. The only odd thing was that they told me multiple times that the JD and title weren't quite right, which was shocking to hear and could throw you off. Since FB uses a grading system from each person, the real focus is on your ability to convey actual scenarios clearly.

3rd Round: 4 Structured Areas (Behavioral, Customer, Technical, and Domain)

You are provided with a guide on what to expect, but it is quite extensive. One to two of the 14 bullets (for example) could take up the entire 45-minute block. Focus on having several real-world scenarios holstered. Follow a STAR method approach and be effective in communicating your role.

The problem with this round is that only one person I met with actually worked directly with the role I was interviewing for. The domain and technical sections require more time, in my opinion, and the interviewer should explain the roles more effectively beforehand, especially since it is really three roles and not clear why it's labeled a Release Manager.

I understand that an RM should have tech knowledge or the ability to manage tech-related content, but I got the impression that I needed to have extremely strong technical knowledge of all systems I managed. System architecture was brought up, and I had to explain the E2E technically, which seems ludicrous since FB has hundreds of internal systems.

Bright Spots: It was fun, challenging, and the desire to work there is still strong. HR reps were extremely helpful and supportive throughout.

Pros:

• Challenging
• Exciting
• Fun
• Smart people
• Ability to be creative and have an impact

Cons:

• Interviewers stuck to the script, and it wasn't very conversational/personable.
• The time for each block is 45 minutes, and they used every second.
• I only had 30 seconds to 1 minute to ask my questions.

Helpful Tips:

• Have several E2E scenarios ready to discuss. You will be asked to dig deeper at times and be required to provide more detail on specific parts.
• Be clear in your responses and feel comfortable asking for clarity.
• If you get to the panel part, understand the guide provided as best you can, but ultimately, you should focus on being able to outline all the steps taken to, for example, troubleshoot an incident and the role you played.
• It seems like FB is more interested in "I" statements rather than inclusive "we" statements.
• Data/metrics are a big deal (of course), so be able to explain how you measure success, whether it's in your role as a contributor or overall within a project.

Good luck and be confident!

Explain the system architecture of the system you implemented.

What was the problem statement?

How did you measure it?

What was your role?