Related Posts
Hi fishes,
I have 4.5 years of experience in .net and angular in cognizant I'm working I got call from Genpact but In Genpact they are asking me join as lead consultant is it normal software engineer position or what any idea ..for only 4.5exp is it sufficient for lead consultant position.. firstly what is the responsibilities for lead consultant in GenpactGenpact
More Posts
Aws L6 in BD, NYC area salary?
Can anyone refer me in Accenture ?
Any good laser removal place near ues?
Additional Posts in Product Management
New to Fishbowl?
unlock all discussions on Fishbowl.




Subject Expert
Definitely option B from my perspective. Always cool to work from the start of a product. The work will be more interesting and the experience more meaningful. I’d also be very wary of joining something where I heard ahead of time leadership is questionable.
Surely Option B. Though not enough data from your post but I strongly felt that option B is outside the comfort zone and also flexibility for you to set up PM process and artifacts that can be used by the team. Also, lot of learn/ unlearn as you progress.
Hello friends ! Thank you all for the thoughts and input! I’m here to say I officially accepted the offer with Option B and I am SO excited and grateful!
Woohoo!!! Enjoy the ride 🙂
Congrats! I would also second the response above ^^. Working on the early days of defining a product is a very cool and exciting experience. Do you know what the competition looks like in the market? If you’re just copying a competitor it may not be as rewarding...
Option B :)
Probably B, BUT - important to weigh all the specifics you know (that we don’t) about how successful you think each team can be within the organization. All else being equal, you’d rather own something new from 0 to 1. But if you think this new team might not have enough support internally, or might get killed if it doesn’t show enough early wins, or if for any reason you have the spidey sense that the team will have trouble succeeding, then you’d rather launch some improvements and features on an existing team that has full organizational support than flounder on a project that doesn’t go anywhere (i saw this happen recently at a known tech company who were trying to explore something new but weren’t actually prepared to fully support it, and the team sputtered out and no one had anything to show for it).
Option B gives you the opportunity to shape the relationship and be an influencer. It is difficult going into an established team that may have been some issues previosly. On Option A I would ask why the last PM left.
Option B jumps out. There are many positives there and not those negatives (bad leadership is non-starter for me and also limits your ability to shine.)
Bowl Leader
Had the same decision to make 4 months ago. Went with option B and it had been absolutely awesome. I’ve upskilled myself in strategy and management significantly because it was needed for the job, which for me is way more exciting work than technical project mgmt.
Less established team B. Enjoy! This is an exciting time.