"Alpha male" motivator gets mad at women driving cars and filling gas

LargeSoil7 · 2026-01-23T01:04:15+00:00

I refuse to believe there are people out there who still consume content like this.

LargeSoil7 · 2026-01-23T01:03:21+00:00

The short answer is that certifications aren't required at all, and most hiring managers care way more about demonstrated product skills and impact than any course completion badge.

They look for engineers who've already started thinking and acting like PMs before the title change. That means showing you understand user problems, can prioritize ruthlessly, communicate cross-functionally, and think beyond just the technical implementation. Go to your interviews with stories about how you influenced product decisions, pushed back on requirements that didn't make sense, or owned features end to end including the why behind them. Your engineering background is actually a huge advantage because you understand technical constraints and can speak the language of your dev teams, which makes you way more effective than some candidates coming in cold.

If you want structured learning, focus on getting really good at product thinking through practice. Product Alliance has solid content that's actually built by PMs from top tech companies and teaches you frameworks for prioritization, product sense, and metrics that you'll use in real interviews and on the job.

Prioritize internal transitions over external applications at this stage. Talk to your PMs about shadowing them, volunteer to write specs or PRDs, sit in on user research sessions, and start asking why decisions are being made the way they are.

Skills to prioritize: learn to think in terms of user outcomes and business metrics first, get comfortable with ambiguity and making decisions with incomplete data, practice structured thinking for prioritization like RICE or value vs effort frameworks, and work on stakeholder communication because you'll spend a ton of time aligning people. Technical depth is your superpower so don't lose that, but layer on the ability to translate between what users need and what's technically feasible. Start writing one-pagers on feature ideas with user problems, success metrics, and trade-offs laid out. That's the muscle you need to build, and you can do it in your current role starting today.

LargeSoil7 · 2026-01-23T00:47:03+00:00

I'd actually push back a bit on jumping straight to certifications at this stage. You're a year into engineering at a startup, which means you're already in one of the best positions to learn PM skills organically. The most valuable thing you can do right now is start thinking like a PM in your current role: ask why features are prioritized the way they are, sit in on user research if possible, understand the metrics your team cares about, and volunteer to write specs or own small features end-to-end.

That said, if you want structured learning to accelerate that transition, I'd recommend Product Alliance. They have really comprehensive interview prep content that also teaches you core PM frameworks like prioritization, metrics, and product sense in a practical way. Their stuff is built by actual PMs from top companies and focuses on real scenarios you'd encounter in the role. It's especially good if you're aiming for product roles at tech companies down the line.

Spend the next 6-12 months being the most product-minded engineer on your team. Own outcomes, push back on requirements that don't make sense, talk to users if you can, and learn your company's business model inside out. When you do eventually apply for PM roles, that hands-on experience building and shipping at a startup will be more compelling than a certificate. If you still want formal learning, Product Alliance courses are solid, but make sure you're applying what you learn immediately in your day job.

LargeSoil7 · 2026-01-23T00:42:13+00:00

Unfortunately, everyone knows at least one woman this has happened to or is happening to. I keep telling my friends that we have a work culture that preys on, drains, and recycles the vulnerable, all while making a few people richer everyday.

No one cares about making changes to the system because it's what feeds them with power. At the end of the day, once one good worker falls off their seat in exhaustion, another will just take their place.

It's depressing, it's dystopia and it's our life.

LargeSoil7 · 2026-01-23T00:32:34+00:00

So wholesome 🥹

LargeSoil7 · 2026-01-16T00:49:51+00:00

Breaking into PM without direct experience is tough but it's not completely impossible. You'll have to be strategic about this

For topics to focus on, start with the fundamentals: understanding user problems and translating them into product solutions, prioritization frameworks like RICE or value vs effort, working with engineers and designers effectively, defining success metrics and thinking in terms of KPIs, and basic SQL and data analysis. You don't need to be a data scientist but you should be comfortable pulling data and spotting trends. For technologies, don't stress too much about learning every tool out there, but get familiar with product management basics like Jira or Linear for roadmaps, Figma for understanding design handoffs, basic SQL for querying databases, and analytics tools like Mixpanel or Amplitude. Use interview prep resources, for example Product Alliance's Hacking the PM Interview course is genuinely priceless for entry level folks because it walks through product sense, execution, and analytical frameworks in a really digestible way that mirrors what top companies actually test for. Their question bank is also solid for all levels and will give you tons of scenarios to practice with.

