In che modo altre persone hanno ottenuto un colloquio
60%
Candidatura online
Candidatura online
20%
Altro
Altro
20%
Segnalazione di un dipendente
Segnalazione di un dipendente
Ricerca colloquio
5 colloqui
Domande frequenti sui colloqui presso Lightdash
Il processo di assunzione presso Lightdash richiede una media di 14 giorni, in base a 1 colloqui inviati dagli utenti per tutte le posizioni lavorative. Il processo di assunzione più rapido è stato quello dei candidati per le posizioni di Full Stack Software Engineer (in media 14 giorni), mentre il processo di assunzione più lento è stato quello dei candidati per le posizioni di Full Stack Software Engineer (in media 14 giorni).
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Lightdash nel mese di ott 2025
Colloquio
Company is very disrespectful to candidate time and takes advantage with free take home assignments, no communication in between processes. Not a serious company and not generous, they want your time and and expertise for free.
Domande di colloquio [1]
Domanda 1
They will ask you to do all strategy and build for free both as application and during interviews. They use you as free consultant.
Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Lightdash (Londra, Inghilterra) nel mese di giu 2024
Colloquio
Non tech chat with software engineer + tech interview with live coding.
My interview ended at the live coding session.
I was more junior than what they were looking for but I really appreciated the process and also the time they took to give me a constructive feedback!
Ho presentato la mia candidatura tramite un'altra fonte. Ho sostenuto un colloquio presso Lightdash
Colloquio
I interviewed for the Analytics Engineer Advocate position and had a generally positive experience with the interviewers themselves. They were thoughtful and respectful throughout the process. However, I found the expectations for the take-home assessment to be excessive and somewhat misaligned with the role.
After completing a technical interview, I was given a take-home assignment that required me to provide recommendations for product improvements. I documented several UX issues and suspected bugs, offering seven observations and four to five specific suggestions, supported by over eight paragraphs of analysis. Despite this, I was told they were looking for more detail, such as Loom recordings or annotated screenshots walking through each issue step by step.
At that point, it felt like the interview process was beginning to resemble unpaid QA work. There is a difference between evaluating a candidate’s product thinking and expecting near-production-level feedback deliverables. While I appreciated the opportunity, I believe candidates should be given clearer and more reasonable expectations for take-home work, especially for roles that are not focused on quality assurance.
Domande di colloquio [1]
Domanda 1
Our partnerships manager wants to see how much revenue each partner brought in during Q1 of 2024, with the highest revenue-generating partner at the top. For reference, they also want to include the partner commission rate and commission amount paid for each partner in Q1.