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

      Glispa

      Questa è la tua azienda?

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Glispa | Offerte di lavoro di Glispa | Stipendi di Glispa | Benefit di Glispa
      Colloqui di GlispaColloqui per Senior Android Developer presso GlispaColloquio di Glispa


      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 Senior Android Developer

      3 apr 2017
      Candidato anonimo a colloquio
      Berlino
      Nessuna offerta
      Esperienza neutra
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un'altra fonte. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Glispa (Berlino) nel mese di apr 2017

      Colloquio

      I was approached through Stack Overflow. Had a positive initial interview covering the role and why it was vacant. We covered my experience in mentoring and leading and what was required from a senior then some other generic screening topics. This was followed by a free-form technical assessment (android project) intended to take around 3 hours. I was given up to a week to complete it. I was then invited to another interview with an Android specialist and Tech lead (which took place the same day I have written this). I found this interview very difficult in comparison to interviews for similar positions. The interviewers did not ask any soft skill questions (Tell me a time when...) or any typical questions like algorithms and Asymptotic notation but the questions they did ask were related to the job (android, java, testing, quality control) and showed that the interviewers did posses a good deal of understanding of the topics themselves. Unfortunately much of the difficulty stemmed from vaguely worded questions and made me unsure if I was answering the correct question or how much detail they needed. As there were not many feedback cues from the interviewers this problem was exacerbated. I was asked vaguely worded questions about whether I had certain skills or experience (particularly with regards to leadership, CI and configuration), I answered in the negative given that they had my CV I assumed they were looking for something not demonstrated and often following questions made me realise they were in fact asking about something I did have proficiency with and I had to backtrack which I think wrongly leaves the impression of bad communication skills.

      Domande di colloquio [1]

      Domanda 1

      What was your role in your previous projects? Do you know about handlers or loaders? What management experience? Whats is generics and do you know the differences in wildcards? Do you think unit tests should be written? Have you ever done Gradle scripting? What do you look for in code review? Do you know any difference in Android tests and unit tests?
      Rispondi alla domanda
      1