Thoughts on DS I worked with inside vs outside FAANG
Our take
The distinction between working as a Data Scientist inside versus outside FAANG companies reveals something fundamental about how we evaluate talent and measure success in our field. Based on firsthand experience at Google after stints in pharma, supply chain, and financial services, the data suggests that FAANG teams prioritize well-rounded foundational skills over narrow specialization. This aligns with broader industry observations about how teams select candidates, as highlighted in Interview Experience: Big teams look for potential, smaller teams look for how fast you can instantly come add value. When you can assume baseline competence across communication, business acumen, and technical execution, entire teams become more adaptable and resilient.
What emerges from this analysis is that the traditional model of deep expertise in one area combined with functional gaps elsewhere may actually hinder career progression at scale. While niche specialization has its place, particularly in research-focused roles, the FAANG approach demonstrates that being a generalist with deep expertise in key areas creates more value. This perspective challenges the common interview preparation advice to memorize cutting-edge algorithms or solve abstract mathematical puzzles, instead emphasizing the practical reality that most data science problems require reliable execution across multiple domains. As Senior level DS at FAANG - what coding interviews to expect illustrates, the technical bar exists not to filter specialists, but to ensure candidates can contribute meaningfully from day one.
Perhaps most significantly, this account underscores that technical capability alone is insufficient for success in these environments. The author notes that many technically proficient data scientists lack basic communication skills or fail to translate business problems into statistical frameworks. This suggests that the interview process evaluates not just what candidates know, but how they think and collaborate. The infamous "airport test" - whether you'd enjoy being stranded with someone for hours - becomes a proxy for assessing cultural fit and interpersonal dynamics that directly impact team performance. In an era where remote collaboration and cross-functional work define modern data science practice, these soft skills become hard requirements.
The implications extend beyond interview preparation to how we conceptualize professional development. Rather than chasing the latest methodological trends or accumulating esoteric knowledge, aspiring data scientists might benefit more from systematically building foundational competency across the entire spectrum of skills required for effective practice. This means not just mastering machine learning techniques, but also developing the ability to explain complex concepts clearly, understand business contexts deeply, and translate ambiguous problems into structured approaches.
Looking forward, we should expect this emphasis on well-rounded capability to intensify as data science becomes more embedded in organizational decision-making. Teams will increasingly value members who can navigate uncertainty, communicate insights persuasively, and adapt their technical approach based on evolving requirements. The question becomes whether educational programs and career development paths will evolve to reflect these broader competencies, or if professionals will continue to rely on self-directed learning to bridge gaps that formal training leaves behind.
I get ask the question online and in person: what it takes to get into a good FAANG company?
I spent the last year working at a Google as DS and spent the previous 3 working at random industries (pharma, supply chain, large buy-side banks, etc.)
I genuinely think that the quality of DS I worked at in FAANG were higher caliber for the following reasons:
All my teammates weren't necessarily experts at a lot of things, but they had a very good grasp of the fundamentals. If you take the DS skill tree divided up into categories (ML/coding, communication, business/product sense, etc), my teammates were at least a 7-8/10 on all of these while being expert level at some things the team was responsible for. While doing mock interviews, what stood out the most is how badly some people commuinicate . I understand that a lot of people working in STEM have English as a second language, but that's not taken into considerationg when evaluating if they want to work with you. Also, I worked with a lot of DS that score very low in some aspect of what I would consider 'fundamentals'. Some knew how to code and develop, but never took a probability class. Others had heavy math background and had no idea what to do outside a notebook. Others had a good industry experience but weren't sure how to quantify their ideas and turn it into a stats problem. At Google everyone could reliably do everything to an acceptable level, and learn how to do it better if they needed to and everyone had a good 'vibe' that made them fun to talk to and work with. Honestly, the best part of the job were the coworkers while the work itself was pretty boring.
I think I was picked for the role since it was a communication heavy role and I had a lot of experience coaching people and public speaking
To land a job at these companies I don't think you need to be an expert specialist for the large majority of the positions. I think what you get evaluated on is if a DS problem is thrown at you, or you are in a discussion about a problem, you know what is being discussed, how the problem is solved generally, or know what to look up to solve it. If you have the extensive knowledge and experience + the things listed above you'll likely get promoted to Staff level pretty quickly or hired there.
So, my final thoughts is if you are studying for these positions, don't spend your time deep diving into niche topics or doing quant style problmes. Instead, have a very good baseline understanding of the fundamentals of what DS does and be able to communicate well and demonstrate that you can contribute.
For companies that can be highly picky (FAANG, MBB, etc) you also need to pass the airport test: How would I feel if I was stuck at an airport with you waiting for my next flight?
[link] [comments]
Read on the original site
Open the publisher's page for the full experience
Related Articles
- Interview Experience: Big teams look for potential, smaller teams look for how fast you can instantly come add valueMy interview experience has been a massively varied at this point, but what I've noticed is the massive difference between big companies like FAANG and smaller orgs like DS in banking or random small companies At FAANG it's kind of like an IQ + knowledge test (what google calls Role related knowledge) and smaller companies do assessments for very specific types of modeling or use cases, like build a model being evaluated on a certain metric. So at FAANG I was asked questions like "why is the formula for s.d. different for pop. vs sample', or 'what happens to the bias/variance in x,y,z situation' mean while at companies that are smaller and pay less they sent me a random 30-60 minute assessment and asked me to directly clean data and code up a model with sklearn/pandas. Is this what everyone else has experienced? It does seem like at smaller or traditional companies test if you will be a good code monkey while others look for actual understanding. submitted by /u/LeaguePrototype [link] [comments]
- Senior level DS at FAANG - what coding interviews to expectWorked at FAANG up until a month ago as mid level DS and now I'm getting callbacks for senior level roles from similar companies. My stats intuition/case studies are pretty good since that's mostly what my last job relied on. However, my coding is so rusty since I just used AI most of the time to move fast and cleaned it up when there was a mistake. I'm mostly concerned about prepping the coding and data manipulation rounds. What level of prep should I prepare for to feel 'good enough'? Should I be expected to do leetcode mediums or is pandas/sql enough? Is describing the solution and logic with pseudocode enough for tougher problems or do I have to take it from start to end with no help? What has your experience been like for expectations at senior level FAANG interviews? submitted by /u/LeaguePrototype [link] [comments]
- DS interviews - RantThis is rant about how non standardized DS interviews are. For SDEs, the process is straight forward (not talking about difficulty). Grind Leetcode, and system design. For MLE, the process is straight forward again, grind Leetcode, and then ML system design. But for DS, goddamn is it difficult. Meta -- DS is sql, experimentation, metrics; Google -- DS is stats primarily; Amazon - DS is MLE light, sql, leetcode; Other places have take home and data cleaning etc. How much can one prepare? Sometimes it feels like grinding leetcode for 6 months pays off so much more than DS in the longer run. submitted by /u/No-Mud4063 [link] [comments]
- How do you keep up without burnout?DS sometimes feels like there's infinite amount of things to learn. Most recent trend has been AI engineering And it's not like AI came in so you can deprioritize something else, but instead it just gets added to the heap. So you already had this massive amount of content to know from stats & product, trad. ML, deployment, ops, engineering, cloud, etc. and then you add the new thing on and the new thing. And when you read the job descriptions they literally list of all of this. I just had an interview for a random gaming company that wanted cloud, snowflake, stats, ML, ops, and AI experience in 1 person and it was for like 3-5 years of experience. And I wish that this was a one off thing but it seems to get more common. It actually feels like FAANG is easier to interview for because they silo people and not expect you to know and do everything What is your strategy for learning these skills without getting exhausted, or do you feel companies expectations are overflated? Is this a by product of AI where people are expected to do a lot more with less? submitted by /u/LeaguePrototype [link] [comments]