Xrfgtjtk

Motosubatsu's answer stresses that

your first position after graduation doesn't mean your "stuck" doing that".

While this is true, SAP is a bit of a special case. I know plenty of SAP consultants and I know how difficult it was for those who wanted to switch jobs to find a position in a different technology.

SAP is a world in itself and when you are considered an "SAP person", it's difficult to start doing something different. Your SAP experience won't mostly count as work related to other technologies, so it's possible that you will need to accept a junior position when you want to switch to a different technology in 1-3 years - unless you want to switch to a job of PM, process specialist or similar.

The good news is, however, at least in Europe SAP positions are currently really well paid. It's also super easy to find a job in SAP. As an SAP specialist you will be receiving plenty of job offers - but yes, they will be related to SAP.

So you need to consider what is most important for you: stability and a good salary or interesting tasks. If the former, stay in this technology and try to learn as much as you can. If the latter, start your job but simultaneously try to find a new position elsewhere.

It's important that you decide where you see yourself in several years. It's only after deciding that you can decide what to do now.

I had a very similar situation. Here's how I managed it:

I found my first time job out of college. I was excited about it and
didn't care much about the nature of the work. I found out that I'll
be writing Winforms in VB.net, and that's ALL I'll be doing.
There's a lot of useful technologies to learn, but VB isn't one of
them. I worked there for exactly one year and quickly switched to
another company that cared about being up to date.

Job hopping too much isn't good. But keeping your first job for 1 year to get that initial experience at the beginning of your career won't hurt you. I'm also speaking like you're in USA, it may be different where you're from.

Option 1 sounds good on paper, and some people can pull it off. I personally can't. I don't program outside of work because 8 hours of it per day are enough since I have a family, friends and hobbies. Some people DO manage to work on personal projects outside of work! Don't let me discourage you. But know that it's more difficult than it seems.

What I suggest:

Stay at this company for 1 year, and find a company that uses tech
that you think are useful for your career. When you land another
interview, explain this to them and they will most likely appreciate
that you stayed with it for a year, and that you care so much about
keeping up to date. That's important to employers.

Best of luck to you. I'm sure you'll have a great career ahead of you.

As a newly minted Software Engineer, you should be soaking in whatever real world knowledge you can get, and learning a system like SAP will be quite the education. A lot of the things you'll do, and the techniques you'll use, and the issues you'll face are universal in software engineering and will apply to most other systems you will ever work on in the future.

Will you get stuck in SAP? That's completely up to you. You never know, you may enjoy it. You have no idea what your experience will be. So I recommend giving it a fair shot and learning as much as you can. It will not be wasted time, unless you allow it to be. If you hate it, move on in a year or so.

I give interviews to engineers, and to me, what you worked on is not as important as the experience and skills you gained from doing it. In your next job interview, when they ask you about your SAP experience, you will have the ability to say something like "There's a few things I would change about SAP, specifically a, b, and c. But they also did a lot of things right, like x, y, and z." Now you've shown the interviewer that you can learn a complex system, grasp the beauty and the flaws of the system, and you can apply the lessons learned. Follow it up by saying that if you can learn something complex like SAP, it should be easy to learn AWS, or Salesforce, or whatever they use.

"Cancel my contract now and start looking for another position right away"

This is almost never an option that should be considered. Trying to get a job while without one is significantly harder than when you do. Even if you've only been with the company a short time.

I would say that #2 should, in fact, be your permanent stance... Work where you are; look for something better. Don't aim to move more than once every couple of years so that you're providing reasonable value for money to the company, but you should always be looking for a company that better suits your requirements.

You are new to the job and the career field in general. Consider that you might actually like the field in the end. Ask yourself what do you want to be doing ultimately? There are many people who accept any entry-level job in their career field. They then move on eventually to other companies doing other interesting work. The key is breadth and depth. You want to be able to do almost anything which will increase your long term job prospects. If you get pigeonholed in one technology, it may make it difficult to find work down the road.

SAP in of itself could translate. You also have intrinsic value in each job where you gain experience in soft skills. Is the SAP team following agile? Are there process improvements that could be made? Think of ways to improve your options long term and exercise those soft skills and leadership skills. Early testing and honing of those skills will matter a lot more than, say, some programming or technical skills. There are a lot of really smart people who can’t get along with others. Guess who we hire more?

I will disagree with the currently most upvoted answer and say:

The first job in technology is often a very important step into a specific direction. It will be much harder to change course later.

Clarification because of comments: In my personal experience, applications by by SAP consultants or other not directly related fields for Software Engineering positions in fancy new technologies will often be already filtered by HR, or automatically be lower on the list. I have come to believe it's easier to land a good Software Engineering job as a junior directly from university than as a professional with non-relevant experience / experience in a different field. True, most people will change technologies multiple times in their lives a tech professionals, but getting into a developer position with a mismatched background on the CV is harder, not easier. This is even more pronounced with SAP, which is a world onto itself, at least in Europe.

