PRO WORKSHOP (ProductWorld): How to Fail Big at Being a Tech Lead


Mihaela-Roxana Ghidersa
Strongbytes, Technical Lead

Software developer and technology passionate- I enjoy building and delivering quality, all the while trying to have fun as much as possible. I am a perceptive and innovative individual that's not afraid to exploit its best version and go the extra mile outside the comfort zone of conventional. This exact desire, of getting out of the comfort zone, led me in the last years to changing the context from full-stack, frontend, API design to technical leadership and architecture. 

Bogdan Sucaciu
Tech Lead | Author

Tech Lead by day, Author by night, Bogdan likes to experiment with cutting-edge technologies and teach about them. His favorite talking subjects are streaming data, event-driven architectures, distributed systems, and cloud technologies. 


Although leadership skills have been analyzed for so long, there is something in the way we choose and raise our technical leads that defy all laws. We often think that the brightest and most creative person in the team will eventually become a technical lead, which actually happens in most cases. The exciting part, though, the process of becoming a technical lead starts when we actually take over the role. What seemed to be a gratification for excellent results can become a long list of failures if you don’t really, really prepare for the challenge. Luckily we can learn from each other’s mistakes, so join us to touch some hot spots in the technical leadership journey.