the stories that got me hired as a PM involved 0 technical skills

how a cappella drama, student government, and event planning beat technical projects every time

💎 Welcome to work smarter, my newsletter on building your career and designing your life. I’ve interviewed 100+ candidates and received offers from Google, Meta, Snap, and Microsoft, and I share templates and guides to help you get offers you’re excited about :)

If you’re not a subscriber yet, here’s what you missed:

• Product management internship & full-time application dates (Google APM, Meta RPM, and more)

• Product sense case interview answers: a detailed ChatGPT/Claude prompt

• How to prepare for AI product manager interviews, part 2: behavioral interviews

• How to build projects without coding

Read time: 5 minutes

---

When I started applying to product management roles, my resume looked nothing like a traditionally successful resume. While other candidates all had computer science degrees and engineering internships, I had music and student government.

But it was these exact experiences — experiences that involved 0 technical skills — that helped me showcase skills that hiring managers look for.

Now, after interviewing 100+ candidates and doing 100+ product management interviews myself, I’m even more confident that your unconventional path isn't a weakness to overcome. It's a story waiting to be told well.

So here’s how to stop apologizing for your passions and start leveraging them. I’ll start with 3 examples, then break down why they work and how you can replicate my results.

---

Pinterest Apprenticeship links

Apprentice product manager link

Apprentice product designer link

Apprentice product researcher link

Interviewing at Pinterest: Advice from Apprentice Alumni link

Getting your resume apprenticeship-ready link

Meet the Pinterest Products Apprenticeship Cohort link

---

Example 1: How I resolved a critical conflict as the music director of my a cappella group

Situation

While leading our 15-person a cappella group, I faced a critical conflict between our lead soloist and vocal arranger over our competition piece. The arranger had created complex jazz harmonies that was challenging for our soloist.

What was at stake?

With just 6 weeks until the competition, this conflict threatened to derail our performance. Our star soloist was considering stepping down, which would have meant restarting arrangement work and potentially missing competition deadlines.

Action

1. I had a 1:1 conversation with both parties to understand their artistic visions and constraints. I discovered that the arranger wanted to showcase our group's technical abilities while the soloist was concerned about authenticity.

2. I organized a workshop where we recorded both versions and collected feedback from the entire group using a structured evaluation framework

3. I facilitated a mediation session where we identified specific sections for compromise. Specifically, we kept complex harmonies in verses, but simplified the chorus to highlight the soloist's strengths.

Result

1. Both parties felt their contributions were valued.

2. Our a cappella group dynamic strengthened, because we had an established process for handling creative differences.

3. This creative process continues to be used by the group, even after all group members have graduated.

Transferrable skills

• Balance competing stakeholder needs while maintaining project momentum

• Use data (recordings, feedback) to make objective decisions

• Create structured processes for resolving creative differences

• Find win-win solutions that serve both individual and group needs.

These skills directly translate to product management, where I'll need to balance engineering constraints with user needs and business goals.

Example 2: How I created a new academic policy at my college that passed with 90% approval rating

Situation

As VP of Academic Affairs for my university’s student government, I led a initiative to reform our pass/fail policy. Students wanted more flexibility, professors worried about academic rigor, and administrators needed to maintain accreditation standards.

Stakes

This was students’ top complaint for 2 semesters in a row. Furthermore, the existing policy was causing dropping enrollment in challenging electives. However, we needed to design a solution carefully, because hasty changes could damage our university's academic reputation and accreditation status, and set bad precedents for future policies.

Action

1. I conducted a comprehensive research study, including student surveys (X% of student body), faculty interviews (20+), and analysis of peer institutions' policies

2. I created a data visualization dashboard showing the impact of current policy on course selection patterns and student outcomes

3. I developed a tiered proposal allowing pass/fail for up to 2 non-major courses per year, with GPA minimums and advisor approval requirements

Result

• Policy approved by X% of faculty senate and student government

• X% increase in students taking courses outside their major the following semester

• Featured as a case study in inter-university policy forum

Transferrable skills

This experience developed crucial PM skills:

• Gathering and synthesizing requirements from diverse stakeholders

• Using data to drive decision-making and build consensus

• Creating scalable solutions that balance flexibility with standards

• Managing complex approval processes with multiple stakeholders

Example 3: How I managed a crisis during a fundraiser gala

Situation

As the president of my club, I led planning for our annual "Future Leaders Summit" - a 200-person fundraiser and speaker event featuring 3 tech executives. 3 hours before the event, our keynote speaker had a family emergency and couldn't attend. This would be very disappointing to our attendees, who paid $50 each to hear her speak.

Stakes

• $10,000 in ticket revenue at risk if attendees demanded refunds

