Good pay, but so stressful. With mandatory 15% to meet, most.
Good pay, but so stressful. With mandatory 15% to meet, most.
- Good insurance and benefits
- Free food
- Good salary
- Good opportunity and experience
- Bad work-life balance for some orgs.
- Stressful 15% for most.
- Some managers know nothing about the tech and can't really track or even follow project execution and planning. They are there to PIP people only.
Additional Ratings
Was this helpful?
Meta Interview Questions
Meta Interview Experiences
Software Engineer
1. Recruiter Call - to discuss your background. 2. Screening interview - 2 to 3 LeetCode medium questions based on the Meta LeetCode list; no behavioral questions. Gave complete answers with optimized solutions.
Software Engineer
The interviewer was very friendly. There were two questions in total, and the time was a bit tight. The interviewer informed me in advance that each question had a 20-minute limit. If I couldn't finish the first question within the allotted time, I
Software Engineer
Recruiter call, then LeetCode tech screen. Passed the screen pretty easily but got rejected a week later. The interviewer seemed to be confused by my coding style and had trouble reading it, although it was a fairly simple and standard solution to th
Software Engineer
Sunnyvale, California, United StatesApril 17, 20251. Recruiter Call - to discuss your background. 2. Screening interview - 2 to 3 LeetCode medium questions based on the Meta LeetCode list; no behavioral questions. Gave complete answers with optimized solutions.
Software Engineer
Sunnyvale, California, United StatesFebruary 1, 2025The interviewer was very friendly. There were two questions in total, and the time was a bit tight. The interviewer informed me in advance that each question had a 20-minute limit. If I couldn't finish the first question within the allotted time, I
Software Engineer
Sunnyvale, California, United StatesOctober 10, 2024Recruiter call, then LeetCode tech screen. Passed the screen pretty easily but got rejected a week later. The interviewer seemed to be confused by my coding style and had trouble reading it, although it was a fairly simple and standard solution to th
