Resume Teardown #16: CS Graduate with Analytics Apprenticeship Targeting PM Roles

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 recent Computer Science graduate with a 6-month fintech apprenticeship and a 3-month developer internship scored 69%. The resume has genuine PM-adjacent signals (analytics tools, KPI tracking, cross-functional collaboration) but relies heavily on support verbs, lacks quantified outcomes, and provides no company context for unfamiliar employers.

The Resume

Background: BE in Computer Science Engineering (Honours) from a private engineering college in South India (CGPA 8.12, graduated 2025). Two roles: Apprentice at a retail stock brokerage platform (6 months) and Developer Intern at a software development company (3 months). Two academic projects: a task management web app and an accessibility-focused communication tool.

What looked good on the surface: Analytics tool proficiency (Google Analytics, CleverTap, AppsFlyer), KPI tracking, cross-functional collaboration with product/engineering/marketing teams, API testing with Postman, AWS deployment monitoring, Agile execution.

Score: 69%

Tier Detection: transition_1_to_5yr_adjacent

The evaluation classified this resume as a career transitioner with product-adjacent experience at software companies. The roles (Apprentice at a fintech, Developer Intern at a software company) are not PM titles, but the work is at tech companies with product-adjacent responsibilities. This triggers weights of Leadership 20%, Experience 25%, Domain 10%, Skills 45%.

This classification is appropriate. The resume shows someone who has worked alongside product teams and used PM-adjacent tools, but has not held a PM title or owned product decisions independently.

Leadership & Impact: 60%

What worked:

The apprenticeship role shows genuine analytics ownership: "Analyzed user behavior using Google Analytics, CleverTap, and AppsFlyer to identify drop-offs and improve product performance across key user funnels." This demonstrates a real PM-adjacent activity (funnel analysis) using specific tools. The evaluation credited this as evidence of data-driven product support.

Cross-functional collaboration with product, engineering, and marketing teams is also a valid signal at this level. For someone in an apprenticeship, working across teams shows initiative beyond a siloed role.

What held it back:

1. Support verbs dominate. "Analyzed," "Supported," "Assisted," "Collaborated" appear throughout. These signal peripheral involvement, not ownership. A hiring manager reads "Supported product decision-making by tracking KPIs" and thinks: you helped someone else make decisions. Did you ever make one yourself?

2. No quantified outcomes anywhere. Every bullet describes activity without results. "Improved product performance" without a number. "Improved user retention" without a metric. "Improving task visibility and usability" without evidence. The resume tells us what was done but never what changed as a result.

For a transition candidate, the evaluation does not expect PM-specific metrics (adoption, conversion, retention numbers). But it does expect some evidence that the work had an effect. Even directional outcomes ("reducing onboarding drop-off" or "increasing feature adoption among new users") would strengthen these bullets.

3. The developer internship bullets are generic. "Collaborated with cross-functional teams to implement real-time communication features, enhancing user engagement and team efficiency." This could describe any developer at any company. No specific feature named, no specific outcome, no evidence of product thinking.

Experience & Background: 65%

What worked:

• Two roles at software/fintech companies (product-adjacent environment)
• Exposure to analytics, deployment, and cross-functional workflows
• Recent graduation with relevant CS degree

What held it back:

• Total work experience is under 1 year (6 months + 3 months)
• No career progression to show (both are entry-level roles)
• The "Developer Intern" title and bullets read as engineering, not product-adjacent
• No evidence of PM-specific learning (courses, certifications, structured programs)

The evaluation does not penalize short tenure for early-career candidates. But with only 9 months of total experience, the resume needs to maximize every bullet. Generic descriptions waste valuable space.

Domain Expertise: 75%

This scored generously because the evaluation is lenient on domain for transition candidates. The resume shows:

• Fintech/brokerage exposure through the apprenticeship (user funnels, onboarding, retention)
• Task management/collaboration tools through the developer internship
• Accessibility/healthcare through the academic project

For a transition candidate, any domain exposure counts. The fintech apprenticeship provides the strongest domain signal because the bullets reference specific fintech activities (user funnels, onboarding flows, retention metrics).

Skills & Tools: 70%

This dimension carries 45% of the total weight and scored reasonably well.

What worked:

