Two candidates describe ByteDance Data Analyst interviews: one had an HR call and a manager round on projects, scenarios, SQL and Python, and the other a phone screen with an algorithm-style question. Both ended without an offer.
$125K
Avg. Base Comp
$150K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidate reports describe ByteDance Data Analyst interviews, and both candidates came away without an offer. Their experiences differ, so it's best to read them separately rather than as one fixed process.
One candidate applied online, heard back about two weeks later with a screening call, and spoke with HR before a manager round. That round included about 10 minutes of self-introduction, roughly 20 minutes of scenario-based questions, and 5 to 10 minutes of small technical questions. The manager asked about data analysis projects, SQL and Python. The candidate found it conversational rather than deeply technical, so the practical preparation is a clear walkthrough of your past projects and direct answers about how you would handle situations in the role. They also got the impression that the job may involve extra hours to cover Asia Pacific time zones.
The other candidate had a phone screen on a poor connection, with repeated questions and follow-ups that didn't connect well. They recall a vaguely framed algorithm-style question and a lot of discussion about background and team fit. They also said window functions have come up in data analyst interviews there, without describing the question, so reviewing them is a reasonable precaution.
Communication was a sore point in both accounts. After the manager round, the first candidate was told to wait for the recruiter and never got a clear update, so be ready to follow up yourself if you hear nothing after a round.
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 Bytedance Inc. process.
I applied online and heard back with a screening call about two weeks later, so the timeline was fairly standard at the start. The process itself was pretty simple and mostly conversational. I first spoke with HR, and then had a technical round with the manager. That manager round was about my data analysis projects, SQL, and Python, but it also leaned a lot on scenarios and how I would handle different situations in the role. The first part was basically an introduction to myself for around 10 minutes, then about 20 minutes of scenario-based questions, and the last 5 to 10 minutes were small technical questions. One thing that stood out was that the interviewer did not really try to dig into my experience in a thoughtful way, and the tone felt condescending at times, which made the round feel worse than it should have been.
Overall, it did not feel like a very deep technical interview, but it was still important to be clear about your past work and how you approach analysis. I also got the impression that the role may require working extra hours to cover Asia Pacific time zones, which was mentioned in the context of the job expectations. After the manager round, I was told to wait for the recruiter for next steps, but I never really got a clear update and the process just faded out. I ended up with no offer, and the main takeaway for me was that you should be ready to talk through your projects and scenario handling very directly, while also being prepared for a process that may not be especially responsive.
Prep tip from this candidate
Be ready to walk through your data analysis projects clearly, then practice short scenario answers and a few basic SQL/Python questions. It also helps to be prepared for questions about working across Asia Pacific time zones, since that came up as part of the role expectations.
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 | |
| Bank Fraud Model | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Client Solution Pushback | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Button AB Test | |
| Comments Histogram | |
| Experiment Validity | |
| Monthly Customer Report | |
| Subscription Overlap | |
| 500 Cards | |
| Session Difference | |
| Employee Salaries (ETL Error) | |
| Last Transaction | |
| User Experience Percentage | |
| Top 3 Users | |
| Raining in Seattle | |
| P-value to a Layman | |
| Like Tracker | |
| Random SQL Sample | |
| Decreasing Comments | |
| Weighted Keys | |
| Liked Pages | |
| Network Experiment Design | |
| Month Over Month | |
| Impression Reach |
Synthesized from candidate reports. Individual experiences may vary.
This candidate applied online and heard back about two weeks later with a screening call. They spoke with HR first and describe the early process as fairly standard and mostly conversational. The wait before that first call is the only timing detail in the reports; neither candidate says how long the full process took.
The same candidate's manager round started with about 10 minutes of self-introduction, then roughly 20 minutes of scenario-based questions, then 5 to 10 minutes of small technical questions. Topics included their data analysis projects, SQL and Python. They found it conversational rather than deeply technical, and felt the interviewer did not probe their experience thoughtfully.
A different candidate describes a phone call with poor audio, repeated questions and follow-ups that didn't connect to their answers. They recall a vaguely framed algorithm-style question and discussion of their background and team fit. They said window functions have come up in data analyst interviews there, but did not describe the question.
After the manager round, the first candidate was told to wait for the recruiter but never got a clear update, and the process faded out. Both candidates report no offer. If you hit similar silence after a round, following up with your recruiter is a sensible step.
