How to become a product manager in 2025 (no CS degree required)

You want to know how to become a product manager, but every job posting asks for 3-5 years of PM experience. It’s the classic catch-22: you can’t get the job without experience, and you can’t get experience without the job. Here’s what those postings don’t tell you—most product managers didn’t start as product managers. They came from engineering, design, marketing, sales, customer support, and fields that have nothing to do with tech at all.

The path into product management is less about checking credential boxes and more about demonstrating you can think like a PM. This guide breaks down exactly how to make that transition, regardless of where you’re starting from.

What companies actually look for in PM candidates

Before mapping your path, you need to understand what hiring managers actually evaluate. Spoiler: it’s rarely a CS degree.

After analyzing hundreds of PM job descriptions and talking to hiring managers at companies ranging from seed-stage startups to Google, the requirements cluster around four areas:

• Problem-solving ability — Can you break down ambiguous problems and identify the right approach?
• Communication skills — Can you articulate ideas clearly to engineers, designers, executives, and customers?
• Customer empathy — Do you instinctively think about user needs and pain points?
• Execution track record — Have you shipped something? Anything?

Notice what’s missing: specific technical credentials. Yes, some companies (particularly FAANG) prefer candidates with technical backgrounds for certain PM roles. But the majority of PM positions—especially at startups and growth-stage companies—prioritize the skills above over pedigree.

Jackie Bavaro, co-author of Cracking the PM Interview and former PM at Asphalt, Asana, and Google, transitioned from software engineering. But she’s noted that some of the best PMs she’s worked with came from non-technical backgrounds—they brought fresh perspectives on user problems precisely because they weren’t anchored in implementation details.

The five most common paths into product management

Understanding the typical entry points helps you identify which path leverages your existing experience.

Path 1: Internal transfer (the most common route)

Roughly 40-50% of first-time PMs get their start through internal transfers. This is the path of least resistance because you’ve already proven yourself and built relationships.

How it works: You’re working at a company in another role—engineering, design, marketing, customer success—and gradually take on PM-adjacent responsibilities. Eventually, a PM role opens, or one gets created for you.

Real example: Maggie Crowley started at Drift as a marketing manager. She noticed gaps in how the team prioritized features and started documenting customer feedback patterns. When Drift needed another PM, she was the obvious choice. She later became VP of Product at Toast.

Your playbook:

1. Identify a product team at your company that needs help
2. Volunteer for cross-functional projects that put you in PM-like situations
3. Start attending product meetings, even as an observer
4. Build relationships with PMs and their managers
5. Make your PM aspirations known—explicitly

Path 2: From engineering or design

Technical and design backgrounds translate most directly because you already understand the product development process.

Engineers understand technical constraints, can evaluate feasibility quickly, and speak the same language as the development team. The gap to close: developing stronger customer intuition and learning to let go of implementation details.

Designers bring user research skills, prototyping experience, and a natural focus on user problems. The gap to close: building business acumen and learning to balance user needs against company objectives.

Real example: Ken Norton, who wrote the famous “How to Hire a Product Manager” essay at Google, was a software engineer first. He deliberately sought out customer-facing projects to build the empathy skills he knew he’d need as a PM. [INTERNAL_LINK: technical skills for product managers]

Path 3: From customer-facing roles (support, success, sales)

If you’ve worked directly with customers, you have something many PM candidates lack: hundreds of hours of real user feedback already in your head.

Customer support/success professionals understand pain points intimately. You’ve seen what actually frustrates users, not just what they say in surveys.

Sales professionals understand what makes people buy, what objections arise, and how to communicate value.

Real example: Lenny Rachitsky, whose newsletter now reaches over 500,000 product professionals, started his career in consulting before moving to Airbnb. His early work there involved deep customer research—understanding both hosts and guests—before transitioning to a full PM role.

Your playbook:

1. Document customer feedback patterns systematically—not just complaints, but underlying needs
2. Propose feature ideas based on your customer insights (with data)
3. Learn the basics of product analytics to complement your qualitative knowledge
4. Ask to shadow product meetings and contribute customer perspective

Path 4: From business roles (marketing, operations, analytics)

Marketing professionals understand positioning, market dynamics, and how to communicate value—all essential PM skills.

Operations people know how to optimize processes and think systematically, which translates well to product operations and growth PM roles.

Analysts bring data fluency that many PMs lack. If you can tell stories with data, you’re ahead of many candidates.

Real example: April Dunford, author of Obviously Awesome, moved from product marketing into product management at several startups. Her positioning expertise gave her a unique angle on product strategy that pure technologists often miss.

