that sounds awfulit's not even about networking. showing that you're engaged with the company is important. i manage people who do exactly what you do. if they blow off work events for soccer games, they aren't going to have a great future under me unless they drastically change their tune.
No.Is being invited to a co-workers house for a team dinner normal in the U.S.? I don't think I've ever heard of that happening over here.
And that is fine.being a "low rung code writer" is still better than the vast majority of jobs, so I'm fine with that
there are plenty of perfectly legitimate reasons to not do something work-related off hours. you've provided one that puts you in the category of "doesn't care".that sounds awfulit's not even about networking. showing that you're engaged with the company is important. i manage people who do exactly what you do. if they blow off work events for soccer games, they aren't going to have a great future under me unless they drastically change their tune.
I don't want my work to dictate my life. Maybe it's because I'm young and stupid but that's where I am right now
We've passed on hiring because of that, tbh. Frequent job hoppers have a negative perception unless it can be explained with contract work.Again, if you want to be a low rung code writer for most of your career, that is fine. If you want to move up in the world, then when people start seeing constant job changes, red flags are going to go up.also, I think you guys are selling how in demand software engineers are in general. I had almost no problem finding this job (After only a year at my previous position) and don't think I would have any problem finding another one if something goes wrong
Get an IT job at a University that covers you under a union. You won't ever be bothered before/after your set hours.that sounds awfulit's not even about networking. showing that you're engaged with the company is important. i manage people who do exactly what you do. if they blow off work events for soccer games, they aren't going to have a great future under me unless they drastically change their tune.
I don't want my work to dictate my life. Maybe it's because I'm young and stupid but that's where I am right now
No.Is being invited to a co-workers house for a team dinner normal in the U.S.? I don't think I've ever heard of that happening over here.
Luncheon, sure. Dinner at a residence during off hours? Abnormal.
I read something recently that people who don't job hop after 4-5 years are viewed as unmotivated.We've passed on hiring because of that, tbh. Frequent job hoppers have a negative perception unless it can be explained with contract work.Again, if you want to be a low rung code writer for most of your career, that is fine. If you want to move up in the world, then when people start seeing constant job changes, red flags are going to go up.also, I think you guys are selling how in demand software engineers are in general. I had almost no problem finding this job (After only a year at my previous position) and don't think I would have any problem finding another one if something goes wrong
There are laws protecting children in the US too, you know?No.Is being invited to a co-workers house for a team dinner normal in the U.S.? I don't think I've ever heard of that happening over here.
Luncheon, sure. Dinner at a residence during off hours? Abnormal.
Maybe this is just a ploy so the manager can get MIMH into bed?
That's a lot extreme.If I held a dinner at my house for co-workers and one did what you did, I'd try like hell to get you removed from the company - for several reasons.
You obviously aren't committed to the company. You are choosing beer league soccer over a team-building exercise for a major company product.
You are a software developer. There are approximately 1 billion other software developers out there to replace you.
Our company encourages switching jobs within the company every 3-4 years. It is unfavorably viewed if you have the same position for a long period of time for the reason you state.I read something recently that people who don't job hop after 4-5 years are viewed as unmotivated.
Mrs Tif has been to about a dozen of them in the past two years.Dinner at a residence during off hours? Abnormal.
Some of the most successful people I've worked with have often told me they view their careers in 5 year chunks. Some of them have been at the same place for 30 years, because they met internal career bogeys that resulted in new 5-year targets being put into place while keeping the same job. Some of them have been at 3 or 4 different places over 15-20 years.I read something recently that people who don't job hop after 4-5 years are viewed as unmotivated.We've passed on hiring because of that, tbh. Frequent job hoppers have a negative perception unless it can be explained with contract work.Again, if you want to be a low rung code writer for most of your career, that is fine. If you want to move up in the world, then when people start seeing constant job changes, red flags are going to go up.also, I think you guys are selling how in demand software engineers are in general. I had almost no problem finding this job (After only a year at my previous position) and don't think I would have any problem finding another one if something goes wrong
Very true as well. I think 4 years is the sweet spot for more of the technical type jobs. Spending a long time at one position, really could make you complacent when it comes to coding.I read something recently that people who don't job hop after 4-5 years are viewed as unmotivated.We've passed on hiring because of that, tbh. Frequent job hoppers have a negative perception unless it can be explained with contract work.Again, if you want to be a low rung code writer for most of your career, that is fine. If you want to move up in the world, then when people start seeing constant job changes, red flags are going to go up.also, I think you guys are selling how in demand software engineers are in general. I had almost no problem finding this job (After only a year at my previous position) and don't think I would have any problem finding another one if something goes wrong
Yes, people that have a track record like that are often questions for the motivations of leaving, and more scrutiny is placed on their background, imo. May be unfair, may be circumstance, but it's certainly looked at.Some of the most successful people I've worked with have often told me they view their careers in 5 year chunks. Some of them have been at the same place for 30 years, because they met internal career bogeys that resulted in new 5-year targets being put into place while keeping the same job. Some of them have been at 3 or 4 different places over 15-20 years.I read something recently that people who don't job hop after 4-5 years are viewed as unmotivated.We've passed on hiring because of that, tbh. Frequent job hoppers have a negative perception unless it can be explained with contract work.Again, if you want to be a low rung code writer for most of your career, that is fine. If you want to move up in the world, then when people start seeing constant job changes, red flags are going to go up.also, I think you guys are selling how in demand software engineers are in general. I had almost no problem finding this job (After only a year at my previous position) and don't think I would have any problem finding another one if something goes wrong
For me, at least, I thought this was a good way to plan both long and short term for what I want my career to look like.
Also, I suspect Malka is talking about people who have 3 jobs in 5 years. I don't think being at two places in a decade, for example, would be viewed as "job-hopping." Or, at least, I would not when I was interviewing a candidate.
There has been manager meetings at the GMs or Corporate Controllers home as well where I work.Mrs Tif has been to about a dozen of them in the past two years.Dinner at a residence during off hours? Abnormal.
That make sense and why I very much enjoy working at an University.Our company encourages switching jobs within the company every 3-4 years. It is unfavorably viewed if you have the same position for a long period of time for the reason you state.I read something recently that people who don't job hop after 4-5 years are viewed as unmotivated.
Your company would not be very good at vetting candidates if they did not do a deep dive into why you were leaving within one year.
Yes, people that have a track record like that are often questions for the motivations of leaving, and more scrutiny is placed on their background, imo. May be unfair, may be circumstance, but it's certainly looked at.
I left that job after one year when I talked to you Slappy, I was questioned on more than one occasion why I was leaving the last company so early.
You should. I'd probably invite you round for dinner.maybe I should just move to Scotland
Users browsing this forum: No registered users and 126 guests
