3 coding E6 rated most likely, behavioral E5, 2 sys design split as E6 and E5. Large assumptions, but just assume for a minute. TC:350K
E6 does not have 3 coding rounds.
Phone screen, my bad
If you had only one sys design, you were never in the E6 loop
Had 2, one I think leveled E6 and one at E5. Updated
Where would you get this level of detail on interview results?? Are hacking their HR system?
this is solid E5 territory
I will say I don’t care too much about the E6/E5 part. Mostly that E6 still has remote roles, and E5 doesn’t as far as I’ve been told. So if anyone has remote iOS roles at Meta, lmk
How important are coding rounds for e5? If one is lean hire but other rounds hire. Does that work ?
Hi OP..How was your coding interviews ? is it from Leetcode Meta Tagged questions?
Yeah
Update: got E5, won’t be able to accept. It was exactly as expected, E5 design, E6 design, coding passes and E5 behavioral. Behavioral is dominant, so that held it back. Honestly, if I’d have played up my projects and mentorship better, I might’ve gotten it, but such is life.
Is there a min YoE needed for E6? What is it?
How can we tailor behavioral questions that can distinguish between roles at E5 and E6 levels? I have upcoming interviews and aim to position myself for an E6 role. Are there specific strategies or techniques to effectively convey my experiences for this level?
Tech Industry
7h
890
Women, help me understand why this is inspirational
Cars
Yesterday
892
Do you really feel special in your Tesla?
Software Engineering Career
7h
400
Attentive offer evaluation
India
Yesterday
1206
Modi is a legend, will be remembered for centuries to come
Working Parents
18h
1310
Closed now - thank you all
Coding rounds at meta are not leveled, more like pass/fail. The leveling primarily comes from the behavioral round, confirmed with system design. If behavioral is E5 then it's E5.
That’s what I’ve been told. I honestly thought behavioral was solid, didn’t know what caused the down level.
Behavioral isn't really about the quality of your responses unless you bomb it. It's an honest assessment of your level and experience. The scope of the problems you've previously worked on and how those problems map to what engineers at each level would typically be doing at meta.