Pros
Nothing I can really think of, the only pro here is that you gain so much experience in a short duration of time due to the amount of tasks that you will have to do.
Cons
The biggest issue at this company is the project management team. A lot of PMs simply aren’t technical enough to be making decisions about scope and timelines, yet they’re the ones committing to deadlines. Work regularly gets approved without a real understanding of how complex it actually is, just to satisfy the CEO.
This creates nonstop crunch for developers, rushed implementations, and bugs that could’ve been easily avoided…when things inevitably break, the frustration somehow lands on engineering—even though the root cause is poor planning and PMs refusing to push back on unrealistic expectations. Instead of protecting the team and the product, PMs mostly act as pressure conduits.
The company doesn’t need more PMs. It needs fewer, genuinely technical leaders who can say “no,” plan properly, and prioritize long-term quality over rushed demos. Shipping unstable software to hit unrealistic deadlines hurts both the codebase and client trust.
It’s especially frustrating because there’s real talent here when it comes to developers and genuinely interesting projects. Unfortunately, the current management style has already burned people out and pushed good engineers to leave. Without a serious rethink of how project management works, these problems will never go away. Hence why I suggest, that, if you join here as a dev, leave AS SOON as you think you have hit a knowledge ceiling. The PMs here are bound to stay because they are the perfect yes men for the unfortunate gullible CEO.