What "I Need A New Job" Really Means..
-
@scottalanmiller said:
@handsofqwerty said:
@scottalanmiller said:
@handsofqwerty said:
@Dashrender said:
@scottalanmiller said:
I was way below eighteen months for most of my career.
Where you really employeed or just a contractor?
He's been mostly a contractor. I know that.
But always an employee. It's not either / or.
It's about how you get paid. When I worked at a specific company, I was a contractor for that company, but considered an employee of the recruiter. So if it's that kind of situation, I see how you say both. But it can also be exclusively one or the other.
No it is not.
And you are unaware who your employer was. Check with the IRS. Employment is not as vague as people think. The company directing your work is your employer. The one signing the check is the payroll firm. Who signs your check is effectively irrelevant to employment.
Contractor and employee are normally the same thing. It's an internal designation, not an employment one.
When I received my W2 this year, I was not shown as an employee of the company I was actually doing work for, but rather the recruiter. I was an employee of the contractor but a contractor to my real employer, if that makes sense...
-
@handsofqwerty said:
@scottalanmiller said:
@handsofqwerty said:
@scottalanmiller said:
@handsofqwerty said:
@Dashrender said:
@scottalanmiller said:
I was way below eighteen months for most of my career.
Where you really employeed or just a contractor?
He's been mostly a contractor. I know that.
But always an employee. It's not either / or.
It's about how you get paid. When I worked at a specific company, I was a contractor for that company, but considered an employee of the recruiter. So if it's that kind of situation, I see how you say both. But it can also be exclusively one or the other.
No it is not.
And you are unaware who your employer was. Check with the IRS. Employment is not as vague as people think. The company directing your work is your employer. The one signing the check is the payroll firm. Who signs your check is effectively irrelevant to employment.
Contractor and employee are normally the same thing. It's an internal designation, not an employment one.
When I received my W2 this year, I was not shown as an employee of the company I was actually doing work for, but rather the recruiter. I was an employee of the contractor but a contractor to my real employer, if that makes sense...
And? The employer field on a W2 is a payroll field and not vetoed as the employer. It's not related. Your employer is the one carrying legal employer responsibilities. You can't sue a payroll firm for not paying you, only the employer.
-
The terms contractor and employee are used very loosely in the US. Contractor is not a status in the US. It's a term that people use to describe how their employers see them and how they are reported to Wall St investors. Being or not being a contractor has no effect on employment status.
-
I've had a mix. I've had most of my full time permanent employee jobs last 2-3 years. My Video production/Live Sound stuff for about 10 yrs. Then lots of other stuff, temp contract jobs for 1-3 months here and there. Did two Fast Food jobs for 2months each. Did some commission sales for 2yrs.
Sadly, the contract/temp stuff I have to take off my resume most of the time, it scares employers away. And then even the only 2-3yrs at most of my IT jobs has scared some away, heck even one of them that @scottalanmiller knows turned me down for a job because of the only 2-3yr stay. They said they wanted someone who had worked the same place for more like 7yrs, even if they didn't have that long actually in IT. They did say, they would consider hiring me as a janitor or something and after I get 4 yrs in with them plus get a masters degree they'd consider letting me do more with IT, before that I would only be allowed to plug in mice & keyboards, etc. no actual IT work. They currently don't have any IT staff besides the manager (who has no previous experience) and they contract out IT.
It seems like while the norm is 1-2 years even a bit longer than that hurts you in getting more jobs, and the temp contract stuff really hurts you. Which is bad, considering at least I've found most places, the only way to progress your career is to leave for a new job.
-
It's really tough because a lot of places will count it against you if you don't last two years or more. But I've been almost turned down because I was at a place for eight years and they were concerned about people who had settled.
-
When hiring practices are so poor, there is no reliable path to winning.
-
In my thoughts contractors are people who have to pay the entire FICA amount and don't get things like medical benefits and paid vacation. Example: Scott does contractor work for NTG's clients.
An employee is someone who the company pays the second half (employer portion) of FICA, and often the employees get things like paid time off and medical benefits.
Contractors also don't typically get overtime for working more than 40 hours in a work week, non-exempt employees always do.
Contractors usually have a definitive start and end date (though I know many companies live and die by contractors, so there is no end date). Employees, while they might have a start/end date, this is not the norm.
-
@Dashrender said:
In my thoughts contractors are people who have to pay the entire FICA amount and don't get things like medical benefits and paid vacation. Example: Scott does contractor work for NTG's clients.
That's usually called a 1099 worker or independent contractor.. Not just a contractor.
-
@thecreativeone91 said:
@Dashrender said:
In my thoughts contractors are people who have to pay the entire FICA amount and don't get things like medical benefits and paid vacation. Example: Scott does contractor work for NTG's clients.
That's usually called a 1099 worker or independent contractor.. Not just a contractor.
That's the only way I've ever used the term contractor in the context of my own employment status.
-
@thecreativeone91 said:
@Dashrender said:
In my thoughts contractors are people who have to pay the entire FICA amount and don't get things like medical benefits and paid vacation. Example: Scott does contractor work for NTG's clients.
That's usually called a 1099 worker or independent contractor.. Not just a contractor.
If we're going to bring out all the possible 'contractors' well then we've completely derailed and the discussion is moot.
-
@scottalanmiller said:
Not sure I know many people topping two years someplace anymore.
Blimey. Either things are very different in the US or we move in very different circles as I'd say the majority of my friends have been in their jobs for over two years.
-
@Carnival-Boy said:
@scottalanmiller said:
Not sure I know many people topping two years someplace anymore.
Blimey. Either things are very different in the US or we move in very different circles as I'd say the majority of my friends have been in their jobs for over two years.
Many people in the US don't even stay for 3-5 months. Which is sad but true.
-
@scottalanmiller said:
Not sure I know many people topping two years someplace anymore.
@Carnival-Boy said:
Blimey. Either things are very different in the US or we move in very different circles as I'd say the majority of my friends have been in their jobs for over two years.
@thecreativeone91 said:
Many people in the US don't even stay for 3-5 months. Which is sad but true.
There are many, many that do. In IT I think there is a tendency to shorter stays than other places.
That said, I am in year 7 of employment where I am. But I feel as a consultant that I get a wide range of experience in various things and stay fresh due to the varied clients.
-
@JaredBusch For IT my experience and what I've read elsewhere agrees - usual job term is 1 to 3 years
-
@MattSpeller said:
@JaredBusch For IT my experience and what I've read elsewhere agrees - usual job term is 1 to 3 years
Yeah thats what my Full Time Jobs have been.
-
It depends on the nature of job. I work in ERP, and these projects tend to last several years so I'd struggle to be productive if I kept moving jobs every 2 years.
But as a general rule, I've always thought 5 years is the ideal length of service regardless of the job (IT Support, President of the United States, Football Coach). It takes a couple of years to settle in and get to know the job, then you have a couple of years where you're really productive, and after that you run out of ideas or slack off and it's time to let a new guy have a go.
I've definitely been in my current job too long, but in my defence, the state of the UK economy since 2008 has been poor so staying at a company that is profitable and secure wasn't necessarily a bad move.
The problem with working in IT for an SMB is there is nowhere to go - the only promotion I could get is to CEO and that's never going to happen, so I'm stuck in my current role. If I worked for HP or Ford I could stay there my whole life and get promoted to new positions every few years.
-
I love this quote from Greg Smith:
"Sometimes, when you have been in an organisation a long time, it starts to feel like a student party in the small hours of the morning. All the decent booze has gone, all the interesting people have left or copped off and you suddenly realise that you should have gone home hours ago. At that point, you start to amplify your organisation’s faults and play down its good points; the exact opposite of what you did when you first arrived."
-
@Carnival-Boy said:
I love this quote from Greg Smith:
"Sometimes, when you have been in an organisation a long time, it starts to feel like a student party in the small hours of the morning. All the decent booze has gone, all the interesting people have left or copped off and you suddenly realise that you should have gone home hours ago. At that point, you start to amplify your organisation’s faults and play down its good points; the exact opposite of what you did when you first arrived."
Excellent
-
@Carnival-Boy said:
It depends on the nature of job. I work in ERP, and these projects tend to last several years so I'd struggle to be productive if I kept moving jobs every 2 years.
Outside of call center helpdesk I think few IT jobs can be productive moving too quickly. In the enterprise space, it often takes months to get people trained and often to even get them system access!
-
@Carnival-Boy said:
But as a general rule, I've always thought 5 years is the ideal length of service regardless of the job (IT Support, President of the United States, Football Coach). It takes a couple of years to settle in and get to know the job, then you have a couple of years where you're really productive, and after that you run out of ideas or slack off and it's time to let a new guy have a go.
I did eight years at a job recently and it mostly worked because of there being three major "stages" of my career there so it was a little like having done one job for two years, another for two and another for four - all while in the same firm. But definitely by eight years, things were getting stale and that's why I left when I did. It was time to move on. Good place, but too much of the same thing.
Some firms are designed for people to be around a long time, they are like families, others are more like jobs and not designed to be a permanent thing and those you really need to move on from.