Path 5: From outside tech entirely

This is the hardest path, but it’s absolutely possible. Teachers, consultants, healthcare workers, and professionals from dozens of other fields have made the switch.

Real example: Shreyas Doshi, former PM at Stripe, Google, and Yahoo, studied electrical engineering but has been vocal about how product management draws on liberal arts skills—writing, psychology, critical thinking—as much as technical ones.

Your playbook:

1. Identify which PM skills you already have from your current role (most professionals have more than they realize)
2. Get technical exposure through no-code tools, basic SQL, or product analytics courses
3. Consider transitional roles (covered below) rather than jumping directly to PM
4. Target industries where your domain expertise is valuable

How to build a PM portfolio without PM experience

The biggest barrier for career changers is the “portfolio problem.” How do you demonstrate PM skills without having held the title?

Option 1: Product teardowns

Write detailed analyses of existing products. Pick apps you use daily and answer:

• Who is this product for? What problem does it solve?
• What’s the core user journey?
• What would you change and why?
• What metrics would you track to measure success?

Publish these on Medium or your own site. Brie Wolfson wrote product analyses while working in operations at Figma, which helped establish her product thinking credentials.

Option 2: Ship something yourself

Build a product, even a small one. No-code tools like Bubble, Webflow, or Glide make this accessible to non-engineers. What matters isn’t technical sophistication—it’s demonstrating the full product cycle: identifying a problem, validating it, building a solution, and measuring results. [INTERNAL_LINK: no-code tools for product managers]

Option 3: Contribute to an existing product

Volunteer with a nonprofit or early-stage startup. Many organizations need product help but can’t afford full-time PMs. You get real experience; they get real value. Check out platforms like Catchafire or reach out directly to small teams building products you care about.

Option 4: Document your PM-adjacent work

You’re probably already doing PM work without calling it that. Have you:

• Prioritized features or improvements based on user feedback?
• Coordinated cross-functional teams to launch something?
• Analyzed data to inform a product or process decision?
• Conducted user research or customer interviews?

Reframe these experiences in PM language. Write them up as case studies with clear problem-approach-outcome structure.

Transitional roles: the stepping-stone strategy

If a direct jump to PM feels too large, consider roles that bridge the gap:

Associate Product Manager (APM) — Entry-level PM roles, often with formal training programs. Google, Meta, Uber, and many others offer APM programs, though they’re competitive.

Product Operations — Supports the product team with processes, data, and coordination. Less common but growing. Provides direct exposure to PM work without full ownership pressure.

Technical Program Manager (TPM) — For those with technical backgrounds who want to practice cross-functional coordination before full PM responsibility.

Growth/Analytics roles — Build data skills and product intuition while working closely with product teams. Many Growth Analysts transition to Growth PM roles.

Product Marketing Manager — Especially good for those with marketing backgrounds. You’ll develop positioning, competitive analysis, and go-to-market skills that translate directly.

Realistic timeline expectations

How long does the transition actually take? Based on patterns from successful career changers:

• Internal transfer (same company): 6-18 months from deciding to pursue PM to landing the role
• From adjacent tech role (engineering, design) to PM at new company: 3-12 months
• From non-tech role to PM: 12-24 months, often with a transitional role in between

These aren’t guarantees—the range depends on your starting point, network, target companies, and effort invested. But they’re realistic benchmarks based on actual transitions.

The skills to develop now (regardless of your path)

While you’re working toward a PM role, invest in these high-leverage skill areas:

User research fundamentals — Read The Mom Test by Rob Fitzpatrick. Practice conducting interviews. This skill separates good PMs from everyone else. [INTERNAL_LINK: user research for product managers]

Data literacy — Learn basic SQL. Understand how to set up and analyze product analytics. You don’t need to be a data scientist, but you need to be dangerous.

Communication — Practice writing product specs, PRDs, or just clear documentation. Teresa Torres emphasizes that clear thinking is inseparable from clear writing.

Product strategy — Understand how to connect company goals to product decisions. Marty Cagan’s work, particularly Empowered, is essential reading here.

Your next step

Knowing how to become a product manager is just the first step—now you need to act on it. Here’s your assignment for this week: identify which path matches your current situation, and take one concrete action toward it. If internal transfer is your path, request a coffee chat with a PM at your company. If you’re building a portfolio, publish your first product teardown. If you’re considering transitional roles, apply to one this week.

The product managers you admire didn’t wait until they felt ready. They started demonstrating PM skills before anyone gave them the title. You can do the same.

Frequently asked questions