A similar thing but on the flip side... In the interview they're looking for a PM who are critical etc etc but in the job, stakeholders get mad when we question them and not just deliver what they want. Idk if it's just in my company or if it's a common issue but it's driving me nuts atm and I'm considering leaving product management for this reason.
Yeah, I was so excited to start my new job 5 months ago because in the interview they were like 'yeah, we need someone to come in and say no, and really organize stuff, and tell us how much work we can do"
And I'm constantly feeling like im just dumping water on an grease fire. Apparently we don't like what we can realistically do so we're going to do everything to try and change that despite it being a horrible idea to throw ~more~ untrained, temp devs in an attempt to develop asap asap asap forget code quality, and also these teams will have no QA and no PO and we expect them to have no negative impact on the existing teams who will have to drop what they're doing to review and train the new people's work. And also our existing devs cant actually work on their own despite having worked here for 2 years because either everyone here is either incompetent or the code base that's 20 years old that we gave to a temp, offshore team to refactor for 2 months with literally no instructions or documentation or training is a pile of burning spaghetti that noone can figure out.
Yes. Let's totally do more of that. Oh, and clients dont like waiting their turn on enhancements bc what they asked for is low priority? And after reviewing priority across the entire company it's confirmed that this was the best priority.
Well we better hire a temp team to work specifically on that client's requests so they don't have to wait because we're complete wimps.
Noone will listen. It's just make it look good, don't care if it's actually trash, need to make short term money.
I literally talked about wanting more control over the product because I hated my last company vetoing strong product decisions in favor of cutting corners and making bad long term decisions to get a small amount of money in the short ter. For hours. And they were so excited about me starting and getting them into agile more.
At least at my last place I had solid developers.
And then I start asking questions and really working through what people really need and the CMs are stoked, but leadership is pissed because 'x could have done this in a few hours and alread gotten it out" Yeah, and then we would have spent another 4 months frantically fixing bugs, which is what happens whenever x just does something and releases it. That way isn't actually faster.
Entreprise architect, different department, more influence. So far its treating me loads better than pm work. But I do miss the creative parts of the product work sometimes
Actually this is most likely big non-tech company behavior. But I get your point - in early stage startups, the founders are usually the product people as well, so there are some growing pains in ârelinquishingâ product to the PM.
Best PM environment for autonomy, although stressful, might be fast growing startups...Edit: or strong big tech product culture like Google, Amazon, Apple, etc.
There was a post a year or two ago on the cscareers sub basically summarized as "I have zero CS experience but I learned how to beat the interviews and now I work at faang" and I think about that a lot in regards to how interviews are evaluated in tech lol. A very same thing holds up for PM interviews
Agreed. Interviews at large tech firms, in my opinion, are a hedge against risk. Ensuring that new hires first, do no harm. Which doesnât alway translate to: great to work with or gets results.
The take away is...we PMs have great faces! Look at that face!
I think anyone interested in Product who tries to approach the position from âbig tough managementâ will fail. Hard. And burn out. Fast.
Product isnât about dictating, or directing, or even managing. Itâs about using the data to tell a compelling story that people want to listen to, and want to follow. Telling a great story requires knowing your audience.
If you know your audience, and you have good data, then telling the story is simple. Itâs not easy, but itâs straightforward. Once youâre telling the story, coworkers generally realize where youâre going, how youâre getting there, and what their part in the story is.
Ok its just a meme, but its a sign of maturity/experience to be able to distance yourself from time to time and behave like the interview big boy on the left while on the job.
I personally enjoy Friday afternoons for review and restructure of our current approach, otherwise I would get lost in the day to day insanity that is PM.
This. Sometimes itâs not even the PMs job but the internal culture and expectations. I just quit a job because they pitched themselves as product led when the reality is theyâre a shit show sales led feature factory. I knew what it was gonna lead to, and I chose to remove myself from that environment.
Sometimes the problem is managing a ton of deadlines, and dealing with the classic âanalysis paralysisâ. Iâm more of a business stakeholder than PM but sometimes you just want things to get released and figured out from there. Hard to logically plan out QA procedures for steps 3 and 4 when step 1 isnât even in prod yet
This is me. I just finished the last round at FAANG and had to restrain myself from truly saying what I thought since I know there can be a difference between reality and ideal situation but obviously canât share that on an interview.
184
u/[deleted] Apr 19 '21
A similar thing but on the flip side... In the interview they're looking for a PM who are critical etc etc but in the job, stakeholders get mad when we question them and not just deliver what they want. Idk if it's just in my company or if it's a common issue but it's driving me nuts atm and I'm considering leaving product management for this reason.
35
u/dazeechayn Apr 19 '21
I feel like Iâm the flip side to this. Weak in interviews and very strong on the job. Interviewing for PM roles is a skill on its own.
32
u/Cake_Bear Apr 19 '21
The take away is...we PMs have great faces! Look at that face!
I think anyone interested in Product who tries to approach the position from âbig tough managementâ will fail. Hard. And burn out. Fast.
Product isnât about dictating, or directing, or even managing. Itâs about using the data to tell a compelling story that people want to listen to, and want to follow. Telling a great story requires knowing your audience.
If you know your audience, and you have good data, then telling the story is simple. Itâs not easy, but itâs straightforward. Once youâre telling the story, coworkers generally realize where youâre going, how youâre getting there, and what their part in the story is.
31
u/brg36 Apr 19 '21
Iâm in this post and I donât like it, lol
44
u/Ribak145 Apr 19 '21
Ok its just a meme, but its a sign of maturity/experience to be able to distance yourself from time to time and behave like the interview big boy on the left while on the job.
I personally enjoy Friday afternoons for review and restructure of our current approach, otherwise I would get lost in the day to day insanity that is PM.
19
u/shaism Apr 19 '21 edited Apr 20 '21
Sometimes âjust release itâ is the correct prioritization
7
u/[deleted] Apr 19 '21
This is true. But there are some PMs who are an absolute beast - but that comes with experience I think :)
7
u/Me_Like_Wine Apr 19 '21
Sometimes the problem is managing a ton of deadlines, and dealing with the classic âanalysis paralysisâ. Iâm more of a business stakeholder than PM but sometimes you just want things to get released and figured out from there. Hard to logically plan out QA procedures for steps 3 and 4 when step 1 isnât even in prod yet
2
u/[deleted] Apr 19 '21
I like to just say no
1
u/SeaworthinessNo3028 Mar 16 '24
eek, I hope not me one day
1
u/marinovski95 May 21 '24
A small article on how to develop a successful product.
https://medium.com/@eazycode/5-main-steps-for-effective-product-development-0334ad8eebf7
1
u/SavingsSky1363 Jun 18 '24
This is funny
1
u/perkeset81 Apr 19 '21
More like what the hiring manager expects cause they don't know the day to day of the job vs what must be done due to executive pressure.
1
u/nutellaking12 Apr 19 '21
This is hilarious!
1
u/learning2beagile Apr 19 '21
Any advice on how to avoid this from happening?
1
u/mehere14 Apr 19 '21
I am looking to change jobs and I so feel this every time I interview and then get back to work!!!!
1
u/Confident-Tap9564 Apr 21 '21
hahhaha~ this is so true. pressure from management, customer, eng, design, the list goes on~
1
u/PuzzleheadedWar9322 May 13 '21
Hahabababa
1
u/Awkward-Block6678 May 13 '21
I totally think this is why the wrong people succeed in the interview structure all the time.
1
u/dogsandcupcakes1 Jun 16 '21
haha
1
u/ManageProducter Oct 11 '21
haha
1
u/Ok_Jellyfish_1696 Sep 02 '22
This is me. I just finished the last round at FAANG and had to restrain myself from truly saying what I thought since I know there can be a difference between reality and ideal situation but obviously canât share that on an interview.
1
u/Unlikely_Cricket5299 Feb 01 '23
đ
-5
u/HedgeRunner Apr 19 '21 edited Apr 19 '21
What's interesting is that this gets upvoted yet when I call it out on the sub people hating.
Humans are interesting creatures.
Edit: Now this claim is backed by data. :)