Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Easygo

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Easygo | Offres d’emploi chez Easygo | Salaires chez Easygo | Avantages sociaux chez Easygo
      Entretiens chez EasygoEntretiens d’embauche pour Senior Software Engineer chez EasygoEntretien chez Easygo


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Senior Software Engineer

      5 mai 2025
      Candidat à l'entretien anonyme
      Melbourne
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Easygo (Melbourne)

      Entretien

      It started with a recruiter phone screen. I had two technical rounds. First was a coding challenge, then system design. Each was a remote interview with one staff member interviewing me. I had to setup a coding environment ahead of time for the coding challenge. And a diagramming tool fr the system design.

      Questions d'entretien [1]

      Question 1

      They wanted to know the maximum profit within a window of a given size. I think it might have originally been an interview about the maximum sub array problem, but the hard part (determining how large a sub array you can use) got lost along the way.
      1 réponse

      Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer chez Easygo

      Entretien pour Senior Software Engineer

      29 juin 2026
      Candidat à l'entretien anonyme
      Melbourne
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Easygo (Melbourne) en févr. 2026

      Entretien

      Overall, the experience was good. I was well prepared for the final round, but I don't think I communicated my examples as effectively as I could have. Aside from that, I think the interview went well overall.

      Questions d'entretien [1]

      Question 1

      leetcode easy to mid then system design then loop interview
      Répondre à cette question

      Entretien pour Senior Software Engineer

      30 juil. 2025
      Candidat à l'entretien anonyme
      Sydney
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Easygo (Sydney)

      Entretien

      First communicate with recuriter, who was very nice to introduce the company and the position. Then first round is coding interview, and the following is System design. Each one is one hour. After that, it will be the last loop, 3 round interviews, on the company values

      Questions d'entretien [1]

      Question 1

      Tell me about a time you faced a major obstacle or setback. How did you overcome it?
      Répondre à cette question

      Entretien pour Senior Software Engineer

      3 sept. 2025
      Candidat à l'entretien anonyme
      Melbourne
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via une agence de recrutement. Le processus a pris 4 semaines. J'ai passé un entretien chez Easygo (Melbourne) en juil. 2025

      Entretien

      First there were coding and system design interviews on video chat. These were fairly straightforward as far as any larger tech company goes; you will likely get some details from your recruiter but I'd recommend being able to describe how to implement some of the basic functions on a streaming site (Kick) or a betting site (Stake) for your focus (frontend/backend). The more opaque part of the process was during the 3 onsite interviews, when different people will ask you to tell them stories about things you've done in your career. I was able to answer all their questions and received positive responses during the interviews. One interviewer said they currently have "unlimited hiring capacity for engineers". After, I got feedback that I was a "great cultural fit" but wasn't getting an offer. I also heard that other candidates have had similar bad luck with this particular company. I have an idea that they wanted to hear more stories about working on things at large scale, but ultimately it was unclear to me exactly what they expected, so if you're going to interview with them I'd be prepared to talk about scale. A red flag to note is that I was interviewed by a very senior engineering manager at the company and in response to one of his questions, I described a time when I optimised some code that was running at O(n^2) to run at O(n) efficiency by implementing a different data structure. He said he didn't know what big O notation was, which I found a little strange.

      Questions d'entretien [1]

      Question 1

      Tell me about a time when you worked on a difficult technical challenge and how you approached it.
      Répondre à cette question