this is an interesting topic to discus, thanks a lot for sharing geekoxi.com

I agree with most of the responses, but I've some things to add upon it. I'd been in a junior position for long - about a year and a half, in a big company like yourself. Most of the times I was given bug fixes to do, which was a learning experience in itself but, that is almost all I did for major part of the year. But the days put into coding small modules / things were worth it.

It's inevitable, that when you are starting things out, you have to start out with things that are really really basic, even boring. Persevere and you'd get to work on something worthwhile.

I didn't much. I quit that job for completely other reasons, but one of the side effects was that I could think about applying for a job where I'd be given more responsibility (spoiler alert: I'm going to apply with hashnode soon 😉).

---

I got to talk to and engage with people, learn something together, watching learning videos together, work on a small side project together and so forth. We even watched horror movies in the big screen conference rooms on Fridays sometime 🚀😆. You can take the best of the environment you are in, instead of just the job you are supposed to be paid for.

One of the things that some of the people in my previous company did is: they endured, and when they had endured enough that they could ask for a project switch because it'd been quite a while now, they did! You could perhaps ? After 5 months or so.

All the best! With whatever you do :)

For starters, you're at IBM which is a remarkable opportunity in itself. You don't want to give up on that too soon. Certainly not before you've really given it a chance.

As far as how long you wait before making a move, I don't know. At the same time, one month seems like a really short time period to make a decision like that. The company will want to make better use of your skills so I'd be surprised if you are still doing low level going forward.

Stick it out for a while longer.

I think as a Junior Developer everyone goes through this phase. Even though we know a lot of things, we need to go through the training phase where the company evaluates our strength, understands our technical knowledge. So, even though you think you are not working on something you like, I say, learn it thoroughly, finish it as soon as you can so that, you keep getting new projects and eventually you will be doing what you like. But again, do not work on something you don't like for too long. Make a smart switch.

Follow your heart ofc, but after 1 month ? Write a checklist "things I'd expect till next year june" and check in june ... :) give it at least 6 months of trying.

if it still sucks you can quit and reason about it, 6 months of "they did not delivered what they've promised but I gave them a chance" is more reasonable than 1 month of "I didn't get what I wanted".

One month really isn't that long in the grand scheme of thing. If it were me, I'd give it a full three months before making a decision. However, you should listen to your instincts. If you feel the job probably won't be fulfilling, move on. Keep in mind, as a junior developer, you have to "pay your dues", which often means doing grunt work, stuff more senior developers don't want to do and will hand off to junior developers.

Having IBM on your CV is a good thing. I imagine they treat junior developers as truly junior, though. A smaller company may be more personally rewarding in a faster time frame.