Software Engineering Manager Interview Experience - Warsaw, Poland
Process
The process was very well organized. Most of the interviewers were really nice people, and we had a very good discussion.
The only exception was one interviewer for the Project retrospective. He was 15-20 minutes late. To cover all his questions, he interrupted me non-stop and could not let me answer.
The recruiter was very helpful and assisted during each step of the interview.
Questions
Create a function to check if a string is a palindrome. Do not consider any punctuation marks.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Meta Software Engineering Manager role in Warsaw, Masovian Voivodeship.
Success Rate
Meta's interview process for their Software Engineering Manager roles in Warsaw, Masovian Voivodeship is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Meta's Software Engineering Manager interview process in Warsaw, Masovian Voivodeship.
Meta Work Experiences
- 5.0Fast pace, great pay, high barSoftware Engineering Manager • Current EmployeeLondon, England, United KingdomJuly 24, 2024Pros: High-performance culture Great salaryCons: High-performance culture Work-life balance
- 5.0Generous, kind, takes care of their peopleSoftware Engineering Manager • Current EmployeeSeattle, Washington, United StatesOctober 27, 2020Pros: Great company culture for engineers - no cult of "genius a-hole". Compensation is more than generous, and you work with some of the most competent people in the business.Cons: They treat you like precious and valuable geniuses, so you're expected to perform up to that standard. Expect to put in 100% here.
- 3.0Great people, but backstabbingSoftware Engineering Manager • Current EmployeeLondon, England, United KingdomSeptember 23, 2022Pros: Great people around. The best I've ever met! Super ambitious goals. Great benefits. WFH flexibility.Cons: Performance review. It works this way: 1. Leadership escalates project X. 2. You clearly don't see any impact of X, but have to disagree and commit. 3. You give the project to an engineer from your team (even if they disagree). 4. The engineer executes the project. 5. PSC comes, and the engineer does not receive credit for X because, guess what, no impact. And this loop happens again and again. You build a special skill on how to dodge from these crappy, non-impactful projects.
Meta Interview Questions
