Should I continue working in current project or look for other company or project within company?
I'm currently working in a product which was ramped down from 19 members to 5. All remaining 5 are new to product.
Current state is:
- We get lots of escalation, and it's good learning in solving them. However, pressure is enormous and also less work life balance, due to Severity 1 issues at times.
- There is no feature development for now, mainly due to less bandwidth and also all new folks in team, who are ramping up.
- There are other priorities like Maintainence of services/system (DevOps), Security, Integration with other products, minor must do feature enhancements reported by customer
- Customers are dropping because we are at times not able to provide the enhancements asked in stipulated time
When i initially started with this project, I thought it would slow down, but there are spikes at times which results in working at whole weekends (Happened four times in 2 months).
Should I leave this product and try to move to other product or company where i should look for balanced work and timeline, product with active development or continue in current one with an hope it would slow down in near future?
![Senior Software Engineer [E5] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta.jpeg%3Falt%3Dmedia%26token%3Da7a5bcc0-e178-4b5b-b71e-09bf6c6aefae&w=48&q=75){kind=small}
![Entry-Level Software Engineer [L3] at Google company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fgoogle.jpeg%3Falt%3Dmedia%26token%3D780356ef-3efc-4728-9eb4-d909b75bb4a6&w=48&q=75){kind=small}
Discussion
(1 comment)- 5
a year agoAndroid Engineer @ RobinhoodMy high level view of your situation seems like the system the product is built in isn't sustainable, which is bleeding into developer bandwidth which then means that developers have less bandwidth to deal with customer concerns.
I don't have the full picture (since I'm not directly in the weeds with you), but have you looked into fixing the issues at a systemic level? If escalations and SEVs are happening frequently to drain developer bandwidth, there should be enough data for some common themes to be extrapolated. Especially when customers are dropping because developer bandwidth goes to responding to these issues & not into feature development, then there's urgency from the business side to recitfy systemic issues (since the raw $ value of the lost customers can be quantified & we just need to sum them up).
If you've already taken attempts to identify and scope out fixes to systemic issues without any support from management, then I'd say you should to switch teams or companies.
