My FAANG Intern Experience — The Good, The Mediocre, and the Meeting That Wasted 3 Hours

I want to preface this by saying I am aware that 'honest FAANG intern experience' content is a genre and the genre has a template: humble-brag opener, list of impressive projects, brief acknowledgment of challenges, conclusion about how much you learned. I am going to try to write something that is actually honest, which means it will be less impressive-sounding and more useful.

The internship was twelve weeks. The team was search infrastructure. The project was real and the code I wrote shipped, which genuinely matters and is not guaranteed for interns. The food was good. The badge was heavy in my pocket in a way I am slightly embarrassed to admit I noticed.

The Meeting That Wasted 3 Hours

Week four. A three-hour meeting to discuss the naming convention for a new internal service. I am not exaggerating the length. The meeting had a doc, a pre-read, and a follow-up document. Eight engineers attended. The decision reached at the end of three hours could have been made by two engineers in twenty minutes and was, functionally, not significantly different from the proposal in the original doc.

This is the thing about big tech that the LinkedIn posts omit: the process overhead at scale is real and it is sometimes significant. I do not say this to be critical — I understand why large distributed engineering organisations develop the processes they do — but as an intern who was used to college projects where the cost of a decision was low and the speed was high, the adjustment was significant.

What Was Actually Great

My mentor was exceptional. She was a senior engineer who had been at the company for six years and who treated my questions as legitimate even when they were clearly the questions of someone who had been there for four weeks. She blocked two hours a week for us, used one hour to review my work and give feedback, and used the other hour to explain the context that my work existed in. This context — understanding why the project mattered to the organisation, what decisions had been made before I arrived and why — was more valuable than anything I learned from the code itself.

The calibre of the engineers around me was also genuinely motivating in a way I had not fully anticipated. Sitting in architecture discussions with people who had built systems that served hundreds of millions of users meant encountering problems at a scale and complexity I had not previously thought about concretely. I left the internship with a clearer sense of what I did not know, which is not nothing.

The Honest Summary

Big tech is a specific kind of place that is right for some people and not right for others, and knowing which one you are requires experiencing it. I am glad I interned there. I am also glad I did not immediately convert the intern offer to full-time without thinking about what else I might want. The experience taught me a lot, including some things about what I did not want from a work environment. Both categories are useful.