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

      Contently

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Contently | Offres d’emploi chez Contently | Salaires chez Contently | Avantages sociaux chez Contently
      Entretiens chez ContentlyEntretiens d’embauche pour Developer chez ContentlyEntretien chez Contently


      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 Developer

      15 juill. 2015
      Employé (anonyme)
      New York, NY
      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 Contently (New York, NY) en juin 2015

      Entretien

      Interviewing at Contently was an exciting and friendly experience. The process consisted of two phone screenings, and two in-person meetings. The first phone call was with the Director of People Operations and lasted about 20 minutes. We discussed my basic background, items on my resume, and why I was interested in the position. The second phone screening was later that afternoon with the VP of Engineering. In this phone call, we talked more about my technical skills and web development background–including specific examples of my work and how I approached programming related problems in the past. After these phone screenings, I was invited to the office to meet 1-on-1 with members of the team I would be working with. In these interviews, I was asked more about my background, coding questions related to TDD and refactoring, along with my career goals for the future. The team made me feel very comfortable and allowed me to ask many questions about their individual backgrounds, standards of code quality, how they collaborate, and more. My final interview and second in-office visit consisted of a short, 15-minute pair programming session and a meeting with two of the co-founders. The pairing was by-far the best technical interview I've ever had–it allowed me to gain an understanding of their code base while also illustrating how I would approach a given problem. Lastly, speaking with two of the co-founders gave me a high-level view of the company, its background and future goals. Overall, my experience interviewing with Contently was extremely positive–they made plenty of time to answer all of the questions and I could tell they cared deeply about finding a mutual fit for the role. It's the type of place where you wake up excited to go to work every day.

      Questions d'entretien [2]

      Question 1

      What got you interested in web development?
      Répondre à cette question

      Question 2

      What is a specific example of a project you refactored? What were the initial problems and how did you improve them?
      Répondre à cette question
      3

      Autres retours d’entretien d’embauche pour un poste comme Developer chez Contently

      Entretien pour Software Engineer

      10 déc. 2020
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Contently

      Entretien

      Had a call with the engineering manager, completed a React app, then met with two engineers, a dev ops engineer, and the CEO over the span of two sessions. Overall, it was very fluid and respectful of my time. Contently's hiring process itself was a deciding factor in accepting the offer.

      Questions d'entretien [1]

      Question 1

      After building a weather app in React you will build out a new feature + collaborate with their engineers. Afterwards, you'll go through a system designs + architectural interview with the head of Engineering.
      Répondre à cette question

      Entretien pour Software Engineer

      2 déc. 2020
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Contently (New York, NY) en nov. 2020

      Entretien

      First you speak to a HR for culture fit. Second they make you build a Rails Todo app and a Weather App in React. They told the recruiter I was not technically adept enough even though they didn't review the PR or check off their internal boxes for the Rails App. They "reviewed" the weather app an hour after another team member told me they'd review it next week. Asked me why I didn't use state management for a SPA with one input field and then asked me how I could overcome the problem in the api of cities with the same names. ~~~ THEY DIDN'T LOOK AT THE CODE BEFORE ASKING QUESTIONS ~~~ I had built the weather app using the zip code option in the API which solves this problem. Had they actually looked before asking questions, the question wouldn't have been asked. Lets recap: They weren't communicating internally before reviewing (next week vs. an hour later) They didn't look at the code properly before asking questions. They didn't review the other app at all. Don't interview here. Their engineering team clearly has communication issues and problems reviewing code after asking you to make two applications for them.

      Questions d'entretien [1]

      Question 1

      How do you work from a remote environment?
      Répondre à cette question
      1
      avatar
      Réponse de Contently
      5y
      Hello --- As the head of engineering, I'd like to apologize for any lapse in communication on your application. We appreciate the time that all candidates spend on these coding exercises, as the first step in getting to know them. I can assure you that we review all candidate submissions thoroughly. On some occasions the team is able to get an understanding of the technical approaches without needing further follow-up questions. On other occasions deeper conversations are definitely merited and happen. We have sense upgraded our initial coding exercises to be administered on an automated platform and get back to candidates as promptly as we can once those are submitted. Contently puts a lot of stock in thoughtful communication and dialogue, and I'm disappointed that you or any other candidate would walk away with a different experience - something we strive to prevent and remedy. Thank you for your patience and candid feedback. Best of luck in the rest of 2021.