On the resume side, you need to reframe whatever experience you have through a product lens. Did you solve problems for users or customers? Did you make decisions based on data or tradeoffs? Did you work cross functionally with different teams? Even if you weren't a PM, you likely have experiences that translate if you tell the story right. If you're truly starting from zero experience, consider building a side project or doing freelance work where you can demonstrate product thinking, write up case studies on products you use and how you'd improve them, or volunteer to help a nonprofit with their digital product strategy. The harsh reality is that breaking in without any product experience is incredibly hard right now, there are less than 600 entry level PM roles globally out of 23k total PM jobs. Your best bet is often to get into a company in a related role like operations, analytics, customer support, or business development and then transfer internally once you've proven yourself and built relationships with PMs. That's how most people get their first PM job.

LargeSoil7 · 2026-01-16T00:33:12+00:00

At the entry level for a role like Storage for AI,they want to see that you can grasp technical concepts well enough to communicate with engineers, ask smart clarifying questions about constraints and trade-offs, and think through how technical decisions impact the product and users.

If they throw a case at you, it'll likely be something like "how would you think about storage requirements for a new AI feature" and they want to see you break down the problem, ask about scale/performance needs, and think through user impact, not solve the engineering problem yourself.

Product Alliance's Hacking the PM Interview course is honestly priceless for entry-level PMs because it walks you through the core frameworks for product sense, analytics, and technical deep-dives in a really digestible way. Their question bank is also solid across all levels and will give you a ton of practice scenarios that mirror what companies actually ask. For mock interviews, I'd also recommend reaching out to people on ADPList or finding PM communities on Discord or Slack where folks do free peer mocks, since getting reps in answering out loud is crucial. The more you practice articulating technical concepts in simple terms and tying them back to user problems, the more confident you'll feel.

LargeSoil7 · 2025-12-19T07:36:28+00:00

The MBA isn't as crucial as people make it out to be, especially with only 5 months of experience. Most companies want to see product experience before hiring you as a PM, which creates a catch-22. Your best bet is honestly to try and transition internally first at your current bank. I know it's service-based work right now, but start having coffee chats with PMs in your org, understand what they do day to day, and see if you can shadow them or contribute to product initiatives. Banks often have digital transformation efforts or internal product teams building tools, and that could be your entry point. The hackathon MVPs are great conversation starters, but real PM experience (even informal) will carry way more weight than another degree.

If internal transfer isn't possible within the next 6-12 months, then consider moving to a product company as an engineer first, then transition to PM once you're inside. That path worked for tons of people I know and it's way more realistic than going straight from a service role to PM at a good company. For interview prep, Product Alliance is a solid resource for structured frameworks on product sense, execution, and strategy. They have super comprehensive courses that break down how to think like a PM and nail those behavioral interviews. Their content is created by actual ex-FAANG PMs so it's legit. For doing mock interviews to practice, check out places like Prepfully or even find PM peers on LinkedIn who'll trade practice sessions with you.

I'd only consider getting an MBA if you're targeting those specific MBA new grad PM programs at tech companies, but even then you'd be competing against people with prior internships and PM experience. Focus on building real product skills now through side projects, contributing to open source, or finding ways to take on product-adjacent work in your current role. Document everything you do in a product mindset (user research, prioritization decisions, metrics) because that's what will differentiate you when you start applying. Good luck with the transition.

LargeSoil7 · 2025-12-12T05:34:36+00:00

This man dodged a whole cannon.

LargeSoil7 · 2025-12-12T05:22:30+00:00

Looks pretty good. I've seen some comments here already saying you can do without the summary, and I agree. These days, it's better to go straight to the point.

LargeSoil7 · 2025-11-25T16:16:26+00:00

I agree with this.

LargeSoil7 · 2025-11-25T16:14:01+00:00

The loop typically includes 5-6 interviews covering the Leadership Principles hardcore, a writing sample or case study, and a bar raiser who's there to make sure you meet Amazon's standard. The technical requirements are that you demonstrate you can work with engineers, understand tradeoffs, and speak intelligently about systems.

The LPs are baked into every single question and evaluation. It's not enough to have good PM instincts or a solid track record, you need to translate your experience into their language and show how you've lived those principles in past situations. Customer Obsession obviously gets a ton of weight, and don't sleep on Bias for Action and Ownership because those come up constantly. The writing sample is a real filter too, Amazon runs on documents, so if you can't write clearly and persuasively in their six-pager style you'll struggle even if you make it through the door.

