If it's for recruiters, put it on github. That's the one they are most probably familiar with and you want to minimize barriers to access.

i tried all three for my personal use. so i can't say much about collaboration aspects. anyway:

• gitlab is old, stable and solid. and it eats half of your servers resources.
• gitea and forgeji are for me equal in experience, which is makes sense, as one being a fork of the other. i haven't had any issues with anything, from setting up, using openid as auth method, to ssh passthrough.
• eventually i settled now on forgejo, simply for ideology reasons. it's heavily developed, so things might change. but they have this nice attitude to not release a latest tag for docker. so you can't accidentally update to a breaking change. had this issue with some other programs, which i spun up to quickly.
• looking forward to federation feature on forgejo!

I'd say Forgejo as it is the most simple of the three. If you want more complexity (like CI/CD), then one of the other two. You can checkout Forgejo at codeberg.org.

So I'm going to suggest something slightly different - put it on both github and codeberg, then note that its synced from your local repo as a mirror and link it in a readme.

Gives you a few things

• Readily accessible and fast options for the recruiter to access, even if your power is out / motherboard blows up / whatever.
• Demonstrates your familiarity with a world beyond github
• Demonstrates you can stand up your own local repo (if this is a thing they care about - if not don't bother with your own repo for just this)

As for the server itself I'd say forgejo personally.

Gitea for me, never had an issue with it. Work's great!

i just put git repos in a dir on my server and use ssh to push/pull

if you need webui theres cgit.

i can say its not very user friendly tho..

I'd use nginx and https://git-scm.com/docs/git-http-backend

If you don't need issue tracker, wki, CI etc., cgit will be enough. If choose from gitlab, gitea and forgejo, use forgejo.