Free lesson · The Job Search System
The 6-Second Review: What Interviewers Actually See First
The 6-Second Review: What Interviewers Actually See First
Student: Brandon, Swati keeps referencing the "6-second review." You've reviewed over 300 resumes at Amazon. What does that actually look like from your side of the desk?
Brandon: Let me be completely honest with you about how resume review works, because I think candidates have a very generous picture of what happens. They imagine a hiring manager sitting in a quiet office, carefully reading every line of their resume, weighing each bullet point, forming a considered opinion over several minutes.
That is not what happens.
What happens is this: I have 25 resumes on my desk. I have 30 minutes before my next meeting. I haven't eaten lunch. I have a production issue simmering that my team is handling but I need to check on. And I need to get through this stack so my recruiter can schedule phone screens before the end of the week.
So I pick up the first resume and my eyes do something very specific. It takes 6 seconds. And in those 6 seconds, a decision is made - not final, but directional. Either "this looks promising, I'll keep reading" or "this doesn't match, next."
Student: What do your eyes actually do in those 6 seconds?
Brandon: Same thing every time. I've done this enough that it's automatic.
The Eye Path
graph TD
A["👁️ SECOND 1-2<br/>Top-left: Name and Current Title<br/>'Who is this person?'"] --> B["👁️ SECOND 2-3<br/>Current Company<br/>'Where do they work?'"]
B --> C["👁️ SECOND 3-4<br/>First Bullet of Current Role<br/>'What do they actually do?'"]
C --> D["👁️ SECOND 4-5<br/>Skills Section (quick scan)<br/>'Do they work with what I need?'"]
D --> E["👁️ SECOND 5-6<br/>Overall Visual Impression<br/>'Is this resume clean and organized?'"]
E --> F{"Decision"}
F -->|"Keep Reading"| G["Full Review<br/>1-2 minutes"]
F -->|"Move On"| H["Next Resume"]
style A fill:#7950f2,color:#fff
style C fill:#51cf66,color:#fff
style F fill:#ff6b6b,color:#fff
This diagram shows the eye path during a 6-second resume review. In seconds 1 to 2, the reviewer looks at the top-left for the name and current title, asking who is this person. In seconds 2 to 3, they check the current company. In seconds 3 to 4, they read the first bullet point of the current role to understand what the candidate actually does. In seconds 4 to 5, they quick-scan the skills section to check technology match. In seconds 5 to 6, they form an overall visual impression of whether the resume is clean and organized. Then a decision is made: keep reading for a full 1 to 2 minute review, or move on to the next resume.
Let me break down each moment.
Seconds 1-2: Name and current title. My eyes go to the top-left corner. I read the name - it registers as a person, not a file. Then I look for the current job title. "Senior Software Engineer" tells me something. "Full Stack Developer" tells me something different. "Software Engineer II at Google" tells me a lot - that's a calibrated level at a known company. Right there, in the first two seconds, I have a rough calibration of this candidate's seniority.
Seconds 2-3: Current company. Where are they working now? This isn't about prestige snobbery - it's about context. If someone is at Amazon and I'm hiring for Amazon, that's an internal transfer and a different process. If someone is at a no-name startup I've never heard of, it doesn't mean they're bad - it means I need the bullets to tell me more. If someone is at Google, Stripe, or Netflix, I have an immediate credibility signal because I know those companies have high hiring bars.
Student: That sounds like bias toward big companies.
Brandon: It is bias, and I'll be honest about it. Unconscious pattern matching happens. But here's the thing - the company name only buys you seconds 3 and 4. If your first bullet is weak, the company name doesn't save you. And if your company is unknown but your first bullet says "Designed the payment processing pipeline handling $2B in annual transactions with 99.99% uptime," I am absolutely going to keep reading. The bullet can override the company. The company just gets you a longer look.
Seconds 3-4: The first bullet. This is the most important 8 seconds of real estate on your entire resume. The first bullet point of your most recent role is where I decide if you're worth a deeper look. If that bullet is activity-based - "Worked on backend services using Java and Spring Boot" - it tells me nothing. What did you build? What was the scale? What was the impact? I don't know, and I don't have time to figure it out.
If that bullet is impact-based - "Architected a cross-region replication system reducing data recovery time from 4 hours to 12 minutes across 3 AWS regions" - now I'm interested. That tells me the domain (distributed systems), the scale (cross-region), the impact (a 20x improvement), and the technical environment (AWS). In one sentence.
Important: Your first bullet is your opening statement in court. It either grabs attention or loses the case. Treat it as the single most important sentence on your resume. Write it last, after you've written everything else, so you can choose the strongest thing to lead with.
Seconds 4-5: Skills scan. I glance at the skills section - usually toward the bottom of the resume. I'm looking for a quick match against my mental checklist. If I need someone who knows Kubernetes, Java, and distributed systems, I'm scanning for those words. If they're there, it confirms the impression from the bullets. If they're not there, it creates doubt.
Seconds 5-6: Visual impression. This sounds superficial, and it is. But in 6 seconds, I also absorb the overall visual quality of the resume. Is it clean and well-structured, with clear section headers and consistent formatting? Or is it dense, cramped, with inconsistent fonts and no white space? A clean resume signals attention to detail. A messy resume signals carelessness. Is that fair? Maybe not. Is it real? Absolutely.
Student: And after 6 seconds, you've made a decision?
Brandon: A directional decision. I've put the resume in one of three mental buckets:
Bucket 1: Read further. Strong first impression - right calibration, strong first bullet, relevant skills, clean format. I'll spend 1 to 2 minutes reading the full resume. Maybe 20 to 30% of resumes make it here.
Bucket 2: Maybe. Mixed signals - something is interesting but something else is concerning. I might have a question. I'll give it another 15 to 30 seconds to see if the rest answers my question. About 30% land here.
Bucket 3: Pass. Weak first impression - wrong level, weak bullets, formatting issues, no technology match. I move to the next resume. About 40 to 50% land here within 6 seconds.
Student: Half the resumes are done in 6 seconds?
Brandon: Yes. And I want to be clear - these are resumes that already passed the recruiter screen and the ATS. The ones that reach my desk are already the top 20 to 30 out of the original 300. And I'm still filtering half of them in 6 seconds. That's how competitive the pipeline is.
What Makes Me Keep Reading
Student: So what specifically makes you go from "6-second glance" to "I'm spending 2 minutes on this"?
Brandon: Three things, consistently.
Numbers. Show me scale. Show me impact. Show me before-and-after. "Reduced API latency from 450ms to 80ms" - I'm reading. "Improved API performance" - I'm not. Numbers are trust signals. They tell me you measured your work. They tell me you think about outcomes, not just activities. An engineer who measures outcomes is an engineer I want on my team.
Specificity. Vague descriptions kill resumes. "Worked on various microservices" tells me nothing. "Owned the authentication service handling 12M daily logins across 3 platforms" tells me everything. The specificity tells me you understood your domain, you knew the scope of your work, and you can articulate it clearly - which is exactly what I need you to do in an interview.
Relevance. If I'm hiring for a distributed systems role and your first three bullets are about React frontends, you might be a great engineer but you're not the right fit for this role. The resume that makes me keep reading is the one where I can see a clear match between what you've done and what I need done.
stateDiagram-v2
[*] --> Glance: Resume arrives
Glance --> KeepReading: Numbers present<br/>Specific impact<br/>Relevant domain
Glance --> Maybe: Some signals but mixed
Glance --> Pass: Vague bullets<br/>Wrong level<br/>Formatting issues
KeepReading --> Shortlist: Strong throughout
KeepReading --> Maybe: Falls off after first bullet
Maybe --> KeepReading: Deeper reading reveals strength
Maybe --> Pass: Deeper reading confirms doubt
Shortlist --> PhoneScreen
note right of Glance: 6 seconds
note right of KeepReading: 1-2 minutes
note right of Maybe: 15-30 seconds
This state diagram shows the three mental buckets during resume review. The initial glance takes 6 seconds. Resumes with numbers, specific impact, and relevant domain move to the Keep Reading bucket for 1 to 2 minutes. Resumes with mixed signals go to the Maybe bucket for 15 to 30 seconds. Resumes with vague bullets, wrong level, or formatting issues go directly to Pass. From Keep Reading, strong resumes move to Shortlist and then Phone Screen. From Maybe, deeper reading can move a resume up to Keep Reading or down to Pass.
The Formatting Factor
Student: You mentioned visual impression. How much does formatting actually matter?
Brandon: More than most engineers want to admit. Let me give you a concrete example.
I recently reviewed two resumes for the same role. Both candidates had similar experience - about 6 years, distributed systems background, AWS heavy. Technically comparable. But one resume used a clean, single-column layout with clear section headers, consistent bullet formatting, and appropriate white space. The other used a two-column design with a sidebar, custom icons for skills, a progress bar showing "Python: 85%," and three different font sizes.
Which one do you think I spent more time reading?
Student: The clean one.
Brandon: The clean one. And here's why - the two-column design forced my eyes to jump between the left sidebar and the right content area. The progress bars made me roll my eyes ("85% Python" - what does that even mean? Compared to whom? Measured how?"). The icons for skills looked nice but when I tried to quickly scan for "Kubernetes," I had to decode which icon represented it. Everything that was supposed to make the resume "stand out" actually made it harder to read.
Good formatting is invisible. It doesn't draw attention to itself. It lets the content do the work.
Tip: Brandon's Resume Formatting Rules:
- Single column. Always. No sidebars, no two-column layouts.
- One font family. Use one professional font in two sizes - larger for your name and section headers, smaller for body text. That's it.
- Consistent bullet style. Every bullet should start the same way - with an action verb. Same indentation, same spacing.
- White space is your friend. If your resume looks dense and cramped, you're trying to fit too much. Cut content. Don't shrink fonts.
- No graphics, icons, or progress bars. They don't add information and they confuse ATS parsers.
- PDF format. Submit as PDF to preserve formatting. But generate the PDF from a text-based tool (Google Docs, Word, LaTeX), not from a design tool (Canva, Figma).
The First Bullet Test
Here's an exercise I give to every candidate I coach. Take your resume right now. Cover everything except the first bullet of your most recent role. Read it out loud. Does it answer these three questions?
- What did you build or accomplish?
- How big was it? (scale, users, transactions, data volume)
- What was the measurable result?
If it answers all three, your first bullet is doing its job. If it misses any of them, rewrite it before you send another application.
Student: My current first bullet says "Developed and maintained microservices for the payments team using Java and Spring Boot." That answers... none of them, really. It tells you what I did but not what I accomplished.
Brandon: Right. And here's how I'd rewrite that based on what you just told me about your work:
Before: "Developed and maintained microservices for the payments team using Java and Spring Boot."
After: "Designed and shipped 3 payment processing microservices handling 15K transactions per minute, reducing payment failures by 23% and processing latency by 40%."
Same work. Same person. Completely different signal. The first version tells me you wrote code. The second version tells me you solved a problem, at meaningful scale, with measurable results.
Warning: The Activity vs. Impact Trap: Most engineers default to describing activities (what they did all day) rather than impacts (what changed because of their work). Activities are inputs. Impacts are outputs. Hiring managers care about outputs.
"Developed APIs" → Activity "Designed REST APIs serving 2M daily requests, reducing client integration time from 3 weeks to 4 days" → Impact
Every bullet on your resume should be an impact statement. We'll build this skill in depth in the next topic.
What Kills a Resume in 6 Seconds
Let me give you the honest list of instant-pass triggers - things that make me skip a resume before I finish scanning it.
Objective statement instead of summary. "Objective: To obtain a challenging position that leverages my skills in software engineering." I've moved on before I finish reading it. This tells me nothing about you.
Wall of text with no bullets. If your experience section is written in paragraph form with no bullet points, I can't scan it in 6 seconds and I won't try.
Irrelevant emphasis. Leading with a certification or coursework that's not relevant to the role. If I'm hiring a backend engineer and the first thing I see is "Certified Scrum Master," we're not aligned.
Typos in the first third. A typo anywhere is bad. A typo in the first few lines - the only lines I'm guaranteed to read - is devastating. It signals carelessness in the one document where you should be most careful.
Student: This is humbling. I think my resume triggers at least two of these.
Brandon: That's why we're here. And the good news is that every one of these is fixable. The next topic - writing impact-driven bullets - gives you the formula for turning every line on your resume into a signal that makes hiring managers keep reading.
Interview: How the 6-Second Review Connects to Your Interview
Here's something most candidates don't realize: the resume sets the interview's agenda. When I go into an interview with a candidate, I've read their resume. The bullets I found most interesting become my follow-up questions. "I see you reduced payment failures by 23% - walk me through how you diagnosed the root cause and what your approach was."
That means every bullet on your resume is a potential interview question. When you write a bullet, ask yourself: "If an interviewer asks me to elaborate on this for 10 minutes, can I? Do I have a detailed story with context, actions, and results?" If the answer is no, either rewrite the bullet to reflect something you CAN elaborate on, or prepare the story now. AlgoInsight's Behavioral Interview Mastery course teaches exactly how to build these stories.
Exercise: Starter: Open your resume. Read only the first bullet point of your most recent role. Does it contain: (a) a specific accomplishment, (b) a metric or scale indicator, (c) a measurable result? If it fails any of these, rewrite it right now.
Intermediate: Show your resume to someone for exactly 6 seconds - use a timer. Then take it away and ask them: "What do I do? What's my strongest skill? Would you want to interview me?" Their answers reveal what your resume actually communicates in the window that matters.
Advanced: Collect 3 job descriptions for roles you'd want. For each one, evaluate your resume's first 6-second impression against that specific role. Does your current title align? Does your first bullet resonate? Do your skills match? If the answer is "no" for any of them, that's evidence you need to tailor - which we'll cover in Topic 07.
Student: I need to rewrite my first bullet immediately. Actually, I need to rewrite most of my bullets. They're all activity-based.
Brandon: That's exactly what we're covering next. Swati is going to teach you the XYZ formula for writing impact-driven bullets that pass both the 6-second test and the interview follow-up test. Once you learn this formula, you'll never write a weak bullet again.
Let's go.