Resume Teardown #7: B.Tech Student with PM Internships and Strong Volume Claims

This is part of our Resume Teardown series where we score real PM resumes (anonymized) and break down what the evaluation found. New teardown every day.

TL;DR: This B.Tech student scored 72% with two PM internships and three portfolio projects. The evaluation detected the student tier and scored appropriately: skills-heavy weights (60%), generous domain scoring, and credit for extracurricular leadership. The main gaps: volume claims without depth ("40+ features") and projected metrics from case studies treated as hypothetical, not measured.

The Resume

Background: B.Tech in AI and Machine Learning (graduating May 2026). Two PM internships: Associate Product Management Intern at a VoIP company (4 months) and Product Lead Intern at a SaaS startup (5 months). Three portfolio projects including a product strategy case study for a legacy brand, a B2B SaaS dashboard, and an AI-powered platform.

What looked good on the surface: End-to-end ownership claims, 40+ feature enhancements, 50+ Jira tickets prioritized, 15+ Figma screens, 300+ LLM prompts designed, a 12-month RICE-prioritized roadmap, and a leadership section with a 30-member team and a Guinness World Record project.

Score: 72%

Strong for a student resume. The evaluation used student-calibrated scoring (weights: Leadership 15%, Experience 15%, Domain 10%, Skills 60%) which is appropriate for someone without full-time PM experience.

Tier Detection: student_undergrad

The evaluation correctly identified this as a student resume based on:

• Degree end date in 2026 (current year)
• Only internship experience (no full-time PM roles)
• PM internships during college do not make someone PM-experienced

This means the scoring expectations are calibrated for a student: ownership within internship scope is credited, extracurricular leadership counts, and the skills dimension carries the most weight.

Leadership & Impact: 61%

What worked:

The resume shows genuine end-to-end ownership. "Owned end-to-end delivery of 3+ modules in a real-time VoIP product; translated ambiguous problems into PRDs, user flows, and execution-ready Jira tickets." For a 4-month intern, owning modules and translating ambiguity into execution is a strong leadership signal.

The extracurricular leadership also counted: leading a 30-member team (GOONJ) and coordinating a district-level Guinness World Record project. For students, this IS their primary leadership evidence.

What held it back:

1. Volume claims without depth. "Implemented 40+ feature enhancements (keypad, conference calling, quick reply, edit/forward, screenshot alerts, video calling, privacy controls); prioritized 50+ Jira tickets using user behavior insights."

This bullet tries to impress with volume but sacrifices depth. A hiring manager reads this and thinks: what was the hardest one? What was the outcome? Did users adopt these features? 40 features in 4 months is roughly 2.5 per week, which suggests these were small enhancements, not substantial product decisions.

Better approach: Pick the 2-3 highest-impact features and tell the story. "Identified that users were dropping calls during handoff, designed conference calling feature with engineering, shipped to 10K users within 3 weeks" is one feature but tells a complete story.

2. No measured business outcomes. Every bullet describes what was done, not what changed. "Eliminated critical system failures" and "resolved high-impact UX/state issues" describe activity. What happened to call reliability metrics? What happened to user drop-off rates? Even directional outcomes ("improving data accuracy" without a number) are weaker than specific measurements.

For a student, this is not a dealbreaker (the evaluation does not expect company-level business outcomes from interns), but it is the difference between 61% and 75%+ in Leadership.

Experience & Background: 66%

What worked:

• Two internships at different companies (VoIP product company + SaaS startup) shows initiative in seeking PM-relevant work
• Both internships involved real product ownership, not just shadowing
• Cross-functional exposure: engineering, design, QA, stakeholders

What held it back:

• Both internships are short (4-5 months each) with no full-time experience
• No evidence of PM coursework or structured learning programs
• The second internship (Product Lead Intern) has a title that overpromises relative to the scope described

For a student, this is solid. The evaluation does not penalize short tenure for internships.

Domain Expertise: 71%

This scored generously (by design for students). The resume shows exposure to:

• VoIP/real-time communication products
• Multi-tenant SaaS platforms
• E-commerce (Hawkins Cookers case study)
• AI/LLM-powered products

For a student, any domain exposure through internships or substantive projects counts. The evaluation does not expect deep vertical expertise.

Skills & Tools: 78%

This was the strongest dimension (and carries 60% weight for students). The resume demonstrates:

• PM tools: Jira, Confluence, Figma, Miro, Notion
• Analytics: SQL, Google Analytics 4, Mixpanel, funnel analysis, A/B testing
• Technical: API basics, system design, Git, HTML/CSS, Java, prompt engineering, LLM workflows
• Research: UX research, user personas, wireframing, usability testing, user journey mapping

The skills are not just listed but demonstrated through the internship and project bullets. Jira appears in the context of "prioritized 50+ Jira tickets." Figma appears as "designed 15+ Figma screens." LLM prompts appear as "designed 300+ LLM prompts."

The gap: skills demonstrated through projects (not production environments) carry slightly less weight. But for a student, this is the expected evidence level.

Case Studies: Credited for Thinking, Not for Numbers

The Hawkins Cookers project claims "targeting 8-12% add-to-cart improvement and 12-18% checkout drop-off reduction." The evaluation correctly noted these are projected outcomes, not measured results. The project was scored on the quality of the analytical approach (UX audit, competitive benchmarking, 7+ user research conversations, RICE-prioritized roadmap) rather than the hypothetical metrics.

This is an important distinction for students: your case studies demonstrate PM thinking (problem framing, research methodology, prioritization frameworks). Frame them that way. "Conducted UX audit and competitive benchmarking to identify 4 structural conversion barriers" is stronger than "targeting 8-12% improvement" because the first is something you actually did, and the second is a guess.

ATS Readiness: 84%

The resume is well-formatted. Standard headers, contact info present, consistent dates, good PM keyword coverage. Minor issues: some acronyms not spelled out on first use (VoIP, PRDs, RICE).

Key Takeaways for Students

1. Depth over volume. "40+ features" sounds impressive but tells no story. Pick your best 2-3 and give each the full treatment: what was the problem, what did you do, what changed. One well-told feature story is worth more than a list of 40.

2. Projected metrics are not outcomes. Case study numbers ("targeting 8-12% improvement") are hypotheses, not achievements. Lead with what you actually did: the research, the analysis, the framework. That is your real evidence.

3. Extracurriculars count (for now). Leading a 30-member team and coordinating a large-scale project is valid leadership evidence for students. But this has a shelf life. Once you have 1-2 years of work experience, extracurriculars should shrink or disappear from your resume.

4. Your skills section is your strongest asset. At the student level, demonstrated tool proficiency and PM methodology knowledge carry the most weight. Make sure every skill listed is backed by at least one bullet somewhere in your experience or projects.

5. Position as a PM thinker, not as a student. The header says "Product Manager" which is aspirational positioning (acceptable for job search). But the summary could do more to anchor around PM thinking: what you have learned about users, problems, and systems, rather than listing your degree or internship titles.

The Pattern

This resume represents the strongest version of a student PM resume: real internship ownership, diverse projects, extensive skills, and extracurricular leadership. The 72% score reflects that it is genuinely strong for the tier. The path from 72% to 80%+ is not about adding more experience (that comes with time) but about reframing what is already there: depth over volume, outcomes over activity, and PM thinking over academic framing.