// interview prep · English · Canadian Tech Job Market
Canadian Tech Interviews
Guia de Entrevistas para Vagas de Tecnologia no Canadá
HR Screening
Technical Interview
Intermediário–Avançado
perguntas + minhas respostas + cultura de entrevista
HR / Recruiter Questions — perguntas comportamentais e de fit
"Tell me about yourself."
Fale sobre você.
Minha resposta (exemplo)
"Sure! I'm a software developer with [X years] of experience, mostly working with [stack, e.g. JavaScript and React]. Right now I'm at [company/role], where I focus on [what you do]. Before that, I [previous relevant background]. I'm looking for a new opportunity where I can [growth goal, e.g. work on larger-scale systems] and contribute to a team like yours."
"Why do you want to work here?"
Por que você quer trabalhar aqui?
Minha resposta (exemplo)
"I've been following [company]'s work on [product/mission], and it aligns with what I care about professionally. I also like that the role focuses on [specific responsibility from the job post] — that's exactly the kind of work I want to grow in."
"Why are you leaving your current job? / Why did you leave your last job?"
Por que você está saindo/saiu do emprego atual?
Minha resposta (exemplo)
"I've learned a lot in my current role, but I'm looking for a position with more [growth / ownership / a different tech stack]. I feel like I've reached a good point to take the next step in my career."
"What are your salary expectations?"
Qual sua pretensão salarial?
Minha resposta (exemplo)
"Based on my research for this role in [city/province] and my experience level, I'm looking at a range of $[X] to $[Y] CAD, but I'm open to discussing the full compensation package, including benefits."
"Are you legally authorized to work in Canada? Do you require sponsorship?"
Você tem autorização legal para trabalhar no Canadá? Precisa de patrocínio de visto?
Minha resposta (exemplo)
"Yes, I'm authorized to work in Canada under [PR / work permit / citizenship], so no sponsorship is needed." — ou, se precisar: "I currently hold a [visa type] and would need [sponsorship/support] to continue working long-term — happy to share more details."
"What's your availability / notice period?"
Qual seu período de aviso prévio / disponibilidade para começar?
Minha resposta (exemplo)
"I'd need to give two weeks' notice at my current job, so I could start around [date]."
"Tell me about a time you had a conflict with a coworker and how you handled it."
Conte sobre uma vez que teve um conflito com um colega e como lidou com isso.
Minha resposta (exemplo — use STAR)
"On a past project, a teammate and I disagreed about which library to use for a feature. I asked to set up a short call to understand their concerns, we compared trade-offs together, and ended up combining both ideas into a solution that worked for the deadline and the codebase."
"Where do you see yourself in five years?"
Onde você se vê daqui a cinco anos?
Minha resposta (exemplo)
"I'd like to keep growing technically, possibly moving into a more senior or specialized role, while continuing to work on products that have real impact for users."
"What are your strengths and weaknesses?"
Quais são seus pontos fortes e fracos?
Minha resposta (exemplo)
"One of my strengths is breaking down complex problems into smaller steps — it helps the whole team move faster. Something I'm working on is delegating more instead of trying to solve everything myself; I've started doing that by pairing with teammates on tasks I'd normally take on alone."
"How do you handle tight deadlines or pressure?"
Como você lida com prazos apertados ou pressão?
Minha resposta (exemplo)
"I try to break the work into priorities early and communicate blockers as soon as I see them, instead of waiting until the deadline is close. That way the team can adjust scope together if needed."
"Do you have any questions for us?"
Você tem alguma pergunta para nós?
Minha resposta (exemplo — sempre tenha perguntas!)
"Yes — what does success look like in this role after the first 90 days? And what's the team's current biggest challenge?"
Technical Recruiter / Hiring Manager Questions
Essas perguntas costumam vir de alguém de tech (dev sênior, tech lead, engineering manager). Eles avaliam profundidade técnica, forma de pensar e comunicação — nem sempre esperam a resposta "perfeita", mas sim o seu raciocínio.
"Walk me through your resume / your most recent project."
Me guie pelo seu currículo / seu projeto mais recente.
Minha resposta (exemplo)
"In my current role, I mainly work on [system/product]. My most recent project was [name], where I was responsible for [your part]. The biggest challenge was [X], and I solved it by [Y], which resulted in [measurable result if possible]."
"Tell me about a challenging technical problem you solved recently."
Conte sobre um problema técnico desafiador que você resolveu recentemente.
Minha resposta (exemplo)
"We had an issue where an API endpoint was timing out under load. I profiled the query, found it was doing a full table scan, added an index and introduced caching for repeated requests. Response time went from ~4s to under 300ms."
"Explain [a technical concept] as if I weren't technical."
Explique [um conceito técnico] como se eu não fosse da área técnica.
Minha resposta (exemplo — para "what is an API")
"An API is like a waiter in a restaurant — you (the app) tell the waiter (the API) what you want, the waiter takes your order to the kitchen (the server), and brings back your food (the data)."
"What's your experience with [our stack, e.g. React, Node.js, AWS]?"
Qual sua experiência com [a stack da empresa]?
Minha resposta (exemplo)
"I've worked with React for about [X years], building [type of apps]. I'm also comfortable with [related tools, e.g. Redux, TypeScript], and I've used AWS mainly for [Lambda / S3 / EC2, etc.] on past projects."
"How do you approach code review / giving feedback on someone's code?"
Como você aborda code review / dar feedback no código de alguém?
Minha resposta (exemplo)
"I focus on the code, not the person — I try to explain the 'why' behind a suggestion and ask questions instead of just pointing out issues. I also make sure to call out what's done well, not just what needs to change."
"Tell me about a time you disagreed with a technical decision made by your team or manager."
Conte sobre uma vez que discordou de uma decisão técnica do time ou do gestor.
Minha resposta (exemplo)
"My team wanted to use a new framework for a small feature. I raised concerns about the learning curve given our timeline, we discussed trade-offs, and agreed to prototype it first before committing. It turned out to be a good fit, so I was glad we tested it."
"What's the difference between [X] and [Y]?" — ex: REST vs GraphQL, SQL vs NoSQL, let vs const
Qual a diferença entre X e Y?
Minha resposta (exemplo — REST vs GraphQL)
"REST exposes fixed endpoints that return fixed data structures, so you sometimes over-fetch or under-fetch data. GraphQL lets the client ask for exactly the fields it needs in a single request, which is great for reducing over-fetching, but it adds complexity on the server side."
"How do you approach testing? What's your experience with unit/integration tests?"
Como você aborda testes? Qual sua experiência com testes unitários/integração?
Minha resposta (exemplo)
"I write unit tests for core business logic as I go, and rely on integration tests for critical user flows. I try to keep test coverage meaningful rather than chasing a percentage — I'd rather have fewer, high-value tests than lots of shallow ones."
"Describe how you'd design [a simple system]." (mini system design)
Descreva como você projetaria [um sistema simples].
Minha resposta (exemplo — estrutura de resposta)
"First I'd clarify requirements and scale — how many users, read vs write heavy. Then I'd sketch the main components: API layer, database, caching. I'd talk through trade-offs, like SQL vs NoSQL depending on data shape, and where I'd add caching or a queue if needed."
"How do you handle production incidents or urgent bugs?"
Como você lida com incidentes de produção ou bugs urgentes?
Minha resposta (exemplo)
"First I check logs and monitoring to understand impact and scope. I communicate status to the team early, even before I have a fix, and focus on mitigating impact first — like a rollback — before doing a deeper root-cause fix."
"How do you stay up to date with new technologies?"
Como você se mantém atualizado(a) com novas tecnologias?
Minha resposta (exemplo)
"I follow a few newsletters and blogs, and I like building small side projects to actually try new tools instead of just reading about them — it helps the knowledge stick."
"Do you have questions about the tech stack or engineering culture?"
Você tem perguntas sobre a stack técnica ou a cultura de engenharia?
Minha resposta (exemplo)
"How does the team handle code review and deployment — is it continuous deployment or scheduled releases? And how much autonomy does the team have in choosing tools?"
Expressões úteis para entrevistas (e para você usar também)
"I'm a quick learner / a fast learner."
Aprendo rápido.
"I'm a quick learner — I picked up Kubernetes on the job within a couple of months."
"I'm a team player."
Trabalho bem em equipe.
"I'm a team player — I enjoy pairing on hard problems."
"I like to wear many hats."
Gosto de acumular várias funções/responsabilidades.
"At a startup, I had to wear many hats — dev, QA, and support."
"I'd be able to hit the ground running."
Eu conseguiria começar produzindo rapidamente, sem muito período de adaptação.
"Since I've used this stack before, I'd be able to hit the ground running."
"Let's circle back to that."
Vamos retomar esse assunto depois.
"That's a great question — can we circle back to it after I finish this point?"
"I really appreciate your time today."
Agradeço muito seu tempo hoje. (ótimo para fechar a entrevista)
"Thank you so much, I really appreciate your time today and I'm looking forward to hearing back."
"Could you clarify what you mean by...?"
Pode esclarecer o que você quer dizer com...? (ótimo se não entender a pergunta)
"Could you clarify what you mean by 'scale' in this context — traffic or team size?"