Resume Teardown #10: Senior Solutions Architect Transitioning to PM — Deep Domain but Missing PM Craft

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 senior Solutions Architect with 15+ years in enterprise telecom scored 58%. Deep domain expertise in BSS/OSS and billing systems (80%), strong executive influence, and $60M+ in contract wins. But the resume reads like an architect's CV: every bullet describes what was built, not what happened for users or the business. Last PM title was 12 years ago, and the gap is not bridged.

The Resume

Background: Solutions Architect / Business Analyst at a large enterprise software company (2014 to present, 10+ years across three roles at the same company). Previously a Product Manager at a major telecom equipment vendor (2011-2014). Software Engineer at the same vendor before that (2008-2010). MBA from a top UK business school. M.Sc. in Engineering. Multiple recent PM and AI certifications.

What looked good on the surface: 15+ years of progressive career in enterprise software. International experience across three countries. Led large-scale system migrations and platform transformations. Influenced $60M+ in contract wins. Recent PM and AI certifications showing intent to transition. Deep telecom domain knowledge.

Score: 58%

The evaluation detected this as a career transition case (5+ years outside PM) and applied transition-appropriate weights: Leadership 25%, Experience 30%, Domain 15%, Skills 30%.

Leadership & Impact: 55%

What worked:

One bullet stands out: "Led the migration of Document Designer system to a SaaS platform, cutting QA time by 30% and improving deployment efficiency." This has clear ownership, a specific system, and a quantified outcome. It is the strongest bullet on the resume.

The resume also shows executive influence: "Advised 3 new business initiatives by providing tailored technical solutions to executives, shaping customer program blueprints and product roadmaps." This demonstrates strategic input at a senior level.

What held it back:

Every other bullet describes delivery and architecture, not product outcomes. The resume answers "what did you build?" but never "what happened for users or the business because you built it?"

"Architected and designed over 50 end-to-end system capabilities with the target to onboard new product offerings, reduce Time to Market, and achieve 100% compliance." This is a scope statement, not an impact statement. 50 capabilities designed... and then what? Did time-to-market actually decrease? By how much? Did compliance improvements affect customer retention?

"Assessed and validated architectural and financial ecosystem impacts for 3 major financial system upgrades." Assessed and validated is advisory work, not ownership. A PM owns the decision and the outcome, not just the assessment.

The core problem: The resume reads like a Solutions Architect's resume because that is what it is. To position for PM, the framing needs to shift: what user or business problems did these solutions solve, and what measurable outcomes resulted?

Experience & Background: 60%

What worked:

• 15+ years of progressive career in enterprise software with clear seniority growth
• International experience across three countries
• "Contributed to Latin American market entry for IPTV and BSS solutions, leading to sold contracts with 2 major telecom operators worth $60M+" — genuine business impact with revenue numbers
• "Achieved 120% of the annual sales quota" — shows commercial acumen beyond pure technical delivery
• MBA from a top business school adds strategic credibility

What held it back:

The last PM title was in 2014. That is 12 years ago. The resume does not bridge this gap.

"Initiated and managed critical phases of a large multi-year transformation program for a Fortune 500 cable operator" — "managed critical phases" is program management language, not PM language. What product decisions were made? What was prioritized and what was cut?

The career progression at the current company (Senior BA → Billing Consultant → Solutions Architect) shows growth in technical leadership but movement away from PM, not toward it. A hiring manager sees this trajectory and asks: "This person was a PM 12 years ago, then spent a decade as an architect. Why should I believe they can do PM now?" The resume does not answer this question.

Domain Expertise: 80%

This is the strongest dimension and the biggest asset for the transition.

• Deep telecom/BSS/OSS expertise across multiple geographies and operators
• Discovery and solutioning sessions in Revenue Management across operators with over 10M subscribers
• Launched a Partner Management system for mobile interconnection serving 300,000+ subscribers
• Recent certifications in 5G, AI, and industry frameworks show the knowledge is current, not stale

For telecom PM roles specifically, this domain depth is genuinely valuable. Few PM candidates can match 15 years of hands-on BSS/OSS expertise combined with an MBA and AI certifications.

The gap: if targeting non-telecom PM roles, this concentration becomes a limitation rather than a strength.

