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

      6sense

      Azienda coinvolta

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su 6sense | Offerte di lavoro di 6sense | Stipendi di 6sense | Benefit di 6sense
      Colloqui di 6senseColloqui per Senior Data Platform Engineer presso 6senseColloquio di 6sense


      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. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Indeed, Inc.

      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 Senior Data Platform Engineer

      2 lug 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso 6sense nel mese di giu 2026

      Colloquio

      The first interview round was with the Hiring Manager which revolved around projects from the resume and based on the work experience and a few managerial questions related to situation handling. The second interview round was of a Difficult level and went into depth about each of the big data tools & frameworks you have worked with. But, the worst part about that was that you could clearly feel that the interviewer had gotten all of those questions from AI, which is why the moment I asked some clarification from him because the question seemed too generic & needed constraints, he wasn't particularly able to clarify it confidently and you could see it on his face. Few of these in-depth questions were good but this latter part made the experience "Not so good" for me. The interviewer was literally asking the names & specific terms within the Flink & Spark ecosystem. It just gave me the impression that they are asking a series of AI slog hard questions with a series of expected answers and not to ask too much of clarifications, rather than testing conceptually.

      Domande di colloquio [1]

      Domanda 1

      Note: Many of these questions were specifically asked based on my work experience and the tools I have worked with. It may differ as per your experience. Explain the entire architecture of Trino. What happens when you submit a query? Explain the architecture of iceberg. What is compaction in iceberg? How do you enable the kafka events in Trino? Differences between Flink and Spark Streaming. When would you use which? Name the operators used in Flink in stream joins. If you have a spark job to process a 10GB csv file, and you have 2 spark executors with 2GB each and 2 cores, will it be able to process it successfully? If yes, are there observed issues/anomalies? If no, why? For a kafka topic where the consumer has a high lag, what will you do to reduce that lag? Will just increasing partitions by sufficient of the consumers are same? How can you delete specific events from a kafka topic? If you have a hive table, which will run faster queries on it, Hive or Trino? Do you need Trino in this usecase when you just have hive tables? If the query is a simple SELECT COUNT(*) FROM table, which will execute it faster? Let's say, you observed Trino was faster. Why would that be? What are the compute engines you can use? What is Tez? What does it mean by the term "split" printed in the Trino logs.
      Rispondi alla domanda