I think Kate Paulk's answer shows that there is still space for some manual testing and quality assurance oversight even amongst a team with effective automated practices.
However, it is a shrinking space to occupy. I would try my best to take on a more 'T-shaped' role. I think a technically minded tester could really add unique value to that team by stepping out of the strict boundaries of manual testing.
Take responsibility for more technical tasks.
We can all think of a host of miscellaneous technically activities that are done by developers. Not because these tasks are programmer things per se, but it's hard and developers are usually the best technical problem solvers. "T-shaped" testers are already pitching in here.
Extend the automated tests.
I'm sure you've found the tests developers write leave out a lot of the edge cases you have patiently been recording. Good. Add them in. Adapt the user input test for your extra long string or your extra horrible clump of unicode. I think this is one of the most valuable things a tester can do, but it is a road that cannot be traveled very far without investing some effort in learning how to understand and write code.
Incidentally, the developers can make my second suggestion easier for you with parametrised tests and test orchestration tools like Cucumber. Talk to them about this and make sure when you do start change tests that they're code reviewing your stuff.