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

      Nuvitek

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Nuvitek | Offres d’emploi chez Nuvitek | Salaires chez Nuvitek | Avantages sociaux chez Nuvitek
      Entretiens chez NuvitekEntretiens d’embauche pour Appian Consultant chez NuvitekEntretien chez Nuvitek


      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 Appian Consultant

      27 mai 2026
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Nuvitek en mai 2026

      Entretien

      The interview process can vary significantly across their practices and at different levels. I interviewed for this mid-level Appian position. For a more senior role, the technical questions will likely be more system-oriented than Appian object-specific. I was asked to apply to both positions, so I took the interview as a senior developer. If the interview were purely for a mid-level position, it would be quite intense and a bit difficult. The overall process was quick, as they were hiring to staff the project quickly. From the day the recruiter initially spoke with me in a meeting to a finalized offer, including a holiday in the middle, it took around two and a half weeks, let's say three. If I move faster on the last round, we can wrap this up in two. My recruiter, Mirella, has been super quick and available throughout the process.

      Questions d'entretien [1]

      Question 1

      As far as I can remember, they are listed as follows. From the screening: What log file contains basic Appian system information for debugging? What is the public-facing external mechanism Appian uses? What does high disk space usage suggest? How do you typically configure Appian user security? From the technical round: Describe process model synchronicity, chained and unchained PM starting timeline. How to ensure Appian record sync after PM side smart service SP trigger? Describe the difference of Record custom fields, and their evaluation time. Describe Record-level security, and how they are reflected to the user. How to optimize interface load time, with many RA icons? Hide them initially, expand on click. Describe the difference between tostring() and touniformstring(). SQL examples, describe a many-to-many relationship user case. See technical preparations. SQL SP/Function: general syntax walkthrough and differences. SQL View, optimizing performance. Remembered Behavioral Questions: Tell me about your project / role etc. (Screen) Hardship? A difficult time you have faced? (Technical) Why do you want to work here? (Screen/CEO)
      Répondre à cette question