Entrevista técnica B1: trajetória

Nível: B1

Objetivo

Apresentar a trajetória profissional em entrevistas técnicas em inglês, descrevendo formação, projetos, responsabilidades e stack, e falar de conquistas de forma clara e sem exagero.

Explicação

A pergunta inicial em quase toda entrevista técnica é Tell me about yourself. Uma resposta em B1 tem três partes bem definidas:

• Present: o que você faz hoje — `I'm a backend engineer at <company>. I work mainly with ...`
• Past: o caminho que trouxe você até aqui — `Before that, I worked at <company> for two years, where I ...`
• Future: por que você está aqui agora — `I'm now looking for a role where I can ...`

Essa ordem presente → passado → futuro evita o erro comum de começar pela infância ou por detalhes irrelevantes. Em B1, espere uma resposta entre 60 e 90 segundos, não mais que isso.

Para descrever projetos e responsabilidades, use padrões fixos:

• `I worked on <project> for <time>.`
• `I was responsible for <area>.`
• `My role was <role>, mostly focused on <area>.`
• `The stack was <tech1>, <tech2>, and <tech3>.`

Para descrever o stack, agrupe por camada em vez de listar tudo solto: `On the backend, we used Java and Spring Boot. On the data side, we used PostgreSQL and Redis.` Em B1, mantenha a lista curta e dê contexto em vez de despejar dez tecnologias.

Para falar de conquistas sem soar arrogante, prefira construções que reconhecem o time e o contexto:

• `I helped <verb> <result>.`
• `I contributed to <project>, where we <result>.`
• `I was part of the team that <result>.`
• `I played a key role in <area>, mainly <verb>ing <result>.`

Resultados com números ficam mais fortes quando são específicos e modestos: `I helped reduce p95 latency from 800ms to 250ms` é mais crível do que `I made the API 10x faster`.

Evite exageros comuns que recrutadores percebem rápido:

• `I single-handedly <verb>` — quase ninguém faz tudo sozinho.
• `I saved the project` / `I saved the company` — forte demais para uma entrevista inicial.
• `I'm the best <role> you'll interview` — quebra a confiança em vez de construí-la.

A regra de ouro: mostre impacto, atribua o resultado ao time e seja específico. `I helped my team ship X, which reduced Y` é mais forte do que qualquer hipérbole.

Exemplos

Erros comuns

• Começar a resposta com dados pessoais irrelevantes: `I'm from São Paulo and I have a cat` deixa o entrevistador impaciente; comece pelo cargo atual.
• Listar tecnologias sem contexto: `I know Java, Python, Go, Rust, Kotlin, Scala` soa como currículo colado; agrupe por camada e explique onde usou cada uma.
• Usar `I single-handedly`, `I saved the project` ou `I was the only one who...`: recrutadores percebem exagero e desconfiam do restante da entrevista.
• Falar por mais de três minutos: a resposta de Tell me about yourself em B1 deve ter entre 60 e 90 segundos; pratique com cronômetro.
• Misturar tempos verbais: o `present` pede present simple, o `past` pede past simple ou present perfect conforme o foco; manter isso consistente mostra clareza.
• Inventar números que você não consegue defender: `I improved performance by 500%` precisa de explicação; prefira números modestos e verificáveis.

Prática guiada

Reescreva cada resposta exagerada em uma versão mais crível e específica.

• Exagerada: `I single-handedly built the entire platform.`

Versão B1: `I was part of the team that built the new platform; my main responsibility was the authentication service.`

• Exagerada: `I made the API 100x faster.`

Versão B1: `I helped reduce p95 latency from 800ms to 250ms by adding a cache layer for the most common queries.`

• Exagerada: `I saved the project from failing.`

Versão B1: `I was part of the team that turned the project around; I focused on stabilizing the release pipeline and improving test coverage.`

Repare que cada versão mantém o impacto, mas atribui o resultado ao time e dá contexto concreto.

Resumo

