Techie shares a tip from another colleague who survived in a nightmare project before he quit

A software engineer, overwhelmed by a toxic project assignment, turned to the popular Indian Workplace subreddit to seek guidance on how to survive the chaos while preserving his peace of mind. He found himself thrust into a high-pressure environment—a project already in a critical state with escalations pouring in from top-level client stakeholders. The situation was grim: unrealistic timelines, weekend work norms, widespread internal politics, and a string of resignations that left him holding the reins.

Though committed to staying at the company for another four to five months before planning an exit, his primary goal was clear—protecting his mental well-being and drawing a clear boundary between professional obligations and personal time.

He identified himself as someone who always completes tasks punctually, takes ownership without shifting blame, avoids office politics, and behaves responsibly. But the current assignment was testing his limits. Luckily, several experienced users on the subreddit chimed in with tried-and-tested survival strategies to weather the storm.

One suggestion stood out for its simplicity yet effectiveness: never proactively submit your deliverables unless someone specifically asks for them—regardless of whether the work is finished early or late. This simple boundary-setting technique helps avoid becoming the go-to person for every firefighting task.

Another user shared their own frustration and declared that being technically capable should not be an invitation to carry the burden of an entire team. Despite being just one of eleven team members, they constantly had to clean up others’ errors. They firmly told their project manager that they were not the team lead and would no longer be stepping in to manage others’ responsibilities. Their method? Ignore irrelevant team emails, avoid unnecessary collaboration, and prioritize personal boundaries over office drama.

A more strategic approach was suggested by someone who has been in the IT industry for more than seven years. They advised the original poster to intentionally downplay their skills to avoid being assigned more complex and time-consuming tasks. Their method of “quiet quitting” involves subtle tactics like delaying submission of completed work, avoiding proactive involvement, and not volunteering for unpleasant or neglected assignments. They warned against falling into the trap of trying to be the workplace savior.

Additional insights poured in as well. Document everything—every task, conversation, and milestone. Do your job and leave on time; your colleagues are not your close companions. Share only what’s necessary, especially when it comes to your personal life. If you make a mistake, don’t dwell on it—reflect, adapt, and move ahead. Before starting any task, ask all the questions you need. It’s better to clarify expectations up front than scramble at the last minute due to miscommunication.

Lastly, a gentle reminder from a seasoned contributor emphasized the value of humility. Even when the workplace feels cutthroat, treating juniors with kindness and basic respect doesn’t cost anything—and it can make the environment a little more humane.

Through these shared experiences, this overwhelmed engineer found not just survival tactics but a sense of solidarity—proof that many others are walking the same tightrope between work demands and personal sanity.