11–20 of 23 posts
Does anyone else feel this way? Curious about your experience and what works for you. I know lots of engineers that are super happy working against solid requirements.
Does anyone else feel this way? Curious about your experience and what works for you. I know lots of engineers that are super happy working against solid requirements.
Would it be sufficient if what is chosen to be built is something you see as a high-value thing to build? Working at a company that is good at setting product directions could be a possible solution.
Does anyone else feel this way? Curious about your experience and what works for you. I know lots of engineers that are super happy working against solid requirements.
The easiest way to do this is to go to a small company where everyone wears multiple hats. 50 people is probably the upper limit.
Consulting companies are ok, but there you pretty much build what clients want. If you can find one that focuses on an interesting domain, that can be a good fit.
At small companies you get to be part time product manager, project manager, customer support, QA, developer, doc writer, and more. Especially if you are relatively senior.
For some folks I know, this is a nightmare. I personally love it. Give it a go!
How can you find such small companies? I'd look in the "Who's hiring" threads and on sites like https://www.builtincolorado.com/ (if they exist for your area). Also, ask in your network.
Does anyone else feel this way? Curious about your experience and what works for you. I know lots of engineers that are super happy working against solid requirements.
Does anyone else feel this way? Curious about your experience and what works for you. I know lots of engineers that are super happy working against solid requirements.
1. The one who tries to reinvent the product and you tend to end up questioning their design or product decisions because they seem flaky and makes no sense. Being a newly promoted lead with my own ideas I was often at loggerheads with them. For anyone who reads this and is in the same position, I would suggest to continue building what the PM asks you to do. Any opposition or pushback you create regarding their choices will just lead to chaos for your team and in the end you would have to go with it since their role is the one making such decisions.
2. The one whose requirement are empty shells waiting to be filled with the questions raising by the people they present it to. I would suggest to get away as far as possible since your requirements will never remain fixed as the PM will be open to suggestions and influences from all over the company and you would end up with a rube goldberg machine.
3. PMs who take time to do research, write down solid requirements, convince stakeholders and also have a iteration based release plan in mind. I worked with only 2-3 PMs like this and based on what I saw, they tend to burn out faster than you do and either quit or regress to type 1 or type 2 just to get the release out.
Having said all this, I would rather be happier working with solid requirements rather than making them. I have played the role of a PM temporarily and found that it is generally a thankless job, regardless of the effort you put in.