Real, anonymous reports from people who interviewed for Software Engineer at ByteDance, newest first and distilled into what to expect across the loop.
Get your personalized ByteDance Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My experience started with recruiter contact, and the timeline was a bit chaotic. In one attempt I had rounds scheduled back-to-back, and when I didn’t clear an earlier step, the later rounds got canceled. On another attempt the scheduling felt unstable too, and it created a strange pressure before I even reached the substantive parts.
When I finally got into the actual interview, it was a first-round style screen that focused on resume-related fundamentals without much deep dive. It felt more like a quick filter than a conversation where you could recover through nuance. The questions were described as easy, but the way it ended still felt abrupt—like I was expected to fail.
4 months ago
For an experienced-hire SDE track, my first round ran like a very focused test of fundamentals and “八股” knowledge. It lasted about 50 minutes and started from resume-adjacent basics, then it shifted into a quick coding exercise where I had to reverse a linked list in place.
After that, I was set up for a hiring-manager round, but it got canceled due to changes in hiring priority. The whole experience felt like it was deliberately front-loading core knowledge—almost like the process wanted to confirm I already had the expected depth before moving on.
6 months ago
Average Positive Singapore
I went through a pretty structured interview flow that felt efficient end to end. After an initial online assessment, I had a sequence of technical ph…
6 months ago
Average Neutral Singapore
My interview jumped straight into design and bilingual communication. In the first stage, the interviewer spoke both English and Mandarin and asked me…
6 months ago
Average Positive United States
My first interview stage started with a deep dive into my resume and past projects, and I felt like the interviewer kept pressing on the technical det…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter Interaction & Timeline
Candidates reported varied experiences with recruiter communication and scheduling, often describing the timeline as chaotic and leading to pressure before substantive interviews. Some noted abrupt cancellations of later rounds if earlier ones were not passed.
RecruiterSchedulingCommunication
Technical Coding Screen
The initial technical rounds typically focused on coding problems, often using LeetCode-style questions that ranged from easy to medium difficulty, with a strong emphasis on demonstrating clear problem-solving and reasoning under pressure.
LeetCodeCodingProblem-Solving
Resume Deep Dive
Interviews often began with a thorough exploration of the candidate's resume, requiring detailed explanations of past projects and technical choices, which set the tone for later technical evaluations.
ResumeTechnical DepthProject Discussion
Behavioral & Cultural Fit
Some rounds included behavioral questions focused on teamwork and communication, with an emphasis on cultural fit, particularly regarding language proficiency and collaboration style.
BehavioralCultural FitTeamwork
System Design & Advanced Concepts
For some candidates, interviews included system design questions and discussions on advanced technical concepts, indicating a need for strong fundamentals in areas like databases and distributed systems.
System DesignAdvanced ConceptsFundamentals
Overall Experience & Feedback
Candidates expressed mixed feelings about the overall interview experience, with some appreciating structured evaluations while others felt the process lacked transparency or closure, particularly regarding feedback after interviews.