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

      HvS-Consulting

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur HvS-Consulting | Offres d’emploi chez HvS-Consulting | Salaires chez HvS-Consulting | Avantages sociaux chez HvS-Consulting
      Entretiens chez HvS-ConsultingEntretiens d’embauche pour .NET Full Stack Developer chez HvS-ConsultingEntretien chez HvS-Consulting


      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 .NET Full Stack Developer

      28 mars 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai passé un entretien chez HvS-Consulting

      Entretien

      I have easley applied online. I was called fairly quick for a short phone interview. Later on, we schedule a teams meeting with questions about my profile. It was between their software development lead, HR and me. It lasted for about 45 minutes. I was informed that I will recieve a home assigment, that I will describe in the questions section of this review. Then we scheduled the second interview which lasted 4 hours long. I was presented the office, I presented my solutiond, I ahd the interview ith the HR, the team leand (again) then with the founder. The promised lunch together did not took place. After a week, the applologised for the delay, and teh missuderstanding on their side. They infomed me that the team leader wanted that the last interview should have beena full day interview. The propesed me to scheduled again, but I have already acceped another offer.

      Questions d'entretien [1]

      Question 1

      It was a home assigment. I will try to detail it the best I can. It was about designing a simple Library Management System. Here are the requirements: The system should be able to keep track of all the borrowable items in the library: a) Books have a unique ID, title, author, and publication year. b) DVDs have a unique ID, title, runtime, director and publication year. c) Don't implement: prepare scenario how to include borrowable board games in the future. Users should be able to search for a borrowable item by its title or type (DVD or book). Users should be able to borrow an item for a certain period. If the item is already borrowed, users should be able to join a waitlist. The system should keep track of all the users and the books they have borrowed. Work in the Observer Pattern in order to watch for items returning to the library to notify waiting users. In theory: what other patterns might be applicable? Guidelines: Use object-oriented principles to design classes and their relationships. Use any object oriented programming language [c#, java, go, ...]. Discuss how you would handle potential edge cases or errors.
      Répondre à cette question