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

      EHS Analytics

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur EHS Analytics | Offres d’emploi chez EHS Analytics | Salaires chez EHS Analytics | Avantages sociaux chez EHS Analytics
      Entretiens chez EHS AnalyticsEntretiens d’embauche pour Full Stack Developer chez EHS AnalyticsEntretien chez EHS Analytics


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

      24 avr. 2024
      Employé (anonyme)
      Calgary, AB
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez EHS Analytics (Calgary, AB) en oct. 2022

      Entretien

      Step 1. First screening: 30 minutes video interview Step 2. Shortlisted candidates are invited to take an hour test in office. The test is a multiple choice and it is not a technical test. It is more focused on measuring the logical thinking capability of candidates. There are numerical reasoning, logical reasoning and some simple SQL questions. 3. Behavioural interview: This happens after the test. Usually takes 45 minutes. 4. Technical challenge: This is a technical task. Usually includes a database and UI. Shortlisted candidates after the last step will be given a task for which they will develop a solution. 5. Technical interview: 2 hour interview. In the first hour, the applicant will represent the solution they built. The technical team will ask questions based on the solution applicant submitted. The second hour is mainly a technical interview covering applicants technical capabilities.

      Questions d'entretien [1]

      Question 1

      Step 1. Q 1.1: What me through your resume. Q 1.2: How do you feel about on-site job? Do you prefer remote. Q 1.3: What's your C#, SQL (SQL Server) level? Step 2. Q 2.1: Some SQL join questions. Q 2.2: There was a question about coil tossing and probability. I don't remember details Q 2.3: Some math questions like with the given inflation what would be the future price. Q 2.4: Logical reasoning question about a parking lot and fines and the other one was about sport match. It was not hard but some were kinda tricky. Needed more attention. Step 3. Q 2.1: Walk us through your resume. Q 2.2: Have you worked with a difficult person? Q 2.3: Why are you leaving your current job? basically standard behavioural questions Step 4: There was a dataset of a bike shop that needed to be imported into a database. My UI option was a web app. I think you had prices and based on model and date you calculate the future or selling price. It task was not hard. They are more interested in your coding. They get really deep into your code line by line and ask questions why you made different decisions. So submit a clean and well organized code with perfect architecture and logic.
      Répondre à cette question