Glassdoor users rated their interview experience at ByteDance as 60% positive with a difficulty rating score of 2.75 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Content Marketing Manager and Computational Linguist rated their interviews as the hardest, whereas interviews for Computational Linguist and Modérateur roles were rated as the easiest.
The hiring process at ByteDance takes an average of 12 days when considering 5 user submitted interviews across all job titles. Candidates applying for Music Content and Community Manager had the quickest hiring process (on average 8 days), whereas Computational Linguist roles had the slowest hiring process (on average 14 days).
Fast paced 30-minute interviews which was great in terms of no time being wasted. All interviewers seemed smart and clear on objectives for the role.
The disappointing part however was after completion they came back with a change in the title which seemed to be a practice according to some.
Interview questions [1]
Question 1
What are the challenges you faced previously and how did you solve them
I applied online. I interviewed at ByteDance (San Jose, CA) in Mar 2024
Interview
The first round of the interview was taken place online with the HR. It went really well, the HR was very kind and informative, and asked simple questions about my background and why I wanted to join ByteDance. They seemed very engaged and gave input on my answers. Then I had my second round of the interview with the hiring manager. The conversation pretty much went nowhere. The interviewer seemed just simply reading from their list of questions they had in front of them instead of engaging like a genuine human. They gave very short and dry answers to the questions I asked at the very end, which made it seem like they were completely bored and uninterested by the interview and ended so abruptly without even saying thank you or discussing what the next steps would be.
Self introduction at first. Then questions about web development like how to use redis properly. Also asked some really boring questions instead of any interesting topics about my projects, then gave me a leetcode hard problem to solve and i failed.
Interview questions [1]
Question 1
Q; How did you solve the problem that redis may crash when running?