Techie Says He Was Suddenly Asked To Resign After 9 Months Despite No Warning: ‘I Thought Things Were Fine’

A young web developer says he was abruptly asked to resign just nine months into a startup role, despite receiving no prior performance warnings. His account, shared online, has reignited discussions about sudden exits, the value of timely feedback, and whether such decisions sometimes reflect broader restructuring rather than individual shortcomings.

A Sudden Exit After Probation

According to his post, the developer joined a mid-sized startup through an off-campus opportunity at a salary of Rs 8 lakh per annum. The early months were tough: a few teammates allegedly minimized his contributions, which dented his confidence as he compared himself to more experienced developers. Still, after completing probation, he felt he was settling in and had not received formal warnings or concrete signals that his role was at risk.

That changed on a Monday when he was called into a meeting and told he wasn’t meeting his manager’s expectations. He was asked to resign by Wednesday and hand over his work. The speed of the decision—and the absence of documented feedback—left him questioning whether performance was the sole reason.

Others Put on PIP the Same Day

Compounding his confusion, he said two or three colleagues were placed on performance improvement plans (PIPs) on the same day. Some of them, he noted, had previously criticized his output. Seeing multiple teammates flagged at once led him to wonder whether the team was undergoing a broader shake-up or cost-cutting effort rather than handling isolated performance issues.

Early-Career Insecurities and Missed Campus Placements

He also reflected on the pressures he felt as a recent graduate. While some teammates had graduated in 2020–21—when campus placements were stronger—he completed his graduation in 2025 and did not land a campus offer, securing this role roughly four months later. Repeated comments implying he wasn’t contributing enough eroded his confidence. He acknowledged gaps in his skill set and said he never considered himself the best developer on the team, but he wished he had received clear, actionable feedback and improvement targets before being asked to leave.

Community Reactions: Cost-Cutting or Communication Gap?

Reactions to the post were mixed. Some readers suggested that abrupt exits often stem from headcount reductions or budget mandates, especially if multiple people are affected in a short timeframe. Others noted that, without specific performance data, it’s impossible to determine whether the issue was individual performance, team dysfunction, or organizational change. Several commenters offered practical advice: seek written reasons and separation terms, maintain a record of offers, payslips, reviews, tickets, and feedback, and frame the experience neutrally in future interviews by emphasizing completed work and learnings rather than the manner of exit.

Practical Takeaways for Early-Career Professionals

• Request clarity in writing: Ask for specific feedback, documented expectations, and any improvement plan details (metrics, timelines, mentorship).
• Document your work: Keep copies of performance reviews, task tickets, code contributions, and any kudos or positive feedback.
• Clarify separation terms: Confirm last working day, handover scope, payout details, benefits, and references in writing.
• Prepare your narrative: In interviews, present the role as an early-career experience that ended unexpectedly; focus on concrete deliverables and what you learned.
• Close skills gaps: Seek mentorship, set a 60–90 day plan to upskill on the frameworks, tooling, or engineering practices used in your target roles.
• Stay professional: Avoid blaming colleagues publicly; keep communication factual and respectful to protect future opportunities.

The Bigger Picture

Startups can move quickly—sometimes too quickly for well-structured feedback cycles. When teams face cost constraints or shifting priorities, managers might consolidate roles or raise performance bars without fully communicating expectations. For employees, silence or vague feedback can be as damaging as negative feedback, because it prevents course correction. This case highlights why organizations should provide timely, specific guidance and why employees benefit from proactively seeking clarity and documenting their progress.

Whether this developer’s exit was due to performance, team dynamics, or a broader restructuring, his story underscores a familiar reality for early-career tech workers: clear expectations, consistent coaching, and transparent processes are essential—not only for fairness, but for building confidence and sustainable growth.