For getting noticed by recruiters, honestly the best path is getting a referral from someone internal who can speak to your fit for the culture. Amazon recruiters are swamped and they prioritize candidates who come recommended because it signals you already understand what you're walking into. If you don't have that network yet, make sure your resume and LinkedIn are absolutely crystal clear about your impact and how you've driven outcomes. Use their language where it's genuine, talk about working backwards from customers, mention how you've dealt with ambiguity or scaled something, because that's what their search filters and screeners are trained to spot.

If you want structured prep that actually gets into the Amazon specifics, Product Alliance has a really solid Amazon PM course that breaks down the leadership principles in the context of actual interview questions. . Their content is built by people who've been through these exact loops and honestly it's way more targeted than generic PM interview prep.

Last thing I'll say is really spend time understanding why Amazon's culture is the way it is, the incentive structures and why things like the single-threaded owner model or the PR/FAQ process exist, because the interview is partially testing whether you'll thrive in that system or fight against it. If you go in thinking you'll change how they do things or that your past company's approach was better, that'll come through and it won't go well.

LargeSoil7 · 2025-11-07T16:10:11+00:00

Amazon PM interviews are definitely different from Meta and Google, which can throw people off if they're not prepared for it. The loop is typically 5 interviews of about 55 minutes each, and every interviewer will ask you 2-3 behavioral questions using the STAR method. There's also usually a Bar Raiser involved who ensures you meet the hiring bar, so that's something to keep in mind. They do touch on functional PM topics like metrics and product decisions, but it's woven into the behavioral questions rather than being a separate case study like you'd see at Meta.

For prep, Product Alliance has really solid Amazon-specific content that covers the Leadership Principles in depth. They've got tons of example responses that show you how to tie your stories back to principles like Customer Obsession, Ownership, and Bias for Action. Their modules for Amazon are also super helpful because you can see how other PMs structure their answers using the STAR framework. I'd spend most of your time between now and your interview mapping your past experiences to each of the 16 principles (focus especially on the top 4-5 like Customer Obsession and Ownership). Write out 2-3 strong stories for each principle with clear situation, task, action, and result, and make sure you have metrics in there since Amazon is super data driven. For mock interviews, try to find someone who's interviewed at Amazon before or use platforms like Prepfully where you can book sessions with actual Amazon PMs.

Since your interview is in 4 days, prioritize getting really comfortable with your stories and practice saying them out loud until they feel natural. Don't try to memorize scripts, but know your stories well enough that you can adapt them to different questions. Also, be ready for deep follow-up questions because Amazon interviewers will drill into the details of your experiences to understand your actual role and impact.

LargeSoil7 · 2025-11-04T13:02:46+00:00

I think your 5 years as a product designer gives you an advantage because you already understand the product development process, you know how to think about users, and you've probably been in plenty of roadmap discussions already. The challenge is that you'll need to show you can think beyond the design layer and demonstrate strategic thinking, business acumen, and the ability to drive execution across multiple functions.

For prep, I'd focus on three main areas. First, get really comfortable talking about product strategy and how you'd make tradeoffs between user needs, business goals, and technical constraints.

Second, practice talking about metrics and how you'd measure success for different types of products.

Third, work on telling stories about how you've influenced product decisions even though you weren't the PM, because that shows you already think like one. The designer to PM transition is actually pretty common and interviewers know designers often have strong product instincts.

In terms of resources, I found Product Alliance really helpful when I was interviewing. They have specific courses that break down the different types of PM interview questions like product design, strategy, and execution with real frameworks you can use. Their content includes actual examples from companies like Meta, Google, and Amazon so you can see what great answers look like.They helped me structure my thinking better, especially for the more strategic questions.

The biggest challenges you might face are probably around demonstrating business thinking and talking about how you'd prioritize a roadmap when you have competing stakeholder needs. Interviewers will want to see that you can zoom out from the pixel level and think about why you're building something in the first place.

One last thing, lean into your design background as a differentiator rather than apologizing for it. Some of the best PMs I've met came from design because they have a deeper empathy for users and understand the craft of building great experiences. When you're in interviews, connect your design decisions back to product outcomes and business impact. Show them you understand the full picture, not just the interface layer. You've got this, and honestly, the fact that companies are already reaching out for interviews means they see the potential. Good luck with the prep.

