How long is too long?
-
No cut and dry. It's about when the position isn't helping you grow (or retire).
Twenty years is too short if the job is right. But the wrong job you should leave after the first day.
-
For an average job, three years is a decent guide. But certainly "it depends".
-
I've been on the average of 3 years for most of my positions. Some a bit longer, but 3 years seems to be where it is for my record.
-
Companies that move you around internally get a lot more years than those that keep you in one role.
-
I'm leaving here after 2. My last job was 6 years. Like everyone says...it depends.
-
I left one job after 9 months. Next job said "that's good, we like to see people who are strong enough to hold out for a year there, but won't hire anyone so foolish as to stay for two."
-
Man.... Not a single "that's what she said" joke on this thread. I am disappoint.
-
@RojoLoco said in How long is too long?:
Man.... Not a single "that's what she said" joke on this thread. I am disappoint.
we can, very occasionally, be actually serious for an entire thread.
-
@JaredBusch said in How long is too long?:
@RojoLoco said in How long is too long?:
Man.... Not a single "that's what she said" joke on this thread. I am disappoint.
we can, very occasionally, be actually serious for an entire thread.
Now that I've seen it, I believe you.
-
@JaredBusch said in How long is too long?:
@RojoLoco said in How long is too long?:
Man.... Not a single "that's what she said" joke on this thread. I am disappoint.
we can, very occasionally, be actually serious for an entire thread.
It's early yet on this one though
-
@NerdyDad said in How long is too long?:
I would, someday, like to become an IT Manager, but am enjoying tinkering with the servers still.
So let's start with three things....
- How do you define "IT Manager" because that could mean any of several pretty standard things from "lone IT guy in charge of an SMB" to "Mid level personnel manager in an enterprise with zero technical responsibilities" with several things in between.
- How far are you from your goal now?
- How is your current job pushing you towards that goal.
-
Then once we define those things, we can start figuring out if and when the current job starts to Peter out and what the next job might hopefully look like as a reason next "hop" along the path.
-
An advantage to an MSP like Bundy or NTG is that we tend to see a wide variety of tasks (vertical experience) and technologies (horizontal experience) either day to day or year to year and tend to have some degree or either mentor or peer support internally. So in an environment like that, you can shift up the career ladder differently than say in an SMB where there is one or two roles to fill and no matter how good you are, you are just really killing that one role.
-
@scottalanmiller said in How long is too long?:
Companies that move you around internally get a lot more years than those that keep you in one role.
Yeah, I've never had this happen personally, but would be complete fine with it.
But when things become stagnant, and there is no opportunity to either grow or learn something else its time to search.
-
I really don't have any major career "goals". Main goal is to keep the family fed and with a roof over their heads.
A couple of aspirations would be
- The head guy in the IT department, including Policy Writing, Financials, along with being in the trenches, if necessary, but not being the only guy in IT in the company, but being the head guy in the IT in the company.
- Being a consultant for server solutions and IT holistically.
A couple of things that I have already taken care of since starting here
- Going from XS to VMware (don't hate me everybody, but it had to be done).
- Move from Symantec Backup Exec to Veeam for better backups
- Established a colocation for a better DR plan
A couple of things left on my to-do list
- Get all servers up to date
- No legacy servers older than 3-5 years old.
- Clean up GPO
- Establish WSUS (again)
- Establish a licensing server for MS
- Learn PS
- Possibly VDI
- Establish WDS
- Possibly escalate System Normalization to at least level 2, if not 3
-
Did anyone mention "career stage" in this discussion? Wouldn't it make sense that earlier in your career that the numbers should be smaller and later in your career that they would get longer? LIke your first job might be 9 months. Your second a year and a half. Your third is three years. Your fourth is five years. And on and on?
-
I am the "IT Manager" = "lone IT guy in charge of an SMB" sometimes i feel like GOD and sometimes i want to hide and cry under my desk...
-
It's cool that your goals are clear to you. That's the first step. So now, you're in a great spot to ask yourself, "What do I need to do today to get where I want to be tomorrow?" You can map out your self learning plan and look for opportunities for growth.
-
I've gone:
- 9 month contract.
- 2 years, one company, then promotion, 2 years again after promotion.
- 1 year at MSP.
- 1 year where I am now.
(I'd say for me, 1 - 1.5 years max anywhere).
-
@Jimmy9008 said in How long is too long?:
I've gone:
- 9 month contract.
- 2 years, one company, then promotion, 2 years again after promotion.
- 1 year at MSP.
- 1 year where I am now.
(I'd say for me, 1 - 1.5 years max anywhere).
I did something like 40 different jobs (all contract plus one startup that went out of business) in my first three years of really active IT work. And even after that, it was only one every year or two. I did a 15 month stint at Dell that was a really big deal for me early on.
