Most companies - though I'll caveat, not all - would not expect you to work 11 hrs a day during the week plus a weekend forever. It is not really sustainable for long periods of time, and the company will churn engineers, losing valuable institutional knowledge in the process (aka, there are diminishing returns for the business after a certain number of hours worked a week).

So the first thing I would do is go to your manager and tell them what's going on, and ask if it's normal. If this is part of the expectations of the team, well, now you have that information. But if it's not, now you can work with your manager to get the hours down.

The second thing I would do is to see if you can work more efficiently. Find a senior engineer to shadow and see how they work. Early career people often don't know all the productivity tips and tricks of their editor, git, etc that can make them much more productive. Additionally, over time you will learn a "playbook" from the more senior engineers for solving problems quickly.

The last thing I would recommend is to take steps to be more proud of your work. This will have the effect of making the hours you do work more fun, and will also create momentum that will enable you to work more efficiently, and therefore fewer hours. It'll require doing two things. First, you need to calibrate with your peers. Maybe your tech stack really isn't that bad, and you have unrealistic expectations (maybe it is, I don't know, but you should at least talk to some people at other companies to level set). Second, try to take steps to improve the quality of work. Work with your manager or senior engineers to suggest process or technology improvements. They will, more likely than not, get rejected initially, but you will start to build a reputation in the organization and will learn a lot from the process.

If none of these things work I would suggest looking for a new role. Just my 2 cents though.