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

      iwoca

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su iwoca | Offerte di lavoro di iwoca | Stipendi di iwoca | Benefit di iwoca
      Colloqui di iwocaColloqui per Software Engineer presso iwocaColloquio di iwoca


      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 Software Engineer

      18 ago 2022
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso iwoca

      Colloquio

      Gruelling 5-stage interview. Starts off with 30-minute call with hiring manager, then a take-home test, then an interview about your work on the test, then a live coding test, then another interview about system design. It's as if you're applying to Google but way below the pay they're offering. There's plenty of other jobs out there that pay similar with easier application processes.

      Domande di colloquio [1]

      Domanda 1

      System design Instagram. How exactly is a database's data stored on disk.
      Rispondi alla domanda
      2

      Altre recensioni di colloqui per Software Engineer presso iwoca

      Colloquio per Software Engineer

      22 mag 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso iwoca nel mese di gen 2026

      Colloquio

      Intro call with HR, coding screen assessment done via accelerate.io platform, then back to back technical and behavioural interview. The technical round was not coding but was essentially a system design scenario going over a long google doc file covering Database Schema Design, HTTP API calls.

      Domande di colloquio [8]

      Domanda 1

      1. Database Schema Design: We have a users table that stores a single address in its own columns. Design a separate Address table, then walk through the migration: how would you read the existing address from the user table and write it into the new structure?
      Rispondi alla domanda

      Domanda 2

      2. Design the schema for a system with Books and Authors, where a book can have multiple authors and an author can write multiple books. (Looking for the Book, Author, and BookAuthor join table.) When deciding what to index, what columns would you choose and why? (i.e. primary keys, foreign keys, and columns you frequently filter by, e.g. author name.)
      Rispondi alla domanda

      Domanda 3

      3. Indexing Trade-offs: What are the downsides of adding indexes? (Looking for: writes become slower because every index must be updated on insert/update, and indexes consume disk and memory.)
      Rispondi alla domanda

      Domanda 4

      4. Concurrency & Lost Updates: Describe a concrete scenario that leads to a lost update. How could you reduce the probability of a lost update occurring? Suppose Richard and Anna both edit the same phone number at the same time — one is adding an international dialing code while the other is changing the number entirely. How would you detect that one person's change is about to overwrite the other's, reject the second write, and inform whoever submitted second? (Looking for optimistic locking / version numbers.)
      Rispondi alla domanda

      Domanda 5

      5. Transactions & ACID: Why do we wrap these multi-table writes in a transaction? Explain in terms of: Not leaving the database in a half-written state (atomicity / rollback), Not reading the database in a half-written state (isolation)
      Rispondi alla domanda

      Domanda 6

      6. Relational vs. JSON Storage: What are the trade-offs of storing data as a JSON blob versus normalized relational tables? (Looking for: with JSON you store column names and all the syntactic structure inside the data itself, whereas Postgres stores that schema metadata outside the row; and JSON encourages data duplication because you embed relational data directly instead of referencing it via foreign keys.)
      Rispondi alla domanda

      Domanda 7

      7. Schema Migration Strategy: After creating the new Address table, how do you safely migrate? Walk through backfilling the address table and then removing the backend's references to the old address fields.
      Rispondi alla domanda

      Domanda 8

      8. API Versioning: The API currently returns a single address, but now needs to support multiple addresses. How would you evolve the endpoint without breaking existing clients? (Looking for: either a new endpoint version, or temporarily exposing both address and addresses fields.) How would you coordinate the frontend rollout? (e.g. first upgrade the frontend to read the new addresses field — showing an error telling the user to refresh if it unexpectedly detects multiple addresses — then later upgrade it to fully support multiple addresses.)
      Rispondi alla domanda
      1

      Colloquio per Software Engineer

      3 mar 2024
      Candidato anonimo a colloquio
      Londra, Inghilterra
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso iwoca (Londra, Inghilterra)

      Colloquio

      Take home test working on prebuilt project. Not too difficult. Recruiter Interview, more of a chat. Technical interview to review take home test and system design interview Behavioural and culture fit interview

      Domande di colloquio [1]

      Domanda 1

      Why do you want to work here?
      Rispondi alla domanda
      avatar
      Risposta di iwoca
      2y
      Thank you for sharing your interview experience, your feedback on our interview process is valuable to us. We hope the take home test and discussions on system design were insightful. Should you have any further questions or feedback, please feel free to reach out. Best of luck with your job search! - The Talent Team

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      Standard Chartered Bank
      3.5★Stipendio e benefit
      avatar
      Barclays
      3.8★Stipendio e benefit
      avatar
      Absa
      3.7★Stipendio e benefit
      avatar
      Standard Bank Group
      4.1★Stipendio e benefit