Tiktok AI Research Scientist interview typically runs 4 rounds: HR screen, technical rounds, and final manager interview. It usually takes about 1-2 weeks and is notably research-heavy, with live coding and deep follow-up questions.
$218K
Avg. Base Comp
$297K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
We’ve seen TikTok’s AI Research Scientist interviews reward candidates who can defend their work at a level deeper than the abstract. Multiple candidates reported that interviewers kept pressing past the headline of a project into the study design, implementation details, and the reasoning behind specific choices. That pattern shows up again in the ML-heavy rounds, where the discussion moved quickly from fundamentals into architectures for multimodal language models and even diffusion-network specifics. The signal here is clear: surface-level familiarity is not enough; the team seems to care a lot about whether you can explain why a method works, where it breaks, and what tradeoffs you made.
Another recurring theme is how applied the technical bar feels. Our candidates report being asked to write pseudo-code for a transformer, implement a cross-attention block, and reason through graph traversal choices live, alongside questions about GPU bottlenecks and evaluation metrics. That mix suggests TikTok is looking for researchers who can move comfortably between theory and code, not just publish or prototype in isolation. We also noticed one unusual but important pattern: one candidate was unexpectedly interviewed in Mandarin with no warning, which implies language flexibility can matter in ways that aren’t always spelled out upfront.
What makes this process distinctive is the emphasis on composure under interruption and follow-up pressure. Interviewers repeatedly challenged answers in real time, and the strongest candidates were the ones who could stay precise while being pushed on details. In our view, TikTok is screening for people who can think like researchers, code like practitioners, and communicate clearly when the conversation gets very specific very fast.
Synthesized from 2 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tiktok process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tiktok
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| P-value to a Layman | |
| Raining in Seattle | |
| Hurdles In Data Projects | |
| Production Model Monitoring | |
| Transformer Encoder Layer | |
| Bias - Variance Tradeoff and Class Imbalance in Finance | |
| Compute Variance | |
| Flatten N-Dimensional Array to 1D Array | |
| Basic Regex | |
| Unsafe Content ML Design | |
| String Mapping | |
| Bias vs. Variance Tradeoff | |
| Overfit Avoidance | |
| Messenger Service Design | |
| Target Value Search | |
| Concurrent LLM Serving | |
| Safe Deployments | |
| Data Preparation for Imbalanced Data | |
| The Longest Journey | |
| Scalable Data Pipelines | |
| f(x,y) in Interval | |
| Facebook Job Board Design | |
| Logistic Regression from Scratch | |
| Data Cleaning Experiences | |
| LRU Cache 1 | |
| Why Do You Want to Work With Us | |
| ReLu vs Tanh | |
| Statistically Significant Test |
Synthesized from candidate reports. Individual experiences may vary.
An initial HR conversation starts the process. This is typically a quick screening to confirm background, motivation, and basic fit before moving into the technical loop.
The first technical round focuses heavily on past research and project experience. Interviewers probe deeply into your study design, implementation choices, and whether you truly understand the details behind your work, sometimes including a coding problem such as dynamic programming.
This round mixes machine learning fundamentals with hands-on coding. Candidates may be asked about classification, evaluation metrics, transformer architecture, GPU bottlenecks, or to write pseudocode for a transformer or solve a LeetCode-style problem.
Another technical round goes deeper into applied ML problem-solving and model internals. Topics mentioned include multimodal language model architectures, diffusion networks, and implementing core components like a cross-attention block from scratch.
The final manager conversation is higher level and centers on research direction and the kinds of problems the team works on. It is less about coding and more about how your interests and experience align with the team’s research priorities.
