There’s a hidden ratio that separates candidates who get offers from those who get rejected. Most people get it completely backwards. Here’s how to fix it before your next interview.
The Moment I Knew Something Was Wrong
I need to tell you about the time I stopped a candidate mid-answer during a mock interview.
This was 2022. I was coaching a TPM candidate preparing for interviews at a major tech company. She had 8 years of experience. Strong technical background. Led multiple successful programs. On paper, she looked great.
We were doing a practice question: “Tell me about a time you delivered a complex project.”
She started: “We had this initiative to migrate our infrastructure to the cloud. We gathered requirements from stakeholders. We designed the architecture. We ran into some challenges with the timeline, but we adjusted and we delivered successfully. The team was really proud of what we accomplished.”
I stopped her.
“How many times did you say ‘we’ in that answer?” I asked.
She paused. “I don’t know. A few times?”
“Nine times,” I said. “How many times did you say ‘I’?”
Another pause. “Maybe three or four?”
“Two,” I said. “You said ‘I’ twice in a 90-second answer about a project YOU led.”
She looked confused. “But it was a team effort. I don’t want to sound like I’m taking all the credit.”
And that’s when I realized: This incredibly talented person was about to fail her interviews, and she had no idea why.
Here’s what I told her, and what I’m about to tell you:
There’s a ratio that separates candidates who get offers from candidates who get rejected. And most people get it backwards.
The ratio is 70-30. Seventy percent of your statements should be about what YOU did (“I designed,” “I led,” “I built”). Thirty percent should acknowledge the team (“with my team,” “the team delivered,” “we accomplished”).
Get this ratio right, and you sound like a leader who takes ownership while acknowledging others.
Get it wrong, and you sound like either a bystander (too much “we”) or an egomaniac (too much “I”).
Let me show you why this matters, and more importantly, how to get it right.
The Problem: The Scrum Master Trap
Before I explain the psychology behind the 70-30 ratio, let me tell you why so many smart, capable people get this wrong.
If you’ve worked in Agile environments, if you’ve been a Scrum Master or facilitative leader, if you come from cultures that emphasize collective achievement over individual recognition, you’ve been trained to say “we.”
“We delivered the sprint.”
“The team accomplished our goals.”
“We collaborated to solve the problem.”
This is good leadership language in your day-to-day work. It builds team cohesion. It acknowledges contributions. It’s humble.
But in an interview? It’s killing your chances.
Here’s why:
When you say “we delivered the project,” the interviewer hears: “Someone on this team delivered the project, and this person was present when it happened.”
When you say “the team solved the problem,” the interviewer hears: “A group of people solved a problem, and I’m not sure what this specific person contributed.”
I learned this the hard way during my own interviews early in my career. I’d come from team-oriented environments. I genuinely believed in collective achievement. I thought humility was a virtue in interviews.
I was wrong.
Not because humility isn’t valuable. But because in a 45-minute interview, the interviewer needs to understand what YOU specifically contributed. They’re not hiring your team. They’re hiring you.
And if you don’t clearly articulate your individual contribution, they’ll move on to the next candidate who does.
The Psychology Behind 70-30 (What Interviewers Are Actually Thinking)
Let me pull back the curtain on what’s happening in an interviewer’s mind when you’re telling your story.
I’ve conducted over 250 format interviews in the last few years of my career. And here’s what I’m thinking when a candidate is answering:
When you say “we”:
My brain asks: “Okay, but what did THIS person do? There are probably 5-10 people on that team. An engineer wrote the code. A PM defined requirements. A QA tested it. An engineering manager managed the people. What did the TPM candidate in front of me actually do?”
When you say “I”:
My brain logs: “Okay, this person designed the architecture. This person led stakeholder alignment. This person identified the risk. I’m getting specific data points about their capabilities.”
Here’s the reality: A team is made of multiple roles. In any project:
- Engineers write code
- Product managers define features
- QA tests quality
- Engineering managers develop people
- TPMs do… what exactly?
If you say “we delivered,” I don’t know if you were the critical path or just along for the ride.
If you say “I coordinated across three engineering teams to align on the technical approach, and the teams delivered 50% faster than our initial estimate,” now I know exactly what value you added.
Let me give you a real example from my own interviews.
When I was interviewing for my current role, I told a story about the store planning accuracy improvement project at my previous company. Here’s what I said:
“I led an engineering team of 6 people focused on improving accuracy for store deployments. We were seeing 50% of stores having issues during bring-up. I analyzed the root causes and discovered our annotation process was the bottleneck. I designed an automation solution that reduced manual effort by 80%. The team implemented it, and we reduced deployment issues from 50% to under 10% over 11 months. I also managed performance reviews and promoted two engineers during this period.”
Count the ratio:
- “I” statements: 5 (led, analyzed, discovered, designed, managed)
- “We” statements: 1 (we reduced)
- “The team” statements: 1 (team implemented)
That’s roughly 71% “I”, 29% “we/team”. Perfect 70-30.
The interviewer knew exactly what I did (analysis, design, people management) versus what the team did (implementation, collective results).
I got the offer.
How to Count Your Ratio (The Self-Audit)
Alright, let’s get practical. How do you actually measure your I vs We ratio?
Here’s the exercise I do with every candidate I coach:
Step 1: Record yourself
Answer a behavioral question out loud. Use your phone to record it. Pick something simple like “Tell me about a recent project you’re proud of.”
Step 2: Transcribe or listen carefully
Either write out what you said word-for-word, or listen to the recording with a notepad.
Step 3: Count
Go through and mark every instance of:
- “I” statements (I led, I built, I designed, I analyzed, I decided, I managed, etc.)
- “We” statements (we delivered, we accomplished, we decided, we built, etc.)
- “The team” statements (the team implemented, the team achieved, etc.)
Step 4: Calculate
Total “I” statements / (Total “I” + Total “we/team” statements) = Your ratio
Example from a real candidate I coached:
Their answer: “We had a challenge with our deployment pipeline. We were seeing failures about 30% of the time. We analyzed the logs and we found that the issue was in our build process. We redesigned the pipeline. I worked with the infrastructure team to implement it. We reduced failures to under 5%. The team was really happy with the improvement.”
Count:
- “We” statements: 7
- “I” statements: 1
- Ratio: 1 / 8 = 12.5% “I”, 87.5% “we”
That’s backwards. That’s a rejection waiting to happen.
Here’s what I helped them rewrite:
“I noticed our deployment pipeline was failing 30% of the time, which was blocking releases. I analyzed the logs and identified the root cause in our build process. I redesigned the pipeline architecture and worked with the infrastructure team to implement the changes. The team reduced failure rate to under 5%, which unblocked our release velocity.”
New count:
- “I” statements: 4 (noticed, analyzed, identified, redesigned)
- “We/team” statements: 2 (worked with, team reduced)
- Ratio: 4 / 6 = 67% “I”, 33% “we/team”
Much better. Now it’s clear what this person specifically contributed.
Before and After: Real Examples from Real Interviews
Let me show you some examples from my own career and from candidates I’ve coached. These are real answers that got real feedback.
Example 1: Store Planning Accuracy Project
BEFORE (Too much “we”):
“We had a problem with store deployments. About half of our stores were having issues during bring-up. We needed to improve this. We looked at the data and we found that annotation quality was the issue. We built automation to help with this. We reduced the issues significantly. The team worked really hard and we’re proud of what we accomplished.”
Count: 0 “I”, 9 “we”, 1 “team” = 0-100 ratio
What the interviewer hears: “A team did some work on store deployments. I was on that team. I’m not sure what this person specifically did.”
AFTER (Correct 70-30):
“I led a team of 6 engineers tackling a critical problem. 50% of our store deployments were failing. I analyzed the root cause and discovered our annotation process was the bottleneck. I designed an automation solution that reduced manual effort by 80%. The team implemented it over 6 months, and we reduced deployment failures from 50% to under 10%. I also promoted two engineers during this period by creating leadership opportunities for them.”
Count: 6 “I”, 2 “we/team” = 75-25 ratio
What the interviewer hears: “This person led the initiative, did the analysis, designed the solution, managed people development. The team executed. Clear division of contribution. This is a leader.”
Example 2: WiFi Business
BEFORE (Too much “we”):
“We started a WiFi management company for airports in India. We built a captive portal system. We had to deal with government compliance which was really complex. We managed to reduce our infrastructure costs significantly. We’re serving multiple airports now.”
Count: 0 “I”, 5 “we” = 0-100 ratio
AFTER (Correct 70-30):
“I co-founded a WiFi management company serving airports in India. I built the government-compliant captive portal system using open-source routing platforms. I navigated complex regulatory requirements by building relationships with government officials. I reduced our infrastructure costs from $1,200 per month to $50 per month by migrating to a more efficient architecture. We’re now managing 1,000+ routers across multiple airports.”
Count: 5 “I”, 1 “we” = 83-17 ratio
Example 3: Cross-Cloud Benchmarking
BEFORE (Too much “we”):
“We needed competitive intelligence on how our platform compared to others. We set up a benchmarking program. We worked with a vendor to run tests. We found some interesting performance differences. We shared the results with our go-to-market team.”
Count: 0 “I”, 5 “we” = 0-100 ratio
AFTER (Correct 70-30):
“I established a cross-cloud benchmarking program to generate competitive intelligence. I wrote the statement of work and managed the vendor relationship. I defined which benchmarks would matter most to our sales team by working backward from customer buying decisions. The team executed benchmarks across AI inference, scaling, and workload isolation. I discovered we had significant advantages in certain areas and gaps in others, which shaped our go-to-market messaging.”
Count: 5 “I”, 1 “team”, 1 “we” = 71-29 ratio
Example 4: Enterprise Platform Migration
BEFORE (Too much “we”):
“We had to migrate 4,000 sites to a new platform. We planned for 8 months but we ended up taking 11 months. We underestimated the complexity. We learned a lot about discovery and planning.”
Count: 0 “I”, 4 “we” = 0-100 ratio
AFTER (Correct 70-30):
“I planned and executed a migration of 4,000 enterprise sites. I estimated 8 months, but we ended up taking 11 months. I underestimated remediation complexity by about 2x. What I learned: I now always build 40% buffer for unknowns, I pilot with larger samples, and I escalate concerns on suspicion rather than certainty. I’ve applied these lessons to three subsequent migrations, all of which came in on schedule.”
Count: 7 “I”, 1 “we” = 88-12 ratio (slightly high, but acceptable for a failure story where you’re owning the mistakes)
When to Use “We” Strategically (The 30% That Matters)
Now, I don’t want you to think you should eliminate “we” entirely. That would make you sound like an egomaniac.
The 30% “we” statements serve specific purposes:
Use “We” for Final Delivery and Results
When talking about outcomes that truly were collective:
- “The team delivered all milestones on schedule.”
- “We achieved 99.9% uptime.”
- “Our solution handled 10 million requests per day.”
This acknowledges that delivery is a team sport.
Use “We” to Show Collaboration
When you worked WITH others (not directing them):
- “I worked with the security team to validate the approach.”
- “I collaborated with product management to prioritize features.”
- “I partnered with engineering leadership to allocate resources.”
Notice these still start with “I” but acknowledge the collaborative nature.
Use “We” for Team Celebrations
At the very end of your story, it’s fine to say:
- “The team was really proud of what we accomplished.”
- “We celebrated this as a major milestone.”
This shows you’re not a solo operator. You value team success.
Example of Strategic “We” Usage
Here’s how I structure answers:
Opening (100% “I”): “I identified a problem…”
Middle (70% “I”, 30% “we”): “I designed the solution. I worked with three engineering teams to align on approach. The teams implemented over 6 months…”
Closing (50-50): “We reduced deployment time by 40%. I learned that process redesign often matters more than technical optimization. The team was energized by this success.”
This feels natural, acknowledges collaboration, but makes my specific contribution crystal clear.
Company-Specific Guidance
Different companies have slightly different cultures around this, though 70-30 is a safe baseline everywhere.
Major E-Commerce Company
Very ownership-driven culture. They want to hear individual accountability.
Lean toward 75-25 or even 80-20 for ownership questions.
When they ask “Tell me about a time you took ownership,” they want to hear about times you made decisions without waiting for permission. Heavy “I” usage is expected.
Example: “I approved the architecture change without my manager’s approval because the team was blocked. I validated the technical approach with our lead engineer first and documented my rationale. I informed my manager immediately afterward.”
Top Cloud Platform Provider
Collaborative culture, but they still want individual contribution clarity.
70-30 is perfect here.
They appreciate seeing both individual initiative AND team collaboration.
Example: “I led the benchmarking program design. I worked closely with product management to define success criteria. The team executed benchmarks across multiple dimensions. I synthesized findings and presented to leadership.”
Startups and Scale-Ups
Often more forgiving of “we” language, but still need to see individual impact.
65-35 is probably fine.
They care more about scrappiness and getting things done than perfect attribution.
But still, don’t hide your contribution behind “we.”
The Practice Framework (How to Fix Your Ratio)
If you’ve done the self-audit and discovered you’re at 30-70 or 40-60 instead of 70-30, here’s how to fix it:
Step 1: Write Out 5 STAR Stories
Pick 5 projects from your Project Matrix. Write out the full STAR answer for each one.
Step 2: Circle Every “We”
Go through with a pen and circle every instance of “we” or “the team.”
Step 3: Ask “Can I Replace This?”
For each circled “we,” ask:
Did I personally do this action?
- If YES: Change to “I”
- If NO: Keep as “we” or “the team”
Step 4: Rewrite
Transform your answers. Here’s the pattern:
Old: “We analyzed the problem…”
Old: “We designed the solution…”
Old: “We reduced costs by 40%…”
New: “I analyzed the problem…”
New: “I designed the solution…”
New: “I reduced costs by 40% by redesigning the architecture. The team implemented the changes…”
Step 5: Read Out Loud
After rewriting, read your answers out loud. They should sound natural, not robotic or egotistical.
If it feels awkward, you might be at 90-10 or 95-5. That’s too high. Balance it back to 70-30.
Step 6: Practice with Someone
Record yourself answering questions. Have someone count your ratio. Iterate until you consistently hit 65-75% “I” statements.
Common Objections (And My Responses)
Let me address the concerns people raise when I teach this:
“But it WAS a team effort. I don’t want to lie.”
You’re not lying. You’re being specific about your contribution vs the team’s contribution.
Saying “I designed the architecture” doesn’t deny that engineers implemented it. It clarifies what YOU did.
Saying “we designed the architecture” makes it unclear whether you led the design or just attended meetings about it.
“I come from a culture that values humility. This feels arrogant.”
I understand. Many cultures, including mine, emphasize collective achievement over individual recognition.
But here’s the thing: An interview is a specific context where you need to clearly articulate your value. It’s not arrogance. It’s clarity.
Think of it this way: If you don’t advocate for yourself in an interview, who will?
“What if I really didn’t do much on the project?”
Then don’t use that project in interviews. Pick different stories where you had clear, significant impact.
The Project Matrix helps with this. You should have 6-8 projects where you genuinely drove outcomes. Use those.
“Won’t this make me sound like I’m not a team player?”
No, because you’re using the 30% “we” statements to show collaboration.
“I designed the solution and worked with three engineering teams to implement it” shows both individual contribution AND collaboration.
That’s better than “we designed and implemented a solution,” which shows neither clearly.
The Self-Diagnostic Question
Here’s a simple test to see if your ratio is right:
After you finish answering an interview question, ask yourself:
“If I were the interviewer, would I know exactly what I did on this project versus what the team did?”
- If the answer is “yes, it’s crystal clear,” you probably have good I vs We balance.
- If the answer is “hmm, it might be unclear,” you probably used too much “we.”
- If the answer is “yes, but it sounds like I did everything myself,” you probably used too much “I.”
The right balance feels like: “This person clearly led this initiative, made key decisions, and delivered results through a team.”
A Personal Reflection
I’m going to be honest with you about something.
For years, I struggled with this balance. Coming from India, from team-oriented work cultures, from Agile environments that emphasize collective achievement, I’d been conditioned to say “we.”
Early in my career, I’d finish interviews feeling good. I’d told great stories. I’d shown humility. I’d acknowledged my team.
And I’d get rejected.
It took me probably 5-6 years to figure out why. Nobody told me. I had to discover it by sitting on the other side of the interview table.
When I started interviewing candidates myself, I’d hear them say “we” constantly. And I’d think: “I have no idea what this person actually did.”
And then I’d realize: That’s what interviewers were thinking about me all those years.
The day I consciously shifted to 70-30 was the day my interview success rate changed completely.
I went from maybe 30% offer rate to probably 70-80% offer rate.
Same experience. Same projects. Same capabilities.
Just clearer communication of my specific value.
That’s what the I vs We ratio gives you. Not a different story. Just clarity about the story you already have.
Your Action Item
Here’s what I want you to do right now:
- Pick one project from your career
- Answer this question out loud: “Tell me about this project”
- Record yourself
- Count your I vs We ratio
- If you’re below 60% “I,” rewrite and try again
Do this for 5 different projects. Get consistent at hitting 65-75% “I” statements.
This single change, this one ratio adjustment, can be the difference between getting offers and getting rejected.
Not because you’re a better candidate. But because you’re communicating your value more clearly.
And in interviews, clarity is everything.