Simulacro

Preguntas de entrevista de trabajo en inglés, por rol

Estas son las preguntas que más se repiten en entrevistas en inglés para trabajos remotos — las mismas que usa nuestro entrevistador IA. Practicalas en voz alta: leerlas no alcanza, la diferencia se nota al hablar bajo presión.

Buscá la guía de tu rol

Cada guía trae las preguntas de ese puesto, el vocabulario en inglés que tenés que poder pronunciar y el error típico del hispanohablante en esa entrevista.

Cómo responder: el método STAR en 30 segundos

Para toda pregunta behavioral ("Tell me about a time..."), estructurá la respuesta en cuatro partes: Situation (contexto en una oración), Task (qué tenías que lograr vos), Action (los 2-3 pasos concretos que tomaste) y Result (el resultado medible: un número, una métrica, un impacto). Apuntá a 45-90 segundos por respuesta y cerrá siempre con el resultado.

Preguntas para Desarrollo de software (general)

Screening con recruiter

14 preguntas
  1. To start, could you walk me through your background and what you've been working on recently?
  2. What caught your attention about this position?
  3. What are you looking for in your next role?
  4. Can you tell me about your experience working with remote or distributed teams?
  5. How comfortable are you working in a fully English-speaking environment?
  6. What time zone overlap can you offer, and how do you usually organize your day?
  7. What are your salary expectations for this role?
  8. Why are you thinking about leaving your current role?
  9. How do you keep yourself productive and accountable when working remotely?
  10. What does your ideal team and manager look like?
  11. How soon could you start, and what's your notice period?
  12. What do you know about our company and product so far?
  13. Tell me about a tool or workflow you rely on to collaborate asynchronously.
  14. Do you have any questions about the company or the role so far?

Entrevista behavioral

13 preguntas
  1. Tell me about a challenging technical problem you solved recently. What made it hard?
  2. Describe a time you disagreed with a teammate about a technical decision. How did you handle it?
  3. Tell me about a project you're particularly proud of. What was your specific contribution?
  4. Describe a time you had to deliver under a tight deadline. What trade-offs did you make?
  5. Tell me about a time you received tough feedback on your code. How did you react?
  6. Describe a situation where you had to learn a new technology quickly to get something done.
  7. Tell me about a time a production incident happened on your watch. What did you do?
  8. Describe a time you improved a process or codebase without being asked to.
  9. Tell me about a time you had to give difficult feedback to a colleague about their code.
  10. Describe a decision you made that turned out to be wrong. How did you notice and what did you change?
  11. Tell me about a time you mentored someone or helped a teammate get unblocked.
  12. Describe how you handled a disagreement with a product manager about scope or priorities.
  13. Tell me about the most complex system you've worked on. How did you get up to speed?

Técnica conceptual

13 preguntas
  1. How would you explain the difference between synchronous and asynchronous code to a junior developer?
  2. Walk me through what happens when you type a URL in the browser and press enter.
  3. How do you decide when to write tests, and what kinds of tests do you prioritize?
  4. Tell me about how you've handled state management in a recent frontend or backend project.
  5. How would you design a simple rate limiter for an API? Just the high-level approach.
  6. What does a good code review look like to you? What do you focus on?
  7. How do you approach debugging an issue you've never seen before?
  8. What trade-offs do you consider when choosing between SQL and NoSQL databases?
  9. How would you design a URL shortener at a high level?
  10. Explain how you'd diagnose and fix a slow API endpoint.
  11. What's your approach to handling errors and retries in a distributed system?
  12. How do you keep an application secure? What do you watch out for?
  13. When would you reach for caching, and what can go wrong with it?

Preguntas para QA / Testing

Screening con recruiter

14 preguntas
  1. To start, could you walk me through your background and what you've been working on recently?
  2. What caught your attention about this position?
  3. What are you looking for in your next role?
  4. Can you tell me about your experience working with remote or distributed teams?
  5. How comfortable are you working in a fully English-speaking environment?
  6. What time zone overlap can you offer, and how do you usually organize your day?
  7. What are your salary expectations for this role?
  8. Why are you thinking about leaving your current role?
  9. How do you keep yourself productive and accountable when working remotely?
  10. What does your ideal team and manager look like?
  11. How soon could you start, and what's your notice period?
  12. What do you know about our company and product so far?
  13. Tell me about a tool or workflow you rely on to collaborate asynchronously.
  14. Do you have any questions about the company or the role so far?

Entrevista behavioral

