Below, I’m sharing back the findings on 1) why it’s helpful for the company 2) thoughts from the candidate side and 3) a few of my own tips for approaching them.
Since PM skills are tough to evaluate in the abstract, this can be *very*, *very* useful.
It’s hard to overstate this given how much PMs must rely on soft power/influence to get things done.
Communication is 🔑.
No one wants to feel like it’s free labor!
For hiring companies, make it about the problem-solving process, not solving some rote work for you.
I’ve got three tips for candidates working through a homework assignment.
Don’t immediately jump into a solution. The team will want to know how you explored and narrowed the problem space.
Wireframes are great - hand-drawn, @balsamiq, whatever. No one wants to read paragraphs of text.
If it’s a data-heavy case, sum up key insights with a well-placed chart or two.
No product idea is perfect so don’t try to sweep problems under the rug. Call them out, explain why they’re the lesser of two evils, etc and explain how they could be mitigated.
It should feel complete and tell a story. So what’s one look like...
It’s not perfect but it resulted in an offer to be PM #4 there. Not taking that offer may have cost me some serious $ but that’s a story for another day.
rocketblocks.me/blog/pm-interv…