​

You might be right about the most useful types of projects, but for me, the project itself can be about anything, as long as you are able to discuss the tech and choices. If it is specifically related to our business though, that's a huge bonus. Since you sound very new, consider keeping notes as build stuff so you can remember what you were thinking at the time. Consider making user stories first, so you can say things like, "when I was making the user stories...". I wouldn't have any code or choice you cant explain. While I like "passionate" people (aka anxiety driven workaholics), I also respect the fact some people are not outwardly passionate or charismatic, but still know what they are doing. In fact some of those types of people have been the best hires.

When I look at the projects of prospective juniors I look for
1. No spelling errors.
2. Works on mobile and desktop
3. Does something different than the classic versions of the project. Rarely are projects unique, which is fine, but if it feels like a tutorial I disregard it.
4. You are able to discuss every aspect of the project in great detail, including why you choose one library instead of another. If you picked, say Styled Components, I would like to know what alternatives you considered and why you went with it.
5. Able to discuss UI choices, in the same manner as above.