Tell me about yourself segue a ordem present → past → future em 60 a 90 segundos. Descreva projetos com `I worked on...`, `I was responsible for...` e `My role was...`, agrupe o stack por camada e fale de conquistas com `I helped...`, `I contributed to...` ou `I was part of the team that...`, sempre com contexto e, quando possível, com números modestos.

História: Entrevista técnica B1: trajetória

Nível: B1

História em inglês

The week before the interview

On a Tuesday morning, Camila opened her laptop and stared at the calendar. She had a technical interview at a fintech the following Monday. She whispered to herself, "Tell me about yourself. Again." Her first version of the answer was three minutes long and full of personal details. Her mentor, João, listened and gave her a short piece of advice. He said, "Start with your current role, then go back, and finish with why you want this job."

Rewriting the trajectory

Camila sat down and rewrote her answer following the present → past → future structure. She started with, "I'm a backend engineer with about three years of experience, mostly in Python and FastAPI." Then she added, "Before that, I worked at a logistics startup for two years, where I was responsible for the order tracking service." She closed with, "I'm now looking for a role where I can work closer to payments." The whole answer was about seventy seconds long. João nodded and said, "Much better. Now let's work on a strong achievement, but no exaggeration."

The interview day

On Monday, Camila joined the video call a few minutes early. The recruiter, Daniel, opened with, "Welcome, Camila. Tell me about yourself." Camila delivered the present → past → future answer almost word for word. Daniel then asked, "What was your main responsibility at the logistics startup?" Camila answered, "I was responsible for the order tracking service, and I helped the team reduce delivery delays by 15%." Daniel smiled and said, "That's a clean answer. Tell me more about the stack you worked with." Camila explained, "On the backend, we used Python and FastAPI. On the data side, we relied on PostgreSQL and Redis."

A question about achievements

Near the end of the interview, Daniel asked a tricky question. He said, "Tell me about a project you are most proud of." Camila took a breath and said, "I was part of the team that migrated the legacy order service to Kubernetes." She continued, "My role was to design the new database schema and write the migration scripts." She finished, "We cut our deployment time in half, and the team owns the service today." Daniel wrote a note, thanked her, and said the team would be in touch later in the week.

Tradução linha por linha

Notas de vocabulário

• Tell me about yourself = pergunta inicial clássica em entrevistas técnicas; pede uma resposta curta e estruturada
• present → past → future = estrutura recomendada para a resposta: cargo atual, experiência anterior e motivo da candidatura
• I was responsible for = usado para descrever a área ou o serviço de que você cuidava
• I was part of the team that = padrão para reconhecer conquistas coletivas sem soar exagerado
• My role was = introduz a função específica que você exerceu dentro de um projeto
• On the backend, we used = forma natural de agrupar o stack por camada em vez de despejar tecnologias soltas
• On the data side, we relied on = complementa a descrição do stack com a camada de dados
• I helped the team reduce = padrão de conquista: reconhece o time, mostra o verbo e dá um número específico
• legacy service = serviço antigo que o time herdou; comum em perguntas sobre migração
• migration scripts = scripts que movem dados ou infraestrutura de um ambiente para outro
• deployment time = tempo necessário para colocar uma nova versão em produção

Perguntas de compreensão

1. When was Camila's technical interview?
2. What was the first version of Camila's answer like?
3. What structure did João suggest for Tell me about yourself?
4. How long was the rewritten answer?
5. What was Camila's main responsibility at the logistics startup?
6. How did Camila describe the stack she worked with?
7. What was the achievement Camila was most proud of?
8. Did Camila exaggerate her achievements in the interview?

Prática com a história

1. Reescreva sem exagero: 'I single-handedly migrated the legacy service to Kubernetes.'
2. Complete: 'My ___ was to design the new database schema and write the migration scripts.'
3. Traduza: 'Do lado de dados, contávamos com PostgreSQL e Redis.'
4. Transforme em uma conquista profissional: 'I made the deploys 2x faster on my own.'