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

      Seven Peaks Software

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Seven Peaks Software | Offres d’emploi chez Seven Peaks Software | Salaires chez Seven Peaks Software | Avantages sociaux chez Seven Peaks Software
      Entretiens chez Seven Peaks SoftwareEntretiens d’embauche pour Middle Frontend Developer chez Seven Peaks SoftwareEntretien chez Seven Peaks Software


      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 Middle Frontend Developer

      23 mai 2022
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Seven Peaks Software en mai 2022

      Entretien

      Until the moment of the interview, I did not read the reviews of people who had already passed the interview. But now, after reading the negative Android developer review from April 2022, I completely agree with him. What are the downsides I have experienced? 1) Too big test task for 1 week. For understanding, it was a PDF file with 17 pages of description :) Also, as a bonus, it was proposed to cover the project with tests and make PWA for offline access. And this test task is given to you without any payment for your time. Considering that usually a test task rarely takes 5-7 hours of time, this is the standard for interviews in IT. Here you are offered to work for a week for free) 2) Very formal questions during a technical interview. The basic things that, as already noted in the review from April, it makes sense to ask before the test task if a perfectionist sits in the head of the company and he sees great benefit in seeing an ideal theorist in the workplace rather than a practical developer. As already mentioned in the previous review, either make technical questions, and then a test task, or cancel the technical questions. What are the benefits? 1) Polite HR 2) I can put this project in my portfolio

      Questions d'entretien [1]

      Question 1

      Basic things about JS, Typescript, React.
      Répondre à cette question
      3
      avatar
      Réponse de Seven Peaks Software
      3y
      Thank you for your feedback on the interview process. I do understand the frustration of spending that much time on a test, and some candidates can dot his very quickly, and other take much more time. We are working on finding a good balance that work for both candidate that allow us to get a good understanding of the candidates capabilities, while not wasting too much time. Regarding the technical interview, this is an important part, where we dig into the way you solved the test, and use that as the case study to discuss technically the solution, and potential ways to improve the solution. We will discuss internally to ensure this is still the case, and not only theoretical.