Sure.
The basic maintenance is having to update your system often. In my experience it’s good practice to do it at least once every 2 weeks, or you risk having more manual interventions (like having to partial update archlinux-keyring which is used verify package signatures, it’s the most common issue in my experience). That’s mostly all of it.
But sometimes, you have to do some manual changes. The last big one was back in May when arch was migrating to git and you had to change your package manager (pacman) configuration. It was a simple change, basically deleting like 2 lines in your config, but if you didn’t do it you’d probably end up with a broken system at some point. The manual interventions are always listed on the main arch page (link).
It’s not that much work if you’re into that, but it’s still more than a lot of people are willing to do.
If you’re somewhat knowledgeable in linux you should have no problems. The documentation is excellent and there’s a big community to help if you need it. As is with most things, arch has an excellent documentation on system maintenance (link).
It’s not that much work honestly. Like in May when arch was migrating to git you had to manually update your pacman config to remove the community repo, if you didn’t do it at some point there’d be a risk of having a broken system. It was a simple change, basically removing a few lines from the config, but keeping up with arch “news” and sometimes having to do something simple is more than a lot of people are willing to do.