The position I interviewed for was a 10-month contract through a staffing agency. To get an in-person interview, I answered a 4-question written test that was emailed to me. In my opinion, the questions were not very well thought out and did not reflect well on the hiring process I was about to enter. At least one of the questions was relevant to the position for which I was interviewing, though it was rather trivial.
The in-person interview consisted of three 45-minute sessions, each of which involved solving a programming problem on the whiteboard. The questions were not relevant to the task I would be performing if hired; they were generic algorithms from a Comp Sci 101 test.
Unfortunately, I am not adept at solving irrelevant problems in a "prison cell interrogation" environment, so I did not receive a callback. Fortunately, this weakness has not prevented me from having an extremely successful career, just not at any companies that utilize this lazy approach to interviewing.
Write a function to compute the square root of a number without using any built-in functions.
Given two very large numbers, each of which is so large that it can only be represented as an array of integers, write a function to multiply them.
Write a function to display a JSON string in pretty format.
The following metrics were computed from 1 interview experience for the Meta Front End Engineer, Infrastructure role in Menlo Park, California.
Meta's interview process for their Front End Engineer, Infrastructure roles in Menlo Park, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Meta's Front End Engineer, Infrastructure interview process in Menlo Park, California.