The good news is: you now have a full month worth of job hunting time.

Good luck!

DO NOT go down the SAP route! First up, it's a dying field, unless you are going to spend a lot of time in Germany (because at least half the country runs on SAP systems) do not do it. Many companies are migrating away from it although it's extremely costly to do so. They would rather take the hit once then keep having to spend it on costly upgrades and armies of consultants. It used to be well-paid... now there are consultants fighting for the crumbs left on the table. I say do not be fearful, you are a fresh, new graduate... there will be tons of new opportunities for you. Have a chat with your prospective employer and tell them that even though you like their company culture (or some other compliment) you have thought about your long-term career prospects and SAP is not an area you want to specialize in. (You never know, they might even respect you for it.)

The thing to learn early on is to be kind to yourself, there are any amount of people willing to exploit people like you. Listen to your inner voice and find a job that, maybe if it's not exactly exciting, does not make you dread going in to work for the next year. Having a fresh skill set is valued more highly in our industry then having decades of experience in some dying field. I know, because I had to get out of SAP after 20 years of it!

"That's why they call it work", as one of my elders used to say. Employers ultimately are interested in "what can you do for the company", not in what might be interesting or attractive. In a most instances, work for an employer is more specific and tedious than what we were used to in academia.

That is also why employers accept that you can leave with reasonable notice, usually no longer than six weeks and more commonly, two weeks.

I would recommend some hybrid of options 1 and 2, unless you can line something more solid up right now.

In my case, I disliked the clerical aspect of our data analysis workload consisting of spreadsheets and asking the dev team to write queries for more complex tasks. I spun up my own little shadow IT with the community version of mySQL on my desktop and developed a solution that was challenging to develop and, frankly, way more fun. Plus I now have SQL skills in my tool kit. In short, I made lemonade from lemons.

I may be naive in assuming your environment would afford that kind of flexibility. It does require tolerant management and significant freedom of choice in how you get the job done.

Don't sweat too hard over this decision. In 1984 when I started, Linux and SQL standards were years in the future. My employers back then scoffed at GUIs, IP networking, and the general idea of a computer in the pockets of the hoi polloi. My point is the workplace and job market will change in ways none of us can predict, so limit your investment in worrying about it.

Finally, a career as an SAP expert might not be the worst fate: I have a friend who makes a living as a COBOL programmer working on systems that are older than me (and that is OLD!). You could avoid this if you keep your skills fresh and invest time in keeping channels to other job choices open while slogging through SAP.

Reading between the lines of the OP, I sense at least some level of a common misconception: Now you have got to the end of your degree course you have learned everything conceptually challenging that you need to know for the rest of your working life, so from now on things are going to get boring.

Unless you plan to "downsize" to flipping burgers, that is 100% wrong. The most useful thing you have learned so far is how to learn. The actual "stuff" that gets you a good grade in exams is just detail. In an average university most of it is out of date already compared with what the real world is doing, and even if that isn't true it soon will be.

Personal anecdote: On average, I've learned a new programming language, "industry-standard" application, or computer OS about every two years of my whole working life. That's not "learning just for fun", it's keeping up with the rest of the world and staying employable. And all I can remember about some of them, looking back 30 years, is their names.

So thinking about the big picture, it doesn't really matter at all what you happen to learn first. SAP is as good (or as bad) as any other choice. But don't get hung up about it being the last thing you will ever learn - even if you don't change employers very often. That won't happen!

Which option should you choose?

No matter what option you go with, I want to stress that you still have the opportunity to do jobhunting research. I'm not just talking about technologies. Products, work environments, business models and any other criterion that you think might give you buyers remorse again.

As far as avoiding being seen as a job-hopper, the easiest way to achieve that is simply to not be a job hopper. What do I mean by that? Switching jobs after a year because you didn't like the job is just healthy. Switching jobs every year is what constitutes job hopping.

What if I personally was in your shoes?

I would go for option 1, but I wouldn't predetermine the amount of time I want to stay. I've had one job that I quit after four months because what seemed like a dream job turned out to be the stuff of nightmares (I didn't do my research well enough either). I was upfront about it in job interviews. There wasn't a single employer who raised eyebrows because I was specific in what I mentioned that I needed in a working relationship and I didn't badmouth the company where I quit. Examples of things I pointed out:
- I found out that I required a well-structured company, which I couldn't find in a startup of 10 people.
- I wanted a big enough company that could help me transition into different roles if the original one didn't fit me well. Again, a 10 person company can't do that.
- I wanted to work in consulting and the company I left, was a product-based one.

When quitting and looking for new jobs, be specific in the reasons you outline when they ask about why you left after a short time, make sure you are not blaming your former company and above all, ensure that the company you are applying to, actually meets the requirements that your previous company couldn't.