ByteDance Software Engineer Interview Questions
224+ questions from real ByteDance Software Engineer interviews, reported by candidates.
Round Types
Top Topics
Questions
TikTok OA
Question1: Given 3 integers m,n,r, find the smallest positive integer \'a\' such that (ma)%n = r. e.g. m = 5, n = 3, r = 1 -> (52)%3 = 1, answer...
ByteDance OA
Hi, I have OA of ByteDance in few days.. Do anyone know what kind of question they ask in OA? Like difficulty .. ##### -------Edit------- So.. There were 4 questions in 2 hours.....
ByteDance TikTok Ph.D. Technical Phone Screen Interview Experience
This post was last edited by only_temp_use on 2025-10-7 12:20. I applied to many companies without any referrals. No online assessment (OA), HR contacted me directly. My research direction wasn't rele
You can find the interview experience and timeline here: [https://reurl.cc/8e2rZR](https://reurl.cc/8e2rZR) Below is a summary of the OA. ### Q1 **Problem:** Given a memory array consisting of 0s and
ByteDance Recent Tech Phone Screens Across Three Teams
Trust and Safety Group First Round: Pure coding 695, follow-up 827 Second Round: Discussed projects on resume, failed the first round Capcut Group Coding: bankSystem credit(account,t, n), debit(accoun
ByteDance Frontend Developer Tech Phone Screen Interview Experience
The Chinese interviewer was very friendly. The interview was conducted in Chinese. Basically, they skimmed my resume, then asked some standard front-end coding questions and some JavaScript coding. Th
ByteDance Tech Phone Screen Experience: Prefix Trie Problem and Interview Insights
I was asked two questions. The first one was too easy, and I can't quite remember it, so I'm posting the second one instead. The following content requires a score higher than 150. You can already vie
First Round: A 40-minute in-depth discussion of my internship and project experience, interspersed with standard interview questions on computer networks, operating systems, Redis, and MySQL. System d
ByteDance 2026 Summer Intern Tech Phone Screen Experience
Please give me some points, thank you!! The interviewer was very serious and unsmiling. First, I introduced myself, then he gave me a question about k most frequent elements. I initially wrote it usin
This was my first coding interview, and my performance was only so-so. The interviewer was quite serious throughout. They spent about 25 minutes asking questions related to my resume, including many f
This post was last edited by vul3su4 on 2025-10-02 17:47 VIP is about to expire, please add points Just a little short to see interview experiences Codesignal exam 1 hour 10 minutes, 4 questions, webc
ByteDance Frontend Engineer Technical Phone Screen Experience
This is my first time posting an interview experience, a newbie trying to survive, please excuse my poor performance. The interviewer was HM, not Chinese, not Indian, not American, seemed more like a
This post was last edited by Anonymous on 2025-10-09 14:30 The following content requires a score of 200 or higher. You can already view it. A white woman with a heavy accent, supposedly a tech lead,
After the referral, the recruiter contacted me via email, asking some behavioral questions: "Why us?" / "Why this new opportunity?" (Of course, I need to find a job after graduation). First Round: Des
This post was last edited by EleanorLiu on 2025-10-10 08:30 First round Exam content: Coding + Project in-depth + General knowledge LC1209. Remove All Adjacent Duplicates in String II Project: Briefly
ByteDance Tech Phone Screen: CIDR Aggregation Challenge in Software Engineer Interview
The problem is to output a shortest list of addresses, represented by their CIDR values, that exactly contain a given range of IP addresses. Example: "127.0.0.7" - "127.0.0.16" -> ['127.0.0.7/32', '12
You can refer to [the previous round](https://programhelp.net/en/vo/tiktok-vo-interview-experience-bq-coding-assistance/) of interview experience,This round also ended well. The interviewer was Chines
Hi everyone, I recently took the TikTok OA for a Research Scientist internship. It was proctored on CodeSignal, consisting of 4 problems with 70 minutes time limit. ##### Breakdown: * Q1 (Easy): Combi
Tiktok Singapore - Senior Frontend - R1
Interviewer didn\'t follow typical tiktok interview template of trivia and behavioral questions before coding. Jumped straight into coding. There were 2 problems Q1: LC 784 Letter Case Permutation I didn\'t know the javascript API...
TikTok OA: Views and Duration
Recently recieved a tiktok oa question: given views array, duration array, and integer k, want to maximize profit by choosing k corresponding elements from views and duration. Profit is calculated...
What ByteDance Looks for in Software Engineer Interviews
ByteDance Software Engineer interviews are calibrated against the level and scope expected of the role. Across 224+ verified candidate reports on LeakCode, the consistent signals interviewers look for: clear problem decomposition before coding, explicit complexity reasoning, structured handling of edge cases, and the ability to articulate trade-offs between two reasonable approaches.
The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the solution. It is the path to the solution: did you ask clarifying questions, did you state your approach before coding, did you handle edge cases without prompting, and did you communicate your reasoning throughout. Reports tagged "no hire" frequently cite a working solution with poor communication; reports tagged "strong hire" cite clear thinking even when the final solution was incomplete.
How To Use This Question Set
Real interview reports are a calibration tool, not a memorization target. Companies update their question pools every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage use: identify the patterns that appear repeatedly in ByteDance Software Engineer reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions below by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of ByteDance's pool. Reports tagged with quantified difficulty (e.g., "medium-hard") are higher-signal than reports without difficulty tags.
Round-by-Round Expectations
ByteDance Software Engineer loops typically span 4-6 rounds across phone screens and on-site or virtual on-site interviews. The structure varies by company: some run 1 recruiter screen + 1 technical phone + 3-4 on-site rounds; others run 1 recruiter screen + 1 OA + 4-5 on-site rounds. The recruiter screen is logistics and culture-light; the technical phone screen is medium-difficulty coding; the on-site loop covers coding, system design (at L4+ levels), and behavioral rounds.
Each round is designed to surface a specific signal. Coding rounds: correctness, code quality, complexity reasoning, communication. System design rounds: requirements clarification, design judgment, operational thinking. Behavioral rounds: ownership scope, leadership, ambiguity tolerance, conflict navigation. Strong candidates explicitly hit each signal dimension out loud during the round; weak candidates focus only on solving the prompt.
Common Interview Mistakes At This Combination
Reports tagged "no hire" at ByteDance Software Engineer commonly cite: jumping into code without clarifying requirements, coding silently for 10+ minutes without verbalizing approach, missing edge cases (empty input, single element, very large input, overflow), and producing a working solution that the candidate cannot explain or refactor when probed. Strong candidates avoid these patterns by following a consistent template: clarify, verbalize approach, code with narration, test with examples.
Behavioral and design rounds have their own failure modes. Behavioral: stories that use "we" instead of "I" diluting individual signal, stories with no quantified outcome, defensiveness when probed about failure. Design: not asking clarifying questions, not stating requirements out loud, designing for a single server when the prompt clearly implies scale, ignoring operational concerns (deployment, monitoring, rollback). These show up in roughly half of ByteDance Software Engineer interview retrospectives on LeakCode.
See All 224 ByteDance Software Engineer Questions
Full question text, answer context, and frequency data for subscribers.
Get Access