I think it's probably fairly random. I.e. you're just as likely to have a "do nothing" job in a FAANG as in some other random corps. But I don't think you can start doing nothing right after being hired - usually people are hired because there's more work in a team that the existing headcount can handle. So, you have to work for some time and then count on "falling into the cracks" - landing in a place where there's…
I agree with the Scrum Master suggestion, my Scrum Master pretty much just creates meeting invites for 40 hours a week. We have a lot of contracts where we have Scrum Masters just because we do Agile, usually the non-technical types do it. The irony is that Scrum Masters are supposed to not make the team reliant on them but by having a dedicated role for it of course the dev team will make the Scrum Master do menial…
If you are actually a good developer and you get a pure Scrum Master role then it's almost impossible to not get endlessly promoted and praised and possibly paid better than a developer role itself whilst actually still doing fuck all work. Imagine, you do a standup, ask in the end if anyone has any blockers, some developer or QA will say something stupid about the CI/CD pipeline or merging a PR and you'll schedule a meeting with the people who need to follow this up and you could actually throw in some suggestions which only a great developer would normally do and the team will look at you as if you're some bloody hero for DeNiro and praise you as "the best Scrum Master they ever had who actually helps the team and lives up to their role". LOL. Then you know you can go to sleep for the rest of the day and nobody will even notice.
The only other thing I can come up with which could be easier than Scrum Master is to apply for a manual QA role. I don't think I have to say more, but essentially, you will look like you've worked around the clock when really you just click a button at the beginning of the day and then go to sleep again.