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

      Stripe

      ¿Esta es tu empresa?

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Stripe | Empleos en Stripe | Sueldos en Stripe | Prestaciones en Stripe
      Entrevistas en StripeEntrevistas para el cargo de Backend/API Engineer en StripeEntrevista en Stripe


      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. Indeed, Inc. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Indeed, Inc.

      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 Backend/API Engineer

      8 de may de 2019
      Candidato de entrevista anónimo
      Los Angeles, CA
      Sin ofertas
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en Stripe (Los Angeles, CA) en may 2019

      Entrevista

      Applied Online, received an initial HR call request next day. Tech recruiter was nice. Answered all those "When and what " questions. Within next few days, setup a technical interview with a developer. They ask only 1 question. Implemented in O(n) complexity. interviewer was happy with the solution(may be he pretended but that is not professional). For a week no reply from HR then i sent multiple reminder and got an auto-reply mail with reject and no feedback eventhough my code ran as passed all the test cases. Moreover i asked interviewer if he looking for a more optimised approach, he replied "No, that the way to do it, i guess". After couple of mails the HR got back me with the message "we have very peculiar process, may be your code not organised or optimised or you probably have less expreince in the language you implemented the code ", (by the i asked many times interviewer if he is looking for any optimsed code also i have 3+ yrs of exprience in the language i coded) And no matter how you answer the question they reject you because basically they are a happy company who are not planning on hiring any candidates. It's a waste of time to attend those interviews. Basically they respect your time.

      Preguntas de entrevista [1]

      Pregunta 1

      /* * Your previous Plain Text content is preserved below: * * # Step 1 Throughout this interview, we'll pretend we're building a new * analytical database. Don't worry about actually building a database though – * these will all be toy problems. * * Here's how the database works: all records are represented as maps, with * string keys and integer values. The records are contained in an array, in no * particular order. * * To begin with, the database will support just one function: min_by_key. This * function scans the array of records and returns the record that has the * minimum value for a specified key. Records that do not contain the specified * key are considered to have value 0 for the key. Note that keys may map to * negative values! * * Here's an example use case: each of your records contains data about a school * student. You can use min_by_key to answer questions such as "who is the * youngest student?" and "who is the student with the lowest grade-point * average?" * * Implementation notes: You should handle an empty array of records in an * idiomatic way in your language of choice. If several records share the same * minimum value for the chosen key, you may return any of them. * * ### Java function signature: ``` public static Map<String, Integer> * minByKey(String key, List<Map<String, Integer>> records); ``` * * ### Examples (in Python): ``` assert min_by_key("a", [{"a": 1, "b": 2}, {"a": * 2}]) == {"a": 1, "b": 2} assert min_by_key("a", [{"a": 2}, {"a": 1, "b": 2}]) * == {"a": 1, "b": 2} assert min_by_key("b", [{"a": 1, "b": 2}, {"a": 2}]) == * {"a": 2} assert min_by_key("a", [{}]) == {} assert min_by_key("b", [{"a": * -1}, {"b": -1}]) == {"b": -1} ``` */
      2 respuestas
      5

      Otras evaluaciones sobre las entrevistas para el cargo de Backend/API Engineer en Stripe

      Entrevista para Backend/API Engineer

      21 de ene de 2026
      Candidato de entrevista anónimo
      Dublín, Dublín
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Stripe (Dublín, Dublín)

      Entrevista

      15 minute call with their recruiter, followed by initial screening round, which was a coding exercise (not leet code, more like string/array manipulation). After passing that, I had to do 6 rounds of: - System design: whiteboard problem, the guy was pleasant and helpful, but I bottled it. - Backend integration: Tests your ability to develop a REST api, easy enough. - Culture: General conversation over career and goals. - Bug squash: They give you a failing test, and you have to fix it. I managed to fix all suites but I didn't perform very well here bc my methodology wasn't strong enough I believe, and the guy wasn't very pleasant (bit pushy but still professional) The interview process was very long and exhausting, but it truly tests your ability as a software engineer without resorting to leet code.

      Preguntas de entrevista [1]

      Pregunta 1

      Identify and fix the code failing this test
      Responder pregunta

      Entrevista para Backend / API Engineer

      11 de nov de 2021
      Candidato de entrevista anónimo
      Cary, NC
      Sin ofertas
      Experiencia neutra

      Entrevista para Backend API Engineer

      5 de oct de 2021
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 6 semanas. Acudí a una entrevista en Stripe en oct 2021

      Entrevista

      It was the first interview of a series (the recruiter said it would be more 5 or 6). The interviewer was a recruiter, but he did some technical questions too.

      Preguntas de entrevista [3]

      Pregunta 1

      - Describe to me/show the projects you have worked with in your career; - Why did you change your career? - Why do you want to move abroad?
      Responder pregunta

      Pregunta 2

      API Engineer specific questions: - Describe to me what these HTTP responses mean: 200, 400, 500 - What is the difference between the 401 and 403 HTTP status? - In a request, what is the header used to indicate the media type? - What are the differences between Compile-Time and Run-Time Error? - What are the main 4 types of methods you can use on a request?
      Responder pregunta

      Pregunta 3

      Python specific questions: - In Python, what type of data structure can you use if you want to have many elements keeping track of the order? - In Python, how do you build a constructor method? - In Python which of these structures have a way of tracking the order of the elements? List, Set, Dictionary and Tuple
      1 respuesta
      2
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Stripe (Cary, NC) en nov 2021

      Entrevista

      Initial screen with recruiter and then a coding session with an engineer. Coding session had nothing to do with Backend engineering or API development at all. Nevertheless, I completed the challenge and all test cases within the allotted time and was able to ask questions to the employee. The next day I received a message that they were not moving forward with me. Not one was my past experience of 8 years asked about. Odd experience.

      Preguntas de entrevista [1]

      Pregunta 1

      Scenario around a log of store closures (whether store contained customers or not) and different intervals of time the store was closed. Depending on the whether the store was closed and there may have been customers a penalty would be added. The goal was to estimate the max penalty based on the conditions. 3 different test cases to apply and test.
      Responder pregunta
      6