Here are the metrics for the bold claim in the review title:
Impact of Work: There are over two billion people on the platform. Even if you're working on advanced business tools like I was, you're still going to have millions of users. This isn't the usage your middle school blog got.
Mentorship: Code review could be a little exhausting. It was the intensity of needing to learn at a rapid pace to reach a level of code quality that the world-class engineers on my team would be willing to accept. It was a summer-long, self-refactoring session that has been the most valuable educational experience I've had so far in advanced coding techniques and conventions.
Benefits: Highest salary, (nice) corporate housing, insane events (who else rents out a section of the Santa Cruz Boardwalk??).
I do say "objectively" in the title. If you're interested in a niche technology field, a certain industry, etc., then you may have a different "subjective" best internship. Also subjectively, there are thousands and thousands of engineers at FB, and teams are bound to have different cultures. Nevertheless, I still feel comfortable saying that this is objectively the best internship.
When there are that many engineers working on the same thing, you're bound to have some merge conflicts.
For an internship at MPK: Referred by a friend. Recruiter sent a take-home puzzle. Had a phone interview. Flown to MPK for a single on-site interview and campus tour. Received offer day after interview.
A recruiter contacted me. I set up a phone interview, but encountered strange telephone problems and could not understand my interviewer very well. The questions were general algorithm questions in Python, well-suited to a phone interview, but I wasn
I was contacted by a recruiter after dropping my resume at the career fair. After two phone screens, I was invited to attend a 'University Day' at the Menlo Park office for one onsite interview. Each phone screen is generally about 45 minutes long
For an internship at MPK: Referred by a friend. Recruiter sent a take-home puzzle. Had a phone interview. Flown to MPK for a single on-site interview and campus tour. Received offer day after interview.
A recruiter contacted me. I set up a phone interview, but encountered strange telephone problems and could not understand my interviewer very well. The questions were general algorithm questions in Python, well-suited to a phone interview, but I wasn
I was contacted by a recruiter after dropping my resume at the career fair. After two phone screens, I was invited to attend a 'University Day' at the Menlo Park office for one onsite interview. Each phone screen is generally about 45 minutes long