Lessons learned: quitting after one month on the job

docrice

I debated whether to write about this or not, but figured some might learn from my professional failure in this regard.

A month and a half ago, I went from working at a relatively small tech company after eight years to a huge Fortune 100. It was a longer commute, but better pay, a good team of co-workers who cared about their work, and the "big company experience." The only downside was that it's a less hands-on type of role (more auditing than infrastructure engineering).

However, a couple of weeks into the new position I started to realize that my passion for doing the low-level work (reading wire traffic, pushing the firewall buttons, etc.) was starting to tap me on the shoulder heavily. Going from a small company to an immense one also comes with a huge corporate culture change that one must adapt to. Some might not be bothered by this. I was.

So it became inevitable that I needed to switch jobs before my new employer invested too much more into me. I gave my two-week notice recently. They, of course, were disappointed. You can't blame them since it takes a long while (maybe a year?) for an employer to get their ROI on a new-hire, plus now they need to restart the process over again in finding someone (getting the requisition approved, sifting through resumes, interviewing, waiting for another hire to come onboard, etc.). A bad decision on my part costs both parties in ways that aren't always obvious.

In short, I feel terrible ... and rightfully so. While we can say that "at-will" employment is what it is and companies terminate good people all the time for whatever reason, I'm more concerned about how I let my new (now former) team down. They're a good group of folks who don't really deserve this kind of professional disrespect. The only way to positively spin this is that they perhaps lost an analyst who could have potentially turned out to be mediocre. Good riddance?

The upside (for me anyways) is that I'm moving to a much smaller company whose business model completely revolves around information security for which I'll be a network security engineer doing firewalls, bad-guy detection / prevention, network monitoring, and incident response. Pretty much a dream job with a group of people in the SOC who I've worked with at another company. Ironically, I was actually offered this role right before I started my (now-previous) job, but since I had already committed to my now-former employer, I initially turned it down.

Still, it doesn't alleviate the guilt I'm feeling. So my lesson here is that when you consider moving into a new position, understand your real needs and don't jump ship just because of working environment tangibles. It's hard though, as sometimes you don't know what you're missing until you really start missing it.

Turgon

docrice wrote: »

I debated whether to write about this or not, but figured some might learn from my professional failure in this regard.

A month and a half ago, I went from working at a relatively small tech company after eight years to a huge Fortune 100. It was a longer commute, but better pay, a good team of co-workers who cared about their work, and the "big company experience." The only downside was that it's a less hands-on type of role (more auditing than infrastructure engineering).

However, a couple of weeks into the new position I started to realize that my passion for doing the low-level work (reading wire traffic, pushing the firewall buttons, etc.) was starting to tap me on the shoulder heavily. Going from a small company to an immense one also comes with a huge corporate culture change that one must adapt to. Some might not be bothered by this. I was.

So it became inevitable that I needed to switch jobs before my new employer invested too much more into me. I gave my two-week notice recently. They, of course, were disappointed. You can't blame them since it takes a long while (maybe a year?) for an employer to get their ROI on a new-hire, plus now they need to restart the process over again in finding someone (getting the requisition approved, sifting through resumes, interviewing, waiting for another hire to come onboard, etc.). A bad decision on my part costs both parties in ways that aren't always obvious.

In short, I feel terrible ... and rightfully so. While we can say that "at-will" employment is what it is and companies terminate good people all the time for whatever reason, I'm more concerned about how I let my new (now former) team down. They're a good group of folks who don't really deserve this kind of professional disrespect. The only way to positively spin this is that they perhaps lost an analyst who could have potentially turned out to be mediocre. Good riddance?

The upside (for me anyways) is that I'm moving to a much smaller company whose business model completely revolves around information security for which I'll be a network security engineer doing firewalls, bad-guy detection / prevention, network monitoring, and incident response. Pretty much a dream job with a group of people in the SOC who I've worked with at another company. Ironically, I was actually offered this role right before I started my (now-previous) job, but since I had already committed to my now-former employer, I initially turned it down.

Still, it doesn't alleviate the guilt I'm feeling. So my lesson here is that when you consider moving into a new position, understand your real needs and don't jump ship just because of working environment tangibles. It's hard though, as sometimes you don't know what you're missing until you really start missing it.

I wouldn't pick the bones out of it. The main thing is you made the decision and have got fixed up with a new job quickly. Just make sure you dont bail on this one so quickly so you can get some continuity back on your CV. Everyone is entitled to a job that didn't work out and that doesn't necessarily mean you were not up to the job or anything like that. If a job really doesn't feel right, particularly a new one after a month then you may need to look elsewhere. Unhappy new people are rarely productive in the long run.

powerfool

Yeah, don't feel too bad... it happens. I had the same thing happen to me when I moved to my current job. I was downsized from my previous job and I needed to find something. I was offered a position as an indefinite contractor for a pretty good company... it was essentially a permanent position, but they couldn't get it approved as one... not a big deal, about a 1/3 of the IT staff were contractors. Anyhow, I had already been in the works with the current employer, but there was a delay for the security clearance process, and I wasn't sure about it due to a lot of medical bills for my wife. After being there for three weeks, I was cleared and I really couldn't pass up the opportunity at my current employer.

DPG

Don't feel guilty. Business is business.

Both you and your employer took the same risk in the fact that either party could terminate your employment at any time if it was in their best interests.

MrRyte

The job that you had wasn't what you were expecting. You were professional enough to give them two-weeks notice so they shouldn't knock you for that. You did the right thing so no point in dwelling on "feeling guilty". Besides; do you think they'd feel guilty if they gave you a pink slip without warning or reason?