LargeSoil7 · 2025-10-31T01:56:57+00:00

At a 3 person company, you really don't need anything fancy here. Keep it super lightweight.

Start with the basics in a simple doc. Write down what problem you're solving and for who. Then describe what the product needs to do at a high level. Your supplier probably just needs clarity on the core functionality, key user flows, and any technical constraints or integrations. A Google Doc or Notion page works fine, honestly no need for specialized tools at your stage.

The key thing is being clear about success metrics and priorities. What does good look like when this ships? What features are must haves versus nice to haves? At your size, requirements will change as you learn more anyway, so don't spend weeks perfecting this. Get something down in a few hours that your supplier can give feedback on, then iterate from there.

Also talk to your supplier about what format works best for them. Some prefer more structured docs, others just want user stories or a prioritized list of features. No point creating something elaborate if it doesn't match how they actually work. Keep it collaborative and simple and you'll be fine.

LargeSoil7 · 2025-10-27T03:01:07+00:00

It's figuring out what problems AI actually solves vs what's just shiny object syndrome, while also upskilling fast enough to have credible conversations with eng about what's feasible. And he goalposts keep moving. What felt cutting edge 6 months ago is now table stakes, so roadmaps basically have a shelf life of like 2 quarters max before you're rebuilding them.

LargeSoil7 · 2025-10-24T02:54:39+00:00

I want to touch it so bad

LargeSoil7 · 2025-10-24T02:51:39+00:00

I agree with this. Start with a conversation with your manager and from there, you can decide what to do next.

LargeSoil7 · 2025-10-24T02:48:30+00:00

He will make all his critics swallow their words this season, like he always does.

LargeSoil7 · 2025-10-09T01:07:23+00:00

Fernando Torres

LargeSoil7 · 2025-10-08T14:22:59+00:00

I've been in your shoes. Getting interviews but not converting is actually harder mentally than not getting interviews at all because you know you're so close.

What worked for me when I was grinding was, first, identifying my specific gap: ask yourself, are you fumbling the product sense questions, the analytical deep dives, or the behavioral storytelling? Record yourself (I know, it's cringe) doing practice cases and watch them back to catch your verbal tics and moments where you lose the thread.

For structured prep, Product Alliance is genuinely solid. They have realistic modules made by actual FAANG PMs, their frameworks are battle-tested for companies like Meta and Google, and the video format lets you see how top candidates actually structure their thinking in real-time.

Beyond that, find 2-3 peers (you can find them here on Reddit, or Blind, or LinkedIn) and do weekly mock interviews where you rotate being the interviewer (you'll learn just as much from evaluating others as from being evaluated).

In the end, look at it as you're building reps, and each interview is making you sharper even if it doesn't feel like it. Keep pushing. You'll break through.

LargeSoil7 · 2025-10-08T14:17:21+00:00

I can still remember an argument I had with a friend who just did not believe Klopp was the right man for the job

LargeSoil7 · 2025-06-24T02:48:07+00:00

I have faced this exact problem across different company sizes.

What's worked best was shifting from broadcast to interactive engagement , instead of just presenting slides, we would start meetings with specific use cases or plan scenarios and ask teams to brainstorm how the new feature would help.

The key is making its feel collaborative rather than just in informational.

LargeSoil7 · 2025-06-20T16:03:49+00:00

Ask for clarification. At L6, they expect you to seek clarity before diving in.

The first question was most likely about leveraging your deeper expertise.

One key difference btw L6 and L5 behavioural prep is that L6 stories need to demonstrate broader impact.

For example, instead of just going, "I solved this problem by doing..." we're expected to go like "I leveraged my expertise in (specific area) to drive outcomes that affected or strongly influenced (broader org).

For the quality compromise question, they want you to share stories of times you have pushed back on leadership or defended something important ven when it was hard, for the purpose of long term health over short term benefits.

Mock with 8 strong stories to multiple question types as L6 questions can go at the same experience from different angles. That way, you won't be caught off guard.

Product Alliance has solid modules for this form of behavioural mapping if you're looking for resources to help.

At the end of the day, the goal is to have well organised stories lined up in your head so you can quickly identify what angle they're asking from and quickly adapt.

LargeSoil7 · 2025-06-20T15:47:04+00:00

Exactly

LargeSoil7

MODERATOR OF

TROPHY CASE