Preparing for an interview? Check out Cracking the Coding Interview
Published on

Meta Product Security Engineer(University Grad) - Native Phone Screen

Author
  • Shared Anonymously

I had my phone screening yesterday for the Product Security Engineer - Native role. The interviewer was very friendly and helpful throughout the interview.

After starting, the interviewer introduced himself and explained the screening process. The first part was a code review, followed by a coding round.

When I asked the recruiter about the interview structure, they mentioned one coding round and some questions about native security. They never mentioned there would be a code review round (I explicitly asked twice). Meta should create interview preparation pages for security engineering roles, similar to what Amazon does, as they currently only have them for software engineering roles.

Code Review: The interviewer pasted a large C++ code snippet and asked me to manually review it for vulnerabilities and security holes. I mentioned that I had never manually reviewed code for vulnerabilities before because we typically use various tools for that. However, he still insisted I try. After asking a lot of clarifying questions and with his help, I managed to answer most of his questions.

Coding Round: The question asked was Valid Palindrome, which I solved within 10 minutes. We chatted for the remainder of the time.

I got an update from my recruiter today, and unfortunately, I was rejected. But there's no Cooldown period for me and I can apply to any other roles at Meta.

ReportMark as Helpful