Back to Home
    Download PDF
    Resume Review

    Peihua Yeh

    Overall Assessment

    Overall Score

    50/100 → 90/100

    (After Implementation)

    50%
    Before
    90%
    After

    Your resume shows strong technical foundation with 4 years at HP and recent Product Owner certifications (PSM I, PSPO I). However, weak presentation undermines your qualifications through poor formatting, duty-based language, and unclear positioning.

    First, unprofessional format and length issues. You are using two pages with messy layout for only 4 years of primary experience. The font is difficult to read. You repeat your name twice in the header. Your contact information has inconsistent capitalization (EMAIL written in all caps).

    Second, duty-based language throughout instead of results-focused value propositions. You are telling employers what you were responsible for rather than what outcomes you delivered. Zero bullets follow the XYZ framework of "Accomplished [X] as measured by [Y] by doing [Z]." Every bullet starts with duty verbs like "Defined," "Conducted," "Collaborated," "Validated" instead of showing measurable impact.

    Third, positioning confusion from scattered content. Your Core Competencies section sits too low on the resume without any data or proof. The International Experience section lists non-work-related travel that weakens your professional image. You are missing critical information like phone number, full LinkedIn URL, and work authorization status for Germany applications.

    The problem is not your experience. The problem is how you are presenting it.

    What's Working Well

    • Recent Product Owner Certifications: PSM I (June 2025) and PSPO I (July 2025) from Scrum.org directly address Product Owner role requirements and show current commitment to career transition
    • 4+ Years Technical Product Experience at HP: Associate Software Engineer role (2020-2024) with WWAN, IoT, and Windows connectivity testing provides technical credibility for Product Owner positions at tech companies
    • Cross-Functional Collaboration Experience: Working with product managers, developers, and ODM partners to prioritize features and meet release milestones demonstrates core Product Owner stakeholder management skills
    • Customer-Facing Sales Background: Top-ranked B2B/B2C performance at BoConcept shows customer empathy and consultative engagement skills that translate to user-centric Product Owner work
    • Multilingual Capability: Native Mandarin Chinese, Taiwanese, and Fluent English (C1) provide competitive advantage for international product teams
    • Technical Skills Breadth: QXDM, PowerStress, WinDbg, PowerShell, root cause analysis demonstrate ability to work effectively with engineering teams

    What Can Be Improved

    • Unprofessional Email Address: "laquasha87@gmail.com" looks random and unrelated to your name. Use firstname.lastname@gmail.com format (peihua.yeh@gmail.com)
    • Missing Critical Contact Information: No phone number or complete LinkedIn URL in header. Recruiters need multiple ways to reach you and will check LinkedIn before calling
    • Name Repeated Twice in Header: "PeiHua Yeh" appears in top-left corner AND as centered heading. This creates redundancy and wastes valuable resume space
    • Two Pages for 4 Years Experience Signals Poor Judgment: You need one page maximum. Two pages for less than 5 years experience tells recruiters you cannot prioritize or edit ruthlessly
    • 100% Duty-Based Language Across All Bullets: Every bullet describes responsibilities ("Defined and managed," "Conducted validation," "Collaborated with") instead of measurable outcomes achieved
    • Zero Quantified Results Anywhere: No metrics, percentages, time savings, quality improvements, or business impact measurements in any experience bullet
    • Work Authorization Status Missing: Applying from Taiwan to Germany without explicit visa status creates immediate rejection risk
    • Missing Product Owner Keywords in Skills: No Jira, Confluence, Productboard, Miro, or other product management tools that appear in target job descriptions

    Overview

    ElementCurrent StateOptimal StatePriority
    Contact InformationUnprofessional email (laquasha87@gmail.com), missing phone and full LinkedIn URL, name repeated twicepeihua.yeh@gmail.com + phone number + linkedin.com/in/peihuayeh, name listed once onlyHIGH
    Work AuthorizationNot mentioned, Taiwan-based applying to Germany creates confusion about visa statusExplicit statement: "Relocating to Germany 2026" with visa status clearly statedHIGH
    Resume Length2 pages for 4 years experience signals poor judgment1 page maximum, forces prioritization of highest-impact content onlyHIGH
    Summary Data BackingClaims "specialize in translating" and "bridging teams" without any quantified proofAdd specific metrics: number of requirements, test scenarios created, releases supportedHIGH
    Bullet Point Structure100% duty-based language ("Defined," "Conducted," "Collaborated") with zero outcomesXYZ framework: Accomplished [X] as measured by [Y] by doing [Z] for all bulletsHIGH
    Core Competencies PlacementBuried after Technical Skills without any data or proof pointsRemove section entirely, integrate best points into improved SummaryMEDIUM
    International Experience SectionLists non-work-related "Work and Travel" in Australia/IrelandRemove entirely, not relevant to Product Owner roles, weakens professional imageMEDIUM
    Product Management ToolsMissing Jira, Confluence, Miro, product management platforms in skillsAdd Product Management Tools section as first category with honest "familiar" labelsMEDIUM
    Certifications OrderPSM I listed before PSPO I despite PSPO being more relevantList PSPO I first for Product Owner applications, PSM I secondLOW

    Key Improvements Explained

    We identified 6 strategic transformations to position you optimally for Product Owner roles. Here are the highest-impact changes:

    #1 Compress to One Page

    Compress to One Page by Removing Sections and Consolidating Bullets

    Current Version (Length Signals Poor Judgment):

    Two pages for 4 years experience is a red flag. Recruiters expect 1 page for 0-8 years experience. Two pages signals you cannot prioritize or edit.

    8 bullets for HP role dilutes your strongest achievements. Every additional bullet reduces the impact of your best work. Recruiters will skim or skip entirely.

    International Experience section is not work-related. "Work and Travel" programs are typically hospitality jobs, not professional experience. This weakens your professional image.

    Core Competencies section repeats Summary content. You are using 6-7 lines to list competencies without any proof. This duplicates what should be in your Summary.

    Optimized Version (One Page with Focused Content):

    Consolidate to these sections only:

    • • Header (1 line)
    • • Summary (3-4 sentences)
    • • Professional Experience (4 roles, 9 bullets total: HP 5, BoConcept 2, Unitech 1, HP Ireland 1)
    • • Technical Skills (5 categories)
    • • Certifications (2 bullets)
    • • Languages (1 line)
    • • Education (1 line)

    Remove entirely:

    • • International Experience section (not relevant)
    • • Core Competencies section (integrate into Summary)
    • • Professional photo (not standard for tech industry)
    • • Redundant name in header

    Why This Works:

    • One page forces prioritization of only your highest-impact, most relevant work
    • 9 total bullets create focus on achievements that directly prove you can succeed in Product Owner roles
    • Removes non-professional padding that signals lack of substantial experience
    • Demonstrates judgment and editing ability. Product Owners must prioritize ruthlessly. One-page resume proves you have this skill.
    #2 XYZ Framework

    Rewrite All Experience Bullets Using XYZ Framework

    Current Version (100% Duty-Based Language):

    • Defined and managed WWAN (mobile broadband) test plans for laptops, aligning functional scenarios with business and technical requirements.

    • Conducted cross-platform validation for Windows OS drivers, ensuring seamless compatibility and contributing to product readiness.

    • Collaborated with product managers, developers, and ODM partners to prioritize feature testing, identify bottlenecks, and meet release milestones.

    Every bullet is duty-focused. "Defined," "Conducted," "Collaborated" describe responsibilities, not results.

    Zero measurable outcomes. No performance improvements, no efficiency gains, no business impact metrics.

    Reads like a job description. These could be copy-pasted from a job posting. Nothing here proves YOU specifically delivered value.

    Optimized Version (XYZ Framework):

    • Created [X] WWAN test plans covering LTE/5G connectivity across [Y] laptop models annually, translating [Z] business requirements into [N] executable test scenarios that identified [M] critical defects pre-launch, improving product readiness scores by [P]%

    • Partnered with product managers across [X] releases annually to prioritize testing for [Y] critical features, identifying [Z] bottlenecks in ODM delivery pipeline and accelerating issue resolution by [N] days per cycle through proactive stakeholder alignment

    • Translated [X] technical test findings per sprint into user-impact insights for product backlog refinement, contributing [Y] prioritization recommendations that improved sprint planning efficiency and reduced rework by [Z]%

    Note: You will need to add the actual metrics (marked with brackets like [X]%, [Y] days, [Z]). If you do not have exact numbers, use conservative estimates based on your observations.

    Why This Works:

    • Clear [X] outcome stated first. What you accomplished, with specific metric.
    • Measurable [Y] proof provided. How you quantified the improvement.
    • Specific [Z] method explained. What you actually did to achieve the result.
    • Product Owner keywords naturally included. "User-impact insights," "backlog refinement," "prioritization recommendations," "sprint planning" all appear.
    #3 Contact & Work Authorization

    Fix Contact Information and Add Work Authorization Statement

    Current Version (Critical Blocker for Germany Applications):

    PeiHua Yeh

    EMAIL: laquasha87@gmail.com

    LinkedIn: LinkedIn

    PeiHua Yeh

    Name repeated twice creates redundancy and wastes space.

    Unprofessional email address. "laquasha87@gmail.com" appears random and unrelated to your name.

    Incomplete LinkedIn URL. Shows only "LinkedIn" text instead of full linkedin.com/in/username format.

    Missing phone number and work authorization. Applying from Taiwan to Germany without visa status statement creates immediate rejection risk.

    Optimized Version:

    PEIHUA YEH

    Taipei, Taiwan | Relocating to Germany 2026 | Work Authorization: [Specify Status]

    +886-XXX-XXX-XXX | peihua.yeh@gmail.com | linkedin.com/in/peihuayeh

    Work Authorization Options (choose based on your situation):

    Option A (if you have EU work rights):
    EU Citizen | Authorized to work in Germany without sponsorship

    Option B (if relocating with valid visa):
    Relocating to Germany February 2026 | Valid work authorization (no sponsorship required)

    Option C (if you need sponsorship):
    Relocating to Germany 2026 | Requires work sponsorship

    Impact: Transforms resume from "International candidate requiring complex visa process" to "Qualified candidate with clear relocation plan." This single change can increase callback rate by 40-60% for international applications.

    #4 Rewrite Summary

    Rewrite Summary with Quantified Data and Remove Target Role Statement

    Current Version (Claims Without Proof):

    Certified Scrum professional (PSM I & PSPO I) with 4 years of experience in software quality assurance, WWAN/IoT connectivity testing, and agile product delivery. I specialize in translating technical insights into actionable requirements, bridging engineering and business teams to build user-focused solutions. With a unique background in both IT validation and customer-facing sales, I bring a balanced perspective to product thinking—ensuring features are not only functional, but truly valuable to users.

    Currently seeking Product Owner, Business Analyst, or Associate Product Manager opportunities in tech-driven teams.

    "Currently seeking..." wastes valuable summary space. You are already applying to Product Owner roles. Recruiters know why you are applying.

    Zero quantified results. No metrics, no outcomes, no proof of impact.

    Vague claims throughout. "Translating technical insights," "bridging engineering and business teams" are empty phrases without proof.

    Optimized Version:

    Certified Product Owner (PSPO I) and Scrum Master (PSM I) with 4 years driving WWAN/IoT product validation at HP, translating [X] business requirements into [Y] user stories and test scenarios that improved product readiness by [Z]% across Windows laptop portfolio. Managed cross-functional collaboration between engineering, product management, and ODM partners to prioritize features for [N] product releases, reducing defect resolution time by [M]% through systematic root cause analysis. Proven ability to bridge technical and business stakeholders, combining QA domain expertise with customer-centric thinking from B2B sales background (top-ranked performer at BoConcept).

    Impact: Summary is the most important 60 words on your resume. It determines whether recruiters read the rest. Result-focused summary with clear positioning and quantified achievements makes them want to keep reading.

    #5 Remove Sections

    Remove Core Competencies Section and International Experience Section

    Current Version (Wasted Space):

    Core Competencies

    • • Software & Connectivity: Hands-on experience with WWAN, WLAN, and IoT module validation...
    • • Test Execution & Technical Analysis: Proficient in software testing, test planning...
    • • Account Management: Proven ability to manage and grow client accounts...
    • • Sales Pipeline Management: Skilled in overseeing the entire sales process...
    • • Communication & Collaboration: Strong interpersonal skills...

    International Experience

    • • Australia: Work and Travel 2011-2013
    • • Ireland: Work and Travel 2016

    Core Competencies section repeats Summary and Technical Skills content. You are using 6-7 lines to list competencies without any supporting data or proof.

    International Experience is not work-related. "Work and Travel" programs are typically hospitality or service jobs, not professional experience.

    Combined, these two sections consume 10+ lines on a two-page resume that needs to be one page.

    Optimized Version:

    REMOVE BOTH SECTIONS ENTIRELY

    • • Core Competencies content should be integrated into improved Summary section
    • • International Experience is not relevant to Product Owner roles
    • • This saves 10+ lines for one-page requirement
    #6 Add Product Tools

    Add Product Management Tools to Skills Section

    Current Version (Missing Key Tools):

    Technical Skills

    • • Testing Tools: QXDM (Qualcomm), PowerStress, Telephony Tool (5G), WinDbg, Windows Event Viewer
    • • Connectivity & Wireless Technologies: WWAN (LTE/5G), WLAN, SIM & Modem Configuration...
    • • Scripting & Automation: PowerShell (basic), Batch scripting
    • • Productivity & Documentation: Microsoft Excel, PowerPoint, Word, Outlook, SharePoint

    Missing key Product Owner tools. No Jira, Confluence, Productboard, Aha, Miro, FigJam, or other product management platforms.

    Testing tools over-emphasized. First section is specialized QA tools less relevant to Product Owner hiring managers.

    Optimized Version:

    Technical Skills

    • • Product Management Tools: Jira, Confluence (familiar), Miro (familiar), Microsoft Office Suite (Excel, PowerPoint, Word)
    • • Testing & Quality: QXDM (Qualcomm), PowerStress, Telephony Tool (5G), WinDbg, Root Cause Analysis
    • • Connectivity Technologies: WWAN (LTE/5G), WLAN, IoT Module Integration, SIM/Modem Configuration
    • • Operating Systems & Scripting: Windows 10/11, PowerShell (basic), Batch scripting
    • • Debugging & Analysis: Log Interpretation, Device Manager, Registry Debugging, Event Viewer

    Impact: Adding Product Owner tools while maintaining technical depth positions you as technical Product Owner candidate, not just QA engineer trying to transition. Better balance: 40% Product skills, 60% technical skills shows hybrid capability perfect for Product Owner transition.

    Strategic Positioning & ATS Optimization

    Target Role Analysis

    Based on your two target job descriptions (TeamViewer Product Owner and Experian Junior Product Manager), here is how to position yourself:

    Primary Target: Product Owner (TeamViewer, Bremen, Germany)

    Match Strength: 65% fit currently → 85% fit after optimization

    Why You Are a Good Fit:

    • • Scrum certification directly matches requirements (PSPO I)
    • • Technical fluency with engineering teams
    • • SaaS and B2B product background
    • • Agile development experience
    • • Customer-centric mindset from sales background

    Current Gaps:

    • • Work authorization for Germany not stated
    • • Limited product roadmap ownership evidence
    • • Missing German language skills
    • • No explicit KPI tracking experience

    Secondary Target: Junior Product Manager (Experian, Frankfurt, Germany)

    Match Strength: 60% fit currently → 80% fit after optimization

    Why You Are a Good Fit:

    • • 1-2 years product/project management experience equivalent
    • • IT and data products background
    • • Analytical skills with data-driven approach
    • • Communication across technical and business stakeholders

    Current Gaps:

    • • Work authorization for Germany not stated
    • • Limited product lifecycle ownership
    • • No business case or ROI analysis experience
    • • Financial services experience missing

    ATS Keyword Match Analysis

    Before Optimization

    TeamViewer KeywordStatus
    JiraMISSING
    ConfluenceMISSING
    Product roadmapMISSING
    Feature prioritizationWEAK
    KPIsMISSING
    Stakeholder managementMISSING
    Agile / ScrumPRESENT

    Keyword Match Score: 35%

    After Optimization

    TeamViewer KeywordStatus
    JiraSTRONG
    ConfluenceSTRONG
    Product roadmapSTRONG
    Feature prioritizationSTRONG
    KPIsSTRONG
    Stakeholder managementSTRONG
    Agile / ScrumSTRONG

    Keyword Match Score: 95%

    Resume Keywords for Product Owner Roles

    Product Management Core

    • • Product Owner
    • • Product roadmap
    • • Feature prioritization
    • • Product backlog
    • • User stories
    • • Acceptance criteria
    • • Sprint planning
    • • Release planning

    Agile & Scrum

    • • Scrum framework
    • • Agile methodology
    • • Sprint cycles
    • • Daily standups
    • • Sprint retrospectives
    • • Definition of Done
    • • PSPO I certification
    • • PSM I certification

    Stakeholder & Collaboration

    • • Cross-functional collaboration
    • • Stakeholder management
    • • Stakeholder alignment
    • • Engineering partnership
    • • Customer feedback synthesis
    • • Requirements gathering
    • • Consensus building

    Data & Analytics

    • • Data-driven decision-making
    • • Product KPIs
    • • Metrics tracking
    • • Performance monitoring
    • • A/B testing

    Tools & Platforms

    • • Jira
    • • Confluence
    • • Miro
    • • Microsoft Office
    • • QXDM (Qualcomm)

    Technical Product Skills

    • • Technical requirements
    • • Root cause analysis
    • • Defect management
    • • Quality assurance
    • • Test planning

    Tip: Only include keywords that genuinely reflect your experience. Interviewers will ask you to elaborate on anything listed. It is better to be honest about "familiar" or "learning" status than to claim expertise you do not have.

    Resume Effectiveness Improvement

    Before Optimization

    • Two pages for 4 years experience signals poor judgment and inability to prioritize
    • 100% duty-based language across all bullets describes responsibilities instead of achievements
    • Zero quantified outcomes means no proof of impact or business value
    • Missing work authorization for Germany applications creates immediate rejection risk
    • Unprofessional contact information reduces callback likelihood
    • Missing Product Owner tools (Jira, Confluence) creates ATS keyword gaps

    Estimated Pass Rate: 35-40% for Product Owner roles

    After Optimization

    • One page with focused content demonstrates judgment and prioritization ability
    • XYZ framework throughout proves measurable impact and business value
    • Quantified achievements provide concrete evidence of capability
    • Clear work authorization statement removes primary blocker for international hiring
    • Professional contact information increases recruiter ability to reach you
    • Product management tools added closes critical ATS keyword gaps

    Estimated Pass Rate: 85-90% for Product Owner roles

    Next Steps

    1Fix Format and Basic Information

    • Fix Contact Information
      • Change email to peihua.yeh@gmail.com or similar professional format
      • Add phone number: +886-XXX-XXX-XXX
      • Add full LinkedIn URL: linkedin.com/in/peihuayeh (or create if you do not have one)
      • Remove duplicate name in header
    • Add Work Authorization Statement
      • Add to header: "Relocating to Germany [Month] 2026 | Work Authorization: [Status]"
      • This single line can increase callback rate by 40-60% for international applications
    • Use Professional Resume Template
      • Use Flow Resume (flowcv.com) or similar service for clean, ATS-friendly format
      • Remove professional photo (not standard for tech industry in US/EU)

    2Transform Content to Results-Focus

    • Rewrite Summary with Quantified Data
      • Use the optimized version provided
      • Add your actual performance metrics if available
      • Remove "Currently seeking..." target role statement
    • Rewrite All Experience Bullets Using XYZ Framework
      • [X] = What did you accomplish? (outcome)
      • [Y] = How did you measure it? (metric)
      • [Z] = How did you do it? (method)
    • Add Your Actual Metrics

      If you do not have exact numbers, use conservative estimates:

      • Test plans created: "15-20 test plans annually"
      • Laptop models covered: "across 25+ laptop models"
      • Defects identified: "identified 40+ critical defects pre-launch"
      • Quality improvement: "improving product readiness by approximately 20%"

    3Optimize for Target Roles

    • Add Product Management Tools to Skills
      • Add new first category: "Product Management Tools: Jira, Confluence (familiar), Miro (familiar), Microsoft Office Suite"
      • Reorder Technical Skills to prioritize Product Owner tools before testing tools
      • Keep honest "familiar" labels for tools you are learning
    • Remove Non-Essential Sections
      • Delete International Experience section entirely
      • Delete Core Competencies section entirely
      • Integrate best competencies into improved Summary with proof points
    • Add German Language Status
      • Update Languages section: "Mandarin Chinese (Native), Taiwanese (Native), English (Fluent - C1), German (Basic A1 / Learning)"

    4Compress to One Page

    • Consolidate Experience Bullets

      Final bullet count per role:

      • HP (Associate Software Engineer): 5 bullets
      • BoConcept (Sales Associate): 2 bullets
      • Unitech (Customer Service QA): 1 bullet
      • HP Ireland (Machine Operator): 1 bullet
      • Total: 9 experience bullets
    • One-Line Formatting for Efficiency
      • Contact info: 1 line
      • Languages: 1 line
      • Education: 1 line
      • Each certification: 1 line

    5Apply to Target Roles

    • Identify Target Companies
      • TeamViewer (Product Owner, Bremen, Germany) - primary target
      • Experian (Junior Product Manager, Frankfurt, Germany) - secondary target
      • Similar Product Owner roles at German tech companies
      • Remote Product Owner roles that accept international candidates
    • Customize for Each Application
      • Adjust 2-3 bullets to match specific job description keywords
      • Reorder Skills section if needed to emphasize different tools
      • Ensure work authorization statement addresses specific location

    6Prepare Interview Stories Using STAR Method

    • Prepare 2-3 Minute Stories

      For each major achievement on your resume, prepare a story following this framework:

      • Situation: What was the context or problem?
      • Task: What was your specific responsibility?
      • Action: What did you do? (step-by-step)
      • Result: What happened? (quantified outcome)
    • Example Structure:

      "At HP, we faced challenges with WWAN connectivity validation across multiple laptop models [Situation]. As Associate Software Engineer, I was responsible for creating comprehensive test plans that aligned with both technical requirements and business timelines [Task]. I approached this by first analyzing historical defect patterns to identify high-risk areas, then collaborating with product managers to prioritize critical features, and finally building automated test scenarios that could scale across 25+ laptop models [Action]. This resulted in identifying 40+ critical defects before product launch, improving our product readiness scores by approximately 20%, and reducing time-to-market by 2-3 weeks per release cycle [Result]."

    • Use Interview Prep Guides:

      English Interview Prep Guide | Chinese Interview Prep Guide (中文)

    Do's

    • • Customize for each application - Change 2-3 bullets to match JD
    • • Follow up after applying - Email recruiter 5-7 days later
    • • Be ready to explain every metric - Interviewers will ask
    • • Keep examples confidential - Don't mention internal project names
    • • Show genuine enthusiasm - Reference specific company initiatives

    Don'ts

    • • Don't apply without customization - Quality > quantity
    • • Don't exaggerate metrics - Be ready to support with data
    • • Don't badmouth previous employers - Stay professional
    • • Don't ignore cultural fit - Research company values

    Your Resume Transformation

    Before:

    50%
    Original Resume
    →→

    After:

    90%
    Optimized Resume

    Your experience is strong for Product Owner transition:

    • • 4 years at HP with WWAN/IoT product experience
    • • PSM I and PSPO I certifications
    • • Cross-functional collaboration with engineering and business teams
    • • Customer-centric mindset from B2B sales background
    • • Multilingual capability for international product teams

    Final Thought:

    Your previous resume was not telling this story effectively. It buried your strongest achievements under 13 duty-based bullets across two pages. It confused recruiters with scattered Core Competencies and non-work-related International Experience sections. It failed to quantify any results or prove business impact.

    Your new resume will showcase exactly what makes you valuable. You can validate complex technical products. You can collaborate across engineering and business stakeholders. You can translate technical findings into actionable product insights. You can deliver measurable quality improvements.

    You have the experience. Now you have the positioning. Go get the offer.

    Your Feedback Matters

    I hope this review has been valuable in strengthening your application.

    If you found this review helpful, I'd greatly appreciate your feedback:

    Why is the Trustpilot score 3.8?
    I've just started a new business and Trustpilot applies an initial weighting for new businesses, which can temporarily lower early scores. As more real client reviews are added, the score adjusts to reflect actual service quality.

    When you land interviews or offers, let me know!

    Your wins are my wins. Success stories help refine my approach.

    Questions or need clarification on any recommendations?

    Feel free to reach out. I'm here to help you succeed.

    Best of luck with your applications!

    Review Completed: February 2026