julianommartins

julianommartins / tech-interview-handbook

Public

Um guia honesto sobre entrevistas técnicas, system design e senioridade em engenharia de software, baseado em padrões observados ao longo de centenas de entrevistas reais.

79
5
100% credibility
Found May 19, 2026 at 82 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
AI Summary

This is a guide written in Portuguese by a software engineer who has conducted hundreds of technical interviews at companies that build large-scale systems. The guide shares patterns observed from the interviewer's perspective—what separates candidates who get hired from those who don't. It covers the typical interview structure at major tech companies, explains what each phase really evaluates, reveals common mistakes that cause technically skilled candidates to fail, and offers practical advice on how to prepare. The guide emphasizes that interviews test how you think and communicate, not how much you can memorize, and provides concrete examples of good and bad answers to common questions.

How It Works

1
😰 Nervous about your upcoming interview

You've got a technical interview at a big tech company next week, and every blog post makes it sound terrifying.

2
📖 You discover this guide

Someone shares a guide written by an experienced interviewer who has conducted hundreds of technical interviews.

3
💡 The first question is never Kubernetes

You learn that interviewers start with basics to check if you really understand what you claim to know.

4
🗺️ You see the interview map

The guide reveals the four phases: initial chat, technical questions, whiteboard discussion, and behavioral questions.

5
You learn what each phase really tests
☕
The initial chat

It's not small talk—it's about whether you'd be pleasant to work with daily.

💻
Technical questions

They come from YOUR resume—every technology you mention becomes fair game for follow-ups.

🎨
Whiteboard challenge

It's a conversation, not a test—asking questions and accepting suggestions matters more than perfection.

🎭
Behavioral questions

Saying 'I don't know' honestly is better than a confident bluff that gets caught.

6
✅ You prepare your real stories

You write down three projects where you made real decisions, with trade-offs you actually considered.

🎉 You walk in confident

You know what interviewers really want: someone who thinks clearly, admits limits honestly, and collaborates well.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 82 to 79 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is tech-interview-handbook?

This is a Brazilian Portuguese guide written by someone who has conducted hundreds of technical interviews, not just survived them. The author shares patterns observed from the other side of the table: what separates candidates who pass from those who fail, why the first question is never about Kubernetes, and how whiteboard challenges really work. It covers the full interview lifecycle from initial cultural fit chats through technical deep-dives, system design discussions, and behavioral traps that sink technically strong candidates. The content focuses on backend and cloud engineering roles at mid-to-senior levels, touching on distributed systems concepts like CAP theorem, concurrency versus parallelism, database indexing strategies, and scaling approaches.

Why is it gaining traction?

Most interview prep content comes from candidates sharing their experiences. This one flips the perspective, revealing what interviewers actually evaluate and why. The hook is the emphasis on thinking over memorization: the guide argues that most interviews test how you reason under ambiguity, not whether you can recite buzzwords. It includes concrete examples of real interview questions and what a strong answer looks like, with specific guidance on whiteboard dynamics, cache patterns, and SLI/SLO/SLA calculations.

Who should use this?

Backend engineers preparing for mid-to-senior roles at companies operating software at scale will find the most value here. It is particularly useful for developers who want to understand the interviewer's perspective and what behaviors consistently earn approvals versus rejections. Candidates who have failed technical rounds despite strong fundamentals will recognize the behavioral pitfalls described.

Verdict

The perspective is genuinely useful and hard to find elsewhere, but with 79 stars this is an early-stage personal project, not a polished resource. The 1.0% credibility score reflects that immaturity. Worth reading alongside established alternatives like Yangshun's Blind 75 or LeetCode patterns, but treat it as one perspective among many rather than definitive guidance.

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.