Details may change every few years but overall, it boils down to two main approaches: 1) find a position through your professional network, as an estimated 80% of jobs come through such connections; 2) be discoverable for the other 20%.

Be active in both.

Present something at a local meeting/event. Often, it doesn't have to be fancy or overly polished. Some events on meetups.com have a few people present for 10 minutes each.

Which leads to #2, be discoverable: put those presentation materials on GitHub or GitLab.

Additionally, there are common interview questions (whiteboard and/or code challenge) such as URL shortener (e.g., TinyURL) or anagram solvers. These have come up a number of times in my interviews over the past few years, so I wrote the code and pinned these on my GitHub profile. (Same user id as here, if you're interested.)

I decided to go a step further and give each the full dev-ops treatment: Dockerfile, Makefile, etc.

But give them a solution, not a problem.

Avoid relying upon AWS/GCP/Azure proprietary offerings unless that's precisely what you're demonstrating, and make it work as-is: fetch all dependencies with version pinning (if possible-- else put versions in README), so then you know that it will build for them exactly as it did for you.