Candidates describe the ByteDance Data Scientist interview as mixing coding, SQL and probability with detailed project discussion and product-minded case questions, often ending with an HR or fit conversation.
$169K
Avg. Base Comp
$220K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The ByteDance Data Scientist interview, as three candidates describe it, tests more than one skill. All three reported no offer, so use their accounts as a guide to where the questions got hard.
Two candidates described a project discussion. One said the first technical round opened with about 20 minutes on a key data project they owned, and the second round returned to project work with a focus on cross-functional collaboration. Another was asked to walk through past work, including decisions, trade-offs and impact. Prepare one project story in detail, covering what you owned, what you chose not to do, and what changed as a result.
Coding and quantitative questions came up in two accounts. One candidate described an online assessment with medium-to-hard LeetCode-style problems, followed by live coding and follow-ups on optimization. Another reported a SQL question counting new invitors in a date range, a triangle-triplet array problem, a sqrt() implementation to two decimals, merging three sorted lists, and a probability question on expected rounds needing two consecutive wins. Practice stating time complexity aloud and handling edge cases.
The third candidate reported a different style, with a resume walkthrough and a case on designing a recommendation system for TikTok Shop vendors. That case covered metrics, seller success and available data. Follow-ups covered LLM hallucination, SQL and analyzing new business growth. Expect to reason about product trade-offs as well as models.
Two candidates mentioned a closing HR or fit conversation covering communication, teamwork, career goals, location and role preferences. One candidate also had a conversational manager round. Another reported a late-night first call because interviewers were in China and Singapore, so confirm scheduling early.
Synthesized from 3 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 Bytedance Inc. process.
The process felt pretty structured and efficient, but it was definitely on the tougher side. I went through an online assessment first, and that part was centered on data structures and algorithms with medium-to-hard LeetCode-style problems. After that, the technical interviews were split into a few rounds and stayed focused on core fundamentals, problem solving, and coding live. There were also follow-up questions meant to test how deeply I understood my approach and whether I could optimize it, so it wasn’t enough to just get to a working answer quickly.
What stood out most was that the interviews weren’t just about coding speed. There was a project discussion where I had to walk through past work in detail, including the decisions I made, the trade-offs I considered, and the impact of the project. The final HR/behavioral round was more standard and covered communication, teamwork, and fit. Overall, the interviewers were professional, and the process moved along without feeling chaotic, but the algorithm questions were definitely the hardest part. I didn’t get an offer, and my main takeaway was that anyone preparing for this should be very comfortable with medium-to-hard coding questions and be ready to explain not just what they built, but why they built it that way.
Prep tip from this candidate
Drill medium-to-hard LeetCode-style problems and practice explaining optimization trade-offs out loud, since the technical rounds included follow-up questions on depth of understanding. Also be ready to discuss past projects in detail, especially the decisions, trade-offs, and impact.
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 Bytedance Inc.
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Size of Joins | |
| Bank Fraud Model | |
| Permutation Palindrome | |
| Hurdles In Data Projects | |
| Targeted sum | |
| Target Value Search | |
| Client Solution Pushback | |
| Pathfinder in Maze | |
| Hidden Substring Segment | |
| LRU Cache 1 | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Subscription Overlap | |
| Last Transaction | |
| Merge Sorted Lists | |
| Longest Streak Users | |
| Button AB Test | |
| Comments Histogram | |
| Employee Salaries (ETL Error) | |
| Ad Comments | |
| Experiment Validity | |
| Monthly Customer Report | |
| Liked Pages | |
| User Experience Percentage | |
| Top 3 Users | |
| Random SQL Sample | |
| Paired Products |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openers. One described an online assessment with medium-to-hard data structures and algorithms problems. Another reported a first call that combined a resume walkthrough with a case question, scheduled late at night for time-zone reasons. The format may vary by team.
Candidates report technical rounds that mixed project discussion with SQL, algorithm and probability questions. One described a 60-minute first round with about 20 minutes on a project. Reported questions included counting new invitors, merging sorted lists, implementing sqrt() and an expected-rounds problem. Follow-ups on optimization and depth of understanding were reported.
One candidate was asked to design a recommendation system for TikTok Shop vendors and discuss success metrics for sellers, available data and business growth analysis. LLM hallucination also came up because of the candidate's resume. Other candidates may see different case material.
One candidate described a more conversational round led by a manager. It revisited SQL and probability and asked about role preferences and location flexibility. This was reported by a single candidate, so treat it as a possible stage, not a guaranteed one.
Two candidates reported a final HR or behavioral conversation. Topics included communication, teamwork, fit, career goals, and logistics such as location and role type. Candidates describe it as more standard than the technical rounds.