Skills & Tools: 50%

This is the weakest dimension and the biggest blocker for the transition.

What is there:

• Solution Architecture, API Management, Cloud Architecture, Microservices — strong technical foundation
• PM and AI certifications from recognized programs — shows intent and investment in upskilling
• Agile methodology mentioned

What is missing:

The resume has zero demonstrated evidence of:

• User research or customer discovery
• Prioritization frameworks (RICE, ICE, or any structured approach)
• Metrics ownership (defining KPIs, tracking adoption, running experiments)
• Go-to-market planning or launch strategy
• Roadmap ownership (not just "shaping" someone else's roadmap)
• Sprint or backlog management
• A/B testing or data-driven product decisions

"Facilitated solutioning and grooming of over 100 end-to-end features as subject-matter expert to enhance platform capabilities." This is the most PM-adjacent bullet on the resume, but the framing undermines it. "Facilitated" and "subject-matter expert" are support roles. A PM does not facilitate grooming; a PM owns the backlog and decides what gets groomed. If this person was actually making prioritization decisions for those 100 features, the bullet needs to say so.

ATS Readiness: 77%

Decent formatting overall. The main issues:

• Non-standard section headers (missing "Work Experience" or "Professional Summary")
• BSS/OSS and other acronyms not spelled out on first use
• Missing PM keywords: A/B testing, user research, prioritization, OKR, sprint, backlog, product strategy, go-to-market, KPI, retention, conversion, MVP

The keyword gap is telling. These are not just ATS keywords — they represent the PM vocabulary that is entirely absent from the resume.

The Summary Problem

The current summary reads: "Telecommunications Professional with over 10 years of experience in Solutions Architecture and Business Analysis... Seeking a Product Manager position, where I bring my product management and technical architecture skills."

This is the fundamental problem in one paragraph. It leads with architecture, mentions PM as an aspiration, and does not demonstrate any PM thinking. "Seeking a Product Manager position" signals "I am not a PM yet" to every hiring manager who reads it.

What it should do: Lead with PM value. Something like: "Product leader with 15 years in enterprise telecom, combining deep BSS/OSS domain expertise with PM craft to build AI-powered customer experience platforms. Track record of driving $60M+ in contract wins, leading platform migrations that cut delivery time by 30%, and shaping product roadmaps for Fortune 500 operators."

Same person. Same experience. Completely different positioning.

Key Takeaways

1. Reframe architecture work as product work. "Architected 50 capabilities" → "Defined and prioritized 50 product capabilities based on customer needs and market requirements, reducing time-to-market by X%." The work is the same. The framing makes it PM work.

2. Bridge the 12-year PM gap explicitly. The resume needs to acknowledge and address this gap. A recent side project, a product case study, or even a clear narrative about how the SA role involved PM-level decisions would help. The certifications alone are not enough.

3. Lead with the destination, not the journey. "Seeking a PM position" tells the reader you are not there yet. "Product leader with deep technical architecture background" tells them you already are one.

4. Target telecom PM roles first. Domain score is 80%. That is the unfair advantage. Telecom companies building AI/5G products need PMs who understand BSS/OSS deeply. Do not fight the domain — leverage it as the entry point.

5. Show PM craft, not just PM certifications. Certifications prove you studied PM. Bullets that mention prioritization decisions, user feedback loops, and metrics ownership prove you practice PM. Add 2-3 bullets per role that describe product decision-making, even if the title was Solutions Architect.

6. Remove GPAs. With 15+ years of experience and an MBA from a top school, undergraduate and graduate GPAs add nothing. They take space that could be used for a PM-focused summary.

The Pattern

This resume represents the classic "senior technical leader who has been doing PM-adjacent work for years but never framed it that way" transition. The work is there — you cannot shape roadmaps for Fortune 500 operators, advise executives on product strategy, and groom 100+ features without doing PM work. But the resume describes all of this in architecture language, not product language.

The fix is not about doing different work. It is about describing the same work through a PM lens: what user problem did you solve, what did you prioritize and why, what was the measurable outcome, and who did you collaborate with to get there. That reframing, combined with targeting telecom PM roles where the domain expertise is a genuine differentiator, is the path from 58% to 75%+.