So, you're looking for a new job, right?
Yep. There is a gig right down the street from where I will be moving. (Bought a house). I qualify for 80% of what they asking. The other 20% I never even heard of, never mind actually know.
- 2
So, you're looking for a new job, right?
Are you the Avaya guy or the Cisco guy?


Avaya.
Ever thought about becoming an Avaya implementation engineer at a local or national Avaya re-seller? I'm sure you could make bank doing that.
Isn't Avaya spiraling down the drain? I'd recommend learning another companies technologies.

Was thinking the same thing when I first saw Avaya mentioned. Although I still have to power up Business Element Manager and Avaya Site Administration now and then we have mostly moved to CUCM. Wouldn't expect Avaya to be bought up by Nortel though since Nortel went bankrupt years ago and most of their tech was acquired by Avaya... Pretty sure what's left of Nortel is still being sued by the canadian govt.Haha, I almost typed that he needs to learn Cisco Telephony (UC) or switching from the other guy and then use that to become a Cisco delivery engineer since he is guaranteed work for the foreseeable future and Avaya just went bankrupt. SeriouslyBrahma , if you are within 10 years of retirement you might be fine; but I already see Avaya clients fleeing to Cisco or MyTel because of the uncertanty around their future. Worst case is one of the giants like Dell/EMC or a Nortel buys them in a fire sale.
Pretty sure what's left of Nortel is still being sued by the canadian govt.
Was thinking the same thing when I first saw Avaya mentioned. Although I still have to power up Business Element Manager and Avaya Site Administration now and then we have mostly moved to CUCM. Wouldn't expect Avaya to be bought up by Nortel though since Nortel went bankrupt years ago and most of their tech was acquired by Avaya... Pretty sure what's left of Nortel is still being sued by the canadian govt.
Sorry for the necro:
Going into a meeting in 30 minutes. I have a co-worker that has the same title as me, but his skill level is a couple notches below mine. He caused a major outage because of his laziness. (estimated a few million lost) During my RCA I figured out what and who the problem was. IF I call him out he might get fired. If I don't call him out I am blatantly lying, and my co-workers will know I am lying, because my RCA won't make sense. I then need to worry about someone going back to my VP with this analysis.
I do NOT like this guy for professional reasons. But he's a good person.
I call him out my team will see me as a sell out?
I am NOT a person to fuck with peoples careers or money this way. But I do my job when told. I try and be professional.
Quick thoughts?
IMO explain the situation exactly as it happened. Provide the name when asked but don't dwell on it. I always take the approach of 'shit happens' when dealing with outages and explaining to superiors. I always try to focus on resolution and future steps to prevent it from happening again. It is their decision as to whether or not they need to come down on this guy, not yours. In my experience if you report without judgement, you'll be fine. If he's incompetent it should come out in the problem/resolution description without you blatantly pointing a finger.Sorry for the necro:
Going into a meeting in 30 minutes. I have a co-worker that has the same title as me, but his skill level is a couple notches below mine. He caused a major outage because of his laziness. (estimated a few million lost) During my RCA I figured out what and who the problem was. IF I call him out he might get fired. If I don't call him out I am blatantly lying, and my co-workers will know I am lying, because my RCA won't make sense. I then need to worry about someone going back to my VP with this analysis.
I do NOT like this guy for professional reasons. But he's a good person.
I call him out my team will see me as a sell out?
I am NOT a person to fuck with peoples careers or money this way. But I do my job when told. I try and be professional.
Quick thoughts?
This is pretty much my approach when covering my ass and throwing someone under the bus. Just be diplomatic about it, but at the end of the day, you have to protect your interests above pretty much all else.IMO explain the situation exactly as it happened. Provide the name when asked but don't dwell on it. I always take the approach of 'shit happens' when dealing with outages and explaining to superiors. I always try to focus on resolution and future steps to prevent it from happening again. It is their decision as to whether or not they need to come down on this guy, not yours. In my experience if you report without judgement, you'll be fine. If he's incompetent it should come out in the problem/resolution description without you blatantly pointing a finger.
Depends on the culture though I imagine
