I interviewed a Big Tech HR Director (let's call her Sarah). She's been in the industry for 12 years, reviewed over 100,000 resumes, and interviewed 3,000+ candidates.

What she says might make you uncomfortable. But it's all true.

Opening

Interview AiBox: Thank you, Sarah, for this interview. Can you start with your background?

Sarah: I've been an HR Director at a major tech company for 8 years. Before that, I led HR at two unicorn startups. I mainly hire for technical and product roles. Over the years, I've probably reviewed 100,000+ resumes and interviewed over 3,000 people.

Honestly, I've developed an instinct for reading resumes.

Q: How long do you spend on a resume?

Sarah: 6 seconds. Really, I only need 6 seconds.

Interview AiBox: 6 seconds? What can you possibly see in 6 seconds?

Sarah: You think I'm reading resumes? No, I'm scanning.

6 seconds is enough for me to scan:

Company names and job titles
Timeline gaps
The first 3 words of each bullet point
Whether there are any numbers

If those 6 seconds don't grab me, that resume goes in the trash. Doesn't matter how good the rest is.

Brutal? Yes. But HR processes hundreds of resumes daily. We don't have time to read novels.

Q: What makes you reject a resume instantly?

Sarah: When I see these words, my finger is already hovering over the "reject" button.

🚩 Red Flag #1: "Responsible for"

"Responsible for developing and maintaining XX system" "Responsible for team daily management"

Sarah: "Responsible for" is the most useless phrase. It tells me what you should do, not what you did.

Everyone in that role is "responsible for" these things. So what's your value?

Change it to:

"Led XX system rewrite, reducing response time from 800ms to 120ms" "Led a 5-person team to deliver Q3 goals 2 weeks ahead of schedule"

See the difference? One says "what I should do," the other says "what I changed."

🚩 Red Flag #2: "Participated in"

"Participated in core project development" "Participated in product iteration optimization"

Sarah: "Participated in" is even worse. It implies you were a spectator.

How much did you participate? 10 lines of code or 10,000? Were you a core contributor or just tagging along?

When HR sees "participated in," we default to: this person didn't make any substantial contribution.

Change it to:

"As a core developer, independently completed the payment module (35% of project codebase)" "Led homepage redesign, conversion rate increased 23% after launch"

🚩 Red Flag #3: "Familiar with"

"Familiar with Java, Python, Go, Rust..." "Familiar with microservices architecture"

Sarah: Tech stack stuffing is the biggest trap in technical resumes.

What does "familiar with" mean? You wrote Hello World? Or shipped production projects?

A resume listing 10+ tech stacks, all "familiar with," gets an instant reject. Either this person is lying, or they don't know what "expert" means.

Change it to:

"Expert in Java (5 years production experience), familiar with Python (for automation scripts)" "Built 3 microservices systems using Spring Cloud, serving 1M+ users"

Tech stacks need levels: Expert > Proficient > Familiar. Don't make everything "familiar."

🚩 Red Flag #4: "Assisted"

"Assisted supervisor with XX work" "Assisted team with requirements analysis"

Sarah: "Assisted" is the most humble-brag word in the workplace. It tells me: this person never had ownership.

Fresh grads using this word, I understand. But someone with 3+ years of experience still using "assisted"? That means you've never truly owned anything.

Change it to:

"Led requirements analysis process, produced 12 PRD documents, reduced development cycle by 30%" "Independently owned XX module, followed through from requirements to launch"

🚩 Red Flag #5: "Various" / "Multiple" / "Several"

"Participated in multiple projects" "Solved various technical challenges" "Received several awards"

Sarah: Vague words are resume poison.

"Multiple" - how many? 2 or 20? "Various" - what kind? Database connection issues or distributed system crashes? "Several" - what level? Participation award or national first prize?

When HR sees vague words, we default to: nothing worth showing off.

Change it to:

"Led 5 core projects, total codebase 80,000 lines" "Resolved Redis cluster split-brain issue, preventing potential loss of $5M/year" "Awarded 2024 Best Newcomer (only 3 recipients company-wide)"

Q: What do you like to see?

Sarah: When these words appear, my eyes light up.

✅ Green Flag #1: "Increased" / "Reduced" / "Shortened"

"Reduced system response time from 2s to 200ms" "Increased user retention by 15%" "Shortened deployment time from 2 hours to 15 minutes"

Sarah: This is what HR wants to see. Number + Direction + Result.

What did you change? By how much? That's value.

✅ Green Flag #2: "Led" / "Independently completed" / "Built from scratch"

"Led XX project, owned the entire process from initiation to launch" "Independently completed payment system rewrite" "Built data platform from scratch, supporting 300% business growth"

Sarah: These words show you're not a cog. You can handle things independently.

✅ Green Flag #3: "Saved" / "Generated"

"Saved $2M/year in server costs through architecture optimization" "Developed marketing tool, generated$ 5M in revenue"

Sarah: Executives love this. You helped the company save or make money.

✅ Green Flag #4: "Patent" / "Paper" / "Open source"

"Holds 2 patents" "Published paper at XX conference" "Open source project with 2000+ stars"

Sarah: These are hard currency. Can't be faked, high value.

✅ Green Flag #5: "Quantified"

"Grew team from 3 to 12 people" "System scaled from 100K to 1M users" "Code review coverage reached 95%"

Sarah: Anything that can be quantified, quantify it.

Q: Any special advice for technical resumes?

Sarah: Technical resumes have two unique traps.

Trap #1: Tech Stack Stuffing

Java, Python, Go, Rust, C++, JavaScript, TypeScript, React, Vue, Angular, Spring Boot, Django, Flask, Kubernetes, Docker, AWS, GCP, Azure...

Sarah: When I see this, I just want to ask: what do you actually know?

More tech stacks ≠ better. Listing 10+ technologies just makes people think you're not expert in anything.

Right approach:

Show levels: Expert (3-5 years production) / Proficient (1-2 years) / Familiar
Only list tech stacks relevant to the target role
Each tech stack should have a concrete project

Trap #2: Empty Project Descriptions

Project: XX E-commerce System Description: A B2C e-commerce platform where users can browse products and place orders.

Sarah: This isn't a project description, it's a product intro. HR doesn't care what the system does. We care about what you did.

Right approach:

Project: XX E-commerce System (50K DAU, $50M GMV/month)

My Role: Core Developer (Backend Lead)

Tech Stack: Java, Spring Boot, MySQL, Redis, RocketMQ

Key Contributions:

Led order system rewrite, improved order success rate from 92% to 99.5%

Designed distributed lock solution, resolved overselling issue, prevented $2M/month loss

Optimized database queries, reduced core API response time from 500ms to 80ms

Led 3-person team, delivered Q3 promotional event on time

Q: One piece of advice for job seekers?

Sarah: Don't write what you did. Write what you changed.

Most people write resumes like work logs:

I did A
I did B
I did C

HR doesn't care what you did. We care:

What result did A bring?
What did B change?
Where's the value in C?

A resume isn't a task list. It's an achievement list.

Real Resume Makeover Case

Before

Work Experience

Tech Company | Backend Engineer | Jun 2021 - Present

Responsible for core business system development

Participated in technical design for multiple projects

Assisted team in solving various technical issues

Familiar with Java, Spring, MySQL, Redis, etc.

Sarah's Review:

"Responsible for" - didn't say what was done
"Participated" - implies spectator
"Multiple" - vague word
"Assisted" - no ownership
"Various" - vague word
"Familiar with" - tech stack stuffing

This resume goes in the trash within 6 seconds.

After

Work Experience

Tech Company | Backend Engineer (Core Member) | Jun 2021 - Present

Key Achievements:

Led order system rewrite, improved order success rate from 92% to 99.5%, generating $8M/year in revenue

Designed distributed lock solution, resolved overselling in flash sales, preventing $2M/month loss

Optimized core API performance, reduced response time from 500ms to 80ms, user complaints down 60%

Led 3-person team for Q3 promotional event, zero system downtime

Tech Stack:

Expert: Java (4 years production), Spring Boot, MySQL

Proficient: Redis, RocketMQ, Docker

Familiar: Kubernetes, Elasticsearch

Sarah's Review:

Every line has numbers
Every line has results
Tech stack clearly leveled
Strong sense of ownership

This resume gets an interview invite.

FAQ

Q: Do I really need numbers on my resume?

Sarah: If you can, write them. Numbers are the most powerful evidence.

If you say "improved system performance," HR will ask: by how much? If you say "improved by 50%," HR will think: this person is reliable, data-driven.

If you truly don't have numbers, at least be specific: