Quitting sounds like it could be the right choice, modulo some real-life constraints. One of which
might be, if it's your very first job, not staying for at least 6 - 12 months. There's some value to putting in those dues, you'll learn for sure what you dislike. But after that...
A lot of people are suggesting to stick it out, learn from what's there, make the best of it, etc. But this advice is lazy at best, and maximizes regret at worst. You see, this could be applied to almost any job, even within software engineering. Because this advice implies that anyone can be fulfilled at any job, it implies to favor the default option of sticking where you ended up, which was made at a time where you had less information and experience. Worse, it may imply that somebody else has authority over your opinion or "tastes", if you will - you ought to like this job, so find something you like there! Because otherwise, your unhappiness is your own damn fault (which it really is, but not the way others mean).
No. Here's what you do. Before you discount it and consider quitting, consider the following:
1) What kind of work would you ideally be doing at this organization that would make you want to stay?
2) Speak with your manager or someone relevant, to figure out what conditions need to be met until you can do the work in 1.
3) Is the path to get there too painful? Pain is relative, and the way to find out is to research other jobs you could be starting in the next month. You can do this on weekends, everyday after work, whatever. It's important, so you'll make time.
I'm trying to advocate that there's nothing wrong with having taste and preferring something else, or simply disliking what you have. But instead of going too far in that direction and just up and leaving, be smart about it and do your homework. At least then you can be more confident that you made the right decision (stay/go) rather than following some blanketed advice based on responses to your limited detail post on your situation.
Hope this helps.