• Club's reputation with both students and industry professionals at stake

• Risk of losing corporate sponsorships for future events

• 200 attendees already en route to the venue

Action

1. Rapid response (first 30 minutes):

   • Quickly assembled core team of 5 officers

   • Had our marketing lead draft transparent communication to attendees

   • Created decision matrix to evaluate possible solutions (full refunds vs. partial refunds vs. alternative speaker)

2. Creative solution (next hour):

   • Leveraged our alumni network through LinkedIn messages and calls

   • Found a recent graduate who had just launched a successful startup who was local

   • Worked with our tech team to set up hybrid format so our original speaker could still do a brief virtual introduction

3. Experience enhancement (Final hour):

   • Restructured event flow to include more networking time

   • Added a panel discussion with other speakers to provide more interactive content

Result

• 95% attendee retention with only 10 refund requests

• Received positive feedback about the last-minute speaker (4.5/5 rating) and restructured event flow (4.4/5 rating)

• Alumni speaker was so successful we invited her to join our advisory board

Transferrable skills

This experience taught me crucial PM skills:

• Crisis management and rapid decision-making

• Stakeholder communication during uncertainty

• Resource reallocation under pressure

• Importance of strong professional networks

Most importantly, I learned that sometimes a crisis can lead to innovation - our hybrid format and enhanced networking sessions became standard features of future events. This translates directly to product management where dealing with unexpected technical issues, shifting market conditions, or resource constraints requires similar quick thinking and stakeholder management.

---

Use my Story Archaeology framework

You already have the stories. You just don't see them yet. Here's how to find the leadership moments hiding in plain sight, and replicate my results:

Step 1: Audit the stakes

List every project, role, or situation where something genuinely mattered to you or others. Ask yourself:

• What would have happened if I failed?

• Who else was counting on me?

• What was at risk beyond just my own success?

Step 2: Identify conflicts

Great stories need tension. Scan your experiences for:

• Competing priorities or stakeholder needs

• Resource constraints or tight deadlines

• Disagreements you had to navigate

• Situations when the obvious solution wasn't available

Step 3: Connect experiences to PM skills

For each potential story, ask: "What PM skill does this demonstrate?"

Examples:

1. Stakeholder management (balancing different needs)

2. Data-driven decision making (using evidence to choose direction)

3. Crisis management (adapting when plans fall apart)

4. Influence without authority (getting results through others)

5. Resource allocation (maximizing impact with constrained time/budget/people)

6. User research and validation (understanding what people actually need vs. what they say they want)

7. Cross-functional collaboration and communication (coordinating across different teams/disciplines)

8. Risk assessment and mitigation (identifying what could go wrong and planning accordingly)

9. Consensus building (getting alignment across diverse viewpoints)

10. User empathy (understanding pain points and motivations)

Step 4: Quantify the stakes

Quantifying the stakes paints a vivid picture of why the problem was worth solving.

Examples of quantifying the stakes, from the 3 stories I shared above:

• Timeline pressure: "6 weeks until competition," "3 hours before event," "2 semesters of student complaints"

• Financial impact: "$10K in ticket revenue at risk," "paid $50 each to hear her speak"

• People affected: "15-person group," "200 attendees," "20% of student body surveyed"

• Reputation risk: "star soloist considering stepping down," "club's reputation with industry professionals at stake," "accreditation standards"

• Cascading consequences: "restarting arrangement work," "missing competition deadlines," "losing corporate sponsorships for future events"

Step 5: Quantify the results

Quantifying the results conveys the impact of your involvement.

Examples of quantifying the results, from the 3 stories I shared above:

• Participation/approval metrics: "90% faculty senate approval," "95% attendee retention," "only 10 refund requests"

• Behavioral changes: "20% increase in students taking courses outside their major," "group dynamic strengthened"

• Feedback scores: "4.5/5 rating for speaker," "4.4/5 rating for event flow"

• Long-term adoption: "process continues to be used after all members graduated," "hybrid format became standard for future events"

• Recognition/expansion: "featured as case study in inter-university policy forum," "alumni speaker joined advisory board"

• Sustained impact: "both parties felt their contributions were valued," "established process for handling creative differences"

The Golden Question

"What situation from my past required me to think like a product manager before I knew what product management was?"

That's your story. All your experiences are proof that you can handle the messy, human side of building products.

What’s an experience you’re inspired to talk about your next interview?

I’m on a mission to help more people design careers they’re happy with!

If this resonated with you:

• Share this post with someone who feels behind because they didn't follow the "traditional" path

• Share this post with a friend who's amazing at what they do but terrible at talking about it in interviews

• Share this post with someone who needs permission to see their unique background as a strength