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

      Helsing

      Azienda coinvolta

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Helsing | Offerte di lavoro di Helsing | Stipendi di Helsing | Benefit di Helsing
      Colloqui di HelsingColloqui per Front End Engineer presso HelsingColloquio di Helsing


      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 Front End Engineer

      30 giu 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio facile

      Candidatura

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

      Colloquio

      I would say this company is a waste of time. I was a bit put off initially when told how many stages there would be. I gave them the benefit of the doubt that this would be for thoroughness, Unfortunately it was not. The first interview was fine. The second interview (technical) also fine. However I was rejected there. After chasing up for feedback, since zero reason was given, I was told that basically it was because I wrote some code for a custom hook, thought out loud "why doesn't the function inside run?" , and since my interviewer answered immediately "you need to call it, in an effect", this indicated I didn't know about useEffects. Forget the fact that I've been a principle code owner on a react codebase for the past 2 years. Thinking out loud "what did I miss" for half a second was interpreted as not knowing these concepts. It did not matter that once the word "effect" was mentioned, I added the code immediately and then explained why it's needed. The interviewer didn't ask any questions about choices I had made. No questions about my thinking process. At the time I thought that was fine; I guessed we were seeing that I can code react. It felt like a fairly normal pair programming task. In my experience, the point of these tasks should not be "always write everything absolutely perfectly" but more about the thinking, the ability to work through a problem, take in suggestions from others, work collaboratively. In my time I've seen many very great developers do something trivial like write a function, forget to call it, and wonder for a second or two why their code isn't running. I've never interpreted that to mean they didn't know what they were doing. It's frustrating to be rejected for something so random after spending time preparing.

      Domande di colloquio [1]

      Domanda 1

      write react code that handles some state
      Rispondi alla domanda