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

      Bynry

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Bynry | Offres d’emploi chez Bynry | Salaires chez Bynry | Avantages sociaux chez Bynry
      Entretiens chez BynryEntretiens d’embauche pour Mobile App Developer chez BynryEntretien chez Bynry


      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 Mobile App Developer

      31 juil. 2025
      Candidat à l'entretien anonyme
      Pune
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez Bynry (Pune) en févr. 2023

      Entretien

      Round 1: Technical Coding (DSA-focused) The interviewer asked me a coding problem commonly known as the "Two Sum" problem. I was given: An array of integers A target value Problem: "Return the indices or values of two numbers from the array that add up to the target." I discussed both brute-force and optimized approaches: Brute-force: Nested loops with O(n²) time Optimized: Using a HashMap for O(n) time I wrote clean, working code and explained edge cases as well. Round 2: Product-Based Case Study The second part involved a real-world app case study. I was presented with a problem scenario and asked: "How would you design a feature in a utility-based mobile application?" They were looking for: My thought process Feature planning UI considerations State management Offline sync / caching API integration strategy I walked them through: Choosing the right architecture (MVVM) Using Flutter widgets efficiently Preferred state management (Provider or Riverpod) Handling API data and exceptions Ensuring user-friendly error messages and retry logic Overall Feedback: They were evaluating: Problem-solving skills Code optimization App architecture understanding Real-world product thinking The discussion was collaborative and practical, aligned with their domain of utility and field workforce applications.

      Questions d'entretien [1]

      Question 1

      Round 1: Technical Coding (DSA-focused) The interviewer asked me a coding problem commonly known as the "Two Sum" problem. I was given: An array of integers A target value Problem: "Return the indices or values of two numbers from the array that add up to the target." I discussed both brute-force and optimized approaches: Brute-force: Nested loops with O(n²) time Optimized: Using a HashMap for O(n) time I wrote clean, working code and explained edge cases as well. Round 2: Product-Based Case Study The second part involved a real-world app case study. I was presented with a problem scenario and asked: "How would you design a feature in a utility-based mobile application?" They were looking for: My thought process Feature planning UI considerations State management Offline sync / caching API integration strategy I walked them through: Choosing the right architecture (MVVM) Using Flutter widgets efficiently Preferred state management (Provider or Riverpod) Handling API data and exceptions Ensuring user-friendly error messages and retry logic Overall Feedback: They were evaluating: Problem-solving skills Code optimization App architecture understanding Real-world product thinking The discussion was collaborative and practical, aligned with their domain of utility and field workforce applications.
      Répondre à cette question