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

      Kanini

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Kanini | Offres d’emploi chez Kanini | Salaires chez Kanini | Avantages sociaux chez Kanini
      Entretiens chez KaniniEntretiens d’embauche pour Tech Lead chez KaniniEntretien chez Kanini


      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 Tech Lead

      27 juin 2022
      Candidat à l'entretien anonyme
      Chennai
      Offre refusée
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Kanini (Chennai) en juin 2022

      Entretien

      Unprofessional Interview. They will ask you to turn on your cam but you have no idea to whom you're talking for an hour. They are expecting scripted answers to their set of scripted questions with exact words(based on their expectations) It was just a 1st round. I'm not going for another round even if they are calling back. Good fit for all-time interview-ready candidates who switch companies regularly for higher CTC

      Questions d'entretien [1]

      Question 1

      All scripted questions you find on the google
      1 réponse
      1
      avatar
      Réponse de Kanini
      3y
      Dear Candidate, We regret that you had an unpleasant interview experience with Kanini. We're really sorry for your experience. At Kanini, we wish to make every candidate experience enriching and rewarding - irrespective of their selection. We respect the time and energy of every individual candidate and always work to provide a memorable and warm interview experience. As any employee would vouch, Kanini is a happy place to work and we extend the same principles to interviews as well.

      Autres retours d’entretien d’embauche pour un poste comme Tech Lead chez Kanini

      Entretien pour Tech Lead

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

      Candidature

      J'ai passé un entretien chez Kanini

      Entretien

      Frustrating and probably biased. He went into depth for questions for those topics I mentioned I didn't know. I don't want to say there was a bias, but interview was skewed towards non-selection.

      Questions d'entretien [1]

      Question 1

      1.There is a requirement/enhancement coming within an existing application. What is the approach you take? What are the artifacts you come up with? How do you start with coming up with the design? 2. Give me a problem statement and the solution you have done — a use case where you are really proud of the design you delivered. 3. After multiple retries, a message goes into the dead letter queue. What are you doing with those messages? 4. Say there is some scenario where a message is going to a dead letter queue — it need not be payment, it could be inventory, orders, whatever. How are you going to solve that, and what are you going to do with those messages? 9. Is your application monolithic or microservices-based? 10. How are you handling data integrity within the microservices? 11. Say order processing: I create an order, check inventory, do the payment, then create the order. If the payment fails and inventory is already deducted — how do you maintain data integrity in this case? 12. You talked about CQRS — why do you need to use the CQRS pattern? 13. (Follow-up) You could reuse the same models for read and write, right? It's just an object with data. Why should you not use the model itself? 14. (Follow-up) Those locks can still be controlled using NO_LOCK or similar mechanisms, right? 15. How do you communicate between one microservice and another? 16. How is your microservice deployed in Azure — are you using App Services or Kubernetes? 17. When do you choose between App Services and Kubernetes? 18. What are extension methods? 19. How do you differentiate between a regular method and an extension method? 20. In an ASP.NET web application, how are you going to handle exceptions across your controller methods? 21. Say I don't want to use try-catch in each controller/action method — how do you handle it in a generic way? 22. (Follow-up) You talked about middleware — how are you going to do that with middleware? 23. How many years of experience do you have developing ASP.NET web applications? 24. How do you improve performance in your ASP.NET application? 25. Do you know what clean architecture is? 26. Do you know what is (unclear) design?
      Répondre à cette question