4.5 Years in One Project: How to Burn Out (and Not Burn Out)

Today, the IT industry is dominated by the idea of rapid job rotation: if a project gets difficult — leave. I followed this myself, changing companies every 1-2 years as a programmer and project manager. However, working on a long-term project changed my perspective.

In this talk, I'll share my experience as a system analyst on a bank's document generation product. We evolved from 4 people to two teams (10 each), building complex business logic, integrations, and proprietary client platforms. I grew from junior to middle+, experienced multiple burnouts, took on excessive responsibility, and rethought my role.

This isn't about “enduring at any cost.” It's about why you sometimes shouldn't leave at first difficulty, how to tell a dead-end from a growth point, and what truly maintains motivation.

This talk is for analysts who are unsure whether to stay or to look for something new.



Comments ({{Comments.length}})
  • {{comment.AuthorFullName}}
    {{comment.AuthorInfo}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to

or
Chat with us, we are online!