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

      Joyent

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Joyent | Offres d’emploi chez Joyent | Salaires chez Joyent | Avantages sociaux chez Joyent
      Entretiens chez JoyentEntretiens d’embauche pour Software Engineer chez JoyentEntretien chez Joyent


      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 Software Engineer

      15 sept. 2019
      Employé (anonyme)
      Offre acceptée
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 3 semaines. J'ai passé un entretien chez Joyent

      Entretien

      There were a couple of phone calls which mostly seemed aimed at fit and pay. Following the phone calls was an in person interview which consisted of five interviewers in a circuit for about four hours. The questions ranged from hypothetical distributed systems questions to on paper C language problems.

      Questions d'entretien [1]

      Question 1

      How would you make a somewhat stateful HTTP API highly available?
      Répondre à cette question

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

      Entretien pour Software Engineer

      4 sept. 2017
      Candidat à l'entretien anonyme
      Telephone, TX
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Joyent (Telephone, TX) en mars 2017

      Entretien

      I've compared notes with successful and unsuccessful candidates, and this is the best I can offer about Joyent's interview process: * they hire almost entirely on reputation; successful candidates remark that their credentials and capabilities are not meaningfully scrutinised in the interview process and that, given Joyent's reputation for a surpassing technical culture, they are somewhat surprised that the interview questions are easy * reputation is established based on two, possibly three things: 1) work on upstreams that matter to Joyent, where they can see sustained contribution and quality; 2) previous work with Joyent staff, generally on the same teams; and possibly 3) reference from someone with whom they've worked directly and rate highly (note: I'm speculating on the third, I've only seen the first two have impact) * the interview process isn't so much about a fit for ability as for interest and process: specifics of substantial development efforts are already public, as is their engineering workflow * first interview is fairly loose, provides instructions on materials to review for second interview In short, while there are clear means of screening false positives and false negatives, they have very little to do with the interview process proper. My experience was that I was socially familiar with Joyent people but had worked in a position that didn't quite give me credentials I knew they preferred. Although we were direct about this in the first interview, and I was told I had a second interview, it never happened. At great length. Was asked to do a coding assignment. Returned assignment, asked to proceed with second interview, and hemming and hawing started. I was able to determine exactly when they looked at the coding assignment, and six weeks passed with e-mail exchanges while the code was completely ignored. First red flag. Hiring manager acknowledged that he had forgotten what understanding was reached about prep at the end of the first interview, hadn't taken notes. Second red flag, as assurances given, recall of credentials also possibly out the window. Did a fair amount of prep work on expectation of second interview. When two months passed after the first interview with none scheduled, I sent a suggested technical discussion agenda reflecting prep. I can only characterise the responses as filibusters: they didn't really make sense as a response to what I said but looked like an attempt to convey reservation, certainly conveyed greater failures of recollection. Third red flag. At the same time, I was explicitly told I was still under consideration and that "we" needed to work through concerns. Never clear how, if not by interview. Asked to look at a "puzzler". Fine, except that it wasn't particularly clear that the format allowed for meaningful evaluation (answers and reasoning were already largely available in the blog post, as is part of the puzzler format). Sent response, never heard back from hiring manager. Three weeks passed with no further word, wrote them off. Weeks after that, recruiter, who never responded to mail except to set up first interview, sent mail saying nice things but finally "no". Three months of dragging filibustering to renege on a second interview commitment is a distinct lack of courtesy. Such courtesy does not seem an unreasonable expectation: I was an employee referral, have referred business to them, etc. Other candidates with whom I've spoken have been told directly about hiring preferences, although ghosting seems a pathology.

      Questions d'entretien [2]

      Question 1

      Please read our RFDs and Engineering process documents from github. We will discuss these at length in second interview.
      Répondre à cette question

      Question 2

      Since you haven't written node.js professionally previously, please review our public node.js style and design guidelines, write a small system in two days or less, make sure you're comfortable doing this full-time for us.
      Répondre à cette question
      4