The skills section is comprehensive and relevant: Git, Notion, Jira, Salesforce, PostgreSQL, AWS, Postman, Excel, Google Workspace, Figma. Plus PM-specific skills: Product Lifecycle, Agile & Scrum, Product Metrics (Conversion, Retention, Engagement), Funnel Analysis, KPI Tracking, User Behavior Analysis, A/B Testing, Google Analytics, CleverTap, AppsFlyer.

Several of these skills are demonstrated in the experience bullets (Google Analytics, CleverTap, AppsFlyer, Postman, AWS, Agile). This is important: skills listed AND demonstrated carry more weight than a bare skills list.

What held it back:

• A/B Testing is listed as "Conceptual Understanding" which the evaluation noted as honest but weak. Conceptual understanding of A/B testing is not the same as having run experiments.
• Product Lifecycle is listed as "Basic Understanding." Again, honest but signals early learning rather than applied knowledge.
• Many skills (Salesforce, PostgreSQL) have zero supporting evidence in the bullets. They are listed but never demonstrated.

ATS Readiness: 81%

The resume is well-formatted with standard headers and consistent dates. PM keyword coverage is decent: KPI, retention, engagement, Agile, user behavior, funnel analysis all appear. Missing keywords that would strengthen ATS performance: roadmap, prioritization, product strategy, go-to-market, MVP, stakeholder.

The main ATS gap: no company descriptions. "Fyers Securities Pvt. Ltd" and "Zidio Developments Pvt. Ltd" are not household names. A hiring manager at a global company has no context for what these companies do, their scale, or their product type. One line of context under each company name would fix this immediately.

The 5 Changes That Would Move This Score

1. Add company descriptions.

Before: "Apprentice — Fyers Securities Pvt. Ltd"

After: "Apprentice — Fyers Securities Pvt. Ltd (retail stock brokerage platform serving 1M+ users across India)"

This takes 5 seconds and immediately gives a hiring manager context about your product environment.

2. Replace one support verb per role with an ownership verb (where honest).

The apprenticeship bullet "Supported product decision-making by tracking KPIs, validating analytics data, and ensuring accuracy of user insights for feature improvements" could become: "Tracked KPIs across onboarding and retention funnels, validating analytics data that informed the prioritization of a new onboarding feature."

Same work. But "tracked KPIs that informed prioritization" shows closer proximity to product decisions than "supported product decision-making."

Important: only upgrade verbs where the bullet context supports it. "Assisted in defining product workflows" should stay as "Assisted" if you genuinely assisted rather than owned. Honest framing is more credible than overclaiming.

3. Add one outcome to the strongest bullet.

The analytics bullet is the strongest on the resume. If there was any measurable result from identifying those drop-offs (even directional: "leading to a redesign of the onboarding flow" or "informing the team's Q4 priority decisions"), add it. If there was no measurable outcome, restructure to show what action was taken: "Identified key drop-off points in the onboarding funnel, presenting findings to the product team and informing the redesign of 3 onboarding screens."

4. Rewrite the summary to position for PM.

Current: "Aspiring Product Analyst / Associate Product Manager with experience in analytics, experimentation, and cross-functional product execution."

This is decent but could be stronger. Anchor around what you have learned about users and products:

"Product-focused analyst with hands-on experience identifying user drop-offs, tracking product KPIs, and supporting data-driven feature decisions at a fintech platform. Seeking an Associate Product Manager role to own the full problem-to-outcome cycle."

5. Add PM keywords to project descriptions.

The academic projects are described in generic terms ("Designed user workflows," "Focused on user experience"). Reframe using PM language: "Identified user pain points in task assignment workflows through usability testing, prioritizing 3 improvements that reduced friction in team collaboration."

The Pattern

This resume represents a common early-career transition pattern: genuine PM-adjacent work described in passive, support-oriented language. The experience is real and relevant. The framing undersells it.

The path from 69% to 78%+ does not require new experience. It requires:

• Company context (so hiring managers know your environment)
• One ownership verb upgrade per role (where honest)
• One quantified or directional outcome per role
• PM keyword density in projects and summary

These are all quick wins that can be done in 30 minutes. The Fix with AI feature can help with phrasing improvements, but adding real outcomes and company context requires the candidate's own knowledge.