Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4 stories

Likes earn the author +10 XP for the first 3 likes each day

TikTok ShopSoftware Engineer
Reported Jul 2026

TikTok Shop Software Engineer interview: KPI, SQL and incident scenarios

The interviewer first asked whether I had questions, then I gave a brief introduction. It quickly turned into a question about setting KPIs for the role, followed by troubleshooting and incident scenarios about user tickets. I was asked how I would investigate a page that would not load for a person new to the platform, what early signs could point to an access-permission cause, and how I would i…

Technical Screen0
TikTok ShopSoftware Engineer
Reported Jul 2026

TikTok Shop Software Engineer interview: scheduling issues and timed OA

The process got off to a bad start with scheduling problems that kept moving things around. I felt as though I was always waiting for someone else to show up, and that disruption carried into the technical portion. The assessment had an array medium question and a tougher trie problem with about 45 minutes total. I finished the array question in roughly the first quarter of that time, but the tri…

Online Assessment0
TikTok ShopSoftware Engineer
Reported Jul 2026

TikTok Shop Software Engineer interview: coding explanations and detailed follow-ups

After a recruiter call, I went through a short series of online interviews. We started with my background and projects, then moved to a medium LeetCode-style question. I had to explain my approach and why I'd chosen it. The interviewer kept returning to the details, almost walking through every step again, and I grew more nervous as the questions continued. The coding itself felt manageable. When…

Technical Screen0
TikTok ShopSoftware Engineer
Reported Jul 2026

TikTok Shop Software Engineer Interview Experience: A disputed reasoning path

I started strongly in the sense that I solved the main LeetCode problem as well as I could, but the interview quickly became uncomfortable. The interviewer kept pulling me into the details of what I said and how I justified it. What threw me off was that, after I gave what felt like a solid answer, the interviewer pushed a sub-optimal approach as the right direction. The repeated follow-ups made…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP