One thing matters
Your repo should prove this: a recruiter can clone it, run one command to build it, then start one binary.
go run is fine while coding, but it does not create the executable you submit. Use go build for the shippable path.
What to ship
A strong final repo is boring in a good way. It has a Go 1.27 module, a clear main package, typed handlers, useful errors, slices or maps, one goroutine or channel use, and proof that the API works.
Keep the shape simple. Do not hide your service behind too many folders just to look senior.