Live data from Hacker News

Ask HN: Early in career – is it a bad idea to change jobs after six months?

news.ycombinator.com

1–10 of 34 posts

Ask HN: Early in career – is it a bad idea to change jobs after six months?

#1
For some context: I am in my mid-twenties, have a computer science degree from a top ten American university and moderate experience developing software applications. After graduation I did a bit of research and worked as a bartender/waiter while going through the whole post-grad thing.

I eventually decided on taking a white collar job in technology. I was hired into a subsidiary of a well known CPG company as an Information Systems Specialist. When I was brought on board, I was told that I would be assisting the head of the IS department in documenting ERP customizations, developing/optimizing SQL, and working closely with other departments in order to build customizations and automations. It sounded great.However, my boss wasn't located in the same office as me and only spent 6 days on location "training" me. My "training" was consistently interrupted as my boss had to go put out fires multiple times per day.

Four weeks later I was brought in to HR and told that my boss resigned without notice and that I was to fly to the HQs the next week to do a knowledge transfer.

The parent company, of course, stepped in and said they would "allocate resources". So far I have had little assistance from them. What little assistance I have from them, ironically, ends up being more work.

Now I'm drowning in work, with no one to give me priority or direction. I have politely let my new boss in the parent company know that there is too much work and that I don't have priorities to work within and I am told that I should just say no whenever someone asks me to do something. The work I am asked to do is important and I don't feel comfortable telling individuals high up in the subsidiary no.

I was given a decent raise in light of my situation. But I'm finding it increasingly difficult to deal with the stress of managing all of this. I am very seriously considering finding a new job, but am concerned that my short tenure in this position will look bad. Thoughts?

Re: Ask HN: Early in career – is it a bad idea to change jobs after six months?

#2
Welcome to software engineering.

I am only partially joking. These types of situations are not uncommon and can actually work out to your benefit if you can take advantage of it. Your new boss told you to say no more often, he/she is giving you a lifeline and you are saying you're scared to take it? Instead of a direct no try saying it as, "I really would like to work on your issue and you have expressed its importance but I am limited in how much I can accomplish and right now my schedule is full. I may be able to get to it in X time period, but I can't make any promises today. However, if you'd like to have this prioritized then you can feel free to speak with Mr X who is my boss." And then you document the details either just to yourself, or you can send a heads up email to your boss.

This happens a lot in companies of all sizes, people make requests of engineers (generally young/new ones) and see just how much they can sneak around the system. One of the most important skills as you mature in your career is to say no. Saying "no" but getting your work done will not get your fired, saying "yes" and failing to keep up on your work will. Think of it this way, if these are higher level people then you that are making requests and their compliant about you is you said no because your schedule is full, it really won't go too far. If instead their compliant is you told them yes and then you never did it, their complaint will be valid.

Re: Ask HN: Early in career – is it a bad idea to change jobs after six months?

#3
I don't think you need to worry. What would make short stints a red flag is if they're common -- having a single short stint early in your career is unlikely cause you difficulties.

Remember, the people considering your application are well aware of the realities of the workplace, and one of those realities is that every so often a job is just a bad fit. In those cases, leaving it sooner rather than later is a good thing for everybody concerned. When I'm looking over resumes, if I see someone who has generally worked for years at each position, but has a couple that only lasted a few months, I see that as perfectly normal.

Re: Ask HN: Early in career – is it a bad idea to change jobs after six months?

#4
> The work I am asked to do is important and I don't feel comfortable telling individuals high up in the subsidiary no.

Your boss told you to say no. You tell people “no”, and refer them to your boss, and keep your boss informed of what your current workload is.

You are drowning in work because even after being directed to do so you refuse to stop accepting new requests when you are overloaded.

Saying “no” is an important skill.

Re: Ask HN: Early in career – is it a bad idea to change jobs after six months?

#7

> The work I am asked to do is important and I don't feel comfortable telling individuals high up in the subsidiary no. Your boss told you to say no. You tell people “no”, and refer them to your boss, and keep your boss informed of what your current workload is. You are drowning in work because even after being directed to do so you refuse to stop accepting new requests when you are overloaded. Saying “no” is an impo…

Agreed.

Learning to do what you are told by your manager is an important skill at the start of your career and some people find it hard to learn.

I once had a new employee at the start of his career and he simply could not bring himself to do as he was told to do.

After his first 8 weeks or so I said “you’ve got a week to start doing what you’re asked or you’re fired”.

He started doing what he was asked and became a star employee.

Re: Ask HN: Early in career – is it a bad idea to change jobs after six months?

#8

It won't look bad, but you do have other things to consider. You got a quick raise -- that's good. The company sounds understaffed in IT and perhaps is less than competent. Crisis can become opportunity.

Was thinking the same thing, I don't know what the original posters career goals are but this is a perfect opportunity to launch into management. If one where so inclined they could explain to the management at the subsidiary as well as their boss that they need funds to hire and build a team to manage the workflow. Prioritize said workflow by getting agreement by all parties and then managing that workflow out to the team.

Re: Ask HN: Early in career – is it a bad idea to change jobs after six months?

#9
Don’t list that you worked for that company. It’s not your fault that the company is full of idiots.

Every company is full of self serving idiots that will throw you under the bus for their own personal gain. The trick is to avoid these useless idiots, and to defend yourself when you have to deal with them.

Also, the only way to climb the ladder and make more money is to jump ship. You will never earn a decent amount of money by sticking around, and accepting the company’s pathetic 2% COLA raise, if you even get that. Meanwhile, they just paid their executives $100+ millions in performance bonuses. And they claim there isn’t any money left over for you.

Re: Ask HN: Early in career – is it a bad idea to change jobs after six months?

#10

Welcome to software engineering. I am only partially joking. These types of situations are not uncommon and can actually work out to your benefit if you can take advantage of it. Your new boss told you to say no more often, he/she is giving you a lifeline and you are saying you're scared to take it? Instead of a direct no try saying it as, "I really would like to work on your issue and you have expressed its importan…

Yep, exactly. I’ve been doing this now going on 30 years, and I felt like OP at my first job back in ’92, so I bailed on it. I found another quickly and immediately felt the same way. I bailed on that one, too, thinking I was just picking the wrong jobs. After four job changes in four years I realized this is just how professional software development feels - and that’s part of the reason it’s such a high-paying profession.
Post reply on HN