Current Events > Yesterday was my last day at the job... Weird situation today...

(+) Yeah! (+)

I don't start my new job until January 6th, so I'm just enjoying free time and getting stuff ready to move to the new apartment. Not even a full day into my free time, I get a call from the guy who took over my role... I told him to call me if something major happened and he couldn't figure it out.

What he was calling about was incredibly basic... Like... incredibly basic and he hadn't even tried to start troubleshooting before calling me. I'm kinda frustrated, lol. I probably shouldn't have answered at all.

---

Should probably tell him that.

Don't answer anymore, you aren't getting paid to train this dude.

---

That persons burdens probably made them incapable.

---

CableZL posted...

I don't start my new job until January 6th, so I'm just enjoying free time and getting stuff ready to move to the new apartment. Not even a full day into my free time, I get a call from the guy who took over my role... I told him to call me if something major happened and he couldn't figure it out.

What he was calling about was incredibly basic... Like... incredibly basic and he hadn't even tried to start troubleshooting before calling me. I'm kinda frustrated, lol. I probably shouldn't have answered at all.

Sounds like not your fucking problem. Tell you'll fix it, but you are going to charge them a consulting fee of 150 dollars an hour, with a minimum billing of 2 hours.

---

Godnorgosh posted...

Company gets what they pay for. If they wanted to keep you they should have made you a strong counter offer or scaled up their IT department so you wouldn't be so overwhelmed.

And see, I was trying to paint this picture to explain this issue to the old director of IT operations. He wouldn't listen and refused to expand the team. From April to November I was doing 60 - 70+ hour weeks every week. So I asked for a raise. They didn't give me the dollar amount I wanted, so I started looking for other jobs.

The new company didn't meet the dollar amount either, but they have proper support infrastructure in place so that their network engineering team... Yes, team... doesn't work 50+ hours at all unless something crazy happens. And even then, if they have to work late, they get to go home early or come in late the next day to make up for that.

I applied at this new job, then the director of IT operations left the company, but... I'm just not willing to wait for the new CIO to fix the staffing levels at this point.

---

Future_Trunks posted...

Youre like not supposed to answer anymore lol wtf you doing

I know, but this is pretty much a major adjustment for me mentally. I built so much of the network and I know the network like the back of my hand, so I'm having to adjust to:

1) My phone being so silent and not getting alerts and messages from people with network requests all the time
2) Not having to bring a laptop with me everywhere I go
3) Having the entire day to myself

It's a weird thing... Not sure why I put up with being so overworked for so long. I actively refused to go to other companies because I was hoping it would go back to being an awesome place to work like it used to be... But it just didn't, so I'm out.

---

Godnorgosh posted...

Sometimes companies have to find out the hard way. My current company doesn't pay competitively or give raises for the experience we're getting here, and so they've been bleeding techs left and right. A bunch of us are actually moving on and getting engineer-level positions at other companies, including me. Upper management just doesn't get the picture, or they do and they just don't care until after it's already impacted them and they've started losing contracts.

Better for me to leave anyway, though.

That's pretty much what's happening at this company, too... The old director of IT operations pretty much screwed all of IT over during his time here. The company is rapidly expanding, but you need to scale IT staff up along with the growth of the company... Because he refused to do that, IT is underwater with trouble tickets and projects...

The company really should have 3 or 4 network engineers instead of just me and a contractor. Or at the very least, two network engineer level guys, 1 junior network engineer, and a network admin... Or some mixture along those lines.

The new CIO is working on fixing that, but I'm not willing to wait any more. I tried to wait long enough. I never expected this new company to hire me, but they're one of the few companies that I would actually leave my old job for regardless of how much I did or didn't like working there.

A few months ago, we lost our security architect and our system admin at the exact same time. This made my job a lot harder. The 3 of us managed the firewalls together, but when they left, all of the firewall management fell to me. I was already swamped with stuff I was working on and it got really rough.

---

Lol if they ain't cutting you a check fuck them.

If he's already calling you about some simple shit you know he's gonna call again.

Unless you think it is a strong possibility you might go back to that place and you gave them proper notice you were quitting then fuck em.

---

CableZL posted...

I told him to call me if something major happened and he couldn't figure it out.

That was a mistake. The next time they call, tell them you changed your mind and you won't work for free.
---

yemmy posted...

Lol if they ain't cutting you a check fuck them.

If he's already calling you about some simple shit you know he's gonna call again.

Unless you think it is a strong possibility you might go back to that place and you gave them proper notice you were quitting then fuck em.

Yeah, I'm definitely not going back. I'm definitely considering just not answering the phone at all at this point.

It amazes me that he's comfortable calling himself a network engineer but he turns his brain off the moment someone asks him about a possible network problem. So much so that he calls someone who doesn't work there any more for help...

Sheesh. That'd be nightmare scenario for me. Maybe I've been selling myself short... I feel like I'm not great at networking because there's sooooo much stuff I don't know that I feel like I should... But I interviewed a couple people who said they were network engineers, but couldn't answer basic network questions... And then this guy who took over my role... He's strong with physical network implementation, but he seems to lack troubleshooting skills, which is pretty bad. He's having to manage the entire network on his own because I just left.

I guess I was covering for him quite a bit in this regard without realizing it.

---

Gotta look out for #1

#1. So I think, the best?

---