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

      Starling

      Azienda coinvolta

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Starling | Offerte di lavoro di Starling | Stipendi di Starling | Benefit di Starling
      Colloqui di StarlingColloqui per IOS Developer presso StarlingColloquio di Starling


      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 IOS Developer

      12 mag 2020
      Candidato anonimo a colloquio
      Londra, Inghilterra
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso Starling (Londra, Inghilterra) nel mese di mag 2020

      Colloquio

      The process consisted of a conversation with the recruitment representative followed by a chat with a developer on the iOS team followed by a coding challenge. The chats with the recruitment representative and developer were very pleasant and informative but the coding challenge was unrealistic within the time that was outlined. The challenge expected use of their API to make a number of calls and calculate a value based on the transaction feed and then add that to a savings goal for an account. This challenge was used across all development disciplines and specifics were added for specific platforms. For iOS specifically at least one view controller was expected to be used. The amount of time expected to be spent on the project was 2-3 hours. The required project needed much more time than the 2-3 hours that were outlined and a lot of assumptions needed to be made. In the end I spent 5-6 hours on the project building out a solid foundation with unit tests covering the key areas, but due to keeping time in mind certain minor concessions were made as I felt there was proof elsewhere in the project of certain skills. Initially the project was outright rejected with no feedback at all. Like others have said this came across as quite unprofessional considering the time that was required to be put into the project. After expressing this disappointment I was given a followup call with some more feedback. It turns out that the project was generally liked, but the few areas where concessions were made due to time constraints were reasons for rejection even though it was made clear that these areas were not ideal in the documentation which was provided. There was no opportunity to discuss the project or why certain concessions were made. I feel like there are some flaws with the recruitment process. The expectation of completing the project within the allotted time is unrealistic given the scope of the requirements. Then the lack of opportunity to talk through the given solution, even relatively good ones with some concessions, doesn't give the candidate a fair chance to explain their reasoning given the very open goals of the challenge. All in all I think Starling has a lot of room to improve with their technical challenge process. As it stands if you are not willing to spend an unreasonable amount of time on the project to make it perfect then don't bother applying as you will be rejected without given any opportunity to discuss your provided solution.

      Domande di colloquio [1]

      Domanda 1

      What do you like most about Swift?
      Rispondi alla domanda
      7
      avatar
      Risposta di Starling
      6y
      Thank you for leaving a review. We appreciate your feedback and have taken on board your concerns around the time required for the tech task.

      Altre recensioni di colloqui per IOS Developer presso Starling

      Colloquio per IOS Software Developer

      28 lug 2021
      Candidato anonimo a colloquio
      Londra, Inghilterra
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto più di 3 mesi. Ho sostenuto un colloquio presso Starling (Londra, Inghilterra) nel mese di apr 2021

      Colloquio

      1. Recruiter call 2. Chat with engineer 3. Take home test They are very keen on reactive solutions that use frameworks such as RxSwift. This and other required criteria should be mentioned in the spec for the challenge otherwise the candidate is left to do what they see fit. How can one meet the criteria if one does not know what they are being tested for. Other companies provide this criteria when it's required and leave the challenge open ended if they don't have specifics. Feedback is relayed over a call by the hiring manager. Hiring manager was rude at one point.

      Domande di colloquio [1]

      Domanda 1

      Generic iOS developer questions that can be found on any website
      1 risposta
      2
      avatar
      Risposta di Starling
      4y
      Thank you for taking time to leave a review. Our approach to the technical test is deliberate, leaving lots of room for your own interpretation. We don't have a one size fits all solution and are interested in understanding your approach. We appreciate your feedback and are sorry to hear that you had a negative recruitment experience with us this time around.

      Colloquio per IOS Developer

      6 mag 2020
      Candidato anonimo a colloquio
      Londra, Inghilterra
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Starling (Londra, Inghilterra) nel mese di mar 2020

      Colloquio

      First stage is fairly standard phone screener with usual questions about iOS platform, CV history etc. This part was fine. Second stage is a home test where you have to implement a "round-up" feature using their API. This stage is where, in my opinion, they're really doing it wrong. I say this for two reasons: 1) The test description says it'll take around 3 hours - but this is wildly inaccurate. If you want to do it properly (i.e. with test coverage, some semblance of architecture, clean code etc) then you need to spend at least 2 or 3 times this. If the idea just to see what you can do in 3 hours and assess how you manage your time, then fine - but say so in the test description. Just setting an unrealistic expectation of how long the test will take to do does no one any favours. 2) More importantly - if you fail at this stage, they give you ZERO feedback. Not a big deal if it's a short test, but for one like this that takes hours then it's massively disrespectful and really not cool. I can see from other reviews that I'm not the only one complaining about this. Starling's excuse is apparently that they don't want to compromise their assessment criteria. Well Starling - with respect, that's nonsense. It's perfectly possible to give feedback without revealing too much about your marking scheme, plenty of other companies manage it just fine. The real reason of course is that giving feedback to failed candidates doesn't advance their interests, so they just don't consider it as important. That probably tells you what you need to know about the moral calibre of the people working there.

      Domande di colloquio [1]

      Domanda 1

      Phone screener - fairly standard questions on platform knowledge, technical competence, CV history and so on.
      Rispondi alla domanda
      5
      avatar
      Risposta di Starling
      5y
      Thank you for taking the time to leave a review. Whilst you feel differently, our reasons for not giving feedback are absolutely to do with the assessment. We do make candidates aware before the test is taken that this is the case so that they can decide is they wish to proceed. We value the time people spend applying with us and thank you for this review also, the feedback has been passed on.