Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      TikTok

      Parte di ByteDance

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su TikTok | Offerte di lavoro di TikTok | Stipendi di TikTok | Benefit di TikTok
      Colloqui di TikTokColloqui per Junior Backend Software Engineer presso TikTokColloquio di TikTok


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Junior Backend Software Engineer

      31 ott 2023
      Candidato anonimo a colloquio
      Sydney
      Nessuna offerta
      Esperienza negativa
      Colloquio facile

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso TikTok (Sydney) nel mese di ott 2023

      Colloquio

      I knew I wouldn't pass the interview within the first 5 minutes. Interviewer spoke very little english. He kept telling me that my microphone sucked. I connected three different microphones and he complained about all of them. Overall, this took roughly 10 minutes to fix. He then asked about a project that was on my resume. He asked me what data structure Redis uses for its sorted set. He then asked what algorithm would be used to insert data. I misspoke and said the wrong thing before correcting myself and mentioning a skip list (I knew inserts were O(logn) and accidentally said binary search initially). He seemed really unimpressed that I didn't know the answer off the top of my head. Next he asked about Cassandra and its benefits. I mentioned high availability and scalability, low latency, linear scalability and a few other points which I have forgotten in a fair amount of detail. I also compared these benefits with postgres. After mentioning postgres, he asked about primary and secondary indexes, read performance, and considerations to make when choosing a primary key. I mentioned in detail index size, tradeoffs of common data types (int, uuid, string, etc). Also, I mentioned seq scans vs index scans and performance at scale. He also asked about briefly about concurrency and some other minor topics regarding db locking. While answering the questions, he was looking around his office/workspace and definitely wasn't paying attention. He also made no comments about my answers to the questions he was asking. After about 25-35 minutes, we moved to the coding section. He gave me the question and didn't say anything to me. He just pulled up the question and sat there. I read out the question to him and asked clarifying questions about the problem and he just responded with "mhm". The question was Merge Two Sorted Lists. I hadn't completed this question for quite a while so I walked through my solution and explained it to the interviewer, He just said "yeah" and didn't add anything. I coded the question up in Go and made a few syntax mistakes which cut off about 5 minutes from the solution. He seemed really unimpressed that I forgot some minor details of Go's syntax. Overall, I completed the problem with tests cases. However, I'm certain the two syntax mistakes I made cost me moving to the next round. Next, he asked me to do it recursively. We had about 10 minutes remaining so I was unsure if I could get the solution done in time as 5 minutes was needed for the question portion of the interview. I wrote pseudo-code and walked him through the solution. He said that it was correct but we needed to move to the question section. I asked about the company work culture, the use of Go and procedural programming, as well as best parts of the job and the company. His answers were each about 10 words or less. Hopefully others interviewing have a more positive than I did. Green Flags: Senior staff that I'm in contact with are really nice and encouraged me to apply. Recruiter was responsive and nice. Red Flags: Hybrid (4 days in office) 1.5hr travel time for me. Junior and Mid-Level engineers have a bad reputation in being rude (unfortunately my experience - not everyone's though!) TL;DR - Interviewer didn't speak much english and wasn't engaged at all. He ignored my answers to most questions and provided no input. Coding question was easy but 2 syntax problems which took roughly 1.5 minutes to solve cost me. Sydney engineers are expected to come into office (Salesforce tower circular quay) four days a week.

      Domande di colloquio [6]

      Domanda 1

      Redis: What data structure is a sorted set?
      1 risposta

      Domanda 2

      Redis: What algorithm is used for inserting into a ZSet?
      Rispondi alla domanda

      Domanda 3

      What are some benefits of Cassandra of other DBs?
      1 risposta

      Domanda 4

      PostgreSQL: Can you explain the benefits of a primary key?
      1 risposta

      Domanda 5

      Database: What considerations do we need to make for a concurrent environment
      Rispondi alla domanda

      Domanda 6

      Coding Question: Merge Two Sorted Lists
      Rispondi alla domanda
      2