Skip to main content
Tweeted twitter.com/StackWorkplace/status/849293198648373250
added info from removed comments
Source Link
Lilienthal
  • 59.4k
  • 42
  • 220
  • 255

My employer is hiring a CTO, mostly to manage ourmy development team --of four developers. Soon we have an one-to-one introduction with him. I was wondering if that's a good time to mention the problems I have had inside the team or it's better to wait for another chance?

If it's okay to mention those problems so early, how and to what extend should I explain them without sounding like I'm back-stabbing my team mates?

I have previously raised these problems with the lead developer, the company's director and the CEO/founder of the company as well, but they still persist. Presumably one of the reasons for the company to hire a CTO is to address those persisting problems.

My employer is hiring a CTO, mostly to manage our development team -- four developers. Soon we have an one-to-one introduction with him. I was wondering if that's a good time to mention the problems I have had inside the team or it's better to wait for another chance?

If it's okay to mention those problems so early, how and to what extend should I explain them without sounding like I'm back-stabbing my team mates?

My employer is hiring a CTO, mostly to manage my development team of four developers. Soon we have an one-to-one introduction with him. I was wondering if that's a good time to mention the problems I have had inside the team or it's better to wait for another chance?

If it's okay to mention those problems so early, how and to what extend should I explain them without sounding like I'm back-stabbing my team mates?

I have previously raised these problems with the lead developer, the company's director and the CEO/founder of the company as well, but they still persist. Presumably one of the reasons for the company to hire a CTO is to address those persisting problems.

Source Link
Mahdi
  • 123
  • 4

First time meeting with the new CTO, should I mention my existing team-wise problems?

My employer is hiring a CTO, mostly to manage our development team -- four developers. Soon we have an one-to-one introduction with him. I was wondering if that's a good time to mention the problems I have had inside the team or it's better to wait for another chance?

If it's okay to mention those problems so early, how and to what extend should I explain them without sounding like I'm back-stabbing my team mates?