12 preguntas
  1. Tell me about the most critical bug you ever caught before release. How did you find it?
  2. Describe a time developers pushed back on a bug you reported. How did you handle it?
  3. Tell me about a time you had to test a feature with incomplete requirements.
  4. Describe how you decided what to automate versus test manually in a past project.
  5. Tell me about a release that went wrong. What did you learn and change afterwards?
  6. Describe a time you improved the testing process for your team.
  7. Tell me about a time you had to prioritize testing under serious time pressure.
  8. Describe a situation where you found a bug that was hard to reproduce. What was your approach?
  9. Tell me about a time you advocated for quality when the team wanted to ship fast.
  10. Describe a time a bug slipped to production. How did you handle it and prevent a repeat?
  11. Tell me about how you built trust with developers as a QA person.
  12. Describe a time you had to test something completely outside your comfort zone.

Técnica conceptual

11 preguntas
  1. How do you decide what test cases to write for a new feature? Walk me through your process.
  2. Explain the difference between smoke, regression, and exploratory testing.
  3. How would you structure a test automation framework from scratch for a web app?
  4. What's your approach to API testing? What tools have you used?
  5. How do you write a bug report that developers actually want to read?
  6. How do you test something with a hard dependency on a third-party service?
  7. What metrics do you use to measure quality in a release?
  8. How do you handle flaky tests in a CI pipeline?
  9. How would you test a login flow end to end? What edge cases matter?
  10. How do you decide what NOT to automate?
  11. Explain how you'd approach performance or load testing for an API.

Preguntas para Soporte técnico

Screening con recruiter

14 preguntas
  1. To start, could you walk me through your background and what you've been working on recently?
  2. What caught your attention about this position?
  3. What are you looking for in your next role?
  4. Can you tell me about your experience working with remote or distributed teams?
  5. How comfortable are you working in a fully English-speaking environment?
  6. What time zone overlap can you offer, and how do you usually organize your day?
  7. What are your salary expectations for this role?
  8. Why are you thinking about leaving your current role?
  9. How do you keep yourself productive and accountable when working remotely?
  10. What does your ideal team and manager look like?
  11. How soon could you start, and what's your notice period?
  12. What do you know about our company and product so far?
  13. Tell me about a tool or workflow you rely on to collaborate asynchronously.
  14. Do you have any questions about the company or the role so far?

Entrevista behavioral

12 preguntas
  1. Tell me about the most difficult customer you ever dealt with. How did you handle the situation?
  2. Describe a time you had to explain something highly technical to a non-technical person.
  3. Tell me about a time you couldn't solve a customer's problem. What did you do?
  4. Describe a situation where you went above and beyond for a customer.
  5. Tell me about a time you had to handle several urgent tickets at once. How did you prioritize?
  6. Describe a time you spotted a pattern in tickets and helped fix the root cause.
  7. Tell me about a time you received negative feedback from a customer. How did you respond?
  8. Describe how you've collaborated with engineering teams to escalate and resolve issues.
  9. Tell me about a time you had to deliver bad news to a customer. How did you frame it?
  10. Describe a time you turned an angry customer into a happy one.
  11. Tell me about a time you improved a support metric like response time or CSAT.
  12. Describe a situation where you had to say no to a customer request. How did you handle it?

Técnica conceptual

11 preguntas
  1. A customer reports the app is slow. Walk me through how you'd troubleshoot that.
  2. How do you decide when to escalate a ticket versus keep digging yourself?
  3. What information do you always gather before escalating an issue to engineering?
  4. How would you handle a situation where a fix requires a change the product team deprioritized?
  5. Explain how you'd use logs to diagnose a customer issue. What are you looking for?
  6. How do you keep a knowledge base useful and up to date?
  7. A customer demands a feature that doesn't exist. What do you say?
  8. How do you communicate an ongoing outage to affected customers?
  9. Walk me through how you'd reproduce a bug a customer is reporting.
  10. How do you handle a ticket where you suspect the problem is on the customer's side?
  11. What makes a great support interaction, in your view?

Los false friends que te delatan en la entrevista

Errores de interferencia español→inglés que escuchamos todo el tiempo. Decir uno no te elimina, pero varios seguidos hacen ruido:

  • actually= en realidad (no “actualmente” — eso es currently)
  • assist= ayudar (no “asistir a un evento” — eso es attend)
  • career= carrera profesional (no “carrera universitaria” — eso es degree)
  • compromise= poner en riesgo / ceder (no “compromiso” — eso es commitment)
  • resume= retomar (el CV es résumé; “resumir” es summarize)
  • eventually= tarde o temprano (no “eventualmente” — eso es occasionally)

Leerlas es fácil. Responderlas en voz alta es otra cosa.

Practicá estas preguntas por voz con nuestro entrevistador IA, con la job description real del puesto al que aplicás. El primer simulacro de 5 minutos es gratis, sin tarjeta.

Practicar ahora gratis

Términos y condiciones · Política de privacidad · hola@simulacroapp.com