Comment by joe_mamba
7 hours ago
>But good technical project managers aka "bridges between the higher-up beancounters and the workers" are worth their weight in gold.
Yeah but it's not easy do distinguish those from the snake oil salesmen who are just good at smooth talking during the interviews.
Pretty easy. Get them to talk about a project they've managed and start poking holes. Who was on the team? How did they organize meetings? What were the bottlenecks? How well did everyone get along? What did they do to help grease the gears? Did they have to change the process? How did they like the software? Which software did they use? Did they have to administer it themselves? How did they deal with management changes / team changes / tons of support requests / issues in production? Where did they draw the line between PM work and engineering work?
From witching other managers, and via LLMs, you can literally learn and interview prep for all those questions on and lie. It's not difficult.
People have a very difficult time keeping their story together, especially when they're asked a couple of questions that interview prep didn't cover.
Beyond that though, there's the probation period. If they can't do the job, they're supposed to be let go before they become permanent.
Trouble I see from most interviewers is a tendency of asking questions with a "right" answer. Those tend to be a lot easier to game. They then fallback on sorting applicants by pedigree - the old, "no one ever got fired for choosing IBM" method.
Then, they come back and rant about how PM's are trash, and Agile is trash, etc. etc.
Well if they’ve learned that much it’s a good thing.
The remaining piece is to speak with some personal references to verify they did some real work.
1 reply →