Método STAR: cómo responder preguntas de comportamiento en inglés
"Tell me about a time when…" es el inicio de las preguntas de comportamiento (behavioral questions), y aparecen en casi cualquier proceso para roles de IT en empresas extranjeras. No evalúan lo que sabes, sino cómo actúas. El método STAR te da una estructura para contar una historia clara en inglés sin perderte a la mitad. Aquí tienes cómo usarlo, qué tiempos verbales necesitas, frases para cada parte y tres respuestas completas.
Qué es el método STAR
STAR son las iniciales de las cuatro partes de tu respuesta:
- Situation: el contexto. Dónde estabas, qué pasaba. Dos o tres frases como máximo.
- Task: tu responsabilidad o el objetivo. Qué tenías que lograr tú.
- Action: lo que hiciste, paso a paso. Es la parte más larga y la que más importa.
- Result: cómo terminó, idealmente con algo medible, y qué aprendiste.
Una buena respuesta dura entre uno y dos minutos. Si la Situation se lleva la mitad del tiempo, algo está mal: el entrevistador quiere escuchar tus acciones.
Preguntas típicas que piden una respuesta STAR:
- Tell me about a time you disagreed with a teammate.
- Describe a situation where you made a mistake.
- Give me an example of a time you worked under pressure.
- Tell me about a project you're proud of.
Los tiempos verbales que necesitas
La historia ocurrió en el pasado, así que el tiempo principal es el past simple: I noticed, I proposed, we deployed. Es el error más común de los hispanohablantes: contar la historia en presente o mezclar tiempos.
- Past simple para las acciones: I set up a meeting with the team lead.
- Past continuous para el contexto de fondo: We were migrating our services to Kubernetes.
- Past perfect para algo que pasó antes de la historia: The client had already rejected two proposals.
- Present simple solo para la lección que aplicas hoy: Since then, I always ask for written requirements.
Cuidado con los verbos irregulares que más aparecen: led (no "leaded"), took, found, wrote, built, chose.
Frases para cada parte
Situation
"At my previous company, I was working as a backend developer on the payments team."
"This happened about a year ago, when we were preparing a major release."
Task
"My responsibility was to make sure the integration was ready on time."
"I was asked to find out why the service kept crashing."
Action
"The first thing I did was…"
"Then I decided to…"
"I suggested that we…"
"To make sure it didn't happen again, I…"
Result
"As a result, we reduced the error rate by around half."
"In the end, we delivered on time."
"What I learned from this was…"
Tres respuestas completas para IT
1. Conflicto: "Tell me about a time you disagreed with a colleague."
"At my last job, I was a DevOps engineer on a team that was moving to a new CI/CD platform. A senior developer wanted to skip the automated security scans to speed up the pipeline. I was responsible for the pipeline design, and I didn't think removing the scans was a good idea.
Instead of arguing in the meeting, I asked him for thirty minutes to look at the data together. I measured how long each stage took and showed that the scans added about four minutes, while the integration tests added fifteen. I proposed running the scans in parallel with the tests instead of removing them.
He agreed to try it for two weeks. The pipeline ended up faster than before, and we kept the security checks. What I learned is that disagreements are easier to solve with data than with opinions."
2. Error: "Tell me about a mistake you made."
"In my first year as a sysadmin, I was asked to update the SSL certificates on our web servers. I updated them, but I forgot to restart one of the load balancers, so it kept serving the old certificate. The next morning, some customers saw security warnings.
As soon as I found out, I told my manager what had happened and fixed it within twenty minutes. Then I wrote a short checklist for certificate renewals and, a few weeks later, I automated the process with a script that also checks the certificate on every server.
We didn't have the same problem again. Since then, I always verify a change from the user's side, not just on the server."
3. Deadline ajustado: "Give me an example of working under pressure."
"Last year, our team had to deliver a new reporting API for a client in three weeks instead of the six we had planned, because their launch date moved up. I was the tech lead, so I had to decide how to make it work without burning out the team.
First, I met with the product owner and we split the features into must-haves and nice-to-haves. Then I reorganized the work so two developers could work in parallel, and I took on the database changes myself. I also sent a short status update to the client every two days, so there were no surprises.
We delivered the must-have features on time, and the rest followed two weeks later. The client renewed the contract, and I learned how much clear scope helps under pressure."
Para más preguntas técnicas y de comportamiento, revisa las preguntas más comunes en entrevistas técnicas en inglés.
Errores comunes
| ❌ Lo que decimos | ✅ Lo que se dice | Por qué |
|---|---|---|
| We fixed the problem and we improved the process. | We had a problem with the release. I wrote the rollback script and set up the alert. | Con puro we no se sabe qué hiciste tú. |
| So I talk with my boss and he say… | So I talked to my manager, and he said… | La historia va en past simple. |
| …and that's it. | As a result, we cut deploy time in half. | Sin resultado, la historia queda incompleta. |
| Five minutes of context about the company. | Two sentences of context, then the action. | Respuestas largas pierden al entrevistador. |
| I leaded the project. | I led the project. | Lead es irregular. |
Un detalle más: no inventes historias. Un entrevistador con experiencia hace preguntas de seguimiento ("What would you do differently?", "How did your manager react?") y una historia inventada se desarma rápido.
Checklist de preparación
- Prepara entre cinco y siete historias reales que cubran conflicto, error, presión, liderazgo, un logro y una vez que ayudaste a alguien. Una misma historia puede servir para varias preguntas.
- Escribe cada historia en cuatro líneas, una por letra de STAR, con palabras clave. No escribas el texto completo para memorizarlo.
- Revisa los verbos: ¿todo está en past simple? ¿Los irregulares están bien?
- Agrega un resultado concreto a cada historia, aunque sea aproximado: around, roughly, more than.
- Practica en voz alta y mide el tiempo. Apunta a menos de dos minutos.
- Prepara una frase de cierre con lo que aprendiste: "What I took away from that was…"
Si todavía no tienes lista tu presentación inicial, empieza por cómo responder "Tell me about yourself".
Prepara tu entrevista en 5 días
El mini-curso gratis te guía con una lección corta por email cada día: tu pitch, tus frases de experiencia, la pronunciación de palabras técnicas y la pregunta "Why do you want this job?".
Quiero el mini-curso gratis