TikTok candidates in 2025 describe an online assessment, then two or three technical interviews with one or two LeetCode-style problems each, often including a hard one, plus a short project review and system design for experienced hires. Reported problems include Word Ladder, Expression Add Operators, a priority queue problem, a min-stack variant and level order traversal; the design prompt in one SWE II loop was Amazon’s fulfillment system. Behavioral questions covered changing requirements and the hardest part of a project.
All eight 2025 reports below ended without an offer; several candidates passed early rounds and stopped at the second coding interview.
TikTok interview process round by round
| Round | Duration | What it tests |
|---|---|---|
| HR or recruiter call | Short | Background, availability |
| Online assessment | Not stated | CodeSignal (US) or three LeetCode-style problems (Singapore intern) |
| Technical interview 1 | ~50 min | One or two LeetCode medium or hard problems |
| Technical interview 2 | Not stated | Project review (25 min in one loop) plus a coding problem |
| System design (experienced) | Not stated | A large system such as Amazon’s fulfillment system |
TikTok interview process in 2025: reports by role
These come from self-reported 2025 write-ups on Taro (jointaro.com). Each is one candidate’s account.
- Backend software engineer, Trust and Safety, Seattle (September 2025, no offer). Round one: Word Ladder (LeetCode hard). Round two: a 25-minute project and experience review with Expression Add Operators (LeetCode 282), plus questions on handling changing requirements or deadlines and the most challenging part of a project. Rejected after round two; the candidate said interviewers gave hints and the process was smooth.
- Software engineer, US (October 2025, no offer). Passed a first technical stage, then failed a coding interview of about 50 minutes with icebreakers, two questions, and time for the candidate’s questions. Priority queues came up.
- Software development engineer, San Jose (October 2025, no offer). A CodeSignal OA: the first two questions quite easy, the last two harder, with long problem statements and little dynamic programming.
- Software engineer SWE II, Canada (March 2025, no offer). HR phone screen; a project, experience and system design round on designing Amazon’s fulfillment system, with a level order traversal coding question; then a coding round.
- Software engineer intern, Singapore (November 2025, no offer). Questions on specific resume bullets, React and parallel programming, plus easy and medium coding problems.
- Software engineer intern, Singapore (October 2025, no offer). An OA with one LeetCode medium and two LeetCode hard problems; the candidate solved one and did not advance.
- Software engineer, Singapore (October 2025, no offer). HR call, an OA of one LeetCode medium with a TikTok interviewer present, then a second round of another LeetCode medium, although HR had said it would be system design. Asked about hobbies.
- Software engineer, Singapore (October 2025, no offer). Tell me about yourself, then a LeetCode medium on a stack that tracks the minimum K values. The candidate felt the interviewer was not listening and was rejected.
Detailed interview experiences
Experience 1: Backend software engineer, Trust and Safety, Seattle (September 2025)
Round 1: Word Ladder.
Round 2: A 25-minute review of projects and experience, then Expression Add Operators. Behavioral questions: how do you handle changing requirements or deadlines, and what was the most challenging aspect of your project.
Result: Rejected after round two.
Takeaways
- What decided it: Two LeetCode hard problems in two rounds.
- How to practice: BFS on implicit graphs and backtracking with running state, timed at 35 minutes each.
Experience 2: Software engineer SWE II, Canada (March 2025)
HR phone screen.
Project, experience and system design: Design Amazon’s fulfillment system, and a level order traversal coding question.
Coding round.
Result: No offer.
Takeaways
- Candidate’s advice: In system design, pick one component and go deep instead of staying high level.
- How to practice: For each design prompt, choose the inventory or the ordering service and cover its data model, consistency and failure cases.
Experience 3: Software engineer, US (October 2025)
First stage: Passed.
Coding interview (~50 min): Icebreakers, two problems including priority queues, then time for questions.
Result: No offer.
Takeaway: Two problems in 50 minutes leaves about 20 minutes each. Practice solving mediums in under 20 minutes with clean code.
Experience 4: Software development engineer, San Jose (October 2025)
CodeSignal OA: Four questions, two easy then two harder, long descriptions, little DP.
Result: No offer.
Candidate’s advice: Practice CodeSignal-style problems, since questions repeat, and get comfortable reading long problem statements.
Experience 5: Software engineer, Singapore (October 2025)
HR call, then an OA of one LeetCode medium with an interviewer present, then a second round of another LeetCode medium instead of the system design HR had described.
Result: No offer.
Takeaway: Prepare for coding in every round even when told the round is design.
TikTok interview questions that come up often
Coding
- Word Ladder
- Expression Add Operators (LeetCode 282)
- A priority queue problem
- A stack that tracks the minimum K values
- Binary tree level order traversal
System design
- Design Amazon’s fulfillment system
Behavioral
- How do you handle changing requirements or deadlines?
- What was the most challenging aspect of your project?
- Tell me about yourself; why did you apply for this job?
TikTok interview tips from these candidates
- Train for hard problems. Two of the Seattle candidate’s problems were LeetCode hard.
- Keep project reviews short; one ran 25 minutes before a coding problem.
- Read OA statements carefully; CodeSignal descriptions are long.
- Expect coding even in a round described as design.
TikTok behavioral round in these reports
Behavioral questions came inside technical rounds: the Seattle project review asked about changing requirements and the hardest part of a project, and Singapore rounds asked about resume bullets, hobbies and why the candidate applied. Sample answers are on the TikTok behavioral interview questions page, and round-by-round prep is on the TikTok interview questions hub.
Sample answers for high-frequency questions
Q. Word Ladder.
A. BFS from the start word; for each word, try every letter at every position and enqueue new dictionary words, removing them from the set. Return the depth when the end word is reached. Bidirectional BFS is the usual optimization.
Q. Expression Add Operators.
A. Backtrack over operand splits, tracking the running value and the last operand. For multiplication, the new value is value minus last plus last times current. Skip operands with leading zeros and use 64-bit integers.
Q. How do you handle changing requirements or deadlines?
A. Re-list what still holds, re-plan the smallest change, agree on what moves to later, tell stakeholders the new plan in writing, and ship the core on the original date.
TikTok interview tips from these reports
Online assessment
- US: CodeSignal, four questions, the last two harder.
- Singapore intern: one medium and two hard problems.
Technical rounds
- Seattle: Word Ladder, then Expression Add Operators.
- US: two problems in about 50 minutes.
Project review
- 25 minutes in one Seattle round, before coding.
- Changing requirements and the hardest part of a project.
Sources
- Taro: backend engineer, Trust and Safety, Seattle, September 2025
- Taro: software engineer, US, October 2025
- Taro: software development engineer, San Jose, October 2025
- Taro: SWE II, Canada, March 2025
- Taro: software engineer intern, Singapore, November 2025
- Taro: software engineer intern, Singapore, October 2025
- Taro: software engineer, Singapore, October 2025
- Taro: software engineer, Singapore, October 2025 (second report)
Similar companies
OpenAI · Palantir · Tesla · SpaceX · Meta · Google · Netflix