Resume Teardown #30: Junior PM with 9 Years of EdTech Domain but Only 2 Years of Actual PM Work
This is part of our Resume Teardown series where we score real PM resumes (anonymized) and break down what the evaluation found.
TL;DR: A Product Manager with 2 years of formal PM experience and 9+ years of EdTech domain expertise scored 67%. The resume has genuine product ownership (MVP launch, user engagement metrics, marketplace operations) and deep EdTech domain knowledge. But the boundary between "PM work" and "operations/delivery work" is unclear across most roles, several metrics lack causal context, and the sheer volume of bullets drowns the strongest signals.
The Resume
Background: Business Head (Product Lead) at an early-stage EdTech SaaS startup building a personalized learning platform (Oct 2024 - Nov 2025). Recently completed a PM certification from a top Indian business school (Oct 2025 - Feb 2026). Previously a freelance product and growth consultant (Mar - Sep 2024). Before that, Product Operations at a healthcare SaaS marketplace in Canada (May 2023 - Feb 2024). AVP of Marketplace Operations at an enterprise LXP platform (May - Dec 2022). Head of Delivery at an EdTech publisher (Aug 2020 - Apr 2022). AVP of Academics at an online education company (Sep 2018 - Aug 2020). Chief Admissions Counselor at a major EdTech platform (Apr 2016 - Sep 2018).
What looked good on the surface: ISB Product Management certification. MVP launch with 30% engagement increase. 100K+ learner impact. $2M+ revenue generated. 73% CSAT and NPS of 48. Multiple named brand partnerships (Microsoft, Cisco, AWS, Google Cloud). 20-member team leadership.
Score: 67%
The Core Strength: Deep EdTech Domain
This resume has something most junior PM resumes lack: genuine industry expertise built over nearly a decade. The candidate has worked across the full EdTech value chain:
- Content marketplace operations (managing 55 content partners)
- Executive education delivery (25 cohorts, 1,400+ professionals)
- Academic program development (partnerships with top institutes)
- Platform engagement (100K+ learners, DAU metrics)
- Enrollment and conversion funnels ($2M+ revenue)
A hiring manager at an EdTech company would immediately see domain fit. This is the resume's biggest asset and should be positioned more prominently.
The Core Problem: Where Does Operations End and PM Begin?
Most roles on this resume have ambiguous PM ownership. Take the strongest-sounding role:
"Business Head (Product Lead) | SaaS EdTech Startup"
The bullets under this role mix genuine PM work with business operations:
- "Defined product vision and prioritized 10+ MVP features" → PM work
- "Drove 65% increase in qualified lead generation by building data-driven marketing strategies" → Growth/Marketing work
- "Built an investor pipeline of 15 potential funding sources" → Founder/BD work
A hiring manager cannot tell: were you the PM who defined the product, or the business head who did everything including some product work? At an early-stage startup, the answer might be "both," but the resume needs to make the PM contributions unmistakable.
The MVP Launch Bullet: Good but Needs Sharper PM Signal
"Launched the ClassTym web application by leading a 6-member cross-functional engineering & design team using Agile/Scrum, achieving a 30% increase in user engagement and student retention in the pilot launch."
This is a solid PM bullet. It names the product, the team composition, the methodology, and the outcome. But "leading a 6-member team using Agile/Scrum" reads more like project management than product management.
The PM signal would be clearer with: What features did you prioritize for the MVP? What did you cut? What user research informed the backlog? The 30% engagement increase is good, but what product decision caused it?
Before: "Launched the ClassTym web application by leading a 6-member cross-functional engineering & design team using Agile/Scrum, achieving a 30% increase in user engagement."
After: "Prioritized 10 MVP features from a 40+ feature backlog based on research with 300+ prospective users. Launched in 6 weeks with a 6-person eng/design team. Pilot showed 30% increase in engagement and measurable retention improvement."
The Operations Roles: Valuable but Overrepresented
The Wiley, Amity, and upGrad roles (2016-2022) contain strong operational metrics:
- "Generated ₹12Cr+ in revenue by developing curriculum"
- "Drove 30% YoY enrollment growth by leading a 20-member academic team"
- "$2M in total revenue with 750+ program enrollments"
These are impressive numbers. But they describe delivery leadership, sales management, and academic operations, not product management. A PM hiring manager scanning quickly will categorize these as "operations background" and move on.
The fix is not to remove these roles. It is to condense them to 1-2 bullets each and explicitly connect them to PM-transferable skills:
- The curriculum development at Wiley → "Identified market demand for Analytics/AI programs through enrollment data. Defined program requirements, worked with academic partners to build content. Programs generated ₹12Cr+ in revenue."
- The enrollment growth at Amity → "Led platform adoption strategy for 15+ professional programs, growing enrollments 30% YoY through partnership positioning and student success initiatives."
The Metric Inflation Problem
Several bullets combine multiple metrics in ways that obscure causation:
"Increased customer satisfaction scores by 40% and reduced churn by 20% by building customer service operations from scratch establishing scalable frameworks that supported 200% business growth during the beta phase."
Four metrics in one bullet (40% CSAT, 20% churn reduction, "from scratch," 200% business growth). A hiring manager cannot tell which of these you directly caused versus which happened because the company was in beta and everything was growing. The "200% business growth" feels particularly overclaimed for a Product Operations hire during a beta phase.
Pick the metric you most directly owned. If you built customer service from scratch, the CSAT and churn numbers are yours. The 200% business growth is company context, not your achievement.
Dimension Scores
Domain Expertise: 82% The highest dimension. Deep EdTech and SaaS exposure with marketplace compliance, settlement workflows, platform engagement, and regulatory frameworks. Real expertise built over many years, not just exposure.
Experience & Background: 68% Clear recent PM experience at an early-stage startup plus PM-adjacent roles. Logical progression from delivery to operations to product. But the transition is recent and concentrated in one startup, limiting breadth of PM evidence.
Leadership & Impact: 65% End-to-end MVP ownership and quantified outcomes across multiple roles. But many metrics lack causal clarity, and the line between "team-level" and "individual" contribution is blurry.
Skills & Tools: 63% Wide range of PM tools and methodologies listed. Recent ISB certification shows active upskilling. But several bullets focus on operational process (QA, bug tracking, frameworks) without connecting to product/feature impact. Some skills (analytics, AI tools) are listed but not demonstrated.
ATS Readiness: 91%
Excellent. All standard headers present, acronyms expanded, no formatting issues, PM keywords distributed throughout both skills and experience sections. This is one of the better ATS-optimized resumes in our teardown series.
The 4 Changes That Would Move This Score
1. Lead with PM decisions, not operational outcomes.
The ClassTym role should be entirely reframed around product decisions: what you prioritized, what you cut from the MVP, what user research revealed, how you defined success metrics. The 30% engagement increase matters less than what product decision drove it.
2. Condense pre-PM roles to 1-2 bullets each.
The Wiley, Amity, and upGrad roles currently take up half the resume. Compress each to one high-impact bullet that connects to PM skills. Use the recovered space for richer ClassTym bullets showing product craft.
3. Remove metric stacking from individual bullets.
One outcome per bullet. "Built customer service operations from scratch, improving CSAT by 40% and reducing churn by 20% within 6 months" is stronger than cramming four metrics together. Let each bullet make one clear claim.
4. Explicitly position the ISB certification as recent PM training, not just another line item.
The ISB PM program is a strong signal. Integrate it into the narrative: "Recently completed ISB's intensive PM program covering product discovery, prioritization frameworks, and GTM strategy. Applied learnings directly to ClassTym's MVP launch and feature prioritization."
The Pattern
This resume represents a common "late starter" PM archetype: someone with deep industry expertise who recently moved into formal product work. The domain knowledge and operational metrics are genuine differentiators. Most junior PMs cannot claim 100K+ user impact or ₹12Cr+ revenue across EdTech programs.
The challenge is convincing a hiring manager that you are a PM who leverages domain expertise, not an operations leader who recently added "PM" to the title. The ClassTym experience is real PM work. Make it the center of the resume, not one section among many.
The path from 67% to 75%+:
- Make ClassTym's product decisions the headline story
- Condense older operational roles to free space for PM evidence
- Stop metric stacking and focus on causal clarity
- Connect domain expertise to product insight ("I understand EdTech users because I served 1,400+ professionals across 25 cohorts")
The raw material is stronger than most junior PM resumes. The packaging just needs to stop trying to claim 11 years of PM experience and instead tell a focused story: "Deep EdTech expert who recently transitioned to PM with real shipped product evidence."
Score your own resume to see how your PM resume performs across all four dimensions.