Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Infosys

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Infosys | Empleos en Infosys | Sueldos en Infosys | Prestaciones en Infosys
      Entrevistas en InfosysEntrevistas para el cargo de ReactJS Developer Interview (AI Screening) en InfosysEntrevista en Infosys


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para ReactJS Developer Interview (AI Screening)

      26 de jun de 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Me postulé en línea. Acudí a una entrevista en Infosys en jun 2026

      Entrevista

      The first round was conducted by an AI interviewer. The interview was well structured and focused on both technical knowledge and problem-solving ability. The AI asked follow-up questions based on my previous answers, so it felt more like a real technical discussion than a simple questionnaire.

      Preguntas de entrevista [1]

      Pregunta 1

      Technical Questions Asked: -- TypeScript -Difference between union types and generic types. -How would you model an API response that can return either data or an error? -Interface vs Type in TypeScript and when to use each. -Preferred approach for type narrowing (discriminated unions vs property existence checks). -- Frontend / React -Local state vs global state management. -How to architect state management for a scalable enterprise React application. -Redux Toolkit, React.memo, useMemo, and state organization. -Deciding what belongs in the global store versus component state. --Performance -Core Web Vitals (LCP, INP, CLS). -Improving Largest Contentful Paint (LCP). -Cross-browser compatibility strategies. -Autoprefixer, polyfills, feature detection, and progressive enhancement. -Debugging browser-specific issues (especially Safari). -Debugging production-only JavaScript errors. --Architecture & Design -SOLID principles with practical examples. -Applying Liskov Substitution Principle and Interface Segregation Principle. -Designing maintainable microservices. -Improving architecture for tightly coupled applications. -Communication between microservices. -REST APIs vs asynchronous messaging. -API versioning and data consistency. --Java / Backend -Performance troubleshooting for enterprise Java applications. -Application-level metrics to monitor during performance analysis. -Database optimization, caching, and connection pooling. --Agile -Estimation techniques when requirements are ambiguous. -Story Points and Planning Poker. -Managing uncertainty and communicating risks to stakeholders. --Quality Assurance -Unit testing vs manual exploratory testing. -Importance of exploratory testing during release cycles. --Coding Round The coding exercise was based on Graphs. The problem required finding the number of Strongly Connected Components (SCC) in a directed graph. It involved implementing a graph traversal algorithm and handling directed edges correctly. If you're preparing for this interview, it's worth practicing: DFS Graph traversal Strongly Connected Components (Kosaraju's or Tarjan's Algorithm)
      Responder pregunta