Role & Expectations
"What would make you say this hire was successful after 3 months?"
Puts you in results language from the start. Signals you care about impact, not task completion.
"What does onboarding look like — first 30 to 90 days?"
Reveals what success looks like early on, and whether there's a structured ramp-up or a "figure it out yourself" culture.
"What are the top priorities for this role in the first 6 months?"
Exposes the real job vs. the job description. Great signal for whether the team has a clear vision for this hire.
Team & Collaboration
"How does the team balance synchronous meetings and async communication?"
Reveals how remote-first they actually are vs. how they claim to be. Critical for understanding your daily rhythm.
🌍 Intl
"What's the typical overlap window for someone working in UTC-3?"
Direct and professional. Much better than hoping timezone is never a problem. Signals global-team maturity.
🇧🇷 BR
"O modelo é full remote de verdade ou existe pressão informal para ir ao escritório? Como o time lida com isso na prática?"
A palavra "na prática" força uma resposta honesta. Empresas que dizem remote-first mas cobram presença revelam cultura de desconfiança.
"How are technical decisions documented — ADRs, RFCs, wikis? Or does most knowledge live in people's heads?"
Mature teams write decisions down. Teams that don't are fragile — onboarding and debugging both suffer.
"How is the engineering team structured, and who would I work with most closely?"
Shows you're thinking about actual collaboration. Good for understanding reporting lines and day-to-day dynamics.
Engineering Quality
"How does the code review process work here?"
Clean and direct. Separates companies with engineering discipline from "push and hope" shops.
"What does engineering quality look like day to day — testing, ownership, release process?"
One question covering multiple quality signals at once. Use when time is short.
"What parts of the codebase are engineers most excited — or most challenged — by right now?"
Gets honest answers. Tells you the real state of the code, not the recruiting pitch.
"When there's a production incident, what does the response look like — on-call, postmortem, runbooks?"
Senior-level signal. Reveals operational maturity. Teams without postmortems repeat the same failures indefinitely.
"How do you handle observability and production monitoring? Which tools matter most for debugging reliability issues?"
Shows you think beyond the feature and care about what happens after deploy.
Product & Business
"What's the balance between feature development and technical debt? Does engineering have a voice in that prioritization?"
Reveals if engineering has real influence or just executes backlog. "Product always wins" = sustained technical suffering.
"What are the biggest technical or product challenges the company is facing right now — not the most glamorous, the most real?"
"Not the most glamorous" disarms the pitch reflex. A specific answer means the manager is connected to the team's reality.
"How does this role contribute to the company's current priorities?"
Shows business awareness. Helps you understand if the role is strategic or peripheral.
Culture
"What trait of the company culture tends to surprise new people joining — something that wouldn't be on the careers page?"
Bypasses the rehearsed HR answer. Specific responses signal authenticity; vague ones signal disconnection from the actual team.
"How does the team handle technical disagreements? If I disagree with an architecture decision, is there a structured way to push back?"
Psychologically safe teams have conflict resolution processes. Dysfunctional hierarchies have "the senior said so, it's decided."
Growth & Career
"How do senior engineers grow here — is there a staff or principal track, or is management the only path?"
Companies with only management tracks don't value technical excellence. Tells you how much code you'll still be writing in 3 years.
"How is performance evaluated? Are the criteria for promotion clear and documented, or more implicit?"
Opaque promotion criteria favor visibility and politics over delivery. Good companies have a documented engineering level rubric.
"Does the company support learning through budget, time, or internal knowledge-sharing?"
Formal budget signals the company sees skill development as an investment. "Depends on the manager" means it doesn't exist in practice.
Logistics (Final Round Only)
🌍 Intl
"Is this role structured as a full-time contractor engagement or employment? Has that model been stable for international team members?"
Legitimate and professional. Relevant for Deel/EOR/PJ contracts. Ask in final round only — never with HR in the first screen.
🇧🇷 BR
"A contratação é CLT ou PJ? Como isso foi definido para o time de engenharia?"
Legítimo e direto. CLT vs PJ impacta muito a equação real de remuneração. Só perguntar em final round — nunca